Tagged: fatal error, woocommerce
-
AuthorPosts
-
December 12, 2022 at 6:39 pm #1375979
Hello dear Supporters,
after seven years using Enfold, we need to upgrade PHP to 8.0 or 8.1.
We use woocommerce and a child theme. After switching PHP to higher than 7.4, the site shows in front- and backend a fatal error and we have to to roll back to access the backend again.
I deleted the child theme´s function.php and disabled all plugins: it works well on PHP 8.0 and 8.1
Once I enable woocommerce and nothing else, it already shows the same error.
Theme is on 5.2.1
WP is on 6.1.1
Woocommerce is on 7.1.1
We are on a nginx environment.
Could you please help us, since PHP7.4 is running out, as you know, Thank you in advance.
GunnarDecember 12, 2022 at 8:18 pm #1375987Hi Gunnar,
Thanks for the login details. Could you share server error logs with us please? Also include admin WordPress login details in private.
Best regards,
RikardDecember 12, 2022 at 9:11 pm #1375995This reply has been marked as private.December 13, 2022 at 7:36 am #1376025Hi,
Thank you for the update.
Would you mind providing a screenshot of the errors instead? We don’t see any errors when we visited the site. Please use imgur, savvyify or dropbox for the screenshot. Thanks.
To save the errors in the log, you have to add this code in the wp-config.php file.
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false); @ini_set( 'display_errors', 0 ); // Use dev versions of core JS and CSS files (only needed if you are modifying these core files) define( 'SCRIPT_DEBUG', true );
Best regards,
IsmaelDecember 14, 2022 at 11:58 am #1376123Hi Ismael, thank you for your answer. I just uploaded screenshot of the
-last working setup of the server
-debug log file
You will see: first I deactivated all plugins and switched to PHP 8. There was a fatal error, because of the enfold-child function.php
Then I disabled enfold child and switched to PHP 8. The website works without problems.
Then I enabled woocommerce and the website went wrong again.Please tell me, if you´d need more information.
All best GunnarDecember 17, 2022 at 3:53 pm #1376472Hi Gunnar,
Sorry for the late reply. The problem seems to be coming from line 11 in your child theme, but I can’t see a way of accessing your child theme via the WordPress backend. Please check your code on that line, and include FTP login details in private if you should need further help from us.
Best regards,
RikardDecember 17, 2022 at 6:27 pm #1376492Hi Rikard,
I quote from my earlier posts:
-first I deactivated all plugins and switched to PHP 8. There was a fatal error, because of the enfold-child function.php
-Then I disabled enfold child and switched to PHP 8. The website works without problems.
-Then I enabled woocommerce and the website went wrong again.
So only with Enfold and woocommerce enabled, the website had the error. The child theme has not been involved (that might be another problem in line 11 of the child theme)The credentials for FTP I already sent some posts ago: here I send them again.
Thank you for your help and greetings GunnarDecember 17, 2022 at 7:31 pm #1376525Hi,
Thanks for the update. So how can we know in what state the error messages in the log are generated then? Maybe you could copy the site to a staging site, and update there first, so that we can see the actual problem? If not, then please only send us logs when the parent theme and WooCommerce are active.
Best regards,
RikardDecember 19, 2022 at 3:15 pm #1376730This reply has been marked as private.December 19, 2022 at 7:23 pm #1376770Hi,
Thanks for the update. The log in private doesn’t indicate any problems coming from the theme, it’s only referring to WooCommerce files. When that was logged, was WooCommerce the only active plugin? Did you modify any WooCommerce core files? You could try to reinstall WooCommerce, to see if that makes any difference.
Best regards,
Rikard -
AuthorPosts
- You must be logged in to reply to this topic.