Support » Plugin: Custom Content Type Manager » [Plugin: Custom Content Type Manager] Can't post

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor fireproofsocks


    Thanks for the heads-up. Could you provide your exact server specs? WordPress version, PHP version, MySQL version, and which operating system your server is running on?

    I’m trying to figure out how the WordPress plugin bug-tracker is supposed to work… it’s easier for me to monitor a bug-tracker than the forums, but I’ll try to get this patched as soon as possible.


    Since topic starter doesn’t respond anymore… I’m having the same issue, as I mentioned on your blog as well.

    My server:
    WiredTree Managed VPS
    cPanel running on CentOS
    Apache version 2.2.15
    PHP version 5.2.13
    MySQL version 5.1.51
    Architecture i686

    WP version 3.0.3
    Latest stable version of your plugin

    Still, when I add or edit a post, I get the ‘are you sure you want to do this, please try again’

    Plugin Contributor fireproofsocks


    Thanks. I’ve identified the source of the problem: I’m incorrectly handling a WordPress NONCE / referrer. I’ve got some paying projects that take precedence, but this is on my to-do list for the weekend. Sorry for the inconvenience!!

    I think the temporary work-around is to “activate” each content type in the manager — this will standardize all custom fields for that content type, which may not be desirable, but it should force the NONCE to be generated correctly so the referrer checking passes.

    Plugin Contributor fireproofsocks


    I submitted the fix in version 0.8.1, so it should show up as an available update shortly. So sorry this got out the door with that problem.

    The CSS issues / UI stuff will be addressed in a future version.

    Plugin Contributor fireproofsocks


    Uh… the changes are visible on the “Changelog” so I know my updates are in WP’s system… but why the F doesn’t this show up as an update? Sigh… WP, where is your documentation when I need it.

    It’s strange as it shows up in the drop down selection.

    I’d give it a few days and if it hasn’t updated, then perhaps email

    Plugin Contributor fireproofsocks


    Rich: as I am writing a book on this process of authoring plugins, it would be HUGELY helpful if you could fill in some of the gaps here.

    • How do you get your plugin listed in the Trak bug tracker? The docs on that seem completely AWOL. WTF?
    • What is the EXACT thing that needs to be updated in a plugin that triggers an update to show up? As far as I can tell, there are 3 things that need to get synced up:
      1. readme.txt: Stable tag:
      2. Info Header: Version:
      3. SVN tag: you must copy the trunk to a named directory in tags

    It seems to be anyone’s guess as to what exactly triggers the update to show up, or how to continue submitting incremental changes on a working copy without indicating a new stable version. E.g. what happens if you put a non-existant “stable” version in your readme.txt file? What happens if you put an arbitrary version number in the plugin’s info header?

    I do a lot of development on a lot of different systems, and WP is notably behind in its docs for developers. If you could point me in the right direction here, it’ll end up in the book and benefit thousands of others in the process. And you’ll be my new best friend. Thanks.

    I only know what I’ve picked up, much the same as yourself.

    Developer FAQ has some info.
    How to Use Subversion also has some info which may or may not be relevant.

    But of late there have been a lot of inconsistencies, so don’t rely on the 15 minutes updates.

    My last change to my plugin was all correct, the download version number changed, but the readme took 2 days+ to update!

    The Stable Tag appears to be the main one to be careful with.

    fps, thanks for the heads up. I will download and install the update once WP has put in their update queue.

    THANKS A LOT for fixing my site 🙂 Much appreciated.


    Your update is actually downloadable from the plugin page. The button says 0.8.0, the zip file you’re downloading says 0.8.1. After installing the plugin still says 0.8.0, but at least it works again 🙂


    After updating the plugin to the 0.8.1 version, my terms page is wrecked.

    Check this out.

    With your plugin disabled:
    with your plugin enabled:

    Any idea what could be wrong?

    Plugin Contributor fireproofsocks


    Please uninstall the plugin and download the latest version: 0.8.8.

    Because these forums are not particularly useful to me as the developer since they don’t notify me of problems, I kindly request that all bug reports be filed here:


Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[Plugin: Custom Content Type Manager] Can't post’ is closed to new replies.