Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Luke Mlsna

    (@bitacre)

    Also you forgot to extend the $nofollow and $target options to the tag links at the top.

    Plugin Contributor David Artiss

    (@dartiss)

    That information doesn’t go in the PHP file – it goes in the README (and, as far as I know, that’s present).

    I’ll correct the issue with the tag links.

    David.

    Thread Starter Luke Mlsna

    (@bitacre)

    Then perhaps it was missing the License: tag in the header. In any case, it told me the header was bad when I tried to activate it and would not let me activate it until I added:

    Stable tag: 1.1.1
    Tested up to: 3.1.1
    License: GPLv2

    to the header comment. WordPress says you need:

    /*
    Plugin Name: Name Of The Plugin
    Plugin URI: https://URI_Of_Page_Describing_Plugin_and_Updates
    Description: A brief description of the Plugin.
    Version: The Plugin's Version Number, e.g.: 1.0
    Author: Name Of The Plugin Author
    Author URI: https://URI_Of_The_Plugin_Author
    License: A "Slug" license name e.g. GPL2
    */

    at a minimum in the PHP file.

    Plugin Contributor David Artiss

    (@dartiss)

    Ok, that explains it better. I’ve come across this behaviour before. It’s one of two things – either the copy in the archive is corrupt (I’ll update a revised version in a minute to illiminate this). Alternatively, when doing automatic updates it can attempt to active the wrong file.

    On my own test site I hadn’t updated the plugin myself, so used the automatic updater. Sure enough I got a failure upon activation. However, it was pointing to the markdown.php file in the sub-folder. This isn’t the right plugin file!

    Attempting to activate the updated plugin via the plugin menu though, worked.

    David.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: WP README Parser] You forgot a couple header lines’ is closed to new replies.