Support » Requests and Feedback » Error messages built into WordPress
Error messages built into WordPress
-
I recently discovered the ‘Cheatin’ uh?’ error message. I then searched my WordPress files for ‘wp_die’ which precedes these messages.
Another discovery “Slow down cowboy, no need to check for new mails so often!”
There is obviously an attempt a humor here. But, as more and more businesses want to use WordPress for their sites, I would suggest these kinds of lines be changed to something less ‘cute’. I have to go thru and change them manually. And, when I upgrade, I assume they will all be back.
I find ‘Cheatin’ uh?’ to be snarky, and not at all helpful to the user.
I did a search and so far have found that text in:
options.php
custom-header.php
customize.php
edit-comments.php
edit-tags.php
edit.php
media-upload.php
nav-menus.php
plugins.php
post-new.php
press-this.php
themes.php
user-new.php
users.php
widgets.php
bookmark.php
site-themes.php
site-users.php
themes.php
admin.phpWordPress, and the team of people who work on it are amazing. I am so grateful that we have this fantastic platform. It allows us who use it to be creative and build great websites. And, I suggest we keep the humor (or not) on the front end!
I hope this can be changed in upcoming versions.
Thank you,
Nancy
-
We’re a little snarky by nature here 🙂 There’s a lot of humor on the backend, and that error message really is a backend ‘You’re trying to look at source code directly via your browser.’
Hi Mike,
Thanks for the response. I actually got the message on a test site of mine. I was logged in as a non-admin user. I am using two plugins to manage user access: S2Member and User Role Editor.
I clicked on a link that was not available to me under my privilege level and the Cheatin Uh message popped up.
So, your saying it should never be shown on the front end?
Thank you,
NancyI was logged in as a non-admin user.
So you’re in the backend.
- The topic ‘Error messages built into WordPress’ is closed to new replies.