I have a weird issue with the diamond question marks for strange symbols in Wordpress. I just migrated my website and content to a new redesigned template. You can see at the bottom of this url what my issue is.
It looks like the diamond is only appearing instead of a space before a html tag. So in the bottom of the page you see the issue with an <a>
tag, but it also happens with for example <strong>
tags through the website.
- My database is InnoDB with
utf8_general_ci
- Meta tag:
<meta http-equiv="Content-Type" content="text/html" charset="UTF-8"/>
- Custom template
- Advanced Custom Fields
Anyone who can help out?
I have a weird issue with the diamond question marks for strange symbols in Wordpress. I just migrated my website and content to a new redesigned template. You can see at the bottom of this url what my issue is.
It looks like the diamond is only appearing instead of a space before a html tag. So in the bottom of the page you see the issue with an <a>
tag, but it also happens with for example <strong>
tags through the website.
- My database is InnoDB with
utf8_general_ci
- Meta tag:
<meta http-equiv="Content-Type" content="text/html" charset="UTF-8"/>
- Custom template
- Advanced Custom Fields
Anyone who can help out?
Share Improve this question asked Oct 8, 2017 at 19:41 ronnyrrronnyrr 3832 gold badges6 silver badges16 bronze badges 2- this sign replace something that is missing or it is just add to the initial content ? if it's just add, you can try to clean the database with a tool like this : github/interconnectit/Search-Replace-DB – mmm Commented Oct 8, 2017 at 20:00
- I searched for the text in the database. But there I just see the space, no weird characters or something. So I don't know where to look for with the replace library. Any suggestions? – ronnyrr Commented Oct 8, 2017 at 20:32
1 Answer
Reset to default 1A diamond question mark is browser for "I can't decode that."
I would assume what is happening is when you migrated the HTML entity for space was encoded in your database wrong or WordPress is reading it with the wrong encoding assumed.