Next3 Offload Changelog

Sem data · 3 versões

1. 4.5.2

   Última

   2 alterações

   Ocultar

   Alterações

   • Googlebot, PageSpeed, and Lighthouse requests were always served the attachment's local URL instead of its cloud URL, even with local files removed after offload (this plugin's own recommended configuration) — meaning every crawl or performance-test hit returned links to files that no longer existed on disk. A page cache keyed by URL rather than by user-agent (several popular caching plugins) could then store that broken render and serve it to real visitors too, until the cache entry expired. The local URL is now only used when that local file is actually still present; otherwise the normal cloud URL is served.
   • An attachment was only ever offloaded once. If new derivative image sizes were generated for it afterward — for example after a crop-size setting change, or via WooCommerce's on-demand thumbnail regeneration — those new files were never uploaded to the cloud, while the plugin continued rewriting every size's URL to the cloud regardless, producing 404s for every newly-generated size. The plugin now also listens for WordPress's standard attachment-metadata-update event (not just the full regeneration pass triggered by a new upload or the "Regenerate Thumbnails" tool) and re-checks for any size that isn't accounted for yet, uploading just the new files without repeating work already done.

2. 4.5.1

   1 melhoria8 alterações

   Ocultar

   Melhoria

   • Improved

   Alterações

   • WebP/AVIF conversion: a new "Exclude GIF files" option (Optimization → WebP settings) leaves `.gif` files unconverted instead of silently turning an animated GIF into a static image when the server has to fall back to Imagick or GD (only the gif2webp CLI tool reliably preserves animation). A matching `next3_webp_skip_gif` filter is also available for finer-grained, code-based control.
   • Offloaded-media counts — the main dashboard totals, as well as Advanced Media Offloader and Infinite Uploads migration progress — now also recognize files offloaded under the plugin's older postmeta-based tracking, not only the current offload table, so sites that have been using Next3 since before that change see accurate numbers without first running a migration.
   • Advanced Media Offloader and Infinite Uploads migration progress is now computed from current state instead of only counting up while a migration batch is actively running, so files that are already offloaded show correctly right away.
   • A serious bug where an offloaded attachment's images could all serve the same, wrong size — most often the full original instead of the requested thumbnail/medium/large/custom size. Two issues combined to cause this: image URLs and dimensions for a given attachment were cached without accounting for which size was actually requested, so every size after the first one loaded on a page returned that first size's result for up to 24 hours; and a separate lookup used to resolve a size's own file name was reading WordPress's attachment metadata in a way that silently failed for every named size, falling back to the original file. Both are fixed, and each requested size now resolves to its own correct file and dimensions.
   • The Media Library's "Offload Status" filter (Offloaded / Unoffload) only checked the plugin's older postmeta-based tracking, so it showed incorrect results on any site using the current offload table.
   • A WP-CLI fatal error ("array_key_exists: Argument #2 ($array) must be of type array, null given") could make WP-CLI unusable on a site, including commands unrelated to media — anything that happens to touch the REST index, such as through WooCommerce's CLI runner.
   • `get_deleteObjects` could emit a PHP warning and incorrectly report success when called without a specific file to delete, on every supported cloud provider.
   • A recurring PHP warning when caching a provider's bucket file listing, caused by writing the cache file before its folder existed.

3. 4.5.0

   1 melhoria1 correção17 alterações

   Ocultar

   Melhoria

   • Improved

   Corrigido

   • Fixed a bug in the "Migrate from WP Offload Media" bulk migration tool where a file whose metadata contained a single quote (common in EXIF/description text) could silently fail to migrate and permanently lose its offload record, with no error shown. The migration path no longer builds raw SQL from that data.

   Alterações

   • Direct-to-cloud upload: a single new "Direct-to-cloud upload" option (Storage Settings → Advanced Options) sends every new upload straight to the cloud and removes the local copy as soon as it's confirmed offloaded, so new media is never left sitting on local storage.
   • Migration from Advanced Media Offloader: media already offloaded by the "Advanced Media Offloader" plugin can now be migrated into Next3 directly from the Tools tab. Amazon S3, DigitalOcean Spaces, and Wasabi migrate without re-uploading; other providers are re-uploaded through your configured Next3 provider.
   • Migration from Infinite Uploads: media already synced by the "Infinite Uploads" plugin can now be migrated into Next3 from the Tools tab.
   • WooCommerce: purchase-gated private media. Private media attached to a product (featured image, gallery image, or variation image) can now be restricted so only customers who actually bought that product receive a working URL, on top of the existing login-based access gate.
   • WooCommerce: downloadable product file protection. A downloadable product file that lives in the media library is kept pointed at its current (offload/privacy-aware) delivery URL automatically, and is upgraded from public to protected on first link so its cloud URL is signed rather than a permanent public link.
   • WooCommerce: media audit tool (Tools tab) reporting how much of a store's product media — images and downloadable files — is offloaded, still local-only, broken, or protected, plus the cloud storage that media uses.
   • File Manager: breadcrumb path navigation ("Buckets / bucket-name / folder / subfolder"). Every segment is clickable and jumps straight to that depth, replacing back/forward-only navigation that gave no visibility into the current path.
   • File Manager: proper icons for Word, Excel, and PowerPoint files, which previously had no icon mapping and displayed a generic "links" icon.
   • File Manager: the WordPress admin footer no longer renders on top of the last row of files on a short file listing.
   • File Manager: CSS/JS for the File Manager now bust visitors' browser cache automatically whenever those specific files change, independent of the plugin's overall version number.
   • The offload table migration tool now removes the legacy postmeta it just migrated once a row is safely confirmed in the table, instead of leaving both copies around indefinitely.
   • Every code path that offloads or migrates media into Next3 (new uploads, "Direct-to-cloud upload," WP Offload Media migration, Advanced Media Offloader migration, Infinite Uploads migration) now writes offload state directly and consistently to the `wp_next3_offload` table.
   • File Manager: the name and file size of every non-image file were rendered twice in grid view.
   • "Restore to local" (unoffload) was only restoring an attachment's main file; every thumbnail size was left missing with no local copy and no error. Fixed by resolving each size's own cloud location directly instead of through a lookup that could only ever resolve the main file.
   • On a server without AVIF encoding support, an attachment configured for AVIF conversion was correctly saved as WebP, but the plugin still tracked it internally as AVIF — causing thumbnail restoration to look for files that didn't exist. The tracked format now always matches what was actually produced.
   • If any single thumbnail size failed to upload during an offload, the local copies of that attachment (including sizes that did upload successfully) could still be deleted by "Remove local media." Local files are now only removed once every required upload for that attachment is confirmed successful.
   • Private media's access rules can now be extended by other plugins (such as WooCommerce) without any change to the core access check.