SazKit – Product Gallery for WooCommerce

1.0.7

• Fixed the variation-image swap (a product’s main slide updating when a shopper selects a variation with its own image) incorrectly targeting an add-on’s 360° spin or before/after comparison slide when one was configured as the gallery’s first slide. A comparison slide holds two images, so this could overwrite both with the same variation image. The swap now only ever targets an actual product-image slide.
• Fixed that same fix causing the slider to auto-navigate away from a deliberately-placed first-slide video/360°/comparison slide the moment a variation resolved (which happens automatically on page load whenever a variation is pre-selected) — it no longer jumps the slider away from that slide, while still applying the variation’s own image to the correct slide underneath it.
• The Style tab’s “Gallery height” setting now auto-selects a matching “Image fit” when changed (Cover for Fixed height, Contain for Auto), since Image fit only applies in fixed mode and the two commonly pair up. Still editable afterward if a different combination is wanted.
• Registered a new 200×200 thumbnail size and switched the gallery’s thumbnail strip to use it instead of WooCommerce’s own 100×100 woocommerce_gallery_thumbnail, which looked blurry once scaled up by the CSS (e.g. showing 4 thumbnails at once). The sazkit_thumb_image_size filter still works for further customization. Note: this only affects images uploaded/cropped after updating — existing product images need a thumbnail regeneration (e.g. via WP-CLI wp media regenerate or a “Regenerate Thumbnails” plugin) to pick up the new size.
• Added a “Force gallery width on desktop” option (Style tab → Gallery sizing) — an escape hatch for themes/page builders whose own layout CSS conflicts with the gallery’s width, letting you pin it to an explicit percentage (default 48%, matching WooCommerce’s own classic-theme default) above the 600px mobile breakpoint. Off by default; doesn’t apply on block themes, which already control the gallery’s width via the product-image-gallery block’s own layout.

1.0.6

• Renamed the plugin folder and main file to match the slug assigned by WordPress.org during review (sazkit-product-gallery-for-woocommerce), resolving a Text-Domain/slug mismatch flagged by Plugin Check. The Text Domain and all translation strings now correctly match the assigned slug. Also removed a stray .claude directory (an AI-assistant config folder) that had been flagged as not belonging in a production plugin.

1.0.5

• Removed the Custom CSS field from the Style tab. Per the WordPress.org plugin review team’s policy against plugins accepting arbitrary user-supplied CSS/JS/PHP for output, the free-form textarea (previously piped straight into wp_add_inline_style) has been removed entirely. The Style tab still offers the arrow/dot color pickers.
• Renamed the main class from SazKit_Gallery to Sazkit_Gallery to resolve a plugin-review prefix-consistency flag (the capitalized “K” didn’t match the lowercase sazkit_ prefix used everywhere else — hook names, filters, the option key). No functional change; only affects code that referenced the class name directly (e.g. the Pro add-on, updated to match).

1.0.4

• Changed the Text Domain to sazkit-product-gallery-for-woocommerce (was sazkit-gallery) and updated every translation string to match. The admin menu slug, enqueued script/style handles, and the .sazkit-gallery CSS class are unchanged — only the translation domain moved.

1.0.3

• Fixed the arrow icons still losing their position to a theme’s own !important rule even after 1.0.2’s hardening: when both sides declare a property !important, it comes down to plain specificity, and a theme selector like button:not(.fa):not(.close-style)::before out-specifies a doubled class. The affected rules (main/thumbnail/lightbox arrow icons) now triple the class instead of doubling it, which reliably exceeds that kind of theme selector regardless of load order.

1.0.2

• Hardened the gallery’s structural CSS (layout, image sizing, arrows, dots, thumbnails, and the lightbox overlay) with !important on every property that would visibly break if a theme’s own generic styling overrode it — not just the arrow icons fixed in 1.0.1. Purely cosmetic details are left as-is; this only covers things that would otherwise stop working correctly.