Amir Helzer

Types 1.1.5 will have a drag-and-drop interface for reordering repeating fields (not groups).

In the next version, we’re going to look at enhancing the field groups. It will still work with Types parent / child relationship, where field groups belong to a post. We understand the limitations of this, but it also seems that many other users are enjoying it.

However, we are planning to make this relationship optionally hidden and transparent. Meaning, if you don’t care for having a container post, Types will not bother you with having to set it up. You will be able to drag fields to a group and Types will handle the underlying container and relationship.

From a DB point of view, we’re happy with having a container for field groups. This makes querying and using them a lot easier more more robust. We understand the issues with usability and will be addressing them.

Types 1.1.5 is scheduled to go out in about 10 days.

The next Types version, with the other changes I’m talking about here, is about 6 weeks away.

I hope this helps.

This is a WordPress thing and not something that we control in Types.

WordPress permalinks build a hierarchy for pages. Since Types parent / child relationship permits different parents to the same child, there’s no way to make the Types parent in the URL.

Just to make sure we’re all on the same page, Types settings are stored in the wp_options table. The best way to move a site is to export the database entirely.

If you’re doing something else, please let us know what.

I hope that the temporary fix is working for everyone here. The problem has been fixed in the code and updated in the current version.

This is coming in Types 1.1.5, hopefully next week. You’ll have a nice drag-and-drop interface for repeating fields. Should have been there from the start, but better late than never ??

I’ll write about this new version in our blog, as soon as it’s ready:
https://wp-types.com/category/blog/

I’m marking this as resolved, as this is most likely not an issue with Types. If you can reproduce this with just Types and no other plugins, please let us know.

So, the exact same call, with the exact same post type that worked before is not working for you anymore?

That’s strange. We use that call intensively in our own sites and it’s working exactly the same.

Any chance that something else has changed too?

I suggest that you create a small test site and check just this, with very basic data. There might be a new conflict coming from something else that has also been updated on your site.

You should do this test with the default WP theme and no other plugins.

We’re not sure. This sort of change requires deep testing. We have it on our list of new features, but haven’t started on it.

I’m writing in our blog when new versions are available and describing all new features. You can subscribe to the blog and get these updates directly:
https://wp-types.com/category/blog/

That blog is mostly intended for version updates, so if you subscribe to it, you will receive only relevant messages.

We got your contributed code and have added to our todo list. We’ll post in our blog when this is added to Types.

Thanks for letting up know. I’ll mark as resolved.

Bruce’s answer should make this work. Please let us know if you need any more help.

You’re right about this. I’m adding it as a future feature request, so that you can setup sites and manage everything from the plugin admin, without going through the post edit screen to finalize the setup.

We’ll just add a numeric ‘order’ field in the post edit. It’s not going to be very ‘stylish’, but will allow you to control things when you setup the site.

I’m marking this as resolved, as it’s not a bug, but more of a feature request. Like Srdjan wrote, you can change the default status of comments for new post types in the Types editor. Let us know if you need any help.

I think that this topic is resolved, as no change in Types is required.

petegale, this seems not directly related to Types support, as it’s more of a generic WordPress query support question. I’m marking it as resolved, as there isn’t anything that we need to update in Types.