Home Forums WoodMart support forum Text Book Centre Website Down Issue

Text Book Centre Website Down Issue

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #724676

    it-1760
    Participant

    Dear WoodMart Support Team,

    We would appreciate your assistance in investigating a performance issue that started immediately after updating the latest version of the WoodMart Theme and WoodMart Core.

    Following the updates, our server monitoring detected approximately an 8x increase in PHP slow log entries compared to the logs from the previous day.

    Our Findings
    After comparing the PHP slow logs before and after the updates, we observed that the majority of the new slow requests consistently originate from WoodMart while rendering HTML Blocks, Header Builder, and Mega Menu content.

    The recurring execution path is:
    woodmart_get_html_block()

    woodmart_get_post_content()

    woodmart_elementor_get_content()

    Elementor\Frontend->get_builder_content_for_display()

    Document->print_elements()

    Element->print_element()

    Widget->render_content()

    The slow requests are primarily triggered while rendering:
    HTML Blocks
    Header Builder
    Mega Menu
    Extra Menu List widgets
    Elementor templates rendered through WoodMart

    We also noticed repeated execution of the following WoodMart methods:
    woodmart_elementor_get_content()
    woodmart_get_post_content()
    woodmart_get_html_block()

    In addition, the Product widgets rendered through WoodMart are repeatedly initiating Elementor rendering and new WP_Query executions.

    Comparison
    Before the updates, the slow logs mainly consisted of isolated WooCommerce queries and normal WordPress operations.
    Immediately after updating WoodMart, the majority of slow requests shifted to the WoodMart → Elementor rendering pipeline.

    Could you please help us verify:
    Whether this is a known issue with the latest WoodMart release.
    Whether there have been recent changes to the HTML Block, Header Builder, or Mega Menu rendering process.
    Whether woodmart_elementor_get_content() is expected to invoke Elementor frontend rendering on every request or whether the output should be cached.
    Whether there are any recommended patches, compatibility fixes, or performance optimizations for the latest WoodMart version.

    We look forward to your findings.

    Attachments:
    You must be logged in to view attached files.
    #724728

    Aizaz Imtiaz Awan
    Keymaster
    Xtemos team

    Hello,

    Thanks for the detailed report and for outlining the exact call stack — that’s very helpful.

    This is not a known widespread issue in the latest public WoodMart release, so we’d like to reproduce and profile it to see why Elementor rendering is being triggered repeatedly for HTML Blocks, Header Builder, and Mega Menu on your setup.

    To proceed, please provide via the forum’s Private Content field:
    – Temporary WP admin access (URL, username, password). A staging site is preferred if available.
    – Exact versions you updated from and to:
    – WoodMart theme and WoodMart Core
    – Elementor (and Elementor Pro, if used)
    – WordPress and WooCommerce
    – A few sample PHP slow log entries (full entries with timestamps and execution time) that show the stack you listed.
    – A URL or steps to trigger the slow request (specific page(s) and whether logged-in or guest).
    – Active caching/optimization layers (server/page cache, object cache/Redis, CDN) and any performance plugins currently enabled.

    While we investigate, a few quick isolation checks you can run to help narrow it down:
    – Temporarily assign a very simple header (no HTML Blocks/Mega Menu) in Header Builder and compare slow logs for the same page.
    – If safe on staging, briefly disable non-essential third‑party plugins and re-check the slow log for the same requests.
    – If you have the previous WoodMart Core/theme versions available, testing a rollback on staging to confirm a regression signal (and telling us the exact versions) will speed up our fix.

    Once we have access and the details above, we’ll profile the rendering path (woodmart_get_html_block → elementor_get_content) and escalate to our developers if we confirm a regression, providing a fix or patch as needed.

    Kind regards,
    XTemos Studio

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