Hi, that's unusual. Have you tried troubleshooting by activating a default theme like Twenty Twenty One and deactivating all plugins except Types and Blocks? Is the pagination block set up to use a custom font, or the default theme font? Where can I see the problem on the front-end of the site?
Sure, that would be helpful. I will activate private reply fields here. You mentioned that the page uses UTF-8 encoding. Can you tell me the DB_CHARSET and DB_COLLATE settings from your wp-config.php file?
Standard settings are:
/** Database Charset to use in creating database tables. */
/** The Database Collate type. Don't change this if in doubt. */
Okay, thanks for the extra information. After some additional investigation I didn't see anything obviously wrong or any obvious conflicts. So I set up a similar test on my own local test site, and it turns out I'm able to replicate the problem there as well. It seems that there is an issue with these specific text characters in Blocks pagination, because they are being replaced with unicode equivalents on the front-end. I'm escalating this to my 2nd tier support team for additional investigation.
Until we get an update, I was able to replace the basic "less-than" and "greater-than" text characters with some similar-looking characters that are not converted to unicode unnecessarily:
It seems to be working now in staging. You can confirm, then copy + paste the text from the pagination block configurations in the staging site into the pagination block configurations in the live site, if you'd like to replicate the solution.
I'll let you know what I find out from 2nd tier support when I have an update.
I does work and I implemented it on the live site... but of course, I hope you'll find the solution (or, if not possible, change the default characters that are added when we enable that feature, since it's the greater than and less than signs that are there by default).
I apologize, I made a mistake in my previous comment. Those versions (3.5.2 / 1.5.2) are already available and do not include the fix. The fix will be included in the upcoming releases, versions 3.5.3 / 1.5.3.