- Edited
400: Bad Request
Hi sammyr ,
Thank you for all your useful information. It appears to be an missing parameter issue which should have been added in a normal situation. Do you have a demo environment available where I could login and test your case?
Also, I see in your screenshot that you're using WordPress 5.4.2, is that correct? And which PHP version are you using?
- Edited
Hello Jasper,
thanks for your feedback.
that you're using WordPress 5.4.2, is that correct?
yes.
And which PHP version are you using?
7.2.2
Do you have a demo environment available where I could login and test your case?
https://staging.senzera-skin.com/wp-login.php
Login information has been removed (we have the information available privately)
Best regards
Sammy.
- Edited
Hi sammyr ,
Thank you for the provided information! That was helpful and I see what is going wrong.
I think the plugin Redirect List
redirects an API endpoint. Currently we do use the endpoint POST /wp-json/buttonizer/buttons
to save the buttons. But it appears some plugin redirects the request to /wp-json/buttonizer/buttons/
and makes it a GET request instead (which will still work, but the request doesn't have the earlier provided data).
Could you try temporarely disabeling that plugin and try if it does save now?
Hello Jasper,
i have deactivate the "Redirect List" Plugin incl. some other ans removed also some htaccess entry, i get however the same issue with saving the settings in the buttonizer plugin.
Best regards
Sammy.
- Edited
Hello Jasper,
can i help you with any further information to solve this issue ?
Best,
Sammy.
- Edited
Hi sammyr ,
We are currently investigating this issue.
This other topic seems to be related but failing on a different request.
https://community.buttonizer.pro/d/437-blank-interface/5
Finding something in common with you two might help us a lot to find out what's causing the issue.
and removed also some htaccess entry
Are some files in your WordPress environment perhaps secured with a password?
If so, could you let us which files are protected?
We would like to reproduce the issue on our end.
Thanks in advance!
Hello James,
the FTP/WP data which i send you should give you access to all files & database through the UpdraftPlus Plugin. With that it should be possible to rebuild the site on another server.
Best regards
Sammy.
Hello,
could you find anything why this save function is not working ?
Best regards
Sammy.
Hi sammyr , apologies for the late reply, we've made several attempts to find out what's going on. Unfortunately we don't see any other notable plugins that are activated and could eventually redirect all URLs. It might be a sideeffect from a plugin.
That said, we have still one possible cause we haven't investigated yet. Are you able to share your .htaccess
file? That is the only file I cannot see with UpdraftPlus (as far as I know of).
Hello Jasper, of course: https://www.dropbox.com/s/4r6h5sd539pn5gl/htaccess.zip?dl=0
Best regards
Sammy.
- Best Answerset by James
Hi sammyr , thanks for sharing the .htaccess
file! That's it! I wish I had asked this earlier.
In your htaccess
you have the following code:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteCond %{REQUEST_URI} /+[^\.]+$
RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L]
</IfModule>
This code redirects all request which don't end with a /
. For example, site.com/some-title
redirects to site.com/some-title/
. These redirects are also happening for the WordPress REST API, which should never happen as these request should have kept intact. Buttonizer and many other plugins are using this WordPress API and don't expect the request to be redirected.
Can you replace the code above to:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
RewriteCond %{REQUEST_URI} /+[^\.]+$
RewriteCond %{REQUEST_URI} !^/(wp-json)
RewriteRule ^(.+[^/])$ %{REQUEST_URI}/ [R=301,L]
</IfModule>
As you see I've added RewriteCond %{REQUEST_URI} !^/(wp-json)
to the code, this means that the redirect of site.com/some-title
still works, but the WordPress REST API, site.com/wp-json
is not affected.
I am wondering, why do you have this code in the .htaccess
in the first place, is it because of the https
redirect? WordPress should automatically redirect posts and pages to their correct URL if they are misspelled or are missing the slash as far as I know.
Let me know if this was the solution!
Hello Jasper,
sorry i send you the .htaccess file from the wrong domain (staging.senzera.com). can you please re-evaluate if this redirection issue also relates to this htaccess file from (staging.senzera-skin.com) ? Thank you very much!
Hello Jasper,
that's it. thank you for your support.
Best regards
Sammy.