Okay. So I just finished upgrading to the new Wordpress 2.5. And so far, nothing has broken. Yay.
As for wp-typogrify; there’s a bug that I’ve noticed (and been told about before) that I haven’t quite fixed yet. Basically, it’s when you use the option to wrap capitals (acronyms, abbreviations, etc.) in <span class='caps'> tags for special styling. What this can result in is HTML in your post titles. Which is fine for actual HTML output, but when your title appears in the <a> tag’s title attribute, your HTML ends up being displayed in the tooltip. Not good.
So how do I fix this? Well I thought I had, using the method I described here.
Unfortunately, it seems that Wordpress no longer acts as it once did. Though I don’t think this is new in 2.5 — I just never noticed it myself since I was using a fairly old version of Wordpress for some time.
Anyway, right now the easiest fix I can think of is to use PHP’s strip_tags() function on the titles. I’ll update the plugin and info pages with this information ASAP. If you have any questions, please let me know in the comments, or by email.
Thanks. And have a great Sunday.
12 Comments
Thanks for the update with regards to typogrify!
Thanks for keeping an eye on Typogrify; it’s probably my favourite plugin. I couldn’t live without my emdashes and widow control!
I noticed on the plugin directory page that the FYI box reads “Compatible up to: 2.2.3”. You could bump that up to 2.5 now.
BTW your tag pages don’t seem to be working, e.g. I click on the “typogrify” tag above and get a page with no posts.
Dan
Thanks Dan. I’m glad you like it. And yeah, I gotta update all the plugin info.
As for the tag pages, just noticed that myself. It’s weird because I thought I tested them after the upgrade.
I love typogrify! I’ve also moved up to WP2.5 and have experienced no problems. I don’t wrap caps, so I don’t suffer from that tooltip problem; and I have absolutely no idea how it can be fixed. I’ll leave that to you. Thanks again for a great plugin.
I see there’s now a version 1.6 — what’s new?
Dan
You can see the changelog at the end of the Readme file.
Wonderful plugin. I’m using the older version for title control. I know I should upgrade but it’s a great feature.
I did have a question about widows on get_post_meta content. This doesn’t seem to be working even with the newer plugin version, any thoughts on this, perhaps I need to surround this with code I’m unaware of?
Also, I added in some additional code to prettify your dashboard back-end area and bring it up to the 2.5 world. I’ll be happy to send this over and spare you the trouble if you’re interested. Thanks
Hello, I may be only person though, I can’t get this plug-in work. The Read-me says “upload the php-typogrify folder” but which folder does it mean? there is no folder called like that. So i upload the “wp-typogrify” folder then activate the plugin but no-effect to ampersands nor quoat marks… Of course I checked all options under Option > Typgrify too. Please assist me the installation and please let me know if you can think why it doesn’t work at all.
Takashi
You’ve done right Takashi. But I think you’re misunderstanding the purpose of the plugin. wp-typogrify doesn’t directly change the appearance of your ampersands, it simply wraps them in a span tag, so you can style them yourself — see John’s post on I Love Typography for more info. (The section on styling ampersands)
You also mentioned quotes, in this case, typogrify should make them proper quotes (left and right) and wrap initial quotes, but styling is again up to you.
I hope that answers your question. Let me know if you have any more concerns.
Hamish
Thank you very for much your quick reply.
Yes, I knew I need to style it in CSS amd I have done it as well but I couldn’t see any tags around ampersand.
However I found out why it didn’t work… It was my bad.
I was testing with typing just &”something” to see how it works. Of course in ths world, there wouldn’t be a paragraph which starts a ampersand. As soon as I typed more words before the ampersand, tags appeared and it got styled as I specify in its CSS.
Also that quotes are not initial quotes either.
Hamish, I apology my bad, i should’ve test it with more realistic example.
Ah yes, the code can be particular about things like that. I’m glad you figured it out!