Custompress Cheatin' Uh message

I've just set up a custom post type and created a few taxonomies. When I attempt to click on the taxonomy names on the admin left sidebar (under my custom post type) I am greeted with the "Cheatin' Uh?" message. I haven't had this issue anywhere else.

Here's the url where I receive the message:

Is there something I can do to give myself permission to veiw/edit these pages?
I am enjoying the plugin so far and thank you for your help!

  • Mason
    • DEV MAN’s Sidekick

    Hiya folks,

    We'll definitely want to take a look at this. Can you provide us with some further information such as what user role you're logged in with when seeing this message - what version of CustomPress and any other plugins you have running?

    Also, take a look at your server's error logs and let us know if anything turns up there. We'll definitely take a look at this.


  • allingtm
    • Site Builder, Child of Zeus

    Wordpress 3.1

    Other Plugins:

    BP Group Calendar 1.2.3
    Branded Login for Buddypress 1.1.2
    Buddypress 1.2.8
    BuddyPress Private Community 0.5
    CustomPress 1.1.1
    Recend Posts for Custom Post Type 1.0
    Remove WP Dashboard Widgets 1.0.3
    Signup TOS 1.2.1
    WPMU DEV Update Notifications 2.0.1

    Not sure how to look at the server logs - can't see any log files on server.

    Basically I upgraded Wordpress from 3.0.5 to 3.1 and upgraded buddypress from 1.2.7 to 1.2.8. then the "Cheatin' Uh?" message appears.

    I wanted to go live tomorrow, but I don't feel I can while I have this problem :slight_frown: So thanks for any help you can provide.

  • Mason
    • DEV MAN’s Sidekick

    Hiya allingtm,

    Ok, I've got an install running most of those plugins and am not able to reproduce this error.

    What user role are you seeing this error with? Is this a multisite install?

    Also, your server error log should be available by signing into cPanel (or similar). If you're unsure, contact your host provider and ask for the php error logs. They can assist.

    Otherwise, you could try deactivating each plugin to see if the error continues - but I'm thinking this isn't a conflict with plugins.


  • cmjnetwork
    • New Recruit

    I am running a single site install of Wordpress 3.1. and am using Custompress 1.1.1. When I try to access my error logs at GoDaddy I get a page not found error. I will look into this further.

    I use the following plugins:
    BM Custom Login
    Category Posts Widget
    Collapsing Categories
    Gravity Forms

    I've also installed Custompress to another site on a different server running 3.0 and it works fine. I plan to upgrade to 3.1 tonight and will keep you posted on the results.

  • allingtm
    • Site Builder, Child of Zeus

    I've looked the Analysis and Log files ::Error Log in cPanel, and there are no errors. I'm logging in with user in Administrator role. It is using standard Wordpress 3.1 rather than multi-site. Thanks for looking at this. I've disabled all the plugins and the same thing happens. I've created another taxonomy and I'm not getting the same issue, so it's only on the first one I created (which was originally working fine). Thanks for helping work out what's going on.

    I've now deleted it and recreated using a different name, and it's all working fine again. So I'm sorted, but I hope a solution to this is found in case it happens again.

  • cmjnetwork
    • New Recruit

    Ok, so previous to running Custompress I had 3 registered taxonomies. After I installed Custompress I deleted the old taxonomies from my functions.php. The names that where recreated gave me the problems. When I create a completely new name it works fine. Is there anything that I can do to allow myself to reuse the old names?

  • Mason
    • DEV MAN’s Sidekick

    Hiya cmjnetwork,

    That's a good question. Kudos on finding out exactly what the issue was as well!

    I'm not sure - short of removing it from the database. Do you have a lot of posts with this particular tag/type?

    I'll see if Ivan can respond directly. I know CustomPress cannot work with post types created through other means, but don't know if there's a way to work around that.


  • Ivan
    • The Incredible Code Injector

    Hi guys,

    So, yeah, as you have found the hard way you cannot have post_types/taxonomies with the same names created in different places. You can reuse old names if you remove them from where they were declared and add them through CustomPress only.

    For a later version we will add the ability to manage content types declared outside CustomPress.

  • cmjnetwork
    • New Recruit

    Thanks for the replies. I just have one more question. Right now it would mean a lot to me to keep my original taxonomy names since they are so specific. Luckily, my site is still in development and I am open to making some steps backwards in order to keep them.

    The problem is that I deleted the old taxonomies from functions.php when I first started and I still got the error. As a test, I reentered them into functions and now I don't get the message (although taxonomies are also appearing under posts). It doesn't matter if I delete them from Custompress and recreate, as long as its not declared in functions, I get a cheatin' message. Is this something that would need to be resolved in my database table?

    Thanks again

  • Ivan
    • The Incredible Code Injector

    There is a plugin_deactivate() function in "custompress/core/core.php" with which you can purge all plugin data. Just change the conditional statement to "true" and deactivate the plugin. Beware though this will remove all plugin, data - post_types, taxonomies, custom_fields, settings etc and not only for the root site.

    Also you can re-save your permalink structure after making changes to post_types so WP can update the rewrite rules. If you are doing this through CustomPress rewrite rules are flushed automatically.

    Try couple of things and get back to me whether the problem persists. If yes please share the declared in functions.php post_types.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.