This topic contains 6 replies, has 2 voices, and was last updated by 
- Posts
My posts (new and old) have started showing an A with a caret at the end of each sentence. It doesn’t show on all devices, but does from my Iphone and some other mobile devices.
http://www.beyondthechickencoop.com
Any advice on how to fix?
Thanks!Are you by chance copying and pasting posts from Word into the WP post editor? Oftentimes, this will cause these very kind of erroneous characters.
If that’s the case, we recommend drafting directly in the WP post editor, preferably in plain Text mode.
Note that this is a universal issue of WordPress, not any specific theme.
Thank you.
Thank you for your response. I am not copying and pasting. I am writing directly into WP. I’ve also posted in WP forums for help. I’m just hoping to resolve the problem. This is a relatively new problem for me, although many (if not all) of my posts seem to have the same issue. Any suggestions to correct this issue?
Thank you.ÂI’ve seen the issue a few times. The corruption is usually encoding related and is sparked from something to do with Word, the WP Visual editor, or both, and the handling of special characters. If it’s only happening on mobile devices, I wonder if it’s to do with a corrupted font.
What are the plugins you have installed?
Can you share a screenshot of the issue?
Thanks
Found it.
It’s the blank space characters causing the problem.
Likely, it’s happening through the WYSIWYG (Visual) editor in WP. Make sure to only add a single space after a sentence, not a double-space.
It appears to be a very old issue:
https://core.trac.wordpress.org/ticket/6942
If you’re using any sort of plugins that enhance the post editor, this might also be the culprit.
I think I’ve got the issue resolved. I deactivated all the plugins and then activated one by one. The problem went away and isn’t there any longer! I don’t know which one cause the problem because it hasn’t reoccurred.
Hopefully the issue won’t occur again.
Thanks for your help!Excellent. I can confirm on my end too, that the problem is gone. Thank goodness, that sure saved you a lot of work. :)
You must be logged in to reply to this topic.