Invalid plugin header

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Jason Judge

    (@judgej)

    The source of the plugin has a “trunk” directory in it, so I’m guessing something has gone very wrong while packaging the zip file. The trunk directory should never be in the plugin.

    Thread Starter Jason Judge

    (@judgej)

    If I remove the trunk directory and everything in it, then the plugin activates.

    Same thing here, I was just going to test it for compatibility within a certain setup. The trunk folder must be removed for the plugin to successfully activate.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Invalid plugin header’ is closed to new replies.