mrhasbean

Thanks for the answer Jim.

They don’t need to be available at the network level or network wide, they just need to be able to be seen even if they’re only defined in the main site. From some tests I did on the weekend I believe the issue is that they’re registered too late in the process for WP Ultimo to “see” them.

By way of explanation, a tool like WPMU Dev’s Content Copier, which works in the Network Dashboard, asks the user to select the blog from which the content will be copied, then it queries and displays a list of CPTs from that blog. It works fine. WP Ultimo, on the other hand, needs to know about the CPTs for the display of two of its settings pages, so although it is using almost identical code to query for the CPTs, it queries for them early in the process and they don’t seem to be registered at that stage, so it never “sees” them.

It seems if the CPTs are registered via the main blog’s theme’s functions.php, WP Ultimo can see them, but due to the manner used by Pods to registered them, they don’t seem to be registered in time for WP Ultimo to know about them.

I suspect I’m going to have to work around the issue by adding “dummy” CPTs of the same type as those used on the child sites to the main site’s theme, hard coded, so that WP Ultimo can see them and allow settings to be created for that post type, which will then match the post type on the child sites. Not exactly elegant, but it should work.

From experimenting over the weekend this is about the only workaround I can come up with.

@alice999 what was the issue if you don’t mind me asking? We seem to have a similar issue on a single site within a multisite network. All others seem to work ok. Very strange.