Daniel Iser

@junxiu6 We have a tool that lets us test various states and transitions for the upgrade process. Built it to try and not have any of these issues.

But I have tried both with the tool and manually and cannot replicate that specific issue.

Would it be possible to get access to the site or a staging site to see the issue and troubleshoot?

That said, are you also saying downgrading, then upgrading worked fine after?

@thomascharbit – Sorry to hear that, this function seems to be problematic when it shouldn’t be.

1. I just added an early bail to restriction checks for WP CLI, sorry didn’t see that coming.
   
   The function in our code in question is is_frontend() and checks a bunch of WP things such as is_rest(). But because that can run on any WP_Query call, to filter restricted posts, somehow it sometimes gets called before $wp_rewrite is ready (plugins_loaded is the only hook I’m aware of, and shoulnd’t be used for post querying really, but what can we do).
   
   v2.0.10 will have the CLI fix I believe that should help with your commands.
2. I also made our query filters not run prior to plugins_loaded 9999999 which hopefully means everything is done by then, if not try this filter:

add_filter( 'content_control/query_filter_init_hook', function () {
    return 'wp_loaded'; // Try setup_theme, after_theme_setup, init or wp_loaded
} );

Look for v2.0.10 tomorrow some time. Keep me posted.

@junxiu6 – do you use browser extensions of some kind that may be blocking things from loading? Just to be sure, you can try in a private browser session (usually they are without extensions).

Also with the health check plug-in active you CAN activate troubleshooting mode. Activating the plugin itself won’t do anything helpful.

with it active go to the Plugins page and next to Content Control you will see Troubleshoot.

Click that and see if the issue is still occurring. If so then you can activate other reenable other plugins a few at a time and retest. When you see it break again one of the last plugins you enabled will be the one we need to investigate.

@nobodee – Hope all is well. Let us know if your still having issues or if the fixes we pushed helped. Would love to get your review restored :).

@lewisburgess79 – If your still having issues feel free to mark this as unresolved again.

If not please take a moment to rate & review the plugin and or support to spread the word.

@junxiu6 – Hmm, that shouldn’t be possible, but I’m happy to try and help.

From the message it seems WP scripts are not loading specific wp files that we depend on, but if they weren’t available WP usually would prevent our code from loading as well. Clearly ours is there, so WP thinks the others are too.

What version of WP do you use?

Can you install the Health Check & Troubleshoot plugin, then use the Troubleshooting mode on just our plugin to see if the issue goes away? If so activate the other plugins one at a time until it comes back so we can find which one is conflicting.

@lukiano880 – Hmm, I was testing with ACF on a separate issue the other day, can’t say I ran into this but I’m happy to help.

The first thing to do is check your Content Control logs, available on the settings page). If you see missing rule notices it likely means something on your site is running post queries before your post types are officially registered. Since we filter post queries, this is forcing our rules to be generated before your types are ready.

You can try this fix here, which will prevent our query filters from running until much later. If you don’t see any adverse side effects its probably safe to leave it.

That said I’ll do some digging and see if maybe there is a more elegant solution.

add_filter( 'content_control/query_filter_init_hook', function () {
    return 'init'; // Try setup_theme, after_theme_setup, init or wp_loaded
} );

• This reply was modified 2 years, 8 months ago by Daniel Iser.