Please install the wp-Typography Disable ACF Integration plugin by @sarukku. Alternatively, you can also directly use the filter hook
typo_disable_filtering in your
There is a bug in the shipped Safari 9 that results in strange characters being rendered when both ligatures and soft hyphens appear on the same line. (The bug is only triggered when the font actually supports ligatures, e.g. with Open Sans.)
Fortunately, adding the following line to your CSS fixes the font rendering and preserves ligatures:
If you enable
Add workaround for Safari hyphenation bug, this CSS property is inserted into your page automatically.
This plugin offers an option to wrap initial quotes in a span of class
dquo. You can then style these classes in your CSS stylesheet. This is useful if you want to-for example-negatively indent quotes so the quote hangs in the left margin and the text is aligned with the text below.
Please note, this applies only to initial quotes — quotemarks that appear as the first character of a block of text (like a paragraph or blockquote). This does not apply to all opening quotes.
This is a known compromise that comes with hyphenation. The hyphenation feature works by inserting soft-hyphen characters at every possible hyphenation point. They are typically invisible, and should only show up at the end of a line if the word wraps.
Unfortunately, not every editor is smart enough to properly handle soft hyphens. Text copied from your web page will include soft hyphen characters. Some programs will display a space instead of a soft hyphen. Some may display actual hyphens. And it may break spell check even if the characters are displayed correctly. If you want hyphenation on the web, you must use soft hyphens. If you use soft hyphens, other programs may not like copied text.
wp-Typography does not have access to HTML stored in your theme files. It only has access to the content passed to it (i.e. post title and content); it is unable to determine the greater contextual awareness.
If you try to filter processing based on a class of the body element — as an example — nothing will happen. wp-Typography does not see the body element. wp-Typography does filter by HTML element, class or ID for any markup present within the parsed content. So if you do not want class
noTypo processed, filtering will only occur within the title or content of your post or page.
More likely than not, your WordPress theme is using an improper function to set the title attribute of your heading’s link. It is probably using the
the_title() function, which delivers the post title after filtering. It should be using
the_title_attribute() which delivers the post title before filtering. Change out this function throughout your theme when it is used inside of an HTML tag, and the problem should go away.
Here are some specific instructions for fixing your theme. Please note that every theme is different, so mileage may vary.
To edit the theme, log in as an administrator and go to:
Appearance > Editor. You will typically want to edit the following files (if they exist):
In each file, search for the code that looks something like this:
<h2><a href="<?php the_permalink() ?>"
title="Permanent Link to <?php the_title(); ?>;"><?php the_title(); ?></a></h2>
Your theme may contain some variations. For instance, the
h2 tags may be
h3… We are looking specifically for the part that says
title=" … <?php the_title(); ?> … ". It should be changed to:
<h2><a href="<?php the_permalink() ?>"
title="Permanent Link to <?php the_title_attribute(); ?>"><?php the_title(); ?></a></h2>
Save the files, and you should be good to go.
If you are uncomfortable editing your theme’s code, you may alternatively go to the wp-Typography settings page in your admin panel and add
h2 to the “Do not process the content of these HTML elements:” field. This will disable typographic processing within improperly designed page title links and page titles.