Greg Raven

Because it would be easier to fix this issue in the parent theme than it is to have to create a child theme for no other reason than to make this correct.

Yep, it’s a font issue. Been years since I had to deal with one of those.

Customized the CSS for

to:

{ font-family: -apple-system, BlinkMacSystemFont, ‘Segoe UI’, Roboto, ‘Helvetica Neue’, Arial, sans-serif; }

It still displays incorrectly in the visual editor, it is correct in the rendered page.

Thank you so much for pointing me in the right direction, Andrew!

For example, here is a sample block quote with the opening double smart quote rendered correctly using Twenty Ten:

https://www.hdcycling.org/2014/03/bicyclings-2014-win-a-bike-contest/

Maybe I should mention that this used to display properly on at least some of the themes before Twenty Seventeen.

Yes, I did try. That “weird invalid speech mark character” is a double opening smart quote.

I want (“):

“

I do not want ("):

“

Great thinking, but not the case. Opening double smart quotes are being turned into opening single smart quotes, and not just at the beginning of the quote, but anywhere in the block-quoted text. If I view the text in the HTML editor, it appears as an opening double smart quote.

Dumb quotes are not replaced.

I’ve never seen anything like this.

In the visual editor, it appears like this:

https://www.dropbox.com/s/v29cef5gfzwjv0n/Screen%20Shot%202018-12-22%20at%206.49.49%20AM.jpg?dl=0

In the rendered page, it appears like this:

https://www.dropbox.com/s/t5b0472ot0jlz5w/Screen%20Shot%202018-12-22%20at%206.54.05%20AM.jpg?dl=0

Editing the post as text shows a double open smart quote when the single open smart quote appears in the visual editor and the rendered page.

I’m seeing the same issue on one of my WordPress sites. When I use any version of PHP up to 7.1, the page is fine. When I switch to 7.2, I get this error message:

Warning: count(): Parameter must be an array or an object that implements Countable in /wp-includes/post-template.php on line 284

So, I compared post-template.php from one of my sites that works fine under PHP 7.2 and the one giving me the error. Each is running version 4.9.2 WordPress. However, there are subtle differences between the two post-template.php files! None of the differences is anywhere near line 284, but I’m still baffled how two supposedly identical files can have different content.

OK, I did some further testing. It turns out that the actions for <sub> and <sup> are reversed. If you apply the superscript tags, the tagged text is placed as a subscript. If you use the subscript tag, the tagged text is placed as a superscript.

I forgot we have the ability to do custom CSS. Thanks. I didn’t want to have to go through creating a child theme just for this issue.

Guess I’ll just do it the hard way.

Not familiar with that theme, but this sounds to be a font issue. Can you temporarily edit the CSS file to remove the font reference to see how that effects your italics?

Yeah, I know I can get the current version from WooThemes, but first I need to get the legacy version 1.1 so I can do a comparison to see what changes were made to the core files. Then, I can use that information to create a child them — which is the way it should have been done in the first place — and only THEN update to the latest version of Editorial.

I’m hoping that someone out there has an old copy I can use as reference to where our developer went off the rails.

You’re working on a child theme, right? Not on the code base as it comes from WordPress?

ThePixelMe’s solution works if you want not to see the footer, but you can replace this text with whatever you want in footer.php, unless I’m missing something.