5.7 "Access Denied" when creating Blog Entry
Permalink
All permissions are set correctly for the page and page type and the error is being triggered as the Super Admin of the site. When I try to add content in the content section, I get the Access Denied error. When I click out of the error box, it continues to pop-up multiple boxes.
This site is for a client of mine and upgrading is not an option right now. Any suggestions?
This site is for a client of mine and upgrading is not an option right now. Any suggestions?
Attached is the error that I am getting and also the errors in the console. Any suggestions are welcome. Thank you again!
Here are the errors
Interesting. I think I would have to debug this in real time. I might have sometime later today to do a screen share if that is cool with you. Let me know what you think.
Could this be an issue with 5.7.5.6 Composer using auto-save? If so, is there a way to disable it? And I am available till 5 pm EST. Thank you.
It could be a 5.7 permission issue. But I don't think its an auto save issue. I have to see it in real time. Here is a link to my Google Hangout. I will leave it up a little while. If you want to debug in real time we can just do a video call and screen share.
Thanks
Wayne
https://hangouts.google.com/call/3Vrrs-zI6FhPJ-kq3Oo8AEEE...
Thanks
Wayne
https://hangouts.google.com/call/3Vrrs-zI6FhPJ-kq3Oo8AEEE...
9/10 times I hit an issue like this where everything appears to be working fine for a site, but then a save of a particular bit of content triggers an error like this, the cause ends up being Mod Security on the server.
Mod Security can sometimes match with a keyword in your content, or a style of request, blocking the request. The blocked response sometimes return a 403, but I've also seen a 500 at times too.
The solution is to contact the host and ask them if:
- they are running Mod Security
- if so, can they check their logs for recent triggers (and if you can tell them the exact URL of the request that was blocked that can be handy)
- and, if they see a matching request, to whitelist the mod security rule that was triggered
Some cPanel setups allow you to turn on and off Mod Security completely, and if this option is available it's a good test to see if it's the problem, but it's not good practice to leave it off as it does help with general protection.
That's my guess!
Mod Security can sometimes match with a keyword in your content, or a style of request, blocking the request. The blocked response sometimes return a 403, but I've also seen a 500 at times too.
The solution is to contact the host and ask them if:
- they are running Mod Security
- if so, can they check their logs for recent triggers (and if you can tell them the exact URL of the request that was blocked that can be handy)
- and, if they see a matching request, to whitelist the mod security rule that was triggered
Some cPanel setups allow you to turn on and off Mod Security completely, and if this option is available it's a good test to see if it's the problem, but it's not good practice to leave it off as it does help with general protection.
That's my guess!
I would start with showing us what is the error you are getting. Then I would pull up Chrome developer tools and see what errors are in the console. Also I would check my PHP log for what errors are coming up. That should at least get you started.