Skip Navigation

[Resolved] Intermediary post custom field values copied to other intermediary posts.

This support ticket is created 2 years, 10 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
- 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/Karachi (GMT+05:00)

Author
Posts
#2073995
ticket-1.jpg
ticket-2.jpg
ticket-3.jpg

So. I had a client delete a post that was involved in a post relationship and had the intermediary post custom field values get moved to another relationship post. They deleted one of their menus (as in food menu ) and the price of food items for that menu were added onto another post relationship between those food items and another menu they are on. I hope that makes sense.

Here is an image that shows what I mean. Under Price and Type Radios you can see that there are comma separated values. The first one is the correct value, but the second one is the value that was used for that food item on a different menu, which is the one that was deleted. Why do those values carry over to another relationship? (ticket-1.jpg)

Here's another screen shot to show you that I can't just remove the second value that appears. I deleted all of the intermediary posts for the deleted menu but this didn't do anything to fix the other things. (ticket-2.jpg)

Finally, here is a screenshot of how it is being displayed on the site. (ticket-3.jpg)

Link to a page where the issue can be seen:

hidden link

I expected to see:

Only one price value should be displayed. The one that was set as the price within the relationship's custom field.

Instead, I got:

Multiple price values: the correct one and the one that appeared on the deleted menu's post relationship with the food items that used to be on it.

#2074361

Waqar
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting us and I'd be happy to assist.

I've performed some tests on my website, but couldn't reproduce this behaviour. The custom field values from the intermediary post didn't carry over to a different post when one of the posts in the relationship was deleted.

I created two post types "Menus" and "Dishes", connected them through many-to-many relationship and added some custom fields to the intermediary post.

After filling some entries with data, I tried deleting the "Menus" and "Dishes" post which were part of relationships, and the custom field values from the associated intermediary posts were not added to the other posts.

Can you please share temporary admin login details, so that I can see exactly how these post types, relationship and custom fields are set up? Please also share the steps that were used to delete the post.

Note: Your next reply will be private and though no changes will be made on your website, please make a complete backup copy, before sharing the access details.

regards,
Waqar

#2076065

Waqar
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for sharing the admin access.

Since the issue is not reproducible on a test website with a similar setup, it seems that something specific to your website is involved.

I see a number of plugins (including Toolset plugins) and the Divi theme are not updated to the latest versions. Can you please update all the plugins and the theme and then test again by deleting any dummy post?

In case the issue still persists, I'll need your permission to download a clone/snapshot of your website, to investigate this on a test server.
( ref: https://toolset.com/faq/provide-supporters-copy-site/ )

This way, your live website won't be affected.

#2083579

My issue is resolved now. Thank you!

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