migster

That’s exactly my point, though.

All I want to add is a dash/hyphen. I shouldn’t have to encode or escape anything, just for that. It’s really quite short-sighted to add that kind of restriction

Hi Denis, thanks for the repsonse.

Unfortunately, I get the same result with the shortcode. All other links are fine, but the lack of https:// on the mailto: seems to be what is causing it to appear as a local url. Curiously, tel: links work perfectly well

Hi Mamunur

Thanks for the quick response. I should have said I’m trying to avoid adding yet another plugin. I use a custom function which adds the Duplicate option to all other posts, including custom post types, but it doesn’t show on the grid list.

I was hoping it was easily fixed, but maybe not.

In ACF, when using a Post Object field type, the field type-specific options (i.e. not the more general options seen in all fields) that use dropdowns in the field settings are not selectable. They can be seen, and technically can be scrolled, but the dropdown itself does not function correctly.

I’m happy to do a video screen capture, and send it privately, if it would be useful

I will try that, thanks, but it’s really not a long term solution, I don’t think. I appreciate you need to include certain functionality, but surely there must be a better i.e. more permanent way?

Weirdly, I had the same problem in WooCommerce yesterday. I found it was every time a product was created which had a + in the product name.

I don’t know if that matches what you see? It’s annoying, even if not fatal.

I’m glad it pointed you in the right direction!

To help people if they still get this and can’t figure out why, it is often caused by rogue bits of code in your text.

Look at the “Text” tab of the edit area, and find any &nbsp or unrequired <div> or </div> tags.

They very often occur if you C&P from other web pages. Basically, your browser is trying to apply the divs but the WordPress editor doesn’t recognise them, and this causes a conflict which shows as the error message you see.

Deleting the unused tags should should fix the problem in most cases.

The main problem does seem to be when an .htaccess rule tries to load a second php version, which does tie in with the variations on that subject which people have mentioned.

For some reason, my .htaccess had two lines, one loading php7.2 (which is what showed in phpinfo and one which then tried to load php7.1

Deleting the second line has solved the white on white problem, but the classic editor still loads in Text mode as default, instead of Visual mode. Switching to Visual loads TinyMCE okay, so I don’t think it’s any kind of permissions or blacklist issue.

My profile has the option to disable Visual mode unchecked.

Hi Konstantin

The update has fixed the issue, thank you for such a quick response. I’ve also just contacted you via the contact form on your site.

Cheers

Migs

I think that’s the only reasonable solution. I don’t want to use another google fonts plugin both for the fact they seem to get abandoned when there are no more feature additions to be made, and that most just seem pretty unreliable

Thanks for the link

Okay, another thread reports a similar issue with the core 2017 theme, so it definitely looks like an issue with the plugin.

It looks like an update to WordPress 4.8 causes the issue, as I have the same problem with a different theme

It also looks like the author has given up supporting this plugin ??

Good to know, thanks!

In that case, all I can offer is my appreciation for what you do, and you deserve every bit of it ??