Plugin conflicts
Most plugins work alongside WP Media Cloud without any setup. This page covers the plugins and server tools that can clash with it, how to spot each one, and what to do.
Quick reference#
| What you see | Likely conflict | Go to |
|---|---|---|
| Media URLs switch between two CDN addresses | Two offload plugins are active | Two offload plugins |
| A notice says more than one copy of WP Media Cloud is installed | Two copies of WP Media Cloud | Two copies of WP Media Cloud |
| The Media Cloud screens show an older version than the Plugins screen | A cache serves the old admin script | Two copies of WP Media Cloud |
| Media URLs use the bucket or an Easy IO address you did not expect | EWWW Easy IO | EWWW Easy IO |
| The Migration tab shows WP Offload Media as Active when it is not installed | The Easy IO helper file | EWWW Easy IO |
| The bulk offload never starts or stops after one batch | A security plugin or password protection | Security plugins and password protection |
| Some pages show old local URLs | A page cache | Page caches |
| Health says “Attachment #N is served from … instead of …” | Another plugin changes media URLs | Other plugins that change media URLs |
Two offload plugins#
Do not keep two offload plugins active. Both change media URLs, so pages can show a mix of addresses. Both may also upload new files.
When you move from WP Offload Media, Media Cloud by ILAB or Advanced Media Offloader:
- Keep the old plugin active while you import its records on the Migration tab.
- Check that your URLs work in WP Media Cloud.
- Deactivate the old plugin.
See Migrating from WP Offload Media, Migrating from Media Cloud by ILAB and Migrating from Advanced Media Offloader.
Two copies of WP Media Cloud#

Uploading a new zip under another folder name, for example wp-media-cloud-1, leaves two copies installed. From 1.2.4, the Plugins screen and the Media Cloud screens show a notice naming each copy, its folder and version, and which one is active.
- Keep the newest copy active.
- Delete the other copies on Plugins > Installed Plugins. With 1.2.5 or newer active, your settings and records stay. With 1.2.4 or older active, update first or remove the extra folder by SFTP: deleting it on the Plugins page would run its uninstall routine and remove the settings and records both copies share.
- Next time, update with Replace current with uploaded. See Installation.
If the Media Cloud screens show an older version than the Plugins screen, a browser, server or CDN cache is serving the old admin script. From 1.2.4 the screen reloads itself once with the new script. See Settings screen shows an old version.
EWWW Easy IO#
When you choose EWWW Easy IO as the CDN for an S3-type provider, WP Media Cloud sets up Easy IO to fetch from your bucket. It does three things:
- It adds
define( 'EXACTDN_LOCAL_DOMAIN', '...' );towp-config.php, marked// Added by WP Media Cloud. - It writes
wp-content/mu-plugins/wpmc-as3cf-shim.php. This file lets Easy IO detect your bucket the same way it detects WP Offload Media. - When an Easy IO site is selected, it uses that address as your CDN URL and rewrites media URLs to it.
WP Media Cloud stops rewriting when the Easy IO plugin is active and WP Media Cloud has no CDN URL. The same happens when the CDN URL is the bucket address. Easy IO then handles all image URLs.
| What you see | What it means | How to fix it |
|---|---|---|
| Media URLs point at the bucket, not Easy IO | No Easy IO site is selected in WP Media Cloud. | In your provider’s CDN card in Settings, choose EWWW Easy IO, load your sites, pick one and save. |
| Easy IO is not rewriting at all | Easy IO is not enabled in EWWW, or has no domain. | Check the Easy IO settings in EWWW Image Optimizer. |
| Migration shows WP Offload Media as Active with “Items table not found, so no offloaded media was detected.” | The shim file makes WP Media Cloud think WP Offload Media is installed. | Ignore that card. It has no effect on your media. |
To stop using Easy IO, choose another CDN option and click Save Settings. WP Media Cloud removes the line from wp-config.php and deletes wpmc-as3cf-shim.php and wpmc-exactdn-local-domain.php from wp-content/mu-plugins. If either file is still there afterwards, delete it by hand.
See EWWW Easy IO.
Other image CDNs#
Some plugins have their own image CDN that rewrites media URLs, such as the CDN feature in Smush Pro. Only one CDN should rewrite your media.
Either turn off the other plugin’s CDN feature, or stop WP Media Cloud from rewriting by turning off Rewrite URLs. Image optimization on its own does not conflict. See Image optimizers.
Security plugins and password protection#
The bulk offload sends requests from your server to its own wp-admin/admin-ajax.php. Anything that blocks those requests slows the run down to one batch every 5 minutes through WP-Cron.
- security plugins or firewalls that block
admin-ajax.phpor the server’s own IP - HTTP basic authentication on a staging site
- hosts that block requests from the server to itself
Check the Loopback Request row on the Health page. If it warns, allow requests from the server’s own IP, or run wp wpmc offload from the command line. See Bulk offload stalled.
Page caches#
Page caching works with WP Media Cloud, because URLs are rewritten when a page is built. Cached pages then hold the CDN URLs.
Pages cached before you set up WP Media Cloud still hold the old URLs. Clear your page cache after setup, after a bulk offload and after you change the CDN URL.
Other plugins that change media URLs#
WP Media Cloud filters wp_get_attachment_url, wp_get_attachment_image_src, image attributes, srcset and post content at priority 99. A plugin that filters the same values at a later priority can replace the CDN address.
- Run the Health checks. A failing URL Rewriting row shows the address that was produced.
- On a staging site, deactivate other plugins one at a time and run the checks again.
- When the row passes, the last plugin you deactivated is the cause. Look for a setting in it that turns off URL changes, or contact its developer.
Reporting a conflict#

- Go to Health, click Run All Checks, then click Download Log.
- Note the other plugin’s name and version and what you see on the page.
- Send both to support.