| 开发者 | clulevelup |
|---|---|
| 更新时间 | 2026年10月28日 16:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
picture element;/wp-content/plugins/ or install its ZIP through Plugins > Add Plugin.clujmi marker and an immutable token. Existing companions from earlier private releases retain their original filenames. Exceptionally long names are shortened only as much as necessary to stay within conservative Windows and SMB path limits.Because the directory slug has changed, the earlier plugin cannot discover this release as an ordinary update. Deactivate Just Modern Images first, then install and activate CLU Just Modern Images. On Multisite, also check Network Admin. Keep the earlier plugin installed until the new status screen confirms that the image data import has finished. The new plugin imports existing settings, image manifests, processing results, history, and pending jobs in resumable batches. It keeps already generated companion files in place. Do not uninstall the earlier plugin before this import: its uninstall routine removes the files and records that need to be transferred. Once the import is complete, the inactive earlier plugin can be deleted.
No. Original JPEG and PNG files and WordPress attachment metadata remain unchanged. Modern files are separate companions.
Newly rendered WordPress pages return to the original image markup and URLs. Previously cached HTML can still reference modern companions, which remain on disk after deactivation. Clear page and CDN caches before uninstalling the plugin, because uninstall removes its companion files. No thumbnail regeneration is required.
AVIF is skipped. WebP continues when available, and the original image always remains the fallback.
Yes. Activation starts a cursor-based background scan that can resume after timeouts or missed cron runs. You can queue the scan again from the status screen.
The source may be unavailable locally, the server may not support the format reliably, the image may exceed the safe memory budget, or the generated file may be no smaller than the original. The settings screen and Media Library show the most relevant explanation and diagnostic code.
The Media Library is refreshed in the background. Existing valid modern files remain active until verified replacements are ready. Images selected manually, newly uploaded, or needed by a frontend response are processed before the remaining library backfill.
The worker measures how long completed images take and starts another only when a safe reserve remains. By default it may use up to 45 seconds on servers whose PHP limit leaves enough room, while IIS and short-lived requests use a conservative budget of up to 20 seconds. It processes at most 50 images across all CLU Just Modern Images events in one request, yields at 80% of the PHP memory limit, and leaves five seconds before the PHP execution limit. These are internal safety limits, not settings that site owners need to manage.
The plugin uses normal WordPress upload URLs and provides a filter for CDN integrations. A CDN or offload plugin must make generated companion files available just like other files in the uploads directory.
Not in this release. The first release intentionally covers attachment images rendered through standard WordPress APIs without buffering or rewriting the entire page.
The plugin preserves existing picture elements and images managed by JavaScript lazy loaders. These images keep their original delivery behavior. Native WordPress loading="lazy" remains supported with modern sources. CDN and offload integrations must also publish the generated companion files; remote-only media remains on its original URLs.
original-name.jpg.clujmi-token.avif, with safe truncation for Windows and SMB paths.picture rendering with an unchanged original fallback.