Parent select field in a post form for child posts not working

This thread is resolved. Here is a description of the problem and solution.

Problem:
A Form publishes/edits child posts from a one-2-many relationship, and includes a field to select the parent post. The parent posts are not loading.

Solution:
Client identified a conflict with the plugin "email address encoder" (https://wordpress.org/plugins/email-address-encoder/).

This support ticket is created 6 years, 4 months ago. 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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	7:00 – 14:00	-
-	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	15:00 – 16:00	-

Supporter timezone: Europe/London (GMT+00:00)

Tagged: Forms with post relationships, Toolset Forms

This topic contains 2 replies, has 2 voices.

Last updated by tylerG 6 years, 4 months ago.

Assisted by: Nigel.

Author

Posts

August 22, 2018 at 9:46 pm #1089657

tylerG

I have a one-many relationship between events and buildings. I went to add the relationship field into a post form for editing events, like in this article: https://toolset.com/documentation/post-relationships/selecting-parent-posts-using-forms-create-child-items/

The problem is it won't pull in any of the buildings.

Here are the steps I took. hidden link

August 23, 2018 at 8:29 am #1090151

Nigel

Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Tyler

I watched the video and took a look at your site, and I can see the issue.

I double-checked on a local test site that this should be working correctly, and on my test site it does.

There are no JS errors in the console on the page where you are editing the event, but are there any warnings or errors in your PHP logs?

If not we'll need to try a no-conflict test, which means switching theme to twentyseventeen and disabling all non-Toolset plugins.

It should work then, and if so it should be possible to identify where any conflict is coming from by a process of elimination.

Do you have a staging site to run such a test?

August 23, 2018 at 4:23 pm #1090380

tylerG

Found the issue! It was the email encoder plugin: https://wordpress.org/plugins/email-address-encoder/