Skip Navigation

[Resolved] Toolset forms Parent Selector Fields empty, gibberish in HTML source

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.

Our next available supporter will start replying to tickets in about 0.37 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 1 reply, has 2 voices.

Last updated by Luo Yang 1 year, 10 months ago.

Assisted by: Luo Yang.

Author
Posts
#2535959
Screenshot 2023-01-17 at 10.20.06.png

Use a Toolset Form to create/edit posts that have a Parent Post (one to many).
Expecting the (generated by forms default) parent post selectors to allow me to select parent posts.

Instead I am presented with a vanilla selector (expecting select2 actually), that is empty, even there are parent posts connected and available.
Source HTML of the Select is gibberish, see screenshot.

Toolset Types 3.4.17 3.4.17 October 31, 2022 Release notes
Toolset Blocks 1.6.5 1.6.5 December 15, 2022 Release notes
Toolset Forms 2.6.14 2.6.14 December 14, 2022 Release notes
Toolset Access 2.8.15 2.8.15 December 14, 2022 Release notes

Debugging this found plugin "Email Address Encoder" by hidden link (https://wordpress.org/plugins/email-address-encoder/) to be causing the issue in form of a conflict.
Deactivating that plugin resolves this issue. Somehow they are messing with Toolset's Forms Select Parent Field.

Not sure you still do compatibility outreach. If so, it would be appreciated if you can look into it.

#2536343

Hello,

Unfortunately, we can not fix such kind of compatibility issue, it is the plugin "Email Address Encoder" changing the select2 outputs, we can not fix their issue.

You might need to check "Email Address Encoder" plugin author: if it is possible to disable their feature in specific pages.