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 |
|---|---|---|---|---|---|---|
| - | 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)
This topic contains 2 replies, has 2 voices.
Last updated by 6 years, 7 months ago.
Assisted by: Nigel.
Hi Adrian
I tried to reproduce this on the current betas but could not, although it did through up one issue while testing.
You are not using the current Types beta (3.0-b1).
The issue I found was that you could re-use the same slug for a custom field added to a repeating field group if you deleted one and then added another without first saving the field group, but if you saved the field group in between you get the customary warning message that you see in the screenshot, which I have reported.
In neither case was the slug of the repeating field group changed, so I think that must have been a bug with a prior beta version.
By the way, I should make sure you are familiar with the Post Field Control button that you see on the page listing your custom field groups (see screenshot), although it's not new.
From there you can completely remove any reference to a custom field and clean the data from the wp_postmeta table, so that you can re-use slugs when adding new fields if they have been used before.
