Release Candidate Bug - Not Saving Value

Ce fil est résolu. Voici une description du problème et la solution proposée.

Problem:
Checkboxes assigned to a Post Type which is used in a M2M Legacy Relationship, are not editable on versions 2.3, 2.3.1 and 3.0(not migrated).

Solution:
Update Toolset

This support ticket is created Il y a 6 années et 6 mois. 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.

Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.

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)

Marqué : Post-relationship

Ce sujet contient 3 réponses, a 2 voix.

Dernière mise à jour par larryB-3 Il y a 6 années et 6 mois.

Assisté par: Beda.

Auteur

Publications

mai 11, 2018 at 2:37 pm #876783

larryB-3

When using many-to-many and using an intermediary customer field called "Status" between "Property" CPT and "Homeowner" CPT.

Here's a video of a bug where this value is not saving. lien caché

mai 11, 2018 at 3:12 pm #876860

Beda

I have watched the video and was able to replicate the BUG after i had a look at your site as well.

Please see the post lien caché - I had to edit both it's related posts fields to see the issue.

I reported this to the developers.

Thank you for the heads up.

BTW; the issue happens only after you add more than one post in the related post table.

mai 15, 2018 at 1:51 pm #889141

Beda

This will be solved in the coming release of Toolset Types.

We do not ship Errata for Beta releases, but the stable release should not be to long away.

mai 15, 2018 at 2:30 pm #889252

larryB-3

Thanks! I look forward to seeing the bug fixed in the next version.