kingjeffrey

FYI, it fails because Memcache is not installed in my local environment, and I really prefer to not have to hack MAMP every time PHP is updated.

Fatal error: Class ‘Memcache’ not found in /path/to/wp-content/plugins/w3-total-cache/lib/W3/Cache/Memcached.php on line 38

In case this is a bug in the core of WordPress, I filed a ticket here: https://core.trac.www.ads-software.com/ticket/21612

Chrome has a conflict with soft-hypens when the stylesheet uses text-rendering: optimizeLegibility;. Make sure this is not in your stylesheet, or in the css rules in the wp-typography options.

Hopefully this FAQ will address your issue.

The plugin does not make any changes to the stored content. It filter’s it on the fly, and is 100% reversible by deactivating the plugin. If your content is still changed after deactivation, it is not this plugin that is causing that – although it could be a cached version of the page this plugin created. If you are using a caching plugin, try flushing the cache.

I started getting this error after I made a change directly to the options table in the database. I cured the issue by simply saving each of the settings pages in the admin panel.

I started getting this error after I made a change directly to the options table in the database. I cured the issue by simply saving each of the settings pages in the admin panel.

If you are experiencing this problem, remove text-rendering: optimizeLegibility; from the CSS code in one of the last fields in the wp-Typography options page. (If the problem persists, you may need to remove it from your style sheets as well).

It appears Chrome has a recently introduced bug in its optimizeLegibility handling.

I’ve reported the bug to Chrome here: https://code.google.com/p/chromium/issues/detail?id=65941

If you are experiencing this issue, leave a comment on that bug report.

Just pushed version 2.0.2 which should resolve this issue.

You are quite welcome.

If you hardcode content into your theme, wp-Typography is unable to access or modify that content. But when the content is accessed from the database, the WordPress functions apply certain filters to that content. wp-Typography works by hooking filters onto these functions.

wp-Typography does not explicitly hook to the wp_title() function, but the wp_title() function apparently (though I have not verified) pulls in all filters used by the the_title() function (which wp-Typography does target). If you do not like the behavior of WordPress in this instance, there is a workaround.

wp_title() accepts a second parameter that allows you to get the results (rather than echo them). This allows you to modify the results using any PHP function you wish, before you manually echo it. See https://codex.www.ads-software.com/Function_Reference/wp_title for the documentation regarding this parameter.

The fix for this is now live in version 2.0

droppyale and janneuu. I think I have resolved the issue in the current development version of the plugin (which will be released as version 1.23). Before I push the update, could you test the development version at https://www.ads-software.com/extend/plugins/wp-typography/download/ and let me know if you are able to enable wrapping acronyms without errors on your sites? You can email me at jeff at kingdesk dot com. Thanks.