I was setting up a repeatable field group and hit a brick wall when I wanted to give website visitors the ability to edit the repeatable fields.
I ended up going with a standard parent child relationship because I was able to do everything I needed with that. Which brings me to my point, why even have repeatable field groups? It wasn't any easier to set up and in my head it worked exactly the same.
I'm sure I'm missing something here but if I could move the admin menu item for child post types as a sub item to their parent, that would be the best solution for me.
Is there a feature of RFG that I'm overlooking?
Which brings me to my point, why even have repeatable field groups?
Right now, repeating field groups do behave very much like child posts in a parent/child post relationship. In fact, RFGs are connected to their corresponding post in a parent/child relationship. RFGs are not listed as a post type, but they are technically handled as such. Our roadmap includes plans to make RFGs more closely integrated with the parent post. That means tighter integration in Views searches, so you can search for parent posts by fields in related RFGs. It also means tighter integration in Forms, so you can manage RFGs along with their parent posts in a single Form. Right now, those features are still pending as RFGs are still relatively new.
I'm sure I'm missing something here but if I could move the admin menu item for child post types as a sub item to their parent, that would be the best solution for me.
This isn't an option in Types right now, but there are 3rd-party plugins that claim to be able to manage wp-admin menus. You might have luck manipulating these menus using another system. You can also request this feature by creating a new ticket in the forum using the "Suggest an improvement" option.
Is there a feature of RFG that I'm overlooking?
One feature I can think of is that a RFG can include a nested RFG, and you can manage multiple nested RFGs from within the main parent post. That's not really possible with nested child posts, where you would only have the ability to edit the custom fields of the top-level child post from within the parent post editor.
I was setting up a repeatable field group and hit a brick wall when I wanted to give website visitors the ability to edit the repeatable fields.
In simple cases, your Users can modify RFGs on the front-end now using Edit Post Forms. The stipulations are:
- You can only edit one row of the RFG at once time, in one Form.
- Nested RFGs are not supported.
If you'd like to try this out now, the process is similar to setting up an edit post Form. Create a new Content Template or Template Layout and insert an Edit Post Form. This Form should be set up to edit the correct RFG type. Create a View of this RFG filtered by post relationship, set by the post where this View is shown. In the Loop, insert custom fields from the RFG and an Edit Post link using the Fields and Views button (this will be moved into the Forms menu in an upcoming plugin release). In the popup dialog, select the CT or Template Layout that includes the edit post (RFG) Form. Then insert this View of RFGs in the template for the parent post. You will see a list of RFGs with a link to edit each row independently. Our goal is to clean up this process so it's more like the RFG editor in the wp-admin post editor.
Thanks Christian, that removes a lot of confusion.
