Plugin Author
wpsoul
(@wpsoul)
403 means that you have security plugin or server settings which blocks any kind of database savings from REST API
You need to check security plugin and whitelist blocked request
@palovk
Hello,
I am facing the same issue (can’t save Blockpress / Greenshift preset).
I am in contact with my hosting support (infomaniak).
Let me know if you found a solution.
I’ll update this ticket if I found one.
Best,
Thread Starter
palovk
(@palovk)
@guygentil
I don’t have a solution yet. My hosting company claims that it is not blocked by them. I put a clean installation on the subdomain (the same server settings) and it works there. We are looking for the problem further.
@palovk
Thanks foe the feedback.
I’ve received the same answer from my hosting (WP error => no error in Apache log)
I’ve provided them a admin account to let them investigate more.
I’ll post here the updates next week.
Plugin Author
wpsoul
(@wpsoul)
If it’s working on the same server, I recommend to start with security plugins on site where it’s not working. Also, ask hoster about max input vars option, maybe you need to increase it.
And logs must be error log of wordpress
Thread Starter
palovk
(@palovk)
@guygentil
Thank you. We have a heavily secured website, so it will probably be somewhere there . We tried to turn it off gradually, but it didn’t help. If you have a response, let me know.
Hello,
Sadly no good news, still have the problem :
– did some tests with hosting => Apache error log stayed empty
– WP debug log stayed empty too
– Verified file permissions
– Trashed htaccess & restored default permalinks
– Removed all plugins except Greenshift free plugin & changed theme (tested with 2019 & 2023)
I also tried the website in local environment => still had the issue
On clean install with blockpress + greenshift it is working.
Ngl, running out of ideas :s
Thread Starter
palovk
(@palovk)
The same, I’ve tried everything and it still doesn’t work.
Plugin Author
wpsoul
(@wpsoul)
Check Wp-config.php on your root folder of site. Does it have?
DISALLOW_FILE_EDIT
Thread Starter
palovk
(@palovk)
@wpsoul
Removing this entry helped. This is how it works.
Plugin Author
wpsoul
(@wpsoul)
It’s clear now. Not sure why this happened because we use WP file system and didn’t change files, plugin creates new css instead. Look like wordpress bug, we will check what we can do
Thread Starter
palovk
(@palovk)
@wpsoul
I still had a record ( define(‘FS_METHOD’, ‘direct’); ) that allows the current user to make changes, but that doesn’t help.
Thanks for help
-
This reply was modified 3 years, 4 months ago by
palovk.
Hello @wpsoul,
sorry for the late reply, was away 😉
It is indeed set to true :
//Disable File Edits
define(‘DISALLOW_FILE_EDIT’, true);
=> If i set it to false, it will work and i’ll be able to save global preset.
Explanation I could see :
– I use “All In One WP Security” and it has an debug option & option to remove database & htaccess settings when you delete the plugin (which i did when debugging), but maybe this plugin does not revert when deleting “define(‘DISALLOW_FILE_EDIT’, true)” (it might change it has a security measure)
I don’t know, can’t really think about other explanation, at least now I know how to fix it 🙂
Thanks,
Plugin Author
wpsoul
(@wpsoul)
Ok. Thank you. We will check if it’s possible to save css files somehow with disallowed option
