Siteground optimizer conflict with WooComerce
-
For months now, the following message has appeared in the php_errolog: Undefined index: post_type in class-wc-admin-list-table-orders.php on line 650, the error occurs when entering the WC orders list. After searching for conflicts with other plug-ins, I detected that the problem occurs when the “Dynamic Caching” option is activated in Speed ??Optimizer. With the option disabled, the following is executed:
Speed Optimizer OFF ejecuta estas 4 invocaciones con post_type:
[10-Feb-2025 15:03:39 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: e-landing-page
[10-Feb-2025 15:03:39 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: e-floating-buttons
[10-Feb-2025 15:03:39 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: shop_order
[10-Feb-2025 15:03:39 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: Array
------------------------------
Speed Optimizer on only Dinmamic Cache Active ejecuta 6 invocaciones con post_type la del error es la que dice "NO DEFINIDO", pero se agraga una para "product", hay algo que esta mal la Cache Dinamica
[10-Feb-2025 15:05:15 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: e-landing-page
[10-Feb-2025 15:05:15 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: e-floating-buttons
[10-Feb-2025 15:05:15 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: product
[10-Feb-2025 15:05:15 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: shop_order
[10-Feb-2025 15:05:15 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: NO DEFINIDO
[10-Feb-2025 15:05:16 UTC] ?? WooCommerce: search_custom_fields() invocado en edit.php con post_type: ArrayThe page I need help with: [log in to see the link]
Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.