Mawhorter.net Forums

I've seen that there are number of issues with the plugin for WordPress.  I unfortunately haven't had time to work on it recently though I expect to soon.

Here's what I have planned for 0.8.8

* Add realFontHeight as a checkbox item for Elements to Replace
* Add option for custom FLIRStyles in Elements to Replace
* Add correct wrap for FancyFonts
* Add check for get_browser - disable checkbox for IE 6 option if not available and add notice
* Fix location of global settings for Automatic (wrap/progressive/etc.) - currently listed with Elements to Replace which only shows when using methods other than Automatic
* Fix font name issue - probably will only note that fonts cannot contain spaces

Planned for 0.8.9

* Branch FLIR for tighter integration of the plugin more closely with WordPress -
** Eliminate need for config-flir.php by pulling those options directly from the wp-options table - this will eliminate some of the upgade issues.
** Add ability to upload and manage fonts from within the plugin.  Will include automatic renaming of fonts to reduce issues.
** Change the fonts path to wp-content/flir-fonts so user fonts are not removed when the plugin is updated from within WordPress.
** Change the cache path to wp-content/flir-cache cache will not cause the upgrade to fail.
* Fix the activation/deactivation of the plugin to clear the cache and hopefully eliminate the one remaining upgrade issue when upgrading from within WordPress.

Planned for 0.9.0

* Add the long promised QuickEffects to the plugin.
* Fix all the bugs caused by me in the previous release.
* Add any last feature requests that seem to fit.
* Should be considered beta for 1.0

Planned for 1.0

* Squash any remaining bugs and release.

Cory-

I hope you don't mind my branching FLIR.  I'm going to try to limit the what I do to just altering the config-flir.php file so that the rest of the code remains essentially unchanged lest you update it.  There are some real issues with having the plugin act as a wrapper that could be eliminated by closer integration with WordPress via the plugin interface.  For example upgrades wipeout the entire directory and leave used with a raw install - I think I can mitigate this considerably though the activation/deactivation calls but it will still leave people without fonts.  I didn't really want to branch the code but I guess I'll just have to merge changes back in for the plugin if it makes the plugin better - there are a lot of plugin users at this point.

Dan