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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. 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/Karachi (GMT+05:00)
This topic contains 4 replies, has 2 voices.
Last updated by michaelO-8 4 years, 2 months ago.
Assisted by: Waqar.
Tell us what you are trying to do?
I am currently using repeated fields in child posts. For example, in a post form, users can add multiple locations (NY, MO, etc.). Then, on the parent page, these values are displayed. This seems to work fine as long as I don't update the parent page.
However, upon updating the parent page, additional/repeating fields seemed to get deleted. If a user inputted NY and also MO, only the first value, NY, would still be stored and be displayed.
I would like for users to be able to input multiple fields, but it seems like I am not supposed to use repeating fields in this way. I did notice the warning "Repeating fields should not be used in child posts. Types will update all field values." Is there a workaround, best practice or other solution?
What is the link to your site?
Here is a link to a sample page on the test site: hidden link
Thank you, this solved my issue! Before I close this, I would like to learn a little bit more about the older implementation of the post-relationship feature vs the newer version.
1. Does the newer implementation handle this situation differently?
2. If I go to "relationships" and click the "run migration" button, will that give me the new implementation?
3. Are there any risks that old data will get corrupted/have issues after the migration? I don't see any downside to running the migration as long as old toolset data will be safe.
