Typogrify 1.6
Wordpress 2.7.1
The Typogrify plugin seems to wipe out the content of some single post pages when the widow prevention option is activated. I don’t have the patience right now to troubleshoot it, but the wp-Hyphenate plugin mentioned on the Typogrify home page also handles widows and also deals with quite a few other typography concerns. It seems Typogrify and wp-Hypenate will be merged at some point.
Note: if you decide to install wp-Hyphenate, don’t download it from the website and then try to directly install it from the Zip file using WordPress’ plugin installer (i.e. “Add New” in 2.7). The Zip file is a wrapper which encloses the actual plugin code in a superfluous directory and causes WordPress to be unable to find the plugin. If you accidentally do this, you’ll have to log into your WordPress install, go to wp-content/plugins/wp-Hyphenate_1_07_beta (or whatever the current wrapper version is) and move the enclosed wp-Hyphenate directory a level up into wp-content/plugins. Also, this plugin doesn’t seem to be available yet on the WordPress plugin directory.
Google Analytics for WordPress 2.7
I’ve only seen this happen on one post so it’s kind of hard to analyze. The Google Analytics for WordPress plugin would do a kind of gag-choke thing:
The things you don’t see here are:
- the Adblock link had a “);” appended to it.
- the second link to Pipes has the Adblock URL assigned to it.
The actual code in the posting shows nothing of any interest:
[sourcecode language=’html’]Pipes suffers quite a bit if you don’t disable the Adblock Firefox add-on for pipes.yahoo.com.[/sourcecode]
…except the malformed URLs for Pipes (which, of course, is a problem – but it shouldn’t be the plugin’s problem). When the “http://” was added the plugin behaved properly. However, even though it’s an error in the HTML I don’t think the plugin should lose its marbles. The regex that parses out the URL should maybe grab whatever is in the quotes, perhaps do something with it (perhaps not) but it shouldn’t behave unexpectedly.
Also, the administrative Options panel for the plugin shows this:
Well, looks like I can retire WebKit for a little while. The Safari developers have released a beta of version 4. I had a bit of trouble starting it at first (Mac OSX 10.5.6). It was the Glims plugin which was crashing it. I removed it from /Library/Application Support and Safari started up nicely.
Update: Turns out Google Gears doesn’t work in this Safari 4 beta.
Update 2: The Glims developers have release a new version which doesn’t crash Safari, but is missing a chunk of functionality.
Update 3: Safari, even in the development WebKit nightlies exhibited an irritating “bug” with the WordPress 2.7 administrative interface. It would cause a modal overlay dialog to hang. The dialog appears when editing a post with the visual editor (e.g. add a link, upload images, etc.). This is still quite present in 4 beta.
Update 4: (June 11, 2009) The bug mentioned in Update 3 with the modal dialog has been fixed in Safari 4.
I’m running a development version of Firefox on an Intel Mac. The new Google Earth browser plugin doesn’t recognize it as Firefox 3.0+ so I installed the User Agent Switcher plugin and added an agent that the plugin would recognize:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; nb-NO; rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3
You also need the Nightly Tester Tools plugin to get the User Agent plugin to override the compatibility check too.
