since your last update, we always get the error message “Cheatin’ uh?” displayed, when you want to save or publish an article. The url just goes to /wp-admin/post.php and shows this message. Nothing like this happens, when your plugin is deactivated. Haven’t found anything on this on the web, do you have an idea, what causes this problem? Hoped on a fast new update, but nothing happened the last days, so hope to get an answer here.
Thanks, Maik
]]>Ist das Problem bekannt? Woher kommt der Fehler? Wie kann ich das verhindern?
Gru?, Max
]]>I’m logged in as admin on my hosted WP site. I have the Impreza theme. If I try to change themes, I get that ultimately helpful “Cheatin’ uh?” message.
What’s up? I’m admin, I should be able to get to that page.
TIA!
PS I’m kind of new to wordpress, so I might be doing (probably am) something wrong.
]]>Just started using this plugin and it is great, particularly for overzealous clients. One issue for me is the “Cheatin’ uh? Sorry, you are not allowed to access this site” message is a bit off for my more corporate clients and I would like to replace it. I have found the wording in the code and tried creating a top level Adminimize folder to customise files but this seems not to be an option. Any suggestions how to replace with my own message? Or is it already in the Adminimize Setting page and I missed it?
Tanks
David Townsend
]]>Despite this issue appearing to be fixed some some ago it occurred for me for the first time just a few days ago.
I was providing Yoast SEO Premium support via a tech user account access to my site.
What I do lately when requiring support is use a dedicated support user account. This user has a subscriber status.
I then use iThemes security pro to escalate the privileges to administrator for X amount of time.
This way the site is reasonably safe if I happen to forget about access being granted without having to have this user set up with two factor and the like, simplifying access for the purpose of support.
When Yoast support tried to access the sites customiser area they got the warning page Cheatin’ uh?
So I tried to access the customiser from the tech support account and I saw the issue every time I tried too also.
So I changed my theme to twenty sixteen and the same thing happened so its not theme related.
Then I tried setting the tech support user account to administrator in the usual WordPress manner without going through iThemes user privilege escalation and the issue stopped occurring.
Now while this could potentially be an iThemes security plugin issue they seem to think its a WordPress bug.
The main purpose of this post is to establish what is causing it (iThemes security or WordPress) so the appropriate people can address the issue and fix it.
Hopefully it doesn’t take to long for someone WordPress support related to recreate this issue and advise either way.
Then I can either wait for WordPress dev to fix this problem in a future minor release and or so that I can inform iThemes it’s their plugin.
Thanks
]]>