WP Manifestindependent plugin directory
manifest / developer / load-media-from-production

Load Media from Production

WordPress plugin that fixes missing images on local and staging sites by loading media from the live site.

by Andrew Murray · github.com/ajm-media/load-media-from-production · website

★ 0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/ajm-media/load-media-from-production/archive/refs/heads/main.zip
Readme github.com/ajm-media/load-media-from-production ↗

WordPress plugin that fixes missing images on local and staging sites by loading media from the live site, so the uploads folder doesn't need copying.

  • Rewrites uploads URLs in WordPress output (attachments, srcset, page builders, theme templates, inline CSS and JSON-escaped URLs).
  • Redirects requests for missing uploads files to production, or downloads them into the local uploads folder.
  • Leaves files that exist locally alone.
  • Never runs on a site explicitly marked as production, never points a site at itself, and pauses when the database moves to another domain.

The wp.org listing text is in readme.txt.

Development

The repo root is the plugin folder. Build the release zip from the committed code; files marked export-ignore in .gitattributes are left out:

git archive --format=zip --prefix=load-media-from-production/ -o ../load-media-from-production.zip HEAD

wp.org listing images (icon, banner, screenshots) are in .wordpress-org/. The icon and banner are rendered from the HTML in listing-images/:

PLAYWRIGHT=/path/to/node_modules/playwright node listing-images/render.mjs

Tests run in GitHub Actions on every branch push (tests/run.sh): WordPress in Docker with a fake production server, across PHP 7.4-8.3, WordPress 6.0 and latest, Apache and nginx, and root, subfolder and multisite installs.

Releasing

  1. Bump the version in the plugin header, LMFP_VERSION and the readme's Stable tag, and add a changelog entry.
  2. Push the commit, then push a tag with the bare version number, e.g. git tag 1.0.1 && git push origin 1.0.1.

The tag runs the tests, checks the three version numbers match, then publishes to WordPress.org SVN (trunk, tags/<version> and the listing images). It needs the SVN_USERNAME and SVN_PASSWORD repository secrets.

wp-config constants: LMFP_PRODUCTION_URL, LMFP_UPLOADS_URL, LMFP_DISABLE. Filter: lmfp_should_proxy( bool $proxy, string $file ).

Support

Found a bug or have an idea? Open an issue.

The plugin is free. If it saves you time, you can buy me a coffee.

Licence

GPLv2 or later.