Blocksy WooCommerce Layout Broken: Gallery, Shop Extra and Template Versions

What a broken Blocksy store looks like up close

Store layouts fail in recognizable shapes. Match yours before you change anything, and check whether it happens logged out, on a phone, and on every product or only some. A layout that is broken for visitors but fine for you points at caching and optimization, not at the theme.

• Gallery images enormous and stacked on top of each other, thumbnails the size of the main image, the summary column pushed below the gallery.
• A gallery that looks right only after you scroll or tap, then snaps into a slider.
• Shop grid images at different heights or cropped oddly after you changed an image ratio in the Customizer.
• Variation swatches, quick view or the floating cart bar missing or showing as plain buttons.
• Cart or mini-cart markup out of place, often after a WooCommerce update, with a notice about outdated template files.
• Header elements shown in red inside the Customizer, meaning a Companion or Pro feature is switched off.

Three layers draw every Blocksy product page

The free theme supplies the structure. Its options sit under Customizer > WooCommerce, split into General, Product Archives and Single Product. Single Product holds Product Gallery (image ratio, image size, thumbnail position, sticky gallery) and Product Elements, the stack of title, price, add to cart and other parts in the summary column. The free Companion plugin and the paid Companion Pro add features on top. Pro's Shop Extra extension, on the Business and Agency plans as of October 2026, is a set of modules including Floating Cart, Quick View, Filters, Wish List, Compare View, Variation Swatches and Advanced Gallery, which adds extra gallery layouts. Modules are switched on under Blocksy > Extensions.

WooCommerce itself supplies the rest, and Blocksy replaces only a handful of its templates. The 2.1.58 theme package carries seven overrides, listed below with the WooCommerce version each one declares. Notice what is missing: the single product page is not an override. Blocksy builds it with hooks and its own gallery code, so a broken product page is rarely a stale template and usually a settings, script or version problem.

Blocksy 2.1.50 and the product page reports

Blocksy 2.1.50 shipped on July 23, 2026 with a refactor of the single product Add to Cart logic, changes to how product gallery layouts and variation swatches are handled, and updated cart and mini-cart templates for WooCommerce 11.0. On the wordpress.org forum, one owner reported that the update broke the product page: gallery overlapping, details pushed below. Reverting to the previous version fixed it, and support asked for a live URL because screenshots were not enough to diagnose it. Another owner reported no problem after updating, so it did not hit every store.

The next two releases touched the same area. The 2.1.51 changelog says the single product gallery now properly respects new format values in the Customizer, and 2.1.52 lists a fix for more reliable applying of default gallery attributes. Neither entry names the forum report, so we will not claim they solved it. The practical reading: if your product page broke around 2.1.50, update the theme, Companion and Pro to the current release together before anything else. If it is still broken there, you have a different cause, listed next.

Six causes, ranked for a Blocksy store

1. Theme, Companion and Pro on different versions

CreativeThemes' documentation says the theme and Companion should run the same version number. In 2.1.58 Companion also checks a minimum theme version and switches its features off if the check fails, which takes Shop Extra modules with it. Check Plugins and Appearance > Themes side by side.

2. Gallery styles held back by an optimizer

The gallery's slider stylesheet, flexy.min.css, is not loaded in the page head. The theme's main.js adds it after finding a gallery on the page. Delay JavaScript until interaction, and the gallery renders unstyled until the visitor moves: big images, stacked. Check by pausing the optimizer and reloading a product page.

3. Outdated overrides in a child theme

A child theme that copied WooCommerce templates years ago keeps serving them after WooCommerce moves on. Check WooCommerce > Status, Templates section, which lists every override and flags old ones.

4. Stale CSS

Layout options live in Blocksy's generated stylesheet. Change the gallery width or ratio and a cached copy keeps the old one. Blocksy CSS not updating gives the purge order.

5. Shop Extra and swatch plugins overlapping

Two variation swatch systems, or a third-party gallery plugin with Advanced Gallery, will fight over the same markup. Blocksy's changelogs keep adding integration fixes for named plugins, a sign of how often this happens. Turn modules off one at a time on staging.

6. A builder template replaced Blocksy's page

An Elementor product template takes the page away from Blocksy's options, so changing them does nothing. See Blocksy with Elementor and Elementor theme conflicts.

Put the product page back together on staging

1. 1

   Copy the store to staging

   Never debug a layout on a site taking orders. Include the database so products, variations and Customizer settings match.

2. 2

   Match the three versions

   Update Blocksy, Companion and Companion Pro to the same current release. Reload a product page logged out.

3. 3

   Pause optimization

   Turn off JavaScript delay, CSS combining and unused CSS removal. If the gallery recovers, exclude Blocksy's main.js from delay and keep CSS processing off.

4. 4

   Read the template report

   Open WooCommerce > Status and find the Templates section. Update or delete any outdated override in your child theme, keeping a copy of custom changes.

5. 5

   Reset the gallery settings

   In Customizer > WooCommerce > Single Product > Product Gallery, set the image ratio and size again and Publish. A Customizer save can queue WooCommerce image regeneration in the background; give it time to finish before judging the shop grid.

6. 6

   Test modules one by one

   Under Blocksy > Extensions, switch Shop Extra modules off and back on individually, checking the product page each time. Do the same for any swatch or gallery plugin.

7. 7

   Compare one version back

   Still broken? Install the previous theme release on staging only. If that fixes it, send CreativeThemes the staging URL, since support has asked for live links rather than screenshots.

Keep the store layout steady through WooCommerce releases

Blocksy follows WooCommerce closely; its 2026 changelogs mention WooCommerce 11.0, 11.1 and 11.2 by number. That is good news, but it means store fixes arrive in a stream of small releases. Treat each one as a change to test, not a chore to click through.

• Update WooCommerce first on staging, then Blocksy, Companion and Pro, then check a simple product, a variable product, the cart and checkout.
• Turn off automatic theme updates on the live store and update weekly after a staging check.
• Before a big change, export your settings in Customizer > General Options > Manage Options.
• Keep custom WooCommerce template copies out of the child theme unless you will maintain them, and recheck WooCommerce > Status after every WooCommerce release.
• If checkout misbehaves rather than looks wrong, start with WooCommerce checkout not working; missing options belong to variations not showing.

For the wider setup, our guide to Blocksy and WooCommerce covers which store features are free and which need Shop Extra, and Blocksy pricing shows which plan carries it.

When the store outgrows a theme, two plugins and an optimizer

A Blocksy product page is assembled by WooCommerce, the theme, Companion, Companion Pro, a swatch or filter plugin and a caching layer. Each can be correct on its own and still produce a broken page together. A small catalog can live with that, and for a simple store Blocksy is a sensible, affordable choice. A store where every release means a staging session, or where the gallery also slows the page, is paying a tax on the stack itself.

Six vendors can each be right and still hand your customer a broken product page.

A Next.js storefront ships the product page as one tested build, with images sized by next/image and no optimizer rewriting scripts after deploy. Athena CMS includes built-in e-commerce for stores that fit it. It costs more to build, so read WooCommerce vs Next.js, the theme-level Blocksy vs Next.js and the move plans in Blocksy to Next.js and WooCommerce to Next.js first. To fix the store you have, our theme repair service works on staging, and theme troubleshooting finds the cause before quoting. The general WooCommerce layout guide and the troubleshooting section cover other themes, and Blocksy mobile menu problems often share the same optimizer cause.