Download the PHP package humanmade/wp-term-images without Composer

On this page you can find all versions of the php package humanmade/wp-term-images. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of humanmade/wp-term-images

Informations about the package wp-term-images

WP Term Images

Forked from stuttter/wp-term-images

Images for categories, tags, and other taxonomy terms.

WP Term Images allows users to assign images to any visible category, tag, or taxonomy term using the media library, providing a customized look for their taxonomy terms.

Installation

FAQ

Does this plugin depend on any others?

Not since WordPress 4.4.

Does this create new database tables?

No. There are no new database tables with this plugin.

Does this modify existing database tables?

No. All of WordPress's core database tables remain untouched.

How do I get the image for a term?

With WordPress's get_term_meta() function

How do I bind a term's image to an Image block?

For WordPress 6.7+, plugin registers a Block Bindings source wp-term-images/term-image that can bind properties on the core Image block to properties of the image assigned to a term. Rendering is done on frontend render; the editor shows that the image is bound but as of 7.0 does not preview any term image properties.

The source answers whichever Image attribute you bind:

Attribute Value
url The attachment URL, required in order for the image to display.
alt The attachment alt text.
title The attachment title.
id The attachment ID. Updates the wp-image-{id} class only; it does not change src, so url must be bound for the image to display.

The term is taken from the termId arg when given. When the termId argument is not provided, the binding will use the associated image when on a taxonomy archive for a term that has an image assigned.

Optional args: termId (defaults to the queried term) and size (image size for url, defaults to full).

When url is bound, the plugin also adds the wp-image-{id} class and computes responsive srcset/sizes for the term's image, so the bound image renders with the same responsive markup as a natively-inserted one. Block Bindings replace scalar attributes only, so this is done in a render_block_core/image filter rather than through the binding itself.

Post content — pin a specific term:

Template — bind to the current term on an archive (no termId):

Local Environment

This project uses wp-env to run a lightweight, containerized WordPress instance at localhost:3003 for testing purposes. The default username for the localhost environment is admin, with the password password.

These commands can be used to interact with the environment:

Command Purpose
npm run env:start Start the local environment at http://localhost:3003
npm run env:stop Turn off the local environment
npm run env:cli -- wp ... Run WP-CLI commands within the environment
npm run env:logs Open (and tail) the error logs for the application‡
npm run env:db Open the database in the mysql command line
npm run env:destroy Fully destroy the local environment (deletes container database)

‡ This command deliberately filters out GET/OPTIONS/HEAD/POST/PUT access log entries

Release Process

[!NOTE] This plugin is currently distributed via Composer as humanmade/wp-term-images, not via the plugins repository.

Merges to main automatically build to the release branch. A project may track the release branch using Composer to pull in the latest built beta version.

Commits on the release branch may be tagged for installation via Packagist and marked as releases in GitHub for manual download, using a manually-dispatched "Tag and Release" GH Actions workflow.

To tag a new release:

  1. Choose the target version number using semantic versioning.
  2. Check out a prepare-v#.#.# branch.
  3. Bump the Version in the wp-term-images.php PHPDoc header.
  4. Update the changelog entries in readme.txt.
  5. Open a pull request titled "Prepare release v#.#.#".
  6. Review and merge the "Prepare release" pull request.
  7. Wait for the release branch to update with the build that includes the new version number.
  8. On the "Tag and Release" GH Action page:
    • Click "Run workflow" in the workflow_dispatch banner.
    • Fill out the "Version tag" field with your target version number. This must match the Version in wp-term-images.php. Use the format v#.#.#.
    • Click "Run workflow" to apply the specified tag to the release branch.

Once the workflow completes, the new version is tagged and listed in releases.

Where can I get support?

Can I contribute?

Yes, please! The number of users needing more robust taxonomy visuals is growing fast. Having an easy-to-use UI and powerful set of functions is critical to managing complex WordPress installations. If this is your thing, please help us out!

All versions of wp-term-images with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2
composer/installers Version ^1.0 || ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package humanmade/wp-term-images contains the following files

Loading the files please wait ...