Support » Everything else WordPress » WordPress Plugin Activate Link Goes To Old Version – Invalid Plugin Header

  • Resolved francdore


    Hi, I built a plugin for WooCommerce and WordPress. It works fine but I found that when you install it through the plugin directory and you click activate, it gives an error: Invalid Plugin Header.

    The activation link also goes to version 1.0.1 where it should go to version 1.0.6 which is the latest version.

    After Google a bit I found that the activation link that points to an old version might cause the problem.

    Does anyone know how to fix that?


    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • Moderator Steve Stern


    When I download your plugin, I find your history in the .zip file rather than only the current version. I suspect you’ve mis-done something in your SVN.

    $ unzip 
       creating: woo-tracking-the-courier-guy/
       creating: woo-tracking-the-courier-guy/1.0.0/
      inflating: woo-tracking-the-courier-guy/1.0.0/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.0/woo-tracking-the-courier-guy.php  
       creating: woo-tracking-the-courier-guy/1.0.1/
      inflating: woo-tracking-the-courier-guy/1.0.1/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.1/woo-tracking-the-courier-guy.php  
       creating: woo-tracking-the-courier-guy/1.0.2/
      inflating: woo-tracking-the-courier-guy/1.0.2/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.2/woo-tracking-the-courier-guy.php  
       creating: woo-tracking-the-courier-guy/1.0.3/
      inflating: woo-tracking-the-courier-guy/1.0.3/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.3/woo-tracking-the-courier-guy.php  
       creating: woo-tracking-the-courier-guy/1.0.4/
      inflating: woo-tracking-the-courier-guy/1.0.4/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.4/woo-tracking-the-courier-guy.php  
       creating: woo-tracking-the-courier-guy/1.0.5/
      inflating: woo-tracking-the-courier-guy/1.0.5/readme.txt  
      inflating: woo-tracking-the-courier-guy/1.0.5/woo-tracking-the-courier-guy.php  
      inflating: woo-tracking-the-courier-guy/readme.txt  
      inflating: woo-tracking-the-courier-guy/woo-tracking-the-courier-guy.php  

    File svn folder looks like this:

    woo-tracking-the-courier-guy >
    > assets
    > branches
    > tags
    > trunk
    > 1.0.0
    > 1.0.1
    > 1.0.2
    > 1.0.3
    > 1.0.4
    > 1.0.5
    > readme.txt
    > woo-tracking-the-courier-guy.php

    Is that wrong?

    • woo-tracking-the-courier-guy
    • assets
    • branches
    • tags
    • trunk
    • 1.0.0
    • 1.0.1
    • 1.0.2
    • 1.0.3
    • 1.0.4
    • 1.0.5
    • readme.txt
    • woo-tracking-the-courier-guy.php
    Moderator Marius L. J.



    I had a look, and yes your SVN directories are unfortunately a bit out of whack, to put it nicely 🙂

    You have all your version directories (1.0.0, 1.0.1 etc) inside the trunkdirectory, these should go inside of tags.

    You’ve also marked 1.0.6 as the stable tag, this does not exist which makes us use the entire trunk directory as a fallback.

    So to fix this, move all your version directories to the proper tags parent folder, and then make sure the stable tag in trunk/readme.txt is a folder that exists in the tags/ directory.

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    Yeah, your SVN is completely busted. You have multiple versions in /trunk instead of in /tags where they belong.

    You need to fix your SVN. If you need help, email plugins at wordpress org for assistance.

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    Yeah, you’re *really* doing it wrong.

    Stop doing anything. You’re not fixing it this way.

    Email plugins (at) wordpress (dot) org and we’ll explain the problem to you. I’ll even go in and fix it for you. But email us.

    • This reply was modified 4 months, 3 weeks ago by  Steve Stern.

    Okay I think I have fixed it.

    I just want to confirm,

    Should /tags contain all the version directories in there like this:

    And the latest version 1.0.6

    What should the trunk directory look like?

    Moderator Samuel Wood (Otto)

    (@otto42) Admin


    Check your email. I committed a fix for you and emailed you about what I did to clean it up. 🙂

    Your latest commit broke it again, actually. You need to put the /tags/1.0.6 back.

    Currently my trunk directory has got readme.txt and woo-tracking-the-courier-guy.php

    Is that wrong?

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    @francdore No, that is correct and what you want to have.

    – /trunk contains the raw plugin, latest version, with no subdirectories.
    – /tags contains various snapshots of the plugin at points in time. Usually these are in subdirectories named after the version. /tags/1.0.0 and /tags/1.0.1 and so forth.
    – The /trunk/readme.txt file has a Stable Tag header line. This points to the current “Stable” version.
    — If it says “1.0.6” then /tags/1.0.6 is the stable version
    — If it says “trunk” then /trunk is the stable version
    — It if says “nonsense” and /tags/nonsense does not exist, then /trunk is the stable version
    – The stable version is the one we use to build the ZIP file that users receive.

    Right now, you have Stable tag set to 1.0.6, but you don’t have a /tags/1.0.6 directory.

    Sorry I was trying to fix it on my end as well.

    Okay so I did a SVN update and my tags folder has got version 1.0.0 to 1.0.5

    My trunk folder has got readme.txt and the php file in there.

    Should my tags folder contain a directory 1.0.6 too which is the latest version.

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    Should my tags folder contain a directory 1.0.6 too which is the latest version.

    Yes, if you have “Stable tag: 1.0.6” then there should be a /tags/1.0.6 directory with version 1.0.6 of the plugin in it.

    Other than that, you’re looking good now.

    Okay so I need to copy the latest stable version into tags/1.0.6/

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    Yeah so the last commit I did should fix it.

    Thanks for the help! Now I know what it should look like!

Viewing 15 replies - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.