Woocommerce error with Elementor
-
Dear all, I have a project in which Elementor is running as a page builder + WooCommerce to manage product registration, etc.
It turns out that when you leave the WooCommerce plugin active, you can no longer edit any page with Elementor, it doesn’t load the preview and therefore it becomes impossible to edit the blocks, information, etc.
See the error image below, when clicking on the debug link it returns the following message.
Warning: include(): Filename cannot be empty in /www/wwwroot/listademae.com.br/wp-content/plugins/woocommerce/includes/wc-template-functions.php on line 52 Warning: include(): Failed opening '' for inclusion (include_path='.:/usr/local/lsws/lsphp74/share/pear:/usr/local/lsws/lsphp74/share/php:/usr/share/pear:/usr/share/php') in /www/wwwroot/listademae.com.br/wp-content/plugins/woocommerce/includes/wc-template-functions.php on line 52 include(): Failed opening '' for inclusion (include_path='.:/usr/local/lsws/lsphp74/share/pear:/usr/local/lsws/lsphp74/share/php:/usr/share/pear:/usr/share/php')
PS: This only happens with the WooCommerce plugin active, when you deactivate it everything works again, that is, I can edit any page with Elementor again.
-
Hi @aquilamendes,
I haven’t been able to replicate this issue on a fresh copy of WordPress with Elementor and WooCommerce. Can you please share the necessary information below to investigate the issue further:
- System Status Report,?which you can find via WooCommerce > Status > Get system report > Copy for support. This will help us learn your system better, including your current theme, plugins, versions of everything, etc.
- Fatal error logs?(if any) under WooCommerce > Status > Logs.
You could copy and paste your reply here or paste it via?https://gist.github.com/?and send the link here.
Once we have more information, we’ll be able to assist you further.
This is what information I have on the paths I indicated.
If possible and necessary, I can create a temporary admin user to access the site to replicate the error that happens to me, please wait and thank you again.
` ### WordPress Environment ### WordPress address (URL): https://www.listademae.com.br Site address (URL): https://www.listademae.com.br WC Version: 8.6.1 REST API Version: ? 8.6.1 WC Blocks Version: ? 11.8.0-dev Action Scheduler Version: ? 3.7.1 Log Directory Writable: ? WP Version: 6.4.3 WP Multisite: – WP Memory Limit: 512 MB WP Debug Mode: – WP Cron: ? Language: pt_BR External object cache: – ### Server Environment ### Server Info: LiteSpeed PHP Version: 7.4.33 PHP Post Max Size: 128 MB PHP Time Limit: 300 PHP Max Input Vars: 1000 cURL Version: 7.29.0 NSS/3.53.1 SUHOSIN Installed: – MySQL Version: 5.6.50-log Max Upload Size: 128 MB Default Timezone is UTC: ? fsockopen/cURL: ? SoapClient: ? DOMDocument: ? GZip: ? Multibyte String: ? Remote Post: ? Remote Get: ? ### Database ### WC Database Version: 8.6.1 WC Database Prefix: wp_ Tamanho total do banco de dados: 20.30MB Tamanho dos dados do banco de dados: 17.36MB Tamanho do índice do banco de dado: 2.94MB wp_woocommerce_sessions: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_woocommerce_api_keys: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_woocommerce_attribute_taxonomies: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_woocommerce_downloadable_product_permissions: Dados: 0.02MB + índex: 0.06MB + mecanismo InnoDB wp_woocommerce_order_items: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_woocommerce_order_itemmeta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_woocommerce_tax_rates: Dados: 0.02MB + índex: 0.06MB + mecanismo InnoDB wp_woocommerce_tax_rate_locations: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_woocommerce_shipping_zones: Dados: 0.02MB + índex: 0.00MB + mecanismo InnoDB wp_woocommerce_shipping_zone_locations: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_woocommerce_shipping_zone_methods: Dados: 0.02MB + índex: 0.00MB + mecanismo InnoDB wp_woocommerce_payment_tokens: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_woocommerce_payment_tokenmeta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_woocommerce_log: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_actionscheduler_actions: Dados: 0.23MB + índex: 0.25MB + mecanismo InnoDB wp_actionscheduler_claims: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_actionscheduler_groups: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_actionscheduler_logs: Dados: 0.16MB + índex: 0.13MB + mecanismo InnoDB wp_commentmeta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_comments: Dados: 0.02MB + índex: 0.09MB + mecanismo InnoDB wp_e_events: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_e_notes: Dados: 0.02MB + índex: 0.17MB + mecanismo InnoDB wp_e_notes_users_relations: Dados: 0.02MB + índex: 0.05MB + mecanismo InnoDB wp_e_submissions: Dados: 0.02MB + índex: 0.27MB + mecanismo InnoDB wp_e_submissions_actions_log: Dados: 0.02MB + índex: 0.11MB + mecanismo InnoDB wp_e_submissions_values: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_links: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_options: Dados: 3.05MB + índex: 0.06MB + mecanismo InnoDB wp_postmeta: Dados: 10.27MB + índex: 0.25MB + mecanismo InnoDB wp_posts: Dados: 2.44MB + índex: 0.06MB + mecanismo InnoDB wp_sbi_feeds: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_sbi_feed_caches: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_sbi_instagram_feeds_posts: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_sbi_instagram_feed_locator: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_sbi_instagram_posts: Dados: 0.02MB + índex: 0.00MB + mecanismo InnoDB wp_sbi_sources: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_termmeta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_terms: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_term_relationships: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_term_taxonomy: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_usermeta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_users: Dados: 0.02MB + índex: 0.05MB + mecanismo InnoDB wp_wc_admin_notes: Dados: 0.06MB + índex: 0.00MB + mecanismo InnoDB wp_wc_admin_note_actions: Dados: 0.05MB + índex: 0.02MB + mecanismo InnoDB wp_wc_category_lookup: Dados: 0.02MB + índex: 0.00MB + mecanismo InnoDB wp_wc_customer_lookup: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_download_log: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_orders: Dados: 0.02MB + índex: 0.11MB + mecanismo InnoDB wp_wc_orders_meta: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_order_addresses: Dados: 0.02MB + índex: 0.06MB + mecanismo InnoDB wp_wc_order_coupon_lookup: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_order_operational_data: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_order_product_lookup: Dados: 0.02MB + índex: 0.06MB + mecanismo InnoDB wp_wc_order_stats: Dados: 0.02MB + índex: 0.05MB + mecanismo InnoDB wp_wc_order_tax_lookup: Dados: 0.02MB + índex: 0.03MB + mecanismo InnoDB wp_wc_product_attributes_lookup: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_wc_product_download_directories: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_wc_product_meta_lookup: Dados: 0.02MB + índex: 0.09MB + mecanismo InnoDB wp_wc_rate_limits: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_wc_reserved_stock: Dados: 0.02MB + índex: 0.00MB + mecanismo InnoDB wp_wc_tax_rate_classes: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB wp_wc_webhooks: Dados: 0.02MB + índex: 0.02MB + mecanismo InnoDB ### Post Type Counts ### attachment: 141 elementor_library: 17 envato_tk_import: 1 nav_menu_item: 6 page: 9 post: 4 product: 31 revision: 181 wp_navigation: 1 wp_template: 2 ### Security ### Secure connection (HTTPS): ? Hide errors from visitors: ? ### Active Plugins (12) ### Akismet Anti-spam: Spam Protection: por Automattic - Anti-spam Team – 5.3.1 Editor clássico: por Colaboradores do WordPress – 1.6.3 Widgets Clássicos: por Colaboradores do WordPress – 0.3 Elementor Pro: por Elementor.com – 3.19.3 Elementor: por Elementor.com – 3.19.4 Essential Addons for Elementor: por WPDeveloper – 5.9.10 Smash Balloon Instagram Feeds: por Smash Balloon – 6.2.9 Login Logo Editor: por AMP-MODE – 1.3.3 Premium Addons for Elementor: por Leap13 – 4.10.22 Template Kit Import: por Envato – 1.0.14 WooCommerce: por Automattic – 8.6.1 WP Rollback: por WP Rollback – 2.0.6 ### Inactive Plugins (3) ### WP Mail SMTP: por WP Mail SMTP – 4.0.1 WP Rocket: por WP Media – 3.9.2 WP Rocket | Remove All .htacces Rules: por WP Rocket Support Team – ### Settings ### API Enabled: – Force SSL: – Currency: BRL (R$) Currency Position: left_space Thousand Separator: . Decimal Separator: , Number of Decimals: 2 Taxonomies: Product Types: external (external) grouped (grouped) simple (simple) variable (variable) Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) exclude-from-search (exclude-from-search) featured (featured) outofstock (outofstock) rated-1 (rated-1) rated-2 (rated-2) rated-3 (rated-3) rated-4 (rated-4) rated-5 (rated-5) Connected to Woo.com: – Enforce Approved Product Download Directories: ? HPOS feature screen enabled: ? HPOS feature enabled: ? Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore HPOS data sync enabled: – ### WC Pages ### Base da loja: #16 - /produtos/ Carrinho: ? Página n?o definida Finaliza??o de compra: ? Página n?o definida Minha conta: ? Página n?o definida Termos e condi??es: ? Página n?o definida ### Theme ### Name: Hello Elementor Version: 3.0.1 Author URL: https://elementor.com/?utm_source=wp-themes&utm_campaign=author-uri&utm_medium=wp-dash Child Theme: ? – Recomendamos você utilizar um tema filho no caso de você estiver personalizando o WooCommerce em um tema ascendente. Veja como criar um tema filho WooCommerce Support: ? ### Templates ### Overrides: – ### Admin ### Enabled Features: activity-panels analytics product-block-editor coupons core-profiler customer-effort-score-tracks import-products-task experimental-fashion-sample-products shipping-smart-defaults shipping-setting-tour homescreen marketing mobile-app-banner navigation onboarding onboarding-tasks product-variation-management product-virtual-downloadable product-external-affiliate product-grouped product-linked remote-inbox-notifications remote-free-extensions payment-gateway-suggestions shipping-label-banner subscriptions store-alerts transient-notices woo-mobile-welcome wc-pay-promotion wc-pay-welcome-page Disabled Features: customize-store minified-js new-product-management-experience product-pre-publish-modal settings async-product-editor-category-field Daily Cron: ? Next scheduled: 2024-02-29 17:23:10 -03:00 Options: ? Notes: 67 Onboarding: skipped ### Action Scheduler ### Concluído: 651 Oldest: 2024-02-23 14:25:40 -0300 Newest: 2024-02-29 10:41:30 -0300 Pendente: 3 Oldest: 2024-02-29 13:03:34 -0300 Newest: 2024-03-01 10:38:41 -0300 Malsucedido: 6 Oldest: 2024-02-23 14:27:42 -0300 Newest: 2024-02-29 11:25:00 -0300 ### Status report information ### Generated at: 2024-02-29 14:49:04 -03:00 `
2024-02-29T14:12:50+00:00 Depura??o Automattic\WooCommerce\Internal\DataStores\Orders\DataSynchronizer::get_current_orders_pending_sync_count was called but no order types were registered: it may have been called too early. 2024-02-29T14:16:38+00:00 Depura??o Automattic\WooCommerce\Internal\DataStores\Orders\DataSynchronizer::get_current_orders_pending_sync_count was called but no order types were registered: it may have been called too early. 2024-02-29T14:22:47+00:00 Depura??o Automattic\WooCommerce\Internal\DataStores\Orders\DataSynchronizer::get_current_orders_pending_sync_count was called but no order types were registered: it may have been called too early. 2024-02-29T16:03:30+00:00 Depura??o Automattic\WooCommerce\Internal\DataStores\Orders\DataSynchronizer::get_current_orders_pending_sync_count was called but no order types were registered: it may have been called too early.
Hey there ??
Please?never?share (or offer to share) login credentials here. This is a public forum and for the best interest of your sites security, this should never be shared. Just to add, it can result in your account being banned, as seen in the?forum guidelines.
If I understand correctly, you’ve tested with just WooCommerce and Elementor active and still got the same result, correct?
?
Can you please let us know if you have also switched the theme to a default one like Storefront in this case?If the issue is still there please reach out to Elementor as a next step as, being the site builder, they should ensure that the builder works well with WooCommerce. Also, help related to third-party plugins is outside our scope of support.
You can reach out in their dedicated support forum here:
Hope this helps point you in the right direction ??
The idea is not to send it publicly (here) but in a secure way, I just said that I am open to this possibility to resolve it.
And to answer your question, yes! The problem persists in any theme (Store Front, any standard WordPress theme, etc.). The problem only occurs when WOOCOMMERCE is active, so we quickly ruled out a problem with Elementor. So there is no reason to blame or have to look for Elementor to solve a problem that is clearly related to the Woocommerce Plugin.
Active Woocommerce Plugin = PROBLEM
Woocommerce Plugin Disabled = NO PROBLEMHowdy!
Thanks for providing additional information ??
The problem only occurs when WOOCOMMERCE is active, so we quickly ruled out a problem with Elementor. So there is no reason to blame or have to look for Elementor to solve a problem that is clearly related to the Woocommerce Plugin.
Just to clarify – you are unable to edit any pages when only WooCommerce core is active, and Elementor is deactivated, correct?
If so, please can you share a clear screenshot of what you are seeing on your end when trying to edit a page while WooCommerce is active so that we can better understand what you are currently experiencing.
Additionally, please can you check the browser console on any page experiencing this issue and see if there are any errors being displayed there. Please share any errors with us here.
Also, you can read more about using your browser console to identify errors here.
Cheers!
Only Woocommerce is active without Elementor, I haven’t tested it but I imagine it no longer has the problem since the central point is precisely that both are active to work together (because I need it to be like that, otherwise it won’t make sense)
The error only occurs in the back-end, the site remains accessible to the end user and without presenting any errors (at least visually)
I already posted the error in question in the initial post, but I will do some more, including from the console, so you can have a broader view:
https://ibb.co/f1DKHDg
https://ibb.co/m0KfFrB
https://ibb.co/L0tNM9P
https://ibb.co/3rnf52WHey there
Thanks for sharing that!
Only Woocommerce is active without Elementor
Checking the console logs, it seems the issue is coming directly from Elementor:
If these console errors are while the Elementor plugin is active, please deactivate Elementor temporarily, and then share any console errors you may see there.
On the other hand, if these console logs are while the Elementor plugin is deactivated, please try logging out of WP Admin, clearing your browser cache and then logging back in and see if this makes any difference?
Cheers!
Without Elementor active, I have no way of trying to reproduce the error since you need both together, what should I do?
Regarding clearing cache, cookies, trying with an incognito tab, all of this has already been done and the error always repeats itself.
Hi @aquilamendes,
I’m noticing that you have other plugins that may alter the editing experience with Elementor.
It’d be best if you could run a conflict test to find out if something external is interfering. Since you’ve mentioned this happens with any theme, including Storefront or WordPress’ defaults, let’s move to plugins now.
?
You’ll want to deactivate all plugins except for WooCommerce and Elementor and take a look. If that fixes the problem, re-enable the other plugins one by one (gradually), checking after each to see where the issue is coming from.Some important considerations:?
— Be sure you have a good backup in place of your full site and database. You can ask your host for backup functionality, or you can consider using a service like?Jetpack. If something goes wrong, you will be able to restore it.
?
— Also, you can consider using a plugin like?Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it is helpful to disable plugins without affecting your current site visitors.
?
— It is important to consider staging functionality as well in case you would not like to touch your production site (you can ask your host if they offer this service), or you can use WP Staging to spin up a new test site quickly.
?
?
You can find more about this in this?guide.
?
Please let us know about your findings.I carried out all the tests suggested and the error remains, I did it with all plugins deactivated and I only activate the element and woocommerce and the same error is reproduced.
By deactivating woocommerce magically everything works perfectly again, I’m starting to want to give up, honestly.
Hello aquilamendes
Thank you for your reply.
This is an odd issue and I cannot reproduce it on my end by using Elementor + Elementor Pro plugins.
For further diagnosis, it would be helpful to get some feedback from Elementor support. It is possible that might provide valuable information that could help us resolve this issue.
Since this issue appears to be related to Template, could you please try deactivating only Elementor Pro and leave the Elementor (free version) active? Let me know about the results of this step.
I appreciate your continued patience and assure you that I am here for your assistance. ??
Best regards.
@doublezed2 Having also carried out this test, the problem persists. As stated numerous times, the problem can only be resolved by deactivating WOOCOMMERCE.
Hello aquilamendes
Thank you for your reply and for trying the troubleshooting steps.I have tried to recreate this issue on my web server and also on my localhost environment but there is no issue at all.
Since I cannot recreate this issue on both servers, it suggests that the problem might lie in the server environment.
To help you resolve this issue, I will recommend migrating your site to a localhost environment like LocalWP and see if the issue persists there.
Here is a guide for the quick import process from Live Server to LocalWP.As previously suggested, did you have a chance to contact Elementor Support for additional insights into the problem?
Rest assured I am here for you until this issue is resolved. ??
Best regards.
I Am having the same issue. I created a fresh install with only elementor en elementor pro and woowommerce.
When woocommerce is active, elementor theme builder does not open and gives a 403 error.
When I disable woocommerce, everything works again.
I manage to fix the problem. It has to do with a firewall rule on your server.
You need to go to your modsecurity section and add this rule to your firewall.
SecRuleRemoveById 218500
you can also add it to your .htaccess file like this:
Hope this helped you fix the issue
<ifmodule mod_security.c> SecRuleRemoveById 218500 </ifmodule>
- The topic ‘Woocommerce error with Elementor’ is closed to new replies.