[Resuelto] The WYSIWYG custom field removes schema org attributes (like itemscope/itemtype)

[Autor]

Mensajes

[Emmanuel]

When I use a WYSIWYG custom field, if I switch the editor to html mode and then back to visual mode, the editor removes attributes like itemscope/itemtype/itemprop.

I had the same problem with WordPress and the problem is corrected by using the following plugin: enlace oculto

But even with this plugin, it doesn't work on WYSIWYG custom fields generated with Tooset.

Could you tell me how to do it ? (maybe you can look at the code of this plugin to tell me how to use it on Toolset?)

Thanks in advance,
Emmanuel

[Minesh Supporter Idiomas: Inglés (English ) Zona horaria: Asia/Kolkata (GMT+05:30)]

Hello. Thank you for contacting the Toolset support.

First of all I would like to know what Toolset plugin version you are using. To know that can you please share debug information with me.

I would like to have debug information that will help us to debug and investigate your issue:
- https://toolset.com/faq/provide-debug-information-faster-support/

[Emmanuel]

Hi,

I use Toolset Views 3.6.3 and Toolset Types 3.4.16. Attached the debug information.

I don't think this is a bug (because the problem was too with the default editor on WordPress and that's why we need an additionnal plugin). The logic is to add this feature (no clean up html entities) on this custom field.

Thank you!

[Minesh Supporter Idiomas: Inglés (English ) Zona horaria: Asia/Kolkata (GMT+05:30)]

We released the Toolset Types plugin version 3.4.17 with few fixed related to WYSIWYG editor.
=> https://toolset.com/download/toolset-types/#changelog

Can you please update ALL Toolset plugins to its latest release version and check if that help you to resolve your issue. You can download the latest Toolset plugins from your account's download page:
- https://toolset.com/account/downloads/
Or
You can update the plugins from the installer:
- https://toolset.com/faq/how-to-install-and-register-toolset/

[Emmanuel]

Thank you for your reply and indeed after an update, the problem was resolved!!

Sorry for my fault... this is the first logic, try to update the plugin 🙂

Thanks again!

[Emmanuel]

My issue is resolved now. Thank you!