kingjeffrey

@sauerland

This problem occurs when HTML tags are inserted into the title attribute of another html tag. The the_title() method returns the raw title text (HTML elements and all), and should never be used to provide content for any HTML element. Rather, you should use the_title_attribute().

If this problem is occurring for you, then the_title() is improperly used somewhere in your theme.

Jeff

prometh,

The double space after a period is legacy from monospaced fonts on typewriters and is not recommended for use with modern proportional-width fonts.

Further, HTML requires browsers to collapse all adjacent spacing to a single space. So even if I inserted an extra space, it would just disappear. I suppose I could insert a no-break space (these don’t collapse), but given the above, that seems unnecessary.

See https://www.itcfonts.com/Ulc/4111/DoubleSpaces.htm for more information.

sauerland,

I have been using wp-supercache successfully with wp-Typography for quite a while. The only think I can think of is that after activating the plugin, your site is still showing an older unhyphenated version of the page. Try clearing your cache after activating the wp-Typography plugin.

sunside, I will look into this.

Jani,

Everything else looks as I’d expect. The only other issue I could think of is perhaps it is not a server issue, but a plugin conflict. Have you tried disabling your other plugins? I know there are conflicts with Kimili Flash Embed, but that has to do with his method of using shortcodes. It shouldn’t make content disappear.

Otherwise, I am at a loss.

Jeff

Jani,

It looks like you have properly installed the mb_string extension on both servers. I notice the working server lists the db encoding as UTF-8, but the errant configuration does not list the db encoding. Is your db encoded UTF-8? Are your WordPress installs similarly encoded UTF-8?

Jeff

Not a problem. My guess is that the first failed upgrade that left some wp setting in an improper state; and that messed up the later tries. This is the only instance of this issue of which I have heard.

Strange. File size is the same as before. Try uninstalling and reinstalling. You could also download and install via the upload interface (or via FTP if you are comfortable with that).

Try the wp-Typography plugin for automatic hyphenation.

Regarding good typography…

Let’s keep some vertical rhythm this time. And main content line length about 30x that of the font size.

Georgia, when sized at 15-16px is just beautiful (and ubiquitously available).

Perhaps we can use a @font-face rule for heading text. With a classy font like a Museo Sans.

I’ll miss Kubrick. I cut my standards-based-web-design teeth dissecting that theme in early 2005.

I am glad to see that a high priority to keep the new theme simple — so it too can act as a teaching tool.

Another vote for HTML5 doctype!

But HTML5 elements as well. I’d love to see posts marked up as <article>s and <h1>s styled by depth of <section> nesting.

This is out of scope, but perhaps we could get a visual editor that outputs HTML5 as well (<figure> wrapped photos and <section> nested <h1>s specifically)

pik256,

I just pushed version 1.19, which should resolve your problem.

CMD-S does now work for Macs. Thanks.

There is another bug I have found. The plugin works as expected for new posts, pages, links as well as editing existing pages and links. But when editing existing posts, it does not have the expected behavior.

Also – but of much less importance – when adding user profiles, link categories, and editing existing posts, media, link categories, comments, theme files, plugin files, user profiles, and settings it does not cause changes to be saved.

Saving posts and pages was my core frustration, and that is now cured (almost).

Thanks for your work.

I agree. On Macs, the Command button replaces the Control key for most keyboard shortcuts. It would be great if this plugin recognized both key combinations.