WPIntell

Source evidence

Performance Issue: Large Query & max_allowed_packet Error

Stackable – Page Builder Gutenberg Blocks · support · 2025-07-31T16:52:00+00:00

complaintsentiment
highseverity
0.97relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
salvo2 unresolved
Hello Stackable Team, I’m experiencing a critical performance issue on my site caused by the Stackable plugin. On a shared hosting environment, the plugin creates a single, extremely large query (over 4 MB) when trying to save the _transient_stackable_get_design_library_json_v4 option. The problematic query is: INSERT INTO \wp_options ( option_name , option_value , autoload ) VALUES ('_transient_stackable_get_design_library_json_v4', ...) This causes a Got a packet bigger than ‘max_allowed_packet’ bytes error and makes my admin area very slow. I cannot change the server’s max_allowed_packet setting because I’m on shared hosting. Could you please provide a way to disable this specific function or suggest a fix for this behavior? Thank you for your help. Hi @salvo2 , Thanks for reaching out! Could you send over some login details to our support email support@wpstackable.com so we can check this further? We would also need FTP access. Sending these details will also allow us to create a ticket on your behalf and properly track the issue. Thank you!

Comments

1 shown
Charmela Malala 2025-10-03T10:47:00+00:00

Hi @salvo2 , Thanks for reaching out! Could you send over some login details to our support email support@wpstackable.com so we can check this further? We would also need FTP access. Sending these details will also allow us to create a ticket on your behalf and properly track the issue. Thank you!