| 开发者 |
kodlo
imaginary222 |
|---|---|
| 更新时间 | 2026年8月24日 03:12 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0+ |
| 版权网址: | 版权信息 |
srcset, and sizes attachment data to reserve media space.fetchpriority="high" and decoding="async"; remaining rendered images receive loading="lazy" and decoding="async".:focus-visible styles, descriptive video titles, active-thumbnail state, and hidden-state handling for limited pagination dots.prefers-reduced-motion by disabling gallery transitions and automatic video playback where appropriate.wcgs_video and woo_gallery_slider keys on an authorized administrator request. If supported legacy data is available, Kodlo asks whether it should be migrated. Nothing is copied until a WooCommerce administrator explicitly selects Migrate legacy data. The migration freezes a per-key metadata snapshot and immediately processes protected 50-row AJAX batches on the current administration page while a progress notice remains visible. Public product views stay read-only. Every destination write is tied to the exact selected legacy row and shares an internal per-object lock with normal Kodlo metadata saves, so a newer or explicitly empty Kodlo value remains authoritative.
During migration, the notice shows exact processed-row progress and asks the administrator not to reload or leave the page. Failed or repeatedly stalled batches stop automatic requests and expose a Retry button. When both jobs finish, the page automatically loads a completion notice with Keep legacy data as the safest default and Delete safely migrated legacy data as a separate explicit action. Both controls share one native WordPress action row. Safe cleanup uses the same visible protected batch runner, keeps an independent snapshot and cursor for each legacy key, and never crosses the corresponding completed migration boundary. It removes an unchanged legacy row only while its exact Kodlo destination still exists with the migrated value. Unsupported, unmatched, unmigrated, later-created, concurrently changed, or subsequently changed rows remain untouched.
SVG Safety
SVG attachments accepted by the standard WordPress and Elementor media workflow are supported like other image attachments, without an additional Kodlo-specific approval layer.
Deactivation and Permanent Deletion
Deactivation stops the widget and its frontend behavior without deleting Elementor widget settings, attachment Video URLs, variation gallery assignments, or migration progress. Reactivating the plugin restores the configured galleries.
Permanent deletion through the WordPress Plugins screen removes Kodlo's internal migration state, temporary locks, and administrator failure notices. Authored gallery content remains in WordPress post metadata to prevent accidental product-data loss, so reinstalling the plugin can reuse it. Delete that product content separately only when you intentionally no longer need it.
/wp-content/plugins/kodlo-product-gallery-for-elementor directory, or install the plugin through the WordPress plugins screen.The widget itself works with Elementor Free or Pro, but it needs a WooCommerce product context on the frontend. Place it on a product page or inside a Single Product template. Building Single Product templates with Elementor Theme Builder requires the relevant Elementor Pro functionality.
Yes. Select Live Preview on WordPress.org. A temporary WordPress Playground site opens with WooCommerce, Elementor, a demo product, local demo images, and the Kodlo widget ready in the Elementor editor. You can safely change controls and responsive modes without affecting a live website. Starting the prepared YouTube video contacts YouTube, but no production store data is used.
Only when that page has a valid WooCommerce product context. The frontend renderer looks for the current WooCommerce product and does not output a gallery when no product can be resolved. In the Elementor editor, the preview can fall back to the first product so the widget remains editable.
Yes. Assign galleries in the WooCommerce variation editor. Kodlo supports complete variation events and partial matching while attributes are being selected.
Open an image in the WordPress Media Library, enter a YouTube, Vimeo, or direct MP4 URL in the Video URL field, and save the attachment. The image becomes the video poster and gallery thumbnail.
Only when the gallery uses an external video URL. Starting a YouTube or Vimeo video loads that provider's player, and starting a remotely hosted MP4 requests that file from its host. Review the provider's privacy terms and your site's consent requirements before publishing external media.
Enable Swipe Edge Bleed in the widget's General settings section. Match Mobile Side Gutter to the horizontal mobile padding around the gallery. Slides remain inside the content gutter at rest, can travel through it while swiping, and are clipped again after the slider snaps. Navigation Arrows Edge applies the same content-edge or screen-edge anchor to both main and thumbnail arrows.
Yes. Kodlo includes keyboard-operable navigation controls, semantic buttons, localized labels, visible focus states, descriptive embedded-video titles, reduced-motion support, and pagination visibility management. Final accessibility still depends on the surrounding page, theme, content, colors, and widget configuration.
Kodlo always outputs attachment dimensions and responsive image data. By default it does not add custom loading, fetchpriority, or decoding attributes. If Image Loading Optimization is enabled, the configured first images in the desktop grid, mobile slider, and mobile thumbnails receive fetchpriority="high" and decoding="async", while the remaining rendered images receive loading="lazy" and decoding="async".
Yes, with administrator consent. Activation resets the notice cycle, then the next authorized administrator request checks only WooGallery video URLs (wcgs_video) and variation gallery image lists (woo_gallery_slider). If either key is present, a WooCommerce administrator can explicitly start a fixed-snapshot migration. Protected 50-row AJAX batches then run immediately on the current page with processed-row progress, leave-page protection, and retry handling. Storefront requests never write migration data, and reactivation never resumes paused work without fresh consent.
After migration, Keep legacy data is the safest default. The separate Delete safely migrated legacy data action processes its own fixed snapshot in 50-row batches without crossing the completed migration boundary, and removes an unchanged row only while its exact Kodlo destination still exists. Unsupported, unmatched, unmigrated, concurrent, and later legacy rows are retained.
Deactivation stops the gallery functionality but preserves its data so the existing galleries return when the plugin is reactivated. Permanent deletion through the WordPress Plugins screen removes Kodlo's migration progress, temporary locks, and administrator failure notices. It intentionally preserves attachment Video URLs and variation gallery assignments because they are authored product content rather than disposable settings.