?wc-ajax=update_order_review 403 (Forbidden) Error on Checkout Page

Hi @jesusmabass,

Thank you for the detailed report.

?However, the drawback of this approach is that the custom fields I’m trying to add don’t appear (why is this happening? It occurs with all “checkout fields editor” plugins I’ve tried).

The custom checkout field edit plugins may not work with the checkout block if they’re not compatible with it, going with the shortcode version would be the safe way to go.

If I edit the page and use the [woocommerce_checkout] shortcode, or if I edit the page through Elementor and use the specific widget for the WooCommerce page, the custom fields I’m adding do appear. However, the checkout page gets stuck loading in the “Order Summary” section. When I check my browser console, I see the error: ?wc-ajax=update_order_review 403 (Forbidden).

However, as I understand from this paragraph, when you’re using the shortcode version of the checkout page, you do see your edits, however you get the 403 error, correct? Now, if you disable the checkout edit plugin your checkout works properly?

I see you’re currently using WooCommerce Checkout Manager: por QuadLayers – 7.5.2. Since the 403 issue appears to be related to the checkout edits you’re making, have you reached out to their support to ask about this? Alternatively, have you tried with other checkout editor plugins while using the shortcode checkout page, and see if the 403 issue persists?

Finally, do you find anything in your WooCommerce > Status > Logs?

Thanks!
-OP

Hi @omarfpg,

Thank you for your response.

Regarding your point:

The custom checkout field edit plugins may not work with the checkout block if they’re not compatible with it, going with the shortcode version would be the safe way to go.

The custom checkout field works with both the shortcode and the Elementor widget (in these two cases, I get the 403 error), but not with the automatically created WooCommerce checkout page (why is this happening?; in this case, there is no 403 error).

However, as I understand from this paragraph, when you’re using the shortcode version of the checkout page, you do see your edits, however you get the 403 error, correct? Now, if you disable the checkout edit plugin your checkout works properly?

Yes, that’s correct. If I use the shortcode version, I see the custom fields, but I get the 403 error. If I disable the checkout edit plugin, the custom fields disappear (logically), but the 403 error remains. This error occurs both in the shortcode version and in the Elementor widget version, even before installing any custom field plugins.

I see you’re currently using?WooCommerce Checkout Manager: por QuadLayers – 7.5.2. Since the 403 issue appears to be related to the checkout edits you’re making, have you reached out to?their support?to ask about this? Alternatively, have you tried with other checkout editor plugins while using the shortcode checkout page, and see if the 403 issue persists?

I have not contacted their support because this issue happens with all similar plugins, and the 403 error occurs even if I don’t have any installed. I understand this error is not caused by these plugins, right?

Finally, do you find anything in your WooCommerce > Status > Logs?

I don’t see anything unusual, I’m not sure. Could you check it? I provided the link in my first message.

Summary of my case:

I have two scenarios:

1. If I leave the automatically created WooCommerce checkout page, there is no 403 error on ?wc-ajax=update_order_review, but I can’t add custom fields (they don’t appear).
2. If I use the shortcode (both from Gutenberg and Elementor) or the Elementor checkout widget, the 403 error occurs on ?wc-ajax=update_order_review. However, the custom fields do appear.

If I disable the custom field plugins, the 403 error persists.

I just noticed something that might help. If I don’t select the checkout page in WooCommerce advanced settings, the page works correctly without the 403 error. Why is that?

Thank you so much, Omar. I hope to find a solution because I don’t know what else to do. I’m desperate.

Best regards, Jesús

Hello jesusmabass

Thank you for your reply.

The most effective approach to solve this problem would be to use the Checkout shortcode.
Most Checkout Manager plugins support this and are fully compatible with the shortcode.
Then disable all other plugins and switch to a default theme like Twenty Twenty-four.

If this is not feasible on the live site, you can create a staging site.
This will allow us to simplify things for a better troubleshooting process.

May I ask which Checkout Manger plugins have you tried so far?

Next, I would recommend reaching out to the Checkout Manager plugin support.
Even if they do not provide a complete solution, their insights might help resolve this issue.

I do not see any other recent reports regarding Checkout Manager plugins.
This indicates that this might be a site-specific issue that we can diagnose and resolve.

Looking forward to your response. ??

Best regards.

Por supuesto, aquí tienes la traducción de tu respuesta:

Hi Zubair,

Thank you for your response, @doublezed2.

The most effective approach to solve this problem would be to use the Checkout shortcode.
Most Checkout Manager plugins support this and are fully compatible with the shortcode.
Then disable all other plugins and switch to a default theme like Twenty Twenty-four.

Ok, I have activated the Twenty Twenty-four theme, deactivated all plugins, and created the checkout page only with the shortcode:

Result:

May I ask which Checkout Manager plugins have you tried so far?

• Checkout Field Manager (Checkout Manager) for WooCommerce by Quadlayers
• Checkout Field Editor (Checkout Manager) for WooCommerce by ThemeHigh
• Flexible Checkout Fields for WooCommerce – WooCommerce Checkout Manager by WP Desk
• WC – APG Campo NIF/CIF/NIE by Art Project Group

Next, I would recommend reaching out to the Checkout Manager plugin support.
Even if they do not provide a complete solution, their insights might help resolve this issue.

I believe this is not necessary when the 403 error occurs even without these plugins installed, right?

Thank you again.

Best regards.

At this point, I’d recommend testing with Checkout Field Editor, also, @jesusmabass .

Before even doing so, best to start a fresh site, with only a default theme like TT3, and the WooCommerce plugin active, to make sure Checkout is error-free. Then go ahead with the Checkout Field Editor plugin, building-up step-by-step.

At times, it is more time-effective to spin a fresh installation and migrate content over, when troubleshooting.

Keep in mind, if you want to try our products, you can leverage our 30-day refund policy. In a nutshell, it gives you 30 days to try it out, and if the product doesn’t work the way you need or you think another product would work better, we are more than happy to offer a full refund.?You’ll find the details of our refund policy here.

I hope this helps! Let us know how it goes.

Hi @anastas10s,

Thank you for your response.

I appreciate your suggestion to test with Checkout Field Editor and to start with a fresh site using a default theme like TT3 with only WooCommerce active.

However, I must reiterate that the 403 error occurs even without any “Checkout Field Editor” plugins installed. As detailed previously, the error is present with just WooCommerce and a default theme active.

The 403 error on ?wc-ajax=update_order_review happens even in a clean environment, without any additional plugins or customizations.

Here’s a recap of my situation:

1. Using the default WooCommerce checkout page, there is no 403 error, but custom fields do not appear.
2. Using the [woocommerce_checkout] shortcode or Elementor widget for checkout, the 403 error occurs, but custom fields do appear.
3. The 403 error persists even when no “Checkout Field Editor” plugins are installed.

Given this, it seems the issue is not related to these plugins. Could you please look into any other possible causes for this 403 error within WooCommerce itself?

Thank you again for your assistance.

Best regards,
Jesús

Hola Jesús, @jesusmabass

Thanks for the additional details. I agree there’s a problem specific with your site, and it should be troubleshooted.

Let’s continue as you were, with only WooCommerce and Twenty Twenty-four theme, using the shortcode based checkout pge (and defined in the page settings in WooCommerce, this is very interesting that it only fails when it’s properly set up).

Then, to learn more, please?enable WP Debug?and try the checkout again. Please share any error log found in?WooCommerce → Status → Logs?and inside the error log file generated on your server.

Looking forward to resolving this issue for you.

Thanks!
-OP

Hi Omar, @omarfpg

Thank you for your response and for trying to help.

Then, to learn more, please enable WP Debug and try the checkout again. Please share any error log found in WooCommerce → Status → Logs and inside the error log file generated on your server.

I deleted all WooCommerce log files before starting the tests again to ensure a clean test (I didn’t see any critical errors previously). Now, I have added products to the cart and gone to the checkout page, but the logs page remains empty (I suppose there are no errors):

In the WordPress debug.log file, I also don’t see anything noteworthy (only errors due to switching the theme to TT4):

What else can I try?

Thank you.

Best regards,
Jesús

Hola ??

Thank you for reaching back, with further details on this @jesusmabass .

I deleted all WooCommerce log files before starting the tests again to ensure a clean test (I didn’t see any critical errors previously).

+

The 403 error on ?wc-ajax=update_order_review happens even in a clean environment, without any additional plugins or customizations.

Just to clarify, clean/fresh installation means a newly created WooCommerce store, with no data migrated or other relation to the existing one (where the error appears). Moreover, with only the WooCommerce plugin installed and activated.

As I understand, from the recap shared here, while in step 1 everything is error-free. The issue begins when customizations to the Checkout page, or other plugins, are added in step 2.

Therefore, best to reach out to their respective support channels (of the plugins/functionality added in step 2), as they would be in a better position to assist you. This falls outside the scope of support at this forum, I’m afraid.

I trust this provides clarity. We’re happy to help, so please feel free to reach out to us again if you have any other questions.

• This reply was modified 4 months, 2 weeks ago by anastas10s. Reason: typo

Hi @anastas10s,

As I understand, from?the recap shared here, while in step 1 everything is error-free. The issue begins when customizations to the Checkout page, or other plugins, are added in step 2.

I apologize if I didn’t explain it clearly. The 403 error begins even without any plugins activated and with the TT3 or TT4 theme, as soon as I create the page and use the shortcode.

The only ways to avoid the 403 error are:

1. Using the default page that WooCommerce creates when it is installed or using the corresponding tool: WooCommerce -> Status -> Tools.
2. When the checkout page is not marked as such in the advanced options of WooCommerce, regardless of how I created it or the plugins I have installed.

What else can I try, please?

Thank you.

Best regards, Jesús

Hola Jesús, @jesusmabass

I apologize if I didn’t explain it clearly. The 403 error begins even without any plugins activated and with the TT3 or TT4 theme, as soon as I create the page and use the shortcode.

I believe the point my colleague is trying to make is that the modifications to the checkout process with multiple plugins may have broke something along the way maybe on the database level.

That’s why he’s suggesting a clean slate. Would you be able to set up a brand new site on your hosting and see if there are any issues with the checkout? If there are, then most likely it’s a problem with your hosting provider, rather than with WooCommerce or any third-party plugin.

On the other hand, if you don’t find any issues, we could determine the problem came somewhere along the checkout edits you were making. Did you have a chance to try the checkout before making any changes? Did it work properly before?

Please let us know.

Cheers!
-OP

Hi Omar, @omarfpg

Thank you for your response.

I will proceed to create a clean installation of WordPress and WooCommerce on my hosting. I will test the checkout process and let you know the results as soon as I have completed the test.

Thank you for your continued assistance.

Best regards,
Jesús

Hi @omarfpg, @doublezed2, and @anastas10s,

It seems that with the clean installation, the 403 error does not occur, so I would rule out hosting issues. I will rebuild the website from scratch, continuously testing to see if the problem reappears and what might be causing it. Please keep this thread open for a few more days until I can update you.

Thank you for all your help.

Hello @jesusmabass,

Thank you for your diligent troubleshooting and for keeping us updated on your progress. It’s great to hear that the clean installation didn’t reproduce the 403 error, which helps narrow down the possible causes.

Please take all the time you need to rebuild your website and test it thoroughly. We’ll keep this thread open and await your update. Feel free to share any new findings or questions you may have. We’re here to support you throughout this process.

We look forward to hearing back from you soon!

Hi there ?? ,

We haven’t heard from you in a while, so I’m going to mark this as resolved for now. Feel free to start a new thread or reply back if you have any more questions.

All the best,
Omar