• Resolved Vidyut

    (@vidyut)


    The checkout page has a greyed out “place order” area with spinners and no orders can be placed. Disabled all plugins except woocommerce. Tried all sorts of themes ranging from twenty ten to storefront and others meant for woocommerce. Disabled the overlays and clicked on Place order anyway, getting “Syntax error unexpected token error” but I don’t have any other plugins active nor do I have ANY payment gateways active other than Bank transfer information. This happens with or without force ssl, with or without wordpress HTTPS active. It happens with ONLY woocommerce active as well with no minify or anything whatsoever.

    https://www.ads-software.com/plugins/woocommerce/

Viewing 15 replies - 16 through 30 (of 32 total)
  • Thread Starter Vidyut

    (@vidyut)

    @mike
    Sorry about the review. It has been a frustrating few days. Will fix it as soon as I get this thing running.

    I have checked the nginx configuration too, switched it with another working configuration as well, same result. ?? All other plugins are working with both. Few other sites on server with same configuration also working. But it is a starting point. Will check again in a few hours, line by line.

    Plugin Contributor Mike Jolley

    (@mikejolley)

    I still think its the NGINX rewrite rules. We’ve seen it happen before. Turning off pretty permalinks will test my theory. Settings > permalinks.

    Plugin Contributor Mike Jolley

    (@mikejolley)

    You can also test by outputting say:

    <?php echo esc_html( $_GET['test'] ); ?>

    In your theme footer, then adding ?test=1 to the query string. If its not echo’d to the page, its being ignored by nginx.

    Plugin Contributor Mike Jolley

    (@mikejolley)

    Thread Starter Vidyut

    (@vidyut)

    @mike Not discounting your experience. It is the first concrete thing that seems possible. God knows all else has failed multiple times. Looking into this right now. Do you have a sample config to compare with that you recommend? I assume you are talking about the try_files line?

    Thread Starter Vidyut

    (@vidyut)

    Okay, so I rebooted on a lark before starting more fiddling and it has started working. No idea what fixed it.

    Much appreciation @mike. Apologies for the bad review. It was a shitty way of taking out my frustration. I am sorry.

    Thread Starter Vidyut

    (@vidyut)

    I will keep an eye to see that all is working as it should, but I think it is. This seems resolved to me. Will confirm in a couple of hours.

    Thread Starter Vidyut

    (@vidyut)

    For the record, result of further testing to identify what worked by switching the Nginx configs I’d tried, in case it helps anyone else.

    This is the “try_files” line recommended by Nginx on their configuration page.

    try_files $uri $uri/ /index.php;

    This does NOT work.

    This below is recommended by wordpress.

    try_files $uri $uri/ /index.php?args;

    Also does not work.

    What worked was:

    try_files $uri $uri/ /index.php?q=$request_uri;

    After I restarted the server, I was planning to troubleshoot further, when I got a notification of an order! By a real client ??

    Thank you @mike.

    Plugin Contributor Mike Jolley

    (@mikejolley)

    I found this post and it used the one WordPress recommends: https://aaronjholbrook.com/debugging-server-problems-step-by-step/

    Perhaps the issue was changing this file and forgetting to reboot so the changes take effect?

    Thread Starter Vidyut

    (@vidyut)

    It is possible, Mike. If it is important, I will happily confirm this by switching the lines again in a day or two. Least I can do, after knowing what I went through.

    Though I suspect you are right about the reboot. Everything just worked after the reboot. I didn’t even have to start testing the permalinks setup.

    Thread Starter Vidyut

    (@vidyut)

    arrrgh. It has stopped working again. I didn’t change anything :/ Trying the wordpress variation of “try_files” but that isn’t working either. Now what?

    Thread Starter Vidyut

    (@vidyut)

    Now I used
    try_files $uri $uri/ /index.php?q=$uri&$args;
    and it is working again, but worried if it stops again on whim :/

    Plugin Contributor Mike Jolley

    (@mikejolley)

    Might be worth asking the host now you know what’s causing it. It’s been a while since I configured an nginx box so it’s hard for me to say what would change that setting randomly.

    Anonymous User 14742457

    (@anonymized-14742457)

    Vidyut I had the same problems on nginx.

    I just reverted to older version, now I live without stress…

    Thread Starter Vidyut

    (@vidyut)

    @mike, it is a VPS. Alas, I cannot blame anyone but me for configurations. What I found strange was that it was working and stopped. Then worked again after a new (4th) configuration (and has continued to work so far). Maybe I will solve this mystery eventually on an idle day. I imagine it will help loads of people. Right now, snowed with work and not fixing what ain’t broke (so far, this time)

Viewing 15 replies - 16 through 30 (of 32 total)
  • The topic ‘Checkout page greyed out place order’ is closed to new replies.