-
AuthorPosts
-
March 3, 2018 at 2:18 am #920609
Hello,
I am having trouble with the latest update on Woocommerce installs. After update, clicking on any products or the shop results in a 502 or 520 response code. It’s happened on multiple sites.
Latest WordPress running on WPEngine (which uses NGINX) in a development environment. It occurred in a production environment too so is a problem with both WPEngine caching and without.
To test, I deactivated all plugins except Woocommerce and updated to 4.2.5 and the had the issue. Both with Woocommerce 3.3.1 & 3.3.3.
I have setup a staging site pre upgrade to Enfold 4.2.5 and pre Woocommerce update with credentials in the private content.
Thank you
March 3, 2018 at 3:34 pm #920821Hey Keith,
The 502 is a server error refering to Bad Gateway, WP Engine explains they have a 60-second timeout for processes
First I’d like to ask if you have your production site up and running again, perhaps with a restore?
Then do you want us to try to update your staging site to see and try to debug the error? If so do you have a backup of the staging site?
Wanted to ensure we understood your request first.Best regards,
MikeMarch 3, 2018 at 5:40 pm #920862I have the same issue with the last theme update. When I switch back to the woocommerce default theme is works fine. it must be an issue with Enfold and woocommerce. This only occurs when I click on any single product page. All the other page are fine.
My Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.Apache/2.4.10 (Debian) Server at mydomain.com Port 80
March 3, 2018 at 6:38 pm #920873Hi,
I believe that I have found a related issue of updating Enfold from v4.2.3 to v4.2.5 via FTP.
We are rewriting the elements and changing the structure in the /avia-shortcodes/ folder, and when you update via FTP some of the older files are being left in the folder at: /wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/
The solution is to delete the /avia-shortcodes/ folder via FTP and re-upload from the new v4.2.5 theme.
Please try this.Best regards,
MikeMarch 3, 2018 at 6:46 pm #920875Should I simply delete the current Enfold and re-upload it?
March 3, 2018 at 6:55 pm #920877Mike, sorry I didn’t mention the state of live / staging. I set up the staging site for you to use in case you couldn’t reproduce on your end. You can do whatever you need in there and I can restore to the current state if you need. Live is working perfectly with the older version of Enfold.
March 3, 2018 at 6:56 pm #920878I just removed the theme and re-uploaded them via FTP and that dis not solve the problem. Could it be something else?
March 3, 2018 at 7:22 pm #920883Hi,
@Keith thank you for updating,
@dhuet Please open a new thread so we can assist, we will want communicate in the Private Content area, for your admin login so we can take a closer look. But as this is not your thread you will not see what we write, nor will your info be private. Thanks for your patience and understanding.Best regards,
MikeMarch 3, 2018 at 7:28 pm #920884Thanks, Mike. I am doing that right now.
March 3, 2018 at 10:04 pm #920907Same problem on my 2 websites. Only occurs when I click on any single product page and other pages are fine.
The website that is hosted on siteground gives 504 error and the other that is hosted on wpengine gives 502 error.
Impossible to load any product pages on both websites.
On wpengine hosted site we updated on staging, the live site still using 4.2.4 is running fine.March 3, 2018 at 10:29 pm #920910Hi,
@Keith I found that it is giving the 502 error on v4.2.5 but not on v4.2.4
You had v4.2.3 on the staging site.
I also updated woocommerce to 3.3.3
Yet on my localhost Enfold v4.2.5 & woo v3.3.3 work good (PHP v7.0, 7.1, 7.2 windows)
so this is odd. can you please add a dropbox link to the error logs for this afternoon? They would be too big to post here.
I’m going to research it more to find the difference between the versions, and hopefully the logs will point to the issue.Best regards,
MikeMarch 4, 2018 at 8:47 pm #921144Hi,
I tried enabling the wordpress debug log, but is not logging the error, so when you get a chance seeing the server error log could help.Best regards,
MikeMarch 4, 2018 at 9:01 pm #921147Hi Mike,
I worked with WPEngine support and they say they have a script that stops the process at 60 seconds, likely before an error. Here is their response after running a trace:
That trace output I got actually does indicate the issue- it looks like there are a ton of database queries that are trying to run when a product page is loaded. The trace I ran was run on a product loading request, and that’s showing that there’s a single database query running 1179 times when the page gets loaded. The full output of the trace I ran (with the output parsed) can be found in the following text file:
It looks like those queries may be getting run by either the WooCommerce plugin itself, or the “enfold” theme, as the top files making the query requests were files from that plugin and theme.
So no errors are being reported because the kill script. I’ve had this problem in both live (cached) and staging (not cached), could it be something to do with WPEngine nginx configuration?
March 4, 2018 at 9:35 pm #921179Hi,
Perhaps with the number of products times the number of terms for the shop page it is going over the 60sec mark.
I just tested going directly to one of your product pages and there was no issue there.
Then I tested setting your Product Count 5 from 15 and the shop page loaded.
Please try.Best regards,
MikeMarch 4, 2018 at 9:57 pm #921208The shop page loads but I can’t get to any individual product page on the staging site. I know WPEngine said 60 seconds but but it really only takes 20-30 seconds to get the 502 error.
You were able to get to a single product page in staging? I’ve tried a number of times with no luck.
March 5, 2018 at 11:32 am #921421March 5, 2018 at 2:34 pm #921490Hi Keith, hallo Mike,
I’m sorry to write here in this thread, but I have the same problem with whoocommerce after the update to the new enfold version 4.2.5.
After the issue I installed Enfold v4.2.4, but the productpage is not loading.I look forward to see a hint what can I do.
Thanks and best regards
AndreasMarch 5, 2018 at 2:58 pm #921503Same issue here after updating to 4.2.5. Everything else has not been touched, so it must be the theme.
Edit: Reverting back to 4.2.4 fixed the issue.
- This reply was modified 6 years, 9 months ago by mchbeck.
March 5, 2018 at 3:34 pm #921515@mchbeck
Yep, it works now with 4.2.4.
ThanksMarch 5, 2018 at 6:49 pm #921684Hi Mike, yesterday you had rolled Enfold back to 4.2.4 and I upgraded later in the day, when you got to the product page was it on that version or 4.2.5? What are our next steps, it seems like more people are having trouble with 4.2.5. Thanks!
March 5, 2018 at 9:19 pm #921807Hi,
If you are using an older version that php 7, there might be a small issue with the installation.
If not – then everything should be OK.Best regards,
BasilisMarch 5, 2018 at 9:59 pm #921841Dear Kriesi support,
It would be nice if you could finally take this issue with 4.2.5 update seriously and sort out the problem. There have been many people reporting the exact same problem with product pages not loading after doing the update and you keep diverting the fault to everything else instead of admitting that 4.2.5 update has an error that needs to be fixed.
The problem starts only after updating to 4.2.5, so it is not the server, it is not other plugins, it ‘s the Enfold update that is causing this problem.I really hope you will finally sort out this issue.
Thank you!
SinisaMarch 5, 2018 at 10:21 pm #921861I also have this problem. I updated theme on staging site – and it has woo product time out error. Luckily I kept live site at previous enfold version.
I contacted SiteGround and they looked and isolated it to Enfold theme also.
I have a different ticket opened but wanted to show this is not an isolated problem and since it’s not opening product pages that is a problem for us who rely on ecommerce sites.
Thank you for looking into this for all of us.March 6, 2018 at 3:24 am #921981Hi,
Opps, wrong thread, this was not intended for the woocommerce issue, but perhaps it is worth a try…The Dev Team found that for some, the new generated files cannot be read. As a temporary workaround we have this filter to supress minification and disable the merge. Please try adding this to your functions.php:
add_filter('avf_merge_assets', function() { return 'none'; });
Best regards,
MikeMarch 7, 2018 at 9:13 am #922799I’m afraid this does not fix the issue. Updating to 4.2.6 doesn’t fix the issue either.
March 7, 2018 at 11:01 am #922840Hey @mchbeck and @pathaug it’s the same story here too (Siteground also isolate the issue to Enfold, like others are reporting)
I am a LIVE site and 4.2.4, 4.2.5 and 4.2.6 break the site in more ways than just Woo (separate threads already opened). I am now testing all Enfold updates on a staging site as a precaution.
This is a very serious issue for people with businesses that rely on their websites for income. Please @mike will you post back to us today on what Kreisi is doing? We appreciate your help and support but this is getting ridiculous now and I’m getting disillusioned with Enfold after 4 years of being loyal.
You can’t mess with people’s livelihoods like this.FYI – the last code snippet doesn’t work.
Kind reagrds
EdMarch 7, 2018 at 11:11 pm #923432I must say that I am very negatively surprised by a slow motion of Kriesi support. The thread I started regarding the woocommerce issue on my 2 websites is deadly quiet. The support responded once in a last 4 days telling me to contact my hosting provider, and that’s it.
I really hope you will sort out this issue soon as this kind of support is far away from professional.
Best wishes,
SinisaMarch 8, 2018 at 4:56 am #923535Hi!
Thank you for the update. We may have found the cause of the issue. Please upgrade to the latest version of the theme 4.2.6 and then modify the config-templatebuilder > aviashortcodes > product_snippet_button.php file. Look for this code around line 101.
ob_start(); //wc_clear_notices(); /** * hooked by: add_action( 'woocommerce_single_product_summary', 'woocommerce_template_single_add_to_cart', 30 ); */ //do_action( 'woocommerce_single_product_summary' ); $output .= ob_get_clean();
Replace the “woocommerce_single_product_summary” hook with the wc_get_template function temporarily.
ob_start(); wc_clear_notices(); wc_get_template( 'single-product/add-to-cart/' . $product->get_type() . '.php' ); $output .= ob_get_clean();
Regards,
IsmaelMarch 8, 2018 at 11:21 am #923750Thanks @Ismael
That works for me!
Kind regards
EdMarch 8, 2018 at 12:37 pm #923834Hi Ed,
Glad we got it working for you! :)
If you need further assistance please let us know.
Best regards,
Victoria -
AuthorPosts
- You must be logged in to reply to this topic.