Hey there,
unfortunately that works fine for one of the post types, but does not work for another. So for me it seems, there has to be a problem within Toolset, if the other plugin works fine with one post type, but not with another?
You can see all post types here (green works with copier, red does not):
hidden link
I checked all settings and all have the REST_API enabled and the custom fields have all the same slugs on all sites of the network.
Hi, the old ticket has been closed and cannot be reopened so I split off a new ticket for you.
So for me it seems, there has to be a problem within Toolset, if the other plugin works fine with one post type, but not with another?
It sounds like you're saying the post is cloned but not the custom fields for this additional custom post type, am I correct? Toolset registers custom post types and custom fields in a predictable, replicable way each time, so I'm not sure why it would be exhibiting different behavior across these cases. It could just as easily be a configuration issue where the post type options are responsible for different behavior across the various post types, or a problem in the cloning plugin that only handles one additional custom post type but not multiple custom post types. Hard to say without understanding the mechanism for cloning posts built into that plugin - their support team would be better qualified to identify a problem here since Toolset provides no built-in features for cloning posts and their field values across a multisite network.
1. Have you compared all the options of these post types, like publicly_queryable, exclude_from_search, query_var, and can_export?
2. Are the post type slugs identical across sites?
3. What about Access Control - are you using Access Control to restrict permissions to these field groups on any of the networked sites?
4. Are there any data-dependent settings for these uncopied field groups , for example, the field group is only shown when a specific Content Template is applied to a post, or there is some other conditional logic applied to these fields? You could find that in Toolset > Custom Fields > Post Fields when you edit the field group containing the missing fields.
5. Have you examined the server logs to see if any server-side errors are thrown when the post is cloned?
