I added the debug = true code and it didn’t show any changes other than the original error shown in the screenshot.
to show the error, an item needs to be in the basket and then go to checkout (shows the error shown in the original screenshot)
on another note, when installing WooCommerce from the Pro/Overview page in wp-admin, it installs 3.2.6 rather than the ‘approved’ 3.1.1
Oh, and I logged in to the ftp using the exact details provided, so I have no idea why that didn’t work for you
Hello There,
I was able to logged in and set the debug mode and other error logging settings. I can see the 503 error in the check out page as well. Nothing is appearing in the error logs as well. I did a little research more about 503 errors and it may have came from your server. Please check this out: https://www.lifewire.com/503-service-unavailable-explained-2622940
I would recommend that you contact your hosting provider as well. I am sure they can easily tell why the server keeps on resulting to an error 503 in your check out page.
Please let us know how it goes.
I have already been speaking to the host before I logged the call to you.
All I have received from Cloudways is that it appears to be related to the theme (which doesn’t makes sense as I have exactly the same set up on other websites on the same server)
the 503 only happens on the checkout page, not on any other so it does not appear to be a resources issues
Hello There,
We have tested WooCommerce and the theme in our local tester servers. None of the testing servers is returning the error 503. We have several hundreds of theme users running WooCommerce as well yet this is the only case we have seen that a 503 error. Could you please create a staging site so that we can test for a different environment?
To know how to create a staging area, please check out these articles:
Thank you in advance.
Hi,
The version you have access to is a staging area, I have a duplicate which I continue to develop on (which also shows the same problem.
a few updates:
I deleted and reinstalled woocommerce plugin, problem still exists
I deleted and reinstalled the Pro theme, problem still exists
the hosting company support tell me it is a theme issue as the problem doesn’t exist when using a different theme
feel free to make whatever changes you require to the site linked in this post as I have a duplicate version of this install
Thank you for your help
Scot
Hi there,
If you check Admin > Woocommerce > Status, you’ll find this line
MySQL version: 5.5.58 - We recommend a minimum MySQL version of 5.6. See: WordPress requirements
Please make sure you followed the recommended versions first.
I also enabled debug logging and looks like it’s not generated, perhaps your host disabled it? It’s the only way we could see what’s happening internally. Plus, this issue could be due to the combination of 3, host, theme, and Woocoomerce. When the checkout shortcode is added to a different page, it works okay, assigning it triggers the same issue. Could you try contacting them why it’s not generating a debug log?
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false );
Thanks!
Thank you Rad,
for me to upgrade MySQL it would require updating the server with over 20 wordpress (x & pro themes) on it. All of the other sites are working perfectly (on the same server and on the same versions)
I am all for updating the 5.6, but not just before the holidays! plus all the other sites suggest that the issue is not the MySQL version
Update:
Turning off the Terms & Conditions page in WooCommerce Checkout Settings, removes the 503 crash
the Terms & conditions page is a standard pro/cornerstone page with a header & text. any ideas why this would cause the issue?
Further update:
if the Terms & Conditions page referenced in the WooCommerce Checkout settings is a Cornerstone or Pro pagebuilder page, it crashes with a 503 error.
if the Terms & Conditions page is a standard wordpress page, it all works wonderfully
is this fixable? as I would like to use the pagebuilder for the terms & conditions
Hi there,
I see, thanks for sharing. But what was the terms & condition page? Please note that editing Woocommerce pages in the cornerstone, or adding cornerstone content within Woocommerce shortcodes (woocommerce checkout is a shortcode) could cause internal error and loops.
Thanks!
Hi Rad, not sure if you saw the very latest update (as they pretty much happened at the same time)
the Terms & Conditions page I had had a V2 headline and a text element with about 20 lorem ipsum paragraphs
nothing complicated and no shortcodes
Hi there,
They are all shortcodes, the checkout uses [woocommerce_checkout], the v2 elements uses shortcodes too. They are just automatically generated once you build your page. Plus, v2 elements are only available from where it’s created, embedding it on another page will not work so please use classic element. And the woocommerce shortcodes has complex process in it.
Thanks!
Good to know that V2 elements will not work on an embedded page. I will try recreating the page with classic elements.
By ‘no shortcodes’, I meant none that I had added manually but I take your point that shortcodes are everywhere
Thank you for your help
Hi there,
Yes, you didn’t add them. Wordpress created them and the builder too. Hence, don’t mix the two 
Thanks!
There are a bunch of problems with WooCommerce 3.2.x and this theme. It’s been ongoing for 3 months now. I asked support to update the templates back when 3.2.0 came out and was told you guys like to wait a little bit (3 months now). We’re 6 release since then and I’m still running 3.1 with the Pro theme. I can’t believe you’re selling a theme that installs WooCommerce 3.2.6 by default but not supporting the new woo commerce templates in the latest point release. Email notifications and downloads are all messed up.
Hey @moebis,
Are you using custom WooCommerce templates and functions? If so, please remove all of them and give us details of the issues you’re experiencing because we need to know if X / Pro is causing the issues. Please also remove all third party plugins. If that could not be done in your live site, please copy your site over to a staging server and test there.
The version compatibility list is currently not up to date. We’re sorry about that.
If that doesn’t help, please open a separate thread and give us WP Admin and FTP access to your staging site in a Secure Note. Also post a link to this thread for reference.
Thanks.
Are you saying that the latest woo commerce now works with the latest pro theme? I already had a thread open and along with all of the other compatibility issues, the one that really bothered me was the email templates (the default ones) would be missing formatting and download links in the receipts. We already confirmed this. I didn’t change anything, nothing customized in the WooCommerce templates. I was told by your support staff that your team hasn’t had time to update the customized X / Pro templates for woocommerce 3.2.x yet, so I’m still sitting on woo commerce 3.1.x until this theme is updated.
Just to give you my experience…
I have 4 sites running either x or pro that have the latest Woocommerce and are functioning fine
Thanks for sharing @scotbaston
@moebis, would you mind providing the thread about Woocommerce issues related to emails? I’ll check it and forward some follow up if needed. Or are you using 3rd party addons for Woocommerce? Because Pro and X theme integration with Woocommerce is just shop template related. Emails templates and processing are internal to Woocommerce.
Thanks!
@scotbaston do your email notifications from Woocommerce include download links?
@Rad X and Pro do have customizations within the theme (look inside the /pro/woocommerce directory) it’s filled with customized templates for woo commerce. Also why would you be recommending to everyone to stick to WooCommerce 3.1.x if there were no compatibility issues? Here is the thread: https://theme.co/apex/forum/t/outdated-copies-of-some-woocommerce-template-files/11546