Skip Navigation

[Gelöst] Custom Fields not working for pages with Gutenburg

This support ticket is created vor 6 Jahren, 3 Monaten. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Dieses Thema enthält 5 Antworten, hat 2 Stimmen.

Zuletzt aktualisiert von jasonH-5 vor 6 Jahren.

Assistiert von: Christian Cox.

Author
Artikel
#1086549

Hello,

I have custom fields assigned to pages with a certain template. So far Gutenburg seems to work fine but I have noticed it is not working with any custom fields assign to pages. When I update custom fields for custom post types it works fine but not with pages. Is there a version I am supposed to be using? I cannot find the beta 2.3 b3 anywhere as listed in the documentation.

UPDATE: Any custom field that uses the "Visual Editor" field does not save. All others save.

#1087104

Hi, you should be using the latest stable Toolset plugins and the latest stable Gutenberg plugin:
Types 3.0.7
Views 2.6.3
Toolset WooCommerce Views 2.7.7
Gutenberg 3.6.2

I'm able to replicate this issue myself with any post type, so I think we have a glitch in the Gutenberg integration. The text tab seems to have some issues as well, especially when more than one WYSIWYG field is on the page. I will escalate this to my 2nd tier support team for further investigation and let you know what I find out.

#1088382

Okay it looks like our team is aware of the compatibility issue between Gutenberg and WYSIWYG custom fields, and we have an internal ticket in place to solve this problem. I will continue to update this ticket as I receive more information. Thanks for the early testing report!

#1090304

Our developers have let me know this issue will be resolved in the next release of the Types plugin. I'll keep you posted here as I receive more information.

#1109542

Hi, Types 3.1 is now available for download on our site and will soon be available for automatic update. Please update to Types 3.1 and let me know if you continue to experience this Gutenberg compatibility problem.

#1143702

So I am using version 3.1.2 and the WYSIWYG field is still not showing in my PHP template using

<?php echo types_render_field('services-text'); ?>