I'm progressing with the WP plugin for WordPress, which is the main thing missing before releasing 1.1.0-alpha1. It will alow users to set options, and activate/deactivate/configure plugins.
It's a lot of (boring) work, but seeing the LP console taking shape and knowing users will have a graphical install/configuration tool integrated with WP is pretty exciting. Stay tuned. :)
That screenshot is tantalizing - far better than the PHP errors in the version I'm currently using! :)
(don't worry though, I still need to update to your latest changes)
I always uhm "forget" Windows compatibility and magic_quotes_gpc :)
Yes, I'm sure Windows is at the top of your priority list. :) My latest commits fixed the above errors, which just leaves two things:
1) A way to save the plugin configuration
2) Re-enable the code in Frontend to use the database if no options are provided. Or maybe I missed something…
Also, with 1.0.6 all comments are being sent straight to moderation again - any ideas?
The WP plugin is not finished yet… :)
And the Spam Checker is now its own plugin, and needs to be enabled in config. My fault, everything will be fixed in 1.1.
And we have to find a way to test the app, unit testing is not enough (not that we have them…) as many things depend on the configuration.
I was thinking we could do some sort of regression testing: feed Frontend different configurations and exercise its various methods, possibly using a few test templates. Definitely a lot of work though… might have to wait until we have more funds after the IPO. :)
Ok, that fixed it - just added CommentSpam to my active plugins. Didn't think of that at all.
A regression test for Frontend is a very good idea. I'd like to get alpha1 out of the door so that (hopefully) a few people will test it, then start developing the tests.