Error 500 internal server after updating WooCommerce to version 8.2

Hi @rafaelamador64

From what I understand, you’re experiencing an Error 500 internal server issue after updating WooCommerce to version 8.2. The error occurs when you’re using the Elementor page editor. You’ve tried a few troubleshooting steps such as checking the available memory for PHP and WP, changing the theme, deactivating all plugins except Elementor, and updating the plugin to version 8.2.1, but the problem persists. I appreciate the detailed information and your efforts to resolve the issue.

The Error 500 is a generic HTTP status code that means “internal server error”. It’s not specific to WooCommerce and could be caused by a number of factors. Since the error occurs when WooCommerce is activated, it’s possible that there might be a conflict with your theme or other plugins, or there might be an issue with the server configuration.

Here are a few steps you can take to resolve the issue:

1. Increase PHP Memory Limit: You’ve mentioned that your PHP and WP memory is at 512M. However, you might want to consider increasing the PHP memory limit to a higher value, such as 768M or 1024M, if your hosting provider allows it. You can do this via your hosting provider or by editing your wp-config.php file. Here’s a guide: ?? Increasing the WordPress Memory Limit.
2. Inspect the .htaccess file: Your .htaccess file in your WordPress installation could be corrupted. You can locate this file in the root directory of your WordPress installation. Try renaming it for a while to see if it fixes the problem. If it does, head to your WordPress admin dashboard, go to Settings > Permalinks, and simply click “Save Changes” to reset the .htaccess file.
3. Conflict Test: You’ve already done a partial conflict test. Now, try a full test by switching to a default WordPress theme (like Storefront) and deactivating all plugins except WooCommerce. If the problem is resolved, reactivate your theme and plugins one by one to pinpoint the conflict. Here’s a helpful guide on how to test for conflicts: ?? How to Test for Plugin and Theme Conflicts.
4. Turn on Debugging: Should the problem still be there, let’s try activating debugging in WordPress. This can help us pinpoint the issue. You can turn on debugging by adding these lines to your wp-config.php file:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

This will create a debug.log file in your wp-content directory, logging any PHP errors or notices. For a more detailed guide on enabling debugging in WordPress, you can visit this link: ?? Debugging in WordPress

If the issue continues after trying these steps, please share more details, like the exact error messages you see when debug mode is on. This will help us identify and solve the problem more effectively.

Also, we’d find it helpful if you could share your site’s System Status report. This will give us a better understanding of your site’s setup and help us pinpoint the problem. You can find it via WooCommerce > Status. Select Get system report and then Copy for support.

Lastly, could you share the fatal error logs (if any) under WooCommerce > Status > Logs.

Once you’ve gathered this information, please paste it inside a Code block in your reply, or use https://pastebin.com to paste it and share the link with us.

Thanks for your patience and cooperation in this matter! We’re here to help you get this sorted.

Hello @bisratlearn, thanks for your response

I already tried recommendations 1 and 2 without results, specifically for 1 I increased the memory sizes to 1024M in PHP (by the way, I am using 8.1.24) and in wp-config.php (WP_MEMORY_LIMIT=1024M & WP_MAX_MEMORY_LIMIT=2048M ), this did not solve the problem

Regarding the .htaccess file, I even deleted it completely (keeping a backup, of course!!) to create a new one the way you suggest without results

Although I also changed the theme (to Hello Elementor) without results, I am going to try it following your recommendations and what is indicated in the article you point out

I have not tried recommendation 4, I will report the results if I have to follow this recommendation, as well as the rest of the information you need

It should be noted that I am doing all these tests on a test site, which is a similar (but not identical) copy of my production site, trusting that the solution I find here will be applicable to production.

If necessary, I will create a staging site to repeat all the tests in the most productive environment possible.

Thank you again for your attention and patience.

Greetings

UPDATE, conflict test

Before doing further testing, I captured the error message as it appears when I use the Elementor page editor, as shown below (2023-10-17 at 11:52:10)

Following your recommendations, I deactivated all plugins except Elementor, Elementor Pro and WooCommerce, and changed the active theme to Storefront, but the problem continued, as shown below (2023-10-17 at 14:06:43)

Due to the above results, I also disabled WooCommerce to observe the result, as shown (2023-10-17 at 14:08:29)

When using the Elementor page editor on the same page as the previous tests, the following result is obtained (2023-10-17 at 14:09:26) where it is observed that the error was corrected

Just for completeness, I activated the WooCommerce plugin again, as shown (2023-10-17 at 14:10:52)

With the expected result (2023-10-17 at 14:11:35)

Since solution recommendations 1 to 3 have not worked, I will have to try alternative 4 by activating debugging in WordPress and collecting the information obtained in this regard.

I will maintain the same conditions on my test server, with the Storefront theme and only the Elementor, Elementor Pro and WooCommerce plugins active, with all others disabled

Unfortunately I am not very skilled in these technical aspects (not to say ignorant), so it will take me some time to collect and provide all the information

Thanks again for your support and patience

Hello again @bisratlearn:

I’m sorry, but I reached my limit trying to follow your instructions, and without achieving results or obtaining any information.

I explain

I had no problems adding the lines of code to the wp-config.php file, along with other lines I already had previously, as you can see (2023-10-18 at 1:05:29)

The result was identical to the previous ones, the error message is the same (2023-10-18 at 1:11:25), although it is assumed that the WP_DEBUG=true option is activated

The worst thing is that no debug.log file is generated in the server’s wp-content folder, as seen in the image (2023-10-18 at 1:13:07), nor in any other directory. from the computer (I have other servers and a similar file appears nowhere else)

As requested, I share the site’s System Status report, hoping it will be useful to you

`
### WordPress Environment ###

WordPress address (URL): https://test.gceo.mx
Site address (URL): https://test.gceo.mx
WC Version: 8.2.1
REST API Version: ? 8.2.1
WC Blocks Version: ? 11.1.2
Action Scheduler Version: ? 3.6.3
Log Directory Writable: ?
WP Version: 6.3.2
WP Multisite: –
WP Memory Limit: 2 GB
WP Debug Mode: ?
WP Cron: ?
Language: es_ES
External object cache: –

### Server Environment ###

Server Info: Apache
PHP Version: 8.1.24
PHP Post Max Size: 128 MB
PHP Time Limit: 300
PHP Max Input Vars: 5000
cURL Version: 7.61.1
OpenSSL/1.1.1k

SUHOSIN Installed: –
MySQL Version: 8.0.34
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.2.1
WC Database Prefix: wp_
Tama?o total de la base de datos: 40.45MB
Tama?o de los datos de la base de datos: 34.87MB
Tama?o del índice de la base de datos: 5.58MB
wp_woocommerce_sessions: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_api_keys: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_attribute_taxonomies: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_downloadable_product_permissions: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_woocommerce_order_items: Datos: 0.08MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_order_itemmeta: Datos: 0.27MB + índice: 0.33MB + Motor InnoDB
wp_woocommerce_tax_rates: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_woocommerce_tax_rate_locations: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_shipping_zones: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_woocommerce_shipping_zone_locations: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_shipping_zone_methods: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_woocommerce_payment_tokens: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_woocommerce_payment_tokenmeta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_woocommerce_log: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_actions: Datos: 0.06MB + índice: 0.13MB + Motor InnoDB
wp_actionscheduler_claims: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_groups: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_actionscheduler_logs: Datos: 0.05MB + índice: 0.03MB + Motor InnoDB
wp_berocket_termmeta: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_blc_filters: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_blc_instances: Datos: 0.01MB + índice: 0.00MB + Motor MyISAM
wp_blc_links: Datos: 0.06MB + índice: 0.01MB + Motor MyISAM
wp_blc_synch: Datos: 0.02MB + índice: 0.02MB + Motor MyISAM
wp_bp_cohort_info: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_commentmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_comments: Datos: 0.15MB + índice: 0.07MB + Motor MyISAM
wp_e_events: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_e_notes: Datos: 0.02MB + índice: 0.17MB + Motor InnoDB
wp_e_notes_users_relations: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_e_submissions: Datos: 0.02MB + índice: 0.27MB + Motor InnoDB
wp_e_submissions_actions_log: Datos: 0.02MB + índice: 0.11MB + Motor InnoDB
wp_e_submissions_values: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_email_customizer_plus_templates: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_gp_oauth_users: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_imagify_files: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_imagify_folders: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_ju_queue: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_links: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_mailpoet_automation_run_logs: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_automation_run_subjects: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_automation_runs: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_automation_triggers: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_automation_versions: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_automations: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_custom_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_dynamic_segment_filters: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_feature_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_forms: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_log: Datos: 0.11MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_mapping_to_external_entities: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_migrations: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_links: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_newsletter_option: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_option_fields: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_posts: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_segment: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_newsletter_templates: Datos: 2.52MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_newsletters: Datos: 0.13MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_scheduled_task_subscribers: Datos: 1.52MB + índice: 0.30MB + Motor InnoDB
wp_mailpoet_scheduled_tasks: Datos: 0.25MB + índice: 0.23MB + Motor InnoDB
wp_mailpoet_segments: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_sending_queues: Datos: 0.16MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_settings: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_statistics_bounces: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_mailpoet_statistics_clicks: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_statistics_forms: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_statistics_newsletters: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_statistics_opens: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB
wp_mailpoet_statistics_unsubscribes: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_mailpoet_statistics_woocommerce_purchases: Datos: 0.02MB + índice: 0.08MB + Motor InnoDB
wp_mailpoet_stats_notifications: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_subscriber_custom_field: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_subscriber_ips: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_subscriber_segment: Datos: 0.05MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_subscriber_tag: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_mailpoet_subscribers: Datos: 0.06MB + índice: 0.23MB + Motor InnoDB
wp_mailpoet_tags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_user_agents: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_mailpoet_user_flags: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_moodle_enrollment: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_options: Datos: 3.48MB + índice: 0.09MB + Motor MyISAM
wp_postmeta: Datos: 2.43MB + índice: 0.57MB + Motor MyISAM
wp_posts: Datos: 0.40MB + índice: 0.08MB + Motor MyISAM
wp_term_relationships: Datos: 0.01MB + índice: 0.02MB + Motor MyISAM
wp_term_taxonomy: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wp_termmeta: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wp_terms: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wp_tm_taskmeta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_tm_tasks: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_usermeta: Datos: 0.08MB + índice: 0.04MB + Motor MyISAM
wp_users: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wp_wc_admin_note_actions: Datos: 0.08MB + índice: 0.02MB + Motor InnoDB
wp_wc_admin_notes: Datos: 0.08MB + índice: 0.00MB + Motor InnoDB
wp_wc_category_lookup: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wc_customer_lookup: Datos: 0.06MB + índice: 0.03MB + Motor InnoDB
wp_wc_download_log: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_order_addresses: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_wc_order_coupon_lookup: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_order_operational_data: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_order_product_lookup: Datos: 0.08MB + índice: 0.06MB + Motor InnoDB
wp_wc_order_stats: Datos: 0.06MB + índice: 0.05MB + Motor InnoDB
wp_wc_order_tax_lookup: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_orders: Datos: 0.02MB + índice: 0.11MB + Motor InnoDB
wp_wc_orders_meta: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wc_product_attributes_lookup: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_product_download_directories: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_product_meta_lookup: Datos: 0.02MB + índice: 0.09MB + Motor InnoDB
wp_wc_rate_limits: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_reserved_stock: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wc_tax_rate_classes: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wc_webhooks: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wfblockediplog: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wfblocks7: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_wfconfig: Datos: 1.28MB + índice: 0.00MB + Motor InnoDB
wp_wfcrawlers: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wffilechanges: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wffilemods: Datos: 12.55MB + índice: 0.00MB + Motor InnoDB
wp_wfhits: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_wfhoover: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wfissues: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_wfknownfilelist: Datos: 6.52MB + índice: 0.00MB + Motor InnoDB
wp_wflivetraffichuman: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wflocs: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wflogins: Datos: 0.02MB + índice: 0.03MB + Motor InnoDB
wp_wfls_2fa_secrets: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wfls_role_counts: Datos: 0.00MB + índice: 0.00MB + Motor MEMORY
wp_wfls_settings: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wfnotifications: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wfpendingissues: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_wfreversecache: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wfsecurityevents: Datos: 0.09MB + índice: 0.00MB + Motor InnoDB
wp_wfsnipcache: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_wfstatus: Datos: 0.14MB + índice: 0.09MB + Motor InnoDB
wp_wftrafficrates: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wfwaffailures: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_woo_moodle_course: Datos: 0.02MB + índice: 0.00MB + Motor InnoDB
wp_wpmf_s3_queue: Datos: 0.02MB + índice: 0.02MB + Motor InnoDB
wp_wpr_rucss_resources: Datos: 0.02MB + índice: 0.06MB + Motor InnoDB
wp_wpr_rucss_used_css: Datos: 0.02MB + índice: 0.05MB + Motor InnoDB
wp_yoast_indexable: Datos: 0.06MB + índice: 0.03MB + Motor MyISAM
wp_yoast_indexable_hierarchy: Datos: 0.01MB + índice: 0.02MB + Motor MyISAM
wp_yoast_migrations: Datos: 0.00MB + índice: 0.01MB + Motor MyISAM
wp_yoast_primary_term: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM
wp_yoast_prominent_words: Datos: 0.01MB + índice: 0.03MB + Motor MyISAM
wp_yoast_seo_links: Datos: 0.03MB + índice: 0.01MB + Motor MyISAM
wp_yoast_seo_meta: Datos: 0.00MB + índice: 0.00MB + Motor MyISAM

### Post Type Counts ###

acf-field: 12
acf-field-group: 2
attachment: 98
boletinesgceo: 3
br_labels: 20
catcursos: 38
customize_changeset: 2
custom_css: 1
eb_course: 1
elementor_library: 22
mailpoet_page: 1
nav_menu_item: 13
oembed_cache: 15
page: 19
post: 9
product: 16
product_variation: 48
revision: 25
shop_coupon: 4
shop_order: 290
shop_order_refund: 3
wapl: 10
wp_block: 1
wp_global_styles: 1

### Security ###

Secure connection (HTTPS): ?
Hide errors from visitors: ?

### Active Plugins (4) ###

Elementor Pro: por Elementor.com – 3.16.2
Elementor: por Elementor.com – 3.16.6
WooCommerce: por Automattic – 8.2.1
Wordfence Security: por Wordfence – 7.10.4

### Inactive Plugins (27) ###

Advanced Custom Fields: por WP Engine – 6.2.1
Broken Link Checker: por WPMU DEV – 2.2.2
Bulk Purchase and Group Registration: por WisdmLabs
India – 2.3.7

CAOS: por Daan from Daan.dev – 4.7.10
CURCY - WooCommerce Multi Currency Premium: por VillaTheme – 2.3.0
Custom Adobe Fonts (Typekit): por Brainstorm Force – 1.0.18
Custom Post Type UI: por WebDevStudios – 1.14.0
Edwiser Bridge - WordPress Moodle LMS Integration: por WisdmLabs – 3.0.1
Edwiser Bridge Single Sign On: por WisdmLabs – 1.4.4
Ele Custom Skin: por Dudaster.com – 3.1.7
Imagify: por Imagify – Optimize Images & Convert WebP – 2.1.2
Loco Translate: por Tim Whitlock – 2.6.6
MailPoet: por MailPoet – 4.32.0
MailPoet Premium: por MailPoet – 4.32.0
Selective Synchronization: por WisdmLabs – 2.1.2
Total Upkeep: por BoldGrid – 1.15.7
WooCommerce Advanced Product Labels: por BeRocket – 3.2.6.3
WooCommerce Integration: por WisdmLabs – 2.2.0
WooCommerce PayPal Payments: por WooCommerce – 2.3.1
WooCommerce Stripe Gateway: por WooCommerce – 7.6.1
WP Media folder: por Joomunited – 5.6.4
WP Media folder Addon: por Joomunited – 3.7.4
WP Rocket: por WP Media – 3.15.2
Yoast SEO: por Team Yoast – 21.4
Yoast SEO: News: por Team Yoast – 13.1
Yoast SEO: WooCommerce: por Team Yoast – 15.8
Yoast SEO Premium: por Team Yoast – 21.4

### Dropin Plugins (1) ###

advanced-cache.php: advanced-cache.php

### Settings ###

API Enabled: –
Force SSL: –
Currency: USD ($)
Currency Position: left
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 WooCommerce.com: ?
Enforce Approved Product Download Directories: –
HPOS feature screen enabled: –
HPOS feature enabled: –
Order datastore: WC_Order_Data_Store_CPT
HPOS data sync enabled: –

### WC Pages ###

Base de la tienda: #2752 - /pagina-de-inicio/tienda/
Carrito: #2753 - /pagina-de-inicio/tienda/carrito/
Finalizar compra: #2754 - /pagina-de-inicio/tienda/finalizar-compra/
Mi cuenta: #2755 - /pagina-de-inicio/tienda/mi-cuenta/
Términos y condiciones: ? Página sin definir

### Theme ###

Name: Storefront
Version: 4.5.3
Author URL: https://woocommerce.com/
Child Theme: ? – Si estás modificando WooCommerce en un tema padre que no has creado personalmente
te recomendamos utilizar un tema hijo. Ver: Cómo crear un tema hijo

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
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
settings
async-product-editor-category-field

Daily Cron: ? Next scheduled: 2023-10-18 21:53:20 -06:00
Options: ?
Notes: 187
Onboarding: completed

### Action Scheduler ###

Completo: 55
Oldest: 2023-09-17 21:30:50 -0600
Newest: 2023-10-18 01:08:16 -0600

Fallida: 16
Oldest: 2022-11-13 19:27:52 -0600
Newest: 2023-10-17 14:04:48 -0600

Pendiente: 1
Oldest: 2023-10-19 01:08:16 -0600
Newest: 2023-10-19 01:08:16 -0600


### Status report information ###

Generated at: 2023-10-18 01:09:22 -06:00
`

You will notice that the Wordfence plugin (version 7.10.4) is also active. this for security reasons and recommendation of the hosting provider

I couldn’t find any WooCommerce > Status > Logs folder or similar path where the fatal error logs would be located, so I’m assuming there aren’t any

It seems that the site can continue working despite the error indicated, so for now (and since I can’t go any further) I will be living with the error hoping that it continues working while an update appears to fix the problem

Thank you very much and I hope this information helps you in some way

Hi @rafaelamador64 ,

A 500 Internal Server Error typically points to a problem on the site’s server, although there can be various factors causing the error.

Can you check for any server-side errors, as these may be helpful in identifying the possible cause of the issue? Your host should be able to help you get these.

Following your recommendations, I deactivated all plugins except Elementor, Elementor Pro and WooCommerce, and changed the active theme to Storefront, but the problem continued, as shown below (2023-10-17 at 14:06:43)

Does this issue still occur while only WooCommerce core is activated on the site, and Elementor and Elementor Pro are?deactivated?

If deactivating Elementor and/or Elementor Pro resolves this issue, I’d suggest reaching out to Elementor plugin support for further help with this, since support related to third-party plugins/themes is outside?our scope of support.

Here is a direct link to Elementor’s dedicated support forum:

• Elementor Support Forum

On the other hand, if the issue is still present with ONLY WooCommerce core active, and the default Storefront theme, please let us know, we’ll be happy to dig into this further ??

Cheers!

Hi @beautyofcode, thanks for your response.

Since I uploaded my original post, an Elementor update came out (from version 3.16.5 to 3.16.6), but Elementor Pro is still on the same version (3.16.2). This didn’t solve the problem, it stayed exactly the same.

I tried what you suggested, but I can’t follow all of your instructions.

I checked with my hosting provider but no server errors were found.

I deactivated all the plugins, except Elementor, Elementor Pro and WooCommerce, using Storefront as the active theme. The problem still occurs when using the Elementor page editor.

I deactivated Elementor Pro, but left Elementor (the basic plugin) active; and the error still occurs when using the Elementor page editor.

By also deactivating Elementor (the base plugin), you can no longer use the Elementor page editor; which was to be expected. So it is not possible to check whether the error is fixed or not.

I tried to activate Elementor Pro only, leaving the basic Elementor plugin disabled, but this does not work and does not allow me to use the Elementor page editor; which was to be expected since Elementor Pro requires a basic Elementor plugin to work.

In short, it is not possible for me to carry out the tests as you suggest in your answer, since the error occurs exclusively when using the Elementor page editor. I clarify that this error is not observed when working in other sections / options of WordPress.

Greetings.

Hello @rafaelamador64,

I tried to activate Elementor Pro only, leaving the basic Elementor plugin disabled, but this does not work and does not allow me to use the Elementor page editor; which was to be expected since Elementor Pro requires a basic Elementor plugin to work.

Just to confirm, do you see the same error when trying to edit a page using the default Gutenberg block editor?

You can create a simple test page with the Gutenberg block editor if it’s not possible to use it to edit existing Elementor pages.

If you don’t see the error with Gutenberg, then the problem is most likely with Elementor as previously mentioned.

Surfing their GH issues, I can see a report that rhymes with what you’re describing, not sure if it’s related: https://github.com/elementor/elementor/issues/13499

I suggest you contact their team for further assistance.

Let us know if there’s anything we can assist with. :?)

Hi there,

We haven’t heard back from you in a while, I hope that you have managed to make some headway in getting this resolved!

I’m going to mark this as resolved, however, feel free to create a new topic if you need any further help.

Cheers!

buenas tengo el mismo error, lo resolviste?

Hola tomasweb1

<span style=”text-decoration: underline;”>Hello tomasweb1</span>

Desafortunadamente no fue posible resolver este problema. Después de seguir las diferentes recomendaciones de las respuestas anteriores la situación siguió igual.

<span style=”text-decoration: underline;”>Unfortunately it was not possible to resolve this issue. After following the different recommendations of the previous answers, the situation remained the same.</span>

La realidad es que este problema no ocasionaba verdaderos conflictos ni afectaba la productividad del servidor, así que decidí mantener la situación como estaba y seguir conviviendo con el problema. Esto es, asumir el riesgo.

<span style=”text-decoration: underline;”>The reality is that this problem did not cause real conflicts or affect the productivity of the server, so I decided to keep the situation as it was and continue living with the problem. That is, assuming the risk.</span>

Si bien agradezco la buena voluntad de quienes me dierón alguna orientación, la verdad es que no sirvió de nada y tal parecía que únicamente estaban tratando de se?alar que no era problema de WooCommerce (incluso algunas de las sujerencias me parecierón absurdas y fuera de contexto).

<span style=”text-decoration: underline;”>Although I appreciate the good will of those who gave me some guidance, the truth is that it was of no use and it seemed that they were only trying to point out that it was not a WooCommerce problem (some of the suggestions even seemed absurd and out of context to me) .</span>

En algún momento esto se resolvió, pero nunca supe como se resolvió ni cual fue la causa del error. Actualmente tengo instalado WordPress 6.5 con WooCommerce 8.7.0, Elementor 3.20.3 y Elementor Pro 3.20.2, y ya no se observa el problama con esta configuración.

<span style=”text-decoration: underline;”>At some point this was resolved, but I never knew how it was resolved or what caused the error. I currently have WordPress 6.5 installed with WooCommerce 8.7.0, Elementor 3.20.3 and Elementor Pro 3.20.2, and the problem is no longer observed with this configuration.</span>

Saludos

<span style=”text-decoration: underline;”>Greetings</span>

tengo esas mismas versiones pero me sigue dando error

Hi @tomasweb1,

I suggest that you start a new thread with your case, so that we don’t mix several troubleshooting sessions in one thread.

Even if the symptoms are the same, perhaps the underlying problem is different in your case.

IHi, have the same problem on a single store using Elementpr free/PRO + WooCommerce.
It doesn’t seem to come from Elementor because my other stores don’t get the 500 error on the product pages before re-saving the permalinks (which solves the problem).

The only notable difference is that the store where the problem occurs is in PHP 7.4, the others in PHP8.2 or 8.3.

Hi @momo-fr,

Sorry to hear that you are experiencing the same issue. However, to align with?forum best practices, please create a new topic so that we can address your issue(s) separately.

You can create a new thread here:?https://www.ads-software.com/support/plugin/woocommerce/#new-topic-0

Thanks for understanding!