I can confirm this, but this is also with administrators. After the update, I cannot save any posts/page/custom posttype… Always get the message above. I have to roll back to version 0.9.9 🙁
Hi everyone.
Thanks for starting this thread off, as we weren’t aware of this issue. We’ll be taking a look at it today (although there’s no timeline for anything right now) and will keep you up-to-date with the investigation.
For now, the workaround is to roll back to the previous release of the plugin.
Hi @coding4tacos, @have-a-byte,
Can you please confirm your WP version? And whether you are using the classic editor or block editor?
I can see a logic bug, and it seems it will trigger with the following conditions:
- Classic Editor is active (not Block Editor)
- A post status transition occurs (saving draft, publishing, etc.)
$_POST['_wpnonce'] is not empty
@garyj I can confirm Classic Editor and post transition in combination are triggering the error on my site. Not sure about the third part – too technical for me!
Thank you. I have a fix being tested, and I’m looking for more potential Classic Editor-related issues. My aim is to get a 0.10.1 release out later today. I’ll reply here when that’s happened.
I was having the same error as mentioned above. I just updated to 10.1 and instead of a single line the browser now returns the following when updating a post. I am using classic editor.
{“status”:”error”,”message”:”Cheatin’ uh?”}<!DOCTYPE html> <html lang=”en-US”> <head> <meta http-equiv=”Content-Type” content=”text/html; charset=UTF-8″ /> <meta name=”viewport” content=”width=device-width, initial-scale=1.0″> <meta name=’robots’ content=’max-image-preview:large, noindex, follow’ /> <title>WordPress › Error</title> <style type=”text/css”> html { background: #f1f1f1; } body { background: #fff; border: 1px solid #ccd0d4; color: #444; font-family: -apple-system, BlinkMacSystemFont, “Segoe UI”, Roboto, Oxygen-Sans, Ubuntu, Cantarell, “Helvetica Neue”, sans-serif; margin: 2em auto; padding: 1em 2em; max-width: 700px; -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, .04); box-shadow: 0 1px 1px rgba(0, 0, 0, .04); } h1 { border-bottom: 1px solid #dadada; clear: both; color: #666; font-size: 24px; margin: 30px 0 0 0; padding: 0; padding-bottom: 7px; } #error-page { margin-top: 50px; } #error-page p, #error-page .wp-die-message { font-size: 14px; line-height: 1.5; margin: 25px 0 20px; } #error-page code { font-family: Consolas, Monaco, monospace; } ul li { margin-bottom: 10px; font-size: 14px ; } a { color: #2271b1; } a:hover, a:active { color: #135e96; } a:focus { color: #043959; box-shadow: 0 0 0 2px #2271b1; outline: 2px solid transparent; } .button { background: #f3f5f6; border: 1px solid #016087; color: #016087; display: inline-block; text-decoration: none; font-size: 13px; line-height: 2; height: 28px; margin: 0; padding: 0 10px 1px; cursor: pointer; -webkit-border-radius: 3px; -webkit-appearance: none; border-radius: 3px; white-space: nowrap; -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; vertical-align: top; } .button.button-large { line-height: 2.30769231; min-height: 32px; padding: 0 12px; } .button:hover, .button:focus { background: #f1f1f1; } .button:focus { background: #f3f5f6; border-color: #007cba; -webkit-box-shadow: 0 0 0 1px #007cba; box-shadow: 0 0 0 1px #007cba; color: #016087; outline: 2px solid transparent; outline-offset: 0; } .button:active { background: #f3f5f6; border-color: #7e8993; -webkit-box-shadow: none; box-shadow: none; } </style> </head> <body id=”error-page”> <div class=”wp-die-message”></div></body> </html>
That HTML is what I saw when I was reproducing the original issue. A cache-clear / force-refresh of the admin page fixed it.
However, I just re-ran the scenario, and yes, it seems that 0.10.1 also fails, as you’ve documented (it’s to do with the revisions check this time). A 0.10.2 release it on it’s way. Thanks for reporting, @benham-design !
@garyj Seems to be working fine for me now – thank you! I’ll try not to break it again doing anything else…
Here the plugin is update to Version 0.10.2 and all caches are empty but still have those type of messages:
{“status”:”error”,”message”:”Cheatin’ uh?”}
For example, here I only try to change an order of statut.
If you could do something it would be nice.
-
This reply was modified 4 months, 1 week ago by
Thomas. Reason: Version 0.10.2
Hi @domtom123,
Thanks for following up. The fix in 0.10.2 addressed a specific issue in the notifications module — it’s possible you’re experiencing a different problem.
To help diagnose, could you clarify a few things?
- Where exactly are you seeing this error? “Changing the order of statuses” sounds like the drag-and-drop reordering on the Edit Flow → Custom Status settings page. Is that correct? (That page is only accessible to Administrators, not Editors.)
- What’s the exact error message? The {“status”:”error”,”message”:”Cheatin’ uh?”} response suggests a nonce verification failure. Are you seeing this in a popup, or in your browser’s Network tab?
- How long has the page been open before the error occurs? WordPress nonces expire after 12-24 hours, so if the page has been open for a while, that could cause this.
- Are you using any caching plugins? Object caching or page caching can sometimes cause stale nonces to be served. If you’re comfortable with browser developer tools, the Network tab showing the failed AJAX request and its response would be really helpful. We’re preparing a 0.10.3 release with additional fixes, but I’d like to understand your specific issue to ensure it’s addressed.
