Hi there,
Thank you for reaching out!
The issue you’re describing, where the WordPress REST API returns a “400 Bad Request” error, could be caused by a conflict with a plugin or theme on your site.
To troubleshoot further, could you please deactivate all plugins except WooCommerce and see if that resolves the issue? For more details on how to run a conflict test, you can refer to this article:
How to Test for Conflicts
In the meantime, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:
- System Status Report which you can find via WooCommerce > Status > Get system report > Copy for support.
- Fatal error logs (if any) under WooCommerce > Status > Logs.
Once we have more information, we’ll be able to assist you further.
Thread Starter
Flyter
(@flyter)
Hey @shahzeenfarooq,
The first time I tested, the problem only disappeared when I disabled woocommerce, but I did it in LocalWP. This time that you asked I tried to replicate it even more and created a staging website, and even after disabling every plugin including woocommerce and switch to 25 theme the error still ocurred.
Now I am not sure if this woocommerce related or not.
-
This reply was modified 1 year, 5 months ago by
Flyter.
Hi @flyter,
Thank you for sharing these details!
Since the issue persists even after disabling all plugins, including WooCommerce, and switching to a default theme like Twenty Twenty-Five. This suggests the problem might not be directly tied to WooCommerce.
Regarding the endpoint:
https://example.com/wp-json/wp/v2/types/post?context=edit
Please note that example.com is a placeholder domain and will return a 404 error because it’s not an actual site. To test your REST API, use your actual domain name instead.
For example https://yourwebsite.com/wp-json/wp/v2/types/post?context=edit
To troubleshoot further, please try refreshing your permalinks:
• Go to Settings > Permalinks in your WordPress dashboard.
• Click Save Changes (no need to modify anything).
This often resolves unexpected REST API issues. Let me know how it goes!
Thread Starter
Flyter
(@flyter)
Hey @mahfuzurwp ,
I ended up figuring it out, it was wordfence causing the issue. I just didnt realize it because I was dumb and forgot to clear out cache so wordpress was showing me the issue was still there.
