WordPress.org

Ready to get started?Download WordPress

Forums

SVN submission -- WP repo not picking up updates correctly? (8 posts)

  1. fireproofsocks
    Member
    Posted 3 years ago #

    I've authored a plugin and I've submitted it to the WordPress repository so it's available for download. No problem.

    But now I've run into problems when I've attempted to publish updates to the plugin. I submit the changes, the WordPress page for my plugin shows the changes to the readme.txt file, but the version that's available for download HAS NOT CHANGED. It's really frustrating, and I can't find any documentation that clarifies this.

    Here's what I've done:

    1. Updated the "Stable tag" parameter thereadme.txt file.
    2. Updated the Changelog and Upgrade Notice sections in the readme.txt file.
    3. Updated the information header in my plugin's main file to reflect the new Version attribute.
    4. Submitted my changes to the SVN trunk.
    5. Made an SVN copy to copy the trunk to a named branch using a command similar to the following:
      svn copy https://wp-repo.com/my-plugin/trunk https://wp-repo.com/my-plugin/tags/1.2.3

    I've submitted many SVN changes and tagged new versions, but no matter what I do here, the plugin page that WordPress displays is always the first version of the plugin -- my updates are ignored, so the plugin users never get notified that there is a new version available. The only way to get the latest version of the plugin right now is by using SVN.

    The only quirk I can think of is that my information header is in a file named index.php instead of a file that shares the name of my plugin. I haven't seen any documentation that says it's required to use a specific file name for the file that contains the plugin info header, but I've seen enough crufty bugs in the WP dev cycle to believe that such a low-brow minutiae could cause problems.

    What am I missing?

  2. elfin
    Moderator
    Posted 3 years ago #

    and your plugin is?

    However there is currently an issue with the plugins that is being looked at, no time frame for the fix atm.

  3. fireproofsocks
    Member
    Posted 3 years ago #

    Oiy... that's a rough bug if it prohibits updates from percolating through to plugins. I'm about to lose my mind with this.

    The plugin is here:
    http://wordpress.org/extend/plugins/custom-content-type-manager/

    Is the "correct" process documented anywhere? I've been looking but I haven't found any documentation that outlines how to correctly update a plugin... the AWOL docs is really the bigger problem here (current glitches aside).

  4. elfin
    Moderator
    Posted 3 years ago #

    Well as you've just made some more changes, I'd suggets leaving it for a few days. If the version hasn't been upped to the latest by that time, email plugins@wordpress.org

  5. fireproofsocks
    Member
    Posted 3 years ago #

    Looks like the updates went through (big sigh of relief).

    Does anyone know where the docs for this are? Or is this time for me to make a blatant plug for my upcoming book where I've killed the dragon and lay it out for the coding public?

    Rich - is there a place where bugs in the SVN repo could be posted?

  6. elfin
    Moderator
    Posted 3 years ago #

    Last Updated: 2010-11-27 though, which is the main issue they are working on.

    You can raise tickets on Trac against WordPress.org (haven't got the link handy atm)

  7. Marcus
    NetWebLogic Support
    Posted 3 years ago #

    http://core.trac.wordpress.org/

    I assume if you assign the component to wordpress.org site that would work, e.g. http://core.trac.wordpress.org/ticket/15138

  8. fireproofsocks
    Member
    Posted 3 years ago #

    Bug filed. If WP is responsive about this bug as they've been about everything else, then I expect absolutely nothing to come from this, but hopefully I get proven wrong.

Topic Closed

This topic has been closed to new replies.

About this Topic