ppwebox
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] wp_wc_category_lookup table corrupted – how regenerate?Thanks, but I tried all WC tools and neither did generate the missing wp_wc_category_lookup table. Have you actually tested your advice?
Forum: Plugins
In reply to: [WooCommerce] wp_wc_category_lookup table corrupted – how regenerate?Hi ckadenge
Thanks for your input.
I think the persistent error even after exchanging the two corrupt table files was due to not flushing the Redis object cache.
I rebuilt the table from the exported table via live server, so this is fine. Disabling and re-enabling Woo did not create the wp_wc_category_lookup table. And if I correctly recall from a previous attempt, neither did deleting Woo. The “Tools” should provide an option to recreate missing Woo tables.
Hi Carla
Better late than never, thanks ??
I was testing with the WP CLI command line tool “wp profile hook –all –orderby=time –spotlight –url=XXX”. But you are right, neither can I detect any traces of Kadence WED being loaded anymore.
I suspect it was due to a bug of Woocommerce, since at the same time I had to raise awareness of the Woo devs at Github about the ever worsening load performance of Woo, mainly due to loading unnecessary Woo elements not required in the front-end. The devs then soon optimized quite a few loading sequences and fixed related performance bugs, so this might explain it.
Best regards – Phil
Forum: Plugins
In reply to: [Maspik - Advanced Spam Protection] URL pattern in text field is not blockedThanks for your swift reply.
I will try the text field option “Considered as spam IF a text-area field containing at least X links…”. Basically, all recent SPAM do contain an URL.
Nevertheless, the regex key “https” should match any full URLs in the text area field, so this is a bug right there.
Now I have to figure out as to why ReCaptcha and the Honey pot trap suddenly have become useless antispam tools.
Uff, Gilbert. Thank you for your efforts anyway. Maybe it’s language barrier thing but you really seem unable to understand the gist of this question.
It’s not a technical question – as you assume – in the sense of how WordPress is loading plugins and functions. Not at all. The question, or rather bug report, is that KWED should not be loaded and executed at all on the frontend. As it is, KWED is loaded on every html page visit by every visitor which is downright silly and a waste of CPU resources. This is generally a real problem with WP, Woo, and co. KWED has no tasks to execute on the frontend (the online content visible to the world). It’s a E-mail template design plugin to be used by the admin in the backend and should only be loaded when editing the templates.
Hopefully you got it now! ??
Thanks Gilbert. But my point is about why KWED is loading on the frontend for nothing. It is not needed there at all. Its role is a backend app to design E-mail templates which Woocommerce will use for backend comms with the customer and admin.
Normally, and as in best practice for better page load performance, only plugins and functions should be loaded that are actually required by the web page being visited. Woocommerce itself is a glaring example of code bloat and useless loading of unneeded components.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsAs to problem #3: yes, the Woo 8.5.1 update seems to have fixed it.
Problem #2: if there is a culprit to name here it’s Woocommerce. If Woo is deactivated on a page, it invalidates the custom product categories as well, which then get tagged as invalid/missing links in the custom WP menu, and thus Elementor cannot display them in the frontend.
Workaround:
- Create the same product categories/URLs in WP > Templates > Categories
- Delete Woocomerce product category links in menu
- Replace with custom links using URLs of WP > Templates > Categories
As to problem #1: this ought to be a Woo problem if handshaking with PayPal during checkout is incomplete. Woo is loaded at checkout and is only unloaded on specific non-shop pages. AssetCleanUp just unloads Woo on some selected unrelated pages.
Why does WP give me here an error “Are you sure you wanted to do that?” when posting new content via form? So silly since the site does not cache what I wrote and everything is lost when I switch back a page. Somehow so typical WordPress – always bugs, always problems, always slow. Sorry for the rant – but this is fact.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsWould you believe the reason for WP complaining about a corrupt database?
Both “siteurl” and “home” entries were suddenly gone in wp_options. Caused by some unknown action (not by me). Everything else was OK.
WP checks in functions.php for existence of siteurl in wp_options and completely freaks out if missing (“‘One or more database tables are unavailable. The database may need to be repaired.”), even though siteurl is available in wp-config.php.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsIt also appears that the downgrade from Woo 4.5 to 4.4 killed the database of the live site. WP altered about corrupted tables two day ago, offered the repair tool, but eventually became unusable. Restored to a 3-day old backup and now the Rest API 403 errors are gone.
But 3 problems remain.
- Unloading the entire Woo plugin in the frontend (not backend!) via Asset Cleanup on all pages except cart, checkout, account, single product archive, product archive (shop page), product pages/archives, checkout, cart, and any page using Woo, will create some unexpected bugs. On site A this will cause PayPal payment on checkout (a) even though Woo is loaded here, (b) but TWINT works) to partially fail. PayPal will successfully finalize payment but the sync with Woo fails, and Woo wrongly sets the order to pending instead of to completed.
- On site B – using Elementor pages and Hello theme – this causes the navigation menu to loose all product link entries in the frontend on those pages with Woo unloaded. This does not happen on site A, though Modern Events Calendar partially manages the eCommerce side of things.
- Woo admin pages cause excessive ajax requests when using Chrome/Chromium – every second! See also other recent support topic “WC admin pages cause excessive ajax requests”.
Forum: Plugins
In reply to: [WooCommerce] WC admin pages cause excessive ajax requestsExactly the same problem, setup and testing here! Don’t expect a helpful response since the real problem is the bloat and inefficiency of Woocommerce. Automattic who purchased Woo a while ago seems to have no real intention to tackle that code mess. They just add more features and bloat. Woo has become the Achilles heel of a modern WP CMS, unfortunately. An opportunity for competitors, which I have seen none so far, though.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsDeactivated all plugs except Woocommerce. REST API 403 and 401 errors en masse. Same when switching Hello theme to Twenty Twenty Four. Woo is version 8.5.0. Another site on the same server is using Woo 8.4.0 and has zero problems. So Woo 8.5.0 seems to be the culprit causing the massive unauthorized errors. To proof this I replaced Woo 8.5 with 8.4, but the errors remain, unfortunately. This on both the localhost (staging) and live server.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsNot related I think but since yesterday there is a new problem with REST API returning 403 server errors:
GET https://www.XXX.XXX/wp-json/wp/v2/users/me?context=edit&_locale=user 403
j @ https://www.XXX.XXX/XXX/wp-includes/js/dist/api-fetch.min.js?ver=0fa4dabf8bf2c7adf21a:2Certain actions such as saving modified products in the WP backend now hang and never finish. Two users with the same login data. Never had such problems until now.
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsHi Carolm
Thanks for evaluating.
For speed measurement I used the WP-CLI Command “wp profile hook” as mentioned previously.
Fatal error logs are only a few and very similar to these strange errors (redirect problem?):
2024-01-07T23:05:23+00:00 CRITICAL Uncaught TypeError: parse_url(): Argument #1 ($url) must be of type string, null given in /XXX/XXX/wp-content/plugins/query-monitor/collectors/http.php:374 Stack trace: #0 /XXX/XXX/wp-content/plugins/query-monitor/collectors/http.php(374): parse_url(NULL, 1) #1 /XXX/XXX/wp-content/plugins/query-monitor/classes/Collectors.php(84): QM_Collector_HTTP->process() #2 /XXX/XXX/wp-content/plugins/query-monitor/classes/Dispatcher.php(108): QM_Collectors->process() #3 /XXX/XXX/wp-content/plugins/query-monitor/dispatchers/REST.php(38): QM_Dispatcher->get_outputters('headers') #4 /XXX/XXX/wp-includes/class-wp-hook.php(326): QM_Dispatcher_REST->filter_rest_post_dispatch(Object(WP_REST_Response)) #5 /XXX/XXX/wp-includes/plugin.php(205): WP_Hook->apply_filters(Object(WP_REST_Response), Array) #6 /XXX/XXX/wp-includes/rest-api/class-wp-rest-server.php(454): apply_filters('rest_post_dispa...', Object(WP_REST_Response), Object(WP_REST_Server), Object(WP_REST_Request)) #7 /XXX/XXX/wp-includes/rest-api.php(424): WP_REST_Server->serve_request('/code-snippets/...') #8 /XXX/XXX/wp-includes/class-wp-hook.php(324): rest_api_loaded(Object(WP)) #9 /XXX/XXX/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #10 /XXX/XXX/wp-includes/plugin.php(565): WP_Hook->do_action(Array) #11 /XXX/XXX/wp-includes/class-wp.php(418): do_action_ref_array('parse_request', Array) #12 /XXX/XXX/wp-includes/class-wp.php(813): WP->parse_request('') #13 /XXX/XXX/wp-includes/functions.php(1336): WP->main('') #14 /XXX/XXX/wp-blog-header.php(16): wp() #15 /XXX/index.php(17): require('/XXX/XXX/wp-blog-header.php') #16 {main} thrown in /XXX/XXX/wp-content/plugins/query-monitor/collectors/http.php at line 374
System Status Report:
` WordPress Environment WordPress address (URL): https://www.XXX.XXX/XXX<br>Site address (URL): https://www.XXX.XXX<br>WC Version: 8.4.0<br>REST API Version: ? 8.4.0<br>WC Blocks Version: ? 11.6.2<br>Action Scheduler Version: ? 3.7.1<br>Log Directory Writable: ?<br>WP Version: 6.4.2<br>WP Multisite: –<br>WP Memory Limit: 512 MB<br>WP Debug Mode: –<br>WP Cron: ?<br>Language: de_DE<br>External object cache: ? Server Environment Server Info: Apache<br>PHP Version: 8.0.30<br>PHP Post Max Size: 128 MB<br>PHP Time Limit: 600<br>PHP Max Input Vars: 1000<br>cURL Version: 8.0.1<br>OpenSSL/1.1.1l-fips SUHOSIN Installed: –<br>MySQL Version: 10.6.15-MariaDB-log<br>Max Upload Size: 128 MB<br>Default Timezone is UTC: ?<br>fsockopen/cURL: ?<br>SoapClient: ?<br>DOMDocument: ?<br>GZip: ?<br>Multibyte String: ?<br>Remote Post: ?<br>Remote Get: ? Database WC Database Version: 8.4.0<br>WC Database Prefix: wp_<br>Total Database Size: 185.45MB<br>Database Data Size: 162.19MB<br>Database Index Size: 23.26MB<br>wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_order_items: Data: 1.52MB + Index: 0.05MB + Engine InnoDB<br>wp_woocommerce_order_itemmeta: Data: 1.52MB + Index: 0.66MB + Engine InnoDB<br>wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_acfef_payments: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_actionscheduler_actions: Data: 0.23MB + Index: 0.23MB + Engine InnoDB<br>wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_logs: Data: 0.23MB + Index: 0.16MB + Engine InnoDB<br>wp_cart_notices: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_cmplz_cookiebanners: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_cmplz_cookies: Data: 0.06MB + Index: 0.00MB + Engine InnoDB<br>wp_cmplz_services: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_comments: Data: 1.52MB + Index: 0.69MB + Engine InnoDB<br>wp_e_events: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_e_notes: Data: 0.02MB + Index: 0.17MB + Engine InnoDB<br>wp_e_notes_users_relations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_e_submissions: Data: 0.20MB + Index: 0.42MB + Engine InnoDB<br>wp_e_submissions_actions_log: Data: 0.11MB + Index: 0.33MB + Engine InnoDB<br>wp_e_submissions_values: Data: 0.22MB + Index: 0.13MB + Engine InnoDB<br>wp_kbp_form_entry: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_kbp_form_entrymeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_ksp_layers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_ksp_sliders: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_ksp_slides: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_mailster_action_bounces: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_action_clicks: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_action_errors: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_action_opens: Data: 0.05MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_action_sent: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_action_unsubs: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_forms: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_mailster_forms_lists: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mailster_forms_tags: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mailster_form_fields: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_mailster_links: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_mailster_lists: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mailster_lists_subscribers: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mailster_logs: Data: 38.02MB + Index: 0.00MB + Engine InnoDB<br>wp_mailster_queue: Data: 0.02MB + Index: 0.14MB + Engine InnoDB<br>wp_mailster_subscribers: Data: 0.05MB + Index: 0.08MB + Engine InnoDB<br>wp_mailster_subscriber_fields: Data: 0.05MB + Index: 0.05MB + Engine InnoDB<br>wp_mailster_subscriber_meta: Data: 0.13MB + Index: 0.25MB + Engine InnoDB<br>wp_mailster_tags: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_mailster_tags_subscribers: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mec_attendees: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_mec_bookings: Data: 0.11MB + Index: 0.22MB + Engine InnoDB<br>wp_mec_booking_attendees: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_mec_dates: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_mec_events: Data: 0.06MB + Index: 0.05MB + Engine InnoDB<br>wp_mec_external_sites: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_mec_occurrences: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_mec_users: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_ms_snippets: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_options: Data: 20.33MB + Index: 0.47MB + Engine InnoDB<br>wp_podsrel: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_postmeta: Data: 23.48MB + Index: 12.97MB + Engine InnoDB<br>wp_posts: Data: 68.22MB + Index: 1.02MB + Engine InnoDB<br>wp_rank_math_404_logs: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_rank_math_analytics_keyword_manager: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_rank_math_analytics_objects: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_rank_math_internal_links: Data: 1.52MB + Index: 0.27MB + Engine InnoDB<br>wp_rank_math_internal_meta: Data: 0.14MB + Index: 0.00MB + Engine InnoDB<br>wp_snippets: Data: 0.05MB + Index: 0.03MB + Engine InnoDB<br>wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_term_relationships: Data: 0.23MB + Index: 0.17MB + Engine InnoDB<br>wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_tm_taskmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_tm_tasks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_toolkit_gtmetrix: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_usermeta: Data: 1.52MB + Index: 1.72MB + Engine InnoDB<br>wp_users: Data: 0.13MB + Index: 0.14MB + Engine InnoDB<br>wp_wc_admin_notes: Data: 0.11MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_admin_note_actions: Data: 0.08MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_customer_lookup: Data: 0.09MB + Index: 0.08MB + Engine InnoDB<br>wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_product_lookup: Data: 0.19MB + Index: 0.19MB + Engine InnoDB<br>wp_wc_order_stats: Data: 0.17MB + Index: 0.16MB + Engine InnoDB<br>wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_meta_lookup: Data: 0.13MB + Index: 0.36MB + Engine InnoDB<br>wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wpmailsmtp_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wpr_rocket_cache: Data: 0.06MB + Index: 0.08MB + Engine InnoDB<br>wp_wpr_rucss_used_css: Data: 0.02MB + Index: 0.09MB + Engine InnoDB<br>wp_wp_phpmyadmin_extension__errors_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB Post Type Counts _pods_pod: 1<br>ajde_events: 6<br>attachment: 130<br>custom_css: 1<br>customize_changeset: 7<br>def_reg_fields: 10<br>ele-check-template: 1<br>elementor_font: 1<br>elementor_library: 59<br>epta: 1<br>event_magic_tickets: 1<br>gfw_report: 33<br>kt_font: 14<br>lc_partial: 1<br>mec_calendars: 18<br>mec_designer: 3<br>mec_esb: 4<br>mec_form: 1<br>mec_invoice: 1200<br>mec-books: 1251<br>mec-events: 16<br>nav_menu_item: 60<br>newsletter: 11<br>option-tree: 1<br>page: 25<br>post: 1<br>product: 1034<br>revision: 130<br>shop_order: 1247<br>shop_order_refund: 96<br>tablepress_table: 1<br>ticket-meta-fieldset: 1<br>wc_order_status: 7<br>wp_global_styles: 1<br>wp_log: 117<br>wp_template: 2<br>wpea_import_history: 1 Security Secure connection (HTTPS): ?<br>Hide errors from visitors: ? Active Plugins (40) Mailster - Email Newsletter Plugin for WordPress (Premium): by EverPress – 3.3.12<br>TablePress: by Tobias B?thge – 2.2.4<br>Better Search Replace: by WP Engine – 1.4.4<br>Classic Editor: by WordPress Contributors – 1.6.3<br>Code Snippets: by Code Snippets Pro – 3.6.2<br>Complianz | GDPR/CCPA Cookie Consent: by Really Simple Plugins – 6.5.6<br>Maspik - Spam blacklist: by yonifre – 0.10.5<br>Disable Cart Fragments: by Optimocha – 2.3<br>Duplicate Menu: by Jonathan Christopher – 0.2.2<br>Duplicate Page: by mndpsingh287 – 4.5.3<br>Elementor Pro: by Elementor.com – 3.18.2<br>Elementor: by Elementor.com – 3.18.3<br>GTmetrix for WordPress: by GTmetrix – 0.4.8<br>Integrate Elementor Form with Mailster: by Fernando A. Perrella – 1.2.1<br>Kadence WooCommerce Email Designer: by Kadence WP – 1.5.12<br>Mailster AmazonSES Integration: by EverPress – 2.13.0<br>Mailster for WooCommerce: by EverPress – 1.7.1<br>mame TWINT for WooCommerce: by mame software development hüttig – 3.3.1<br>Manage Notification E-mails: by Virgial Berveling – 1.8.6<br>Elementor Shortcode Builder for MEC: by Webnus – 1.8.1<br>Elementor Shortcode Designer: by Webnus – 1.3.1<br>Elementor Single Builder for MEC: by Webnus – 1.9.6<br>WooCommerce Integration for MEC: by Webnus – 2.1.2<br>Modern Events Calendar: by Webnus – 7.5.0<br>Perfmatters: by forgemedia – 2.1.4<br>Object Cache Pro: by Rhubarb Group – 1.20.0<br>Search Exclude: by QuadLayers – 2.0.7<br>Rank Math SEO: by Rank Math – 1.0.210<br>Zeige das ?nderungsdatum in den Admin-Listen an: by Apasionados.es – 1.4<br>User Role Editor: by Vladimir Garagulya – 4.64.1<br>WC Multiple Email Recipients: by Con Schneider – 1.4.1<br>WooCommerce: by Automattic – 8.4.0<br>Asset CleanUp Pro: Page Speed Booster: by Gabe Livan – 1.2.4.6<br>WP Crontrol: by John Blackbourn & crontributors – 1.16.1<br>WP-DBManager: by Lester 'GaMerZ' Chan – 2.80.9<br>Export WordPress Menus: by Tyche Softwares – 1.2<br>WP phpMyAdmin: by Puvox.software – 5.2.1.02<br>WP Rocket: by WP Media – 3.15.4<br>WP-Sweep: by Lester 'GaMerZ' Chan – 1.1.8<br>Sequential Order Numbers for WooCommerce: by WebToffee – 1.5.8 Inactive Plugins (5) Mailchimp Importer for Mailster: by EverPress – 2.0<br>Mailster Gmail Integration: by EverPress – 1.3.1<br>MEC Advanced Reports: by Webnus – 1.0.9<br>MEC Ticket and Invoice: by Webnus – 3.0.0<br>Query Monitor: by John Blackbourn – 3.15.0 Dropin Plugins (2) advanced-cache.php: advanced-cache.php<br>object-cache.php: Object Cache Pro (Drop-in) Must Use Plugins (1) Asset CleanUp Pro: Plugin Filtering: by Gabriel Livan – 1.0 Settings API Enabled: –<br>Force SSL: –<br>Currency: CHF (CHF)<br>Currency Position: right<br>Thousand Separator: '<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5) Connected to Woo.com: –<br>Enforce Approved Product Download Directories: –<br>HPOS feature screen enabled: –<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: – WC Pages Shop base: #7 - /kap-events/<br>Cart: #8 - /warenkorb/<br>Checkout: #224229 - /checkout/<br>My account: #12 - /mein-konto/<br>Terms and conditions: #226357 - /agb-allgemeine-geschaftsbedingungen/ Theme Name: Kadence<br>Version: 1.1.50<br>Author URL: https://www.kadencewp.com/<br>Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme<br>WooCommerce Support: ? Templates Overrides: – Admin Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>navigation<br>onboarding<br>onboarding-tasks<br>product-variation-management<br>product-virtual-downloadable<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page Disabled Features: customize-store<br>minified-js<br>new-product-management-experience<br>product-external-affiliate<br>settings<br>async-product-editor-category-field Daily Cron: ? Next scheduled: 2024-01-12 16:45:35 +01:00<br>Options: ?<br>Notes: 195<br>Onboarding: completed Action Scheduler Complete: 291<br>Oldest: 2023-12-12 21:31:59 +0100<br>Newest: 2024-01-12 11:21:58 +0100 Failed: 271<br>Oldest: 2022-09-24 11:36:34 +0200<br>Newest: 2024-01-09 18:01:11 +0100 Pending: 2<br>Oldest: 2024-01-12 13:35:27 +0100<br>Newest: 2024-01-12 13:35:27 +0100 Status report information Generated at: 2024-01-12 11:30:46 +01:00<br>`
Forum: Plugins
In reply to: [WooCommerce] Loading Woo only on specific pages – some unexpected bugsHi Pepe
Thanks for chiming in. While this is rather a bug report, here’s a measurement from today on a highly optimized site with object cache and page cache in place.
wp profile hook –all –orderby=time –spotlight
With Woocommerce loaded on the front page:
total callback | time | query_time | query_count | cache_ratio
total (55) | 2.0337s | 0.0204s | 10 | 86.36%
Without Woocommerce loaded on the front page:
total callback | time | query_time | query_count | cache_ratio
total (31) | 0.893s | 0.0084s | 7 | 84.35%
Roughly 250% percent faster.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Google Maps via Modern Events CalendarThanks Jarno, this is the case, indeed. Once again, the culprit is Modern Events Calendar.