[Bug] Custom fields group assignment is not exported properly

The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.

This support ticket is created 6 years, 11 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: Types plugin, Views plugin

This topic contains 16 replies, has 2 voices.

Last updated by Beda 5 years, 6 months ago.

Assisted by: Beda.

← 1 2

Author

Posts

June 23, 2017 at 10:57 am #540471

Beda

This is planned to get fixed in Types 2.4 (the current issue, not the feature, which I can not state any plans or goals of the Developers yet)

Thank you.

October 19, 2018 at 8:39 am #1130561

Beda

This will be fixed with Types 3.2.

We now store the Content Template SLUG instead of the ID.
BUT already existing field groups assigned to Content Templates will STILL have the IDs stored BEFORE they are saved again.

This is important because just by updating to 3.2, the export/import wouldn't be enough for old field groups to work with the new methods, but you'd need to save them once first.

← 1 2

The forum ‘Types Community Support’ is closed to new topics and replies.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.