Nathan: I noticed that this plugin disabled when I performed my 2.8 upgrade a
couple of nights back, and just poked around at it. After googling about, I did
some editing to replace direct refs to 'wp-content' (based on info from
http://plugincheck.bravenewcode.com/), but that didn't appear to do it.
Continuing on; it appeared the file header info was ok (I got the same "invalid
headers" msg as Zane), but I finally noticed after comparing to other plugins
that my install was one level deeper than most: (ie,
plugins/wplicense/wplicense/*.phpfiles). I'm by no means a WP plugin dev, but
skimming the docs, it appeared that the plugin admin engine wants a header file
in that uppermost dir.
I copied wplicense.php to the upper wplicense dir, got an error (the widget
support require assumes widget.php will be in same dir), copied the widget.php
file to upper directory, and things are working again.
There's probably a "cleaner" way to do it, with a file containing just the
activate code, etc. But quick and dirty worked. I actually went back and used
the original wplicense.php file (w/o the 'wp-content' changes), and it appears
to work as well. So just moving some files about should do it, I think. I can
forward you a patch with my edits for the 'wp-content' changes, if you're
interested (see
http://codex.wordpress.org/Determining_Plugin_and_Content_Directories for the
relevant issue). Just let me know.
|