Home Forums WoodMart support forum Single product page renders blank/incomplete (silent crash) after updating to W

Single product page renders blank/incomplete (silent crash) after updating to W

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #728693

    niezgubki
    Participant

    Site: https://niezgubki.pl/excelsior/ (staging clone of production, created with WP Staging) Theme: WoodMart 8.5.7 (child theme active, parent updated) WoodMart Core plugin: 1.1.8 WooCommerce: 7.8.4 (not yet updated — this bug is blocking that update) WordPress: 7.0.4 PHP: 7.4.33 (PHP-FPM) Page builder: WPBakery Page Builder Hosting: LH.pl (Apache + PHP-FPM)

    Problem:

    After updating the WoodMart theme from 7.2.4 to 8.5.7 and WoodMart Core from 1.0.39 to 1.1.8, one specific product page renders as a blank/truncated page. The affected product is “SafeKid ID Smart Tag” (post ID 22350, ?product=safekid-id-smart-tag). No other product on the site is affected.

    The rendered output is not empty — the <head>, header, and the first part of <main> (including a “Nowość” featured-product badge) render correctly. The response then stops mid-markup, with no closing </main>, </body>, or </html> tags, and no PHP error, warning, or notice anywhere.

    Exact crash location (confirmed via raw HTTP response inspection, bypassing browser rendering):

    The response is always truncated immediately after this markup:

    html
    <div class=”product-labels labels-rounded”>
    <span class=”featured product-label wd-shape-round”>Nowość</span>
    </div>

    <figure class=”woocommerce-product-gallery__wrap

    i.e. it dies while constructing the product gallery wrapper (woocommerce-product-gallery__wrapper wd-carousel wd-grid), before the <figure> tag is even finished. This has been 100% reproducible across dozens of tests over two days.

    What we have ruled out (each confirmed via a disposable draft copy of the product, made with “Copy to a new draft”, tested, then trashed — the live product itself was reverted/confirmed unaffected after any direct test):

    Gallery image count: tested with the full 11-image gallery, and with the gallery completely emptied (0 images) — identical crash both times.
    Gallery image content — not a factor, since even 0 images still crashes.
    Main “Product image” (_thumbnail_id) — cleared entirely (confirmed via server-side check, not just UI) — still crashes.
    WPBakery product description content — replaced with a placeholder — still crashes.
    Product type — converted the live product from a variable product (size/design swatches) to a simple product and back — crashes identically either way.
    Per-product WoodMart layout settings: _woodmart_thums_position = “without” (hide thumbnails), _woodmart_single_product_style = “1” (Small image) — both tried individually — still crashes.
    WoodMart Core plugin deactivated entirely (site-wide, for the duration of one test) — the crash still occurred, at the exact same byte position. This indicates the hang is in the WoodMart theme’s own gallery template code, not the WoodMart Core plugin.
    Variation Swatches for WooCommerce plugin — deactivated, no change.
    WP-Optimize page cache — cleared, ruled out (this was an earlier false lead, not the real cause).
    Server-side resources — our host (LH.pl) confirmed no above-normal CPU/RAM usage, no entries in PHP-FPM error_log, and no entries in Apache error_log for the timeframe of repeated reproductions. WP_DEBUG_LOG (via the WP Debugging plugin) is also enabled and has never caught a fatal error or exception for this crash, despite it reproducing on every request.

    Working theory: given that no log anywhere (WordPress, PHP-FPM, Apache, host resource monitor) records any error, warning, timeout, or resource spike for this crash, we suspect a silent infinite loop or hang inside the WoodMart 8.5.7 gallery-wrapper rendering code, triggered by something specific to this one product’s data (since it is 100% product-specific and independent of every image/gallery/description/type-related factor we could test), which is eventually cut off by a connection or proxy-level timeout that isn’t logged anywhere we have access to check.

    What we’d appreciate from support:

    Given the exact crash point (woocommerce-product-gallery__wrapper wd-carousel wd-grid construction), can you point us to what in a product’s data (attributes, variations, terms, or a specific postmeta key) could cause this to hang in 8.5.7’s gallery template code?
    Are there any known regressions in 8.5.7 (vs. 7.2.4, which worked fine) in the single-product gallery rendering path?
    Is there a debug/verbose logging mode specific to WoodMart’s gallery rendering that would surface something PHP’s own error log doesn’t catch (e.g., a caught exception that’s silently swallowed)?

    We’re happy to provide staging access, a full export of the product’s data, or run any diagnostic snippet you can provide.

    Thank you!

    #728697

    niezgubki
    Participant

    Follow-up — same issue also confirmed on production, on the OLD (pre-update) theme version:

    We just discovered the same class of failure is occurring on our production site (https://niezgubki.pl — still running WoodMart 7.2.4 / old WoodMart Core, WooCommerce 7.8.4, i.e. NOT yet updated) on a different product: “Obywatel Zwierz” (https://niezgubki.pl/produkt/stylowe-adresowki-dla-czworonogow-z-klasa/, post ID 8330).

    Symptoms are the same category of failure, but slightly different in character: instead of a quickly truncated 200 response, this request simply hangs with no response at all for 30+ seconds (tested both as a logged-in admin and as an anonymous visitor, with cache disabled).

    Important detail: our production site uses the WP-Optimize page-cache plugin. We believe this explains why the bug seems to “come and go” across random products over time — when a product’s page happens to render successfully once, WP-Optimize caches it and it keeps working for visitors (~24h TTL) even if the underlying render is broken; when the cache entry expires or is purged, the next request re-triggers a live render, which can hang again if the issue is still present for that product. We confirmed this directly: we fully purged the WP-Optimize cache for this product and immediately re-requested it fresh — it still hung with no response, ruling out a stale-cache artifact.

    This suggests the underlying issue may not be a new 8.5.7 regression at all, but a pre-existing rendering bug (also present in 7.2.4) that intermittently affects different products’ galleries, which page caching has mostly been masking on production until now. We’ve temporarily set this production product to “Private” to stop it serving a broken page to customers while this is investigated, but wanted to flag this since it significantly broadens the scope of the issue — it’s not isolated to one product on the updated staging site.

    No CDN sits in front of this site (only Apache + WP-Optimize in the response headers), so this isn’t a CDN masking or interfering with anything.

    #728732

    Aizaz Imtiaz Awan
    Keymaster
    Xtemos team

    Hello,

    Thank you for the detailed information.

    I have checked the staging website and tested the affected product “SafeKid ID Smart Tag – wrist locator” (ID: 22350). At the moment, the product page is loading and displaying correctly on our end, including the product gallery.
    See Screenshot for clarification: https://postimg.cc/14zRRLhX

    Since the issue is not currently reproducible, could you please let us know if there are any specific steps or conditions required to trigger the problem?

    This will help us investigate the issue further and compare the behavior with your environment.

    Best Regards

Viewing 3 posts - 1 through 3 (of 3 total)