=== WP sIFR === Contributors: Jake Snyder Donate link: http://labs.jcow.com/donate/ Tags: sifr, scalable inman flash replacement, fonts, flash Requires at least: 2.5 Tested up to: 2.7.1 Stable tag: 0.6 WP sIFR makes any font possible in your Wordpress installation in under five minutes. == Description == **0.6.1 was developed to drop sIFR out of Firefox on Macs. This issue is blurry at the moment, because some macs, using Firefox, can see sIFR and some cannot. We have reverted back 0.6 as the main download, but if you are worried about some Mac users not being able to see your text, you may want to use 0.6.1 which can be downloaded by selecting "» Other Versions".** **Attention**: If you use Wordpress' built-in upgrade system, it will delete your fonts. If that happens, your settings will be deleted the next time you visite the settings page. If you accidentally delete your fonts, replace them before going to the settings page. This is one of our main concerns for the next version. WP sIFR was created to remove the complications from getting custom fonts on a Wordpress site. With WP sIFR, you only have to upload your SWF font file to the plugin directory and then login, activate it, and configure its styles all in the Settings panel. **WP sIFR benefits** * Works on subpages * Simple backend code and setup * No customization necessary outside of Wordpress Admin * New fonts working on your site in under five minutes Currently, to simplify font addition and removal, WP sIFR removes all settings for the removed font when you delete it from the fonts folder. This is permanent. The addition and removal script runs on plugin activation and when the Settings Panel page is visited. == Installation == 1. Upload the `wp-sifr` folder to the `/wp-content/plugins/` directory 1. Activate the plugin through the 'Plugins' menu in WordPress 1. Add fonts (SWF files) to the fonts folder 1. Set the options in the Admin Panel under `Settings` for your fonts == Frequently Asked Questions == **It doesn't work...** First. Does your template have a in the 'header.php' file? That one is important. Second. Does your SWF file have any funny characters (dashes) in it or spaces in the filename? At this point, your SWF file filename can only have letters and numbers in it. An underscore might work as well, but we are having trouble with special characters. **It works like a charm... Except in Firefox 3 on my Mac.** We have quick update (0.6.1) to disable on FF/Mac while we trouble shoot why sIFR isn't showing up currently in that environment. This appears to be outside of the plugin scope at this point and is an actual problem with sIFR, but we are trying see what can be done. 0.6.1 is a current work-around. It detects the browser and OS and doesn't include the code on Mac Firefox. This isn't ideal, but it is better than hiding the text from users. Once the issue gets worked out, we will remove the detection. **How do I create fonts?** To create a font, you can upload your TTF file to: sIFR Generator (http://www.sifrgenerator.com/). Or you can follow these directions: sIFR Wiki (http://wiki.novemberborn.net/sifr/How+to+use). The Flash file used to create fonts is included in the "fonts/flash" folder. Be sure to remove any spaces from the file name or you will have trouble ("timesnewroman.swf" = GOOD | "times new roman.swf" = BAD). **How do I add fonts?** After fonts are created in Flash, upload them to the "fonts" directory in the plugin folder and they will show up here. Then you can activate and manage the font settings. **What version of sIFR does this use?** WP sIFR uses the latest nightly which is **v3 r436**. Fonts created for sIFR v2.x will most likely *not* work. **Can I add multiple selectors to the same font?** You *can* enter more than one selector, just seperate them with a comma. The only issue with entering multiple selctors is that they will use the same styles. Sometimes this ok, but other times, it can be limiting. For instance, your "h1, h2, h3" tags, if listed on the same font, would all *have* to be the same size even though you usually would want the size to decrease through the headline tags. **I have multiple selectors on the same font, but how do I style them separately?** Short Answer: You can't. Although we *are* working on a system to allow you to add selectors under a font that can then be styled separately. **Long Answer** (hack): The work-around currently is to create a copy of the font file with a different name. Then you could style a second selector for that font separately. For example: Take a file named "futura.swf", make a copy named "futura_h1.swf". This would allow you to use separate selectors, styled differently. This is a complete hack though and causes the same font to have to be downloaded twice. The next major version should have the new system in place. == Screenshots == 1. The WP sIFR Admin Panel == Future Features == Currently, to simplify font addition and removal, WP sIFR removes all settings for the removed font when you delete it from the fonts folder. This is permanent. A future edition will store the settings, and only make sure that the font is deactivated, so that settings are not lost on a whim, and will come back if a font is reuploaded. Allow ticks and commas in the CSS. Fix the space in the file name issue. Allow users to add multiple selectors that can be styled seperately. == Change Log == **v0.6.1** - March 11, 2009 *Added a browser/os detection to keep from adding to Firefox on Macs since sIFR is currently experiencing difficulty on that setup. **v0.6** - March 4, 2009 *Fixed adding fonts issue, plugin did not allow addition of any fonts if it was ever activated without fonts in the fonts folder *Added two sample fonts from sIFR Vault as well for good measure **v0.5.1** - March 4, 2009 *Updated Options to be compatible with PHP 4 **v0.5** - March 4, 2009 *Simplified header code **v0.4** - March 2, 2009 *Simplified updating fonts from the fonts folder into the database *Fixed adding fonts so that plugin reactivation is no longer required *Stopped deletion of settings when plugin is deactivated **v0.3** - February 28, 2009 *First Public Version