[Resuelto] Address field type interferes with WordPress visual editor

[Autor]

Mensajes

[chuckH]

I am trying to use the visual editor.

Link to a page where the issue can be seen when editing the Events custom post type using the editor in the WordPress admin.

I expected to see the WYSIWYG toolbar buttons and be able to toggle back and forth between the visual/text editors.

Instead, I am unable to toggle between the visual/text editors and I am unable to see the WYSIWYG toolbar buttons. Also, the editor content while not visible (it's rendered as white text on white background) is still present.

The inspector shows the following warning/error:
google.maps.event.addDomListener() is deprecated, use the standard
addEventListener() method instead:
enlace oculto
The feature will continue to work and there is no plan to decommission
it.

When I disable the Address field type in use for this particular custom post type (Events), the editor works again.

Thank you for your help to resolve this issue.

[chuckH]

Here are screenshots with Address field type activated (WYSIWYG editor missing) and Address field type deactivated (WYSIWYG editor working again).

[Nigel]

Hi there

I checked your site and see the problem. It persisted after disabling non-Toolset plugins and switching theme.

I couldn't readily determine the cause, and I was unable to reproduce the issue on my own test site.

So I've taken a copy of the site to work on locally to do some further testing.

I'll get back to you when I have some findings to share.

[Nigel]

I installed the copy of your site locally, and there is no problem there, the tinyMCE editor is working fine, even with Maps active.

I returned to your staging site and repeated the tests with all plugins except for Types and Maps disabled, with twentytwentyone theme active, and the problem still occurs there.

I tried deleting and manually uploading new copies of Types and Maps, in case something had gone wrong with the plugin installation, to no effect.

So I'm at a bit of a loss to explain why it is happening on your staging server.

I'll keep investigating there, please bear with me while I do that.

[Nigel]

I've made a little progress.

I see that the reason it is working on my copy of your site but not on your staging site is that you are using PHP 8.2.

There is a problem which triggers a PHP Notice on my local install, but the same triggers a fatal error for an ajax request on your site which then has collateral consequences.

I can't reproduce the same problem on a clean test site, so it seems particular to your site, but at least I can investigate it on my local copy now.

Again, I'll keep you updated, but in the meantime, if this is a blocking issue for you, I would avoid running PHP 8.2 yet (WordPress itself isn't compliant yet, I don't think).

[Nigel]

Got it.

In the custom field group "Event - Location" there is a single custom field, and it has an incompletely-specified display condition (screenshot), and that is triggering the error which has cascading side effects.

I edited the field and deleted the condition, and now everything appears to be working correctly.

Could you check the staging site to confirm? (Currently it is still in the minimal install set up to isolate the problem.)

[chuckH]

Hi Nigel,
Issue resolved! I just implemented your fix on our production site.

I really appreciate your dogged determination to research, troubleshoot and resolve this issue. Since becoming a customer over a decade ago, your team's customer support has yet to let me down. In the beginning it the technology Toolset offered (MVP-like framework within WordPress; similar to what I was used to with Python/Django) that attracted me, but it's been the support that's kept me around.

Thanks again,
Chuck