Download the PHP package humanmade/asset-manager-framework without Composer

Asset Manager Framework

This WordPress plugin provides a framework for replacing the contents of the standard WordPress media library with assets from an external provider such as a DAM, another WordPress website, or a central site within a Multisite installation.

It handles the necessary integration with WordPress (Ajax endpoints and Backbone components) leaving you to focus on just the server-side API connection to your DAM.

The intention is that the media manager, the block editor, the classic editor, the REST API, XML-RPC, and anything that calls wp.media() should "just work" and not need to implement changes in order to support a media library that is powered by an external provider.

Installation

Install with Composer:

Status

Current status: Alpha. Generally very functional but several features still in development.

The following features work as expected:

• [X] Block editor: All media features
• [X] Classic editor: All media features
• [X] Media screen: All features
• [X] Widgets: All media widgets
• [ ] Customizer:
  • [X] Background Image
  • [ ] Logo (functions if you skip cropping)
  • [ ] Site Icon (unable to skip cropping of large images)
• [X] REST API media endpoints
• [X] XML-RPC requests for media
• [X] Any code that calls wp.media() to open the media manager and work with the selected attachments

The following custom field libraries have been tested and are compatible out of the box:

• [X] CMB2
• [X] Advanced Custom Fields (ACF)
• [X] Fieldmanager

The following third party plugins are supported via an included integration layer:

• [X] MultilingualPress 3

The following new features are planned but not yet implemented:

• [ ] Various degrees of read-only media (to prevent local uploading, editing, cropping, or deletion)
• [x] Support for multiple simultaneous media providers

The following features will not be supported:

• Side-loading media from an external media provider. The intention of this framework is that media files remain remotely hosted.
• Built-in handling of authentication required to communicate with your external media provider. This responsibility lies within your implementation. Consider using the Keyring plugin if an OAuth connection is required.
• Built-in support for any given media provider (such as AEM Assets, Aprimo, Bynder, or ResourceSpace). This is a framework built to be extended in order to connect it to a media provider.

Known Implementations

• AMF WordPress for using another WordPress site, or another site on a Multisite network, as source for your media library.
• AMF Unsplash for using Unsplash as a source.

Implementation

There are two main aspects to the plugin.

1. Allow the media manager grid to display external items which are not existing attachments.
2. Subsequently create a local attachment for an external item when it's selected for use.

The design decision behind this is that allowing for external items to be browsed in the media manager is quite straight forward, but unless each item is associated with a local attachment then most of the rest of WordPress breaks when you go to use an item. Previous attempts to do this have involved lying about attachment IDs, or switching to another site on a Multisite network to provide a media item. Neither approach is desirable because such lies need to be maintained and eventually you run into a situation where your lies become unravelled.

Asset Manager Framework instead allows external media items to be browsed in the media library grid, but as soon as an item is selected for use (eg. to be inserted into a post or used as a featured image), an attachment is created for the media item, and this gets returned by the media manager.

The actual media file does not get sideloaded into WordPress - it intentionally remains at its external URL. The correct external URL gets referred to as necessary, while a local object attachment is maintained that can be referenced and queried within WordPress.

Integration

There are two steps needed to integrate a media provider using the Asset Manager Framework:

1. Create a provider which extends the AssetManagerFramework\Provider class and implements its get_id(), get_name() and request() methods to fetch results from your external media provider based on query arguments from the media manager.
2. Hook into the amf/register_providers action to register your provider for use.

Full documentation is coming soon, but for now here's an example of a provider which supplies images from placekitten.com:

Try it and your media library will be much improved:

The MediaResponse object takes a MediaList along with the total number of available items and the number of items requested per page. This is to ensure pagination in the media library (introduced in WordPress 5.8) works.

You also have access to provider instances during registration via the amf/provider filter, so you could use it to decorate providers:

This is useful, for example, when you are using a third-party provider implementation and want to change certain behavior.

Local Media

Local media is supported by default and can be used side by side with any additional media providers but can also be controlled by using one the following methods:

1. Defining the AMF_ALLOW_LOCAL_MEDIA constant as a boolean
2. Use the amf/allow_local_media filter to return a boolean
3. Use the amf/local_provider/name filter to change the Local Media label.

The filter will take precedence over the constant.

License: GPLv2

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.