Daniel Iser

@guy101 – Sorry for the confusion, basically if you only used the shortcode our upgrader is crashing for some reason.

I have a fix coming but its almost 5am here and I need to get some sleep. I have my team looking over the solution to hopefully make sure we don’t miss anything or cause any side effects.

We are also adding a step to save a backup file prior to processing migrations going forward so there won’t be any concerns.

Also as of now there were no migrations or changes to the shortcodes, so if that is all you used it for before, they should work as expected even if upgrades haven’t completed yet.

@henro2k, @guy101, @liebberger

Can everyone confirm they were not using the Global Restrictions prior to v2 found under Settings -> Content Control. For example if you primarily used the [content_control] shortcode or widget controls?

I’ve had 3 other similar cases I’ve studied and just found that all actually had 0 restrictions to migrate and that is where it was getting stuck.

@kionae – Ok so for another user I found that they had a theme/plugin that was making post queries before init action. This effectively made our rules init run earlier than your tags are being added to the pages.

The temporary fix while I investigate why those other plugins do what they do was to remove our filters early on and readd them back just before we normally would expect them. This may result in some content not protected on some sites, but that is unlikely for most simpler setups:

remove_filter( 'the_posts', [ \ContentControl\plugin('Frontend\Restrictions\QueryPosts'), 'restrict_query_posts' ], 10, 2 );

add_action( 'init', function () {
	add_filter( 'the_posts', [ \ContentControl\plugin('Frontend\Restrictions\QueryPosts'), 'restrict_query_posts' ], 10, 2 );
} );

If this works for you, it likely also means you have similar. Can you tell me what plugins your using, would BuddyBoss be one of them by chance?

Can you confirm something for me, does changing this line in your code make it work?
add_action( 'init', 'add_taxonomies_to_pages', 9 );

If so I have a fix coming that should hopefully fix it.

As I suspected it seems to have been all about timing.

Understandable. This isn’t the only report of similar nature, so I’m trying to track it down quickly. Strangely we should support that out of the box as our rules are dynamically generated based on the existing post types & taxonomies.

I’m wondering if this is happening in a scenario where the code you have to add tags to pages isn’t running or is running too late (or ours is running too early).

Can you install a plugin by chance?

This is a tool we built for testing & troubleshooting migration issues during the build of v2.

https://github.com/code-atlantic/content-control-migration-tester/releases/tag/v1.1.0

Specifically it adds an menu to the admin toolbar with options to Export v1 Data and Import v1 Data. You can uninstall it right after, and you can see the source on github.

It might help you can export the settings your using so I can try to replicate as closely as possible.

You could either paste the contents here, or submit a ticket at https://contentcontrolplugin.com/support/ with the contents of the file or attaching it.

@kionae – Sorry to hear that, happy to help.

Can you copy/paste the custom code used to register the categories functionality from your theme here?

I need to determine why it shows up some times and not others in our systems.

Further if you’d like you can follow the guide here, and send a token via the support form I will be happy to check out the site directly.

@heartitwebdesign – Ugg, sorry to hear that.

For reference can you give me the version of PHP & WP you have currently.

Rest assured I will be working to smooth out all the kinks today.