You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2022. It is now read-only.
AB Blocks Pro (Beta) seems to be registering a Portfolio Items custom post type of it's own. It's frustrating I now see 2 "Portfolio Items" in the dashboard.
Ideally the block would use the existing portfolio CPT, but short of that, there at least ought to be a user friendly way to disable the duplicate without resorting to code.
At the very least it should go away when the portfolio block itself is disabled in the block manager. I don't think that's a very discoverable or expected way to get rid of it, since I suspect most people wouldn't even know the source of it was AB Blocks Pro, but I guess it's an option.
FWIW, yes remove_action( 'init', 'atomic_blocks_pro_register_portfolio_post_type' );
works but really seems like to technical a hurdle for most on something like this.
The text was updated successfully, but these errors were encountered:
@jb510 thanks for taking the time to test and give feedback. This is the sort of feedback we want in the beta. I agree that we should have an easier way to opt out. I'll add this to our todo list and see if we can get an option added in an update soon.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AB Blocks Pro (Beta) seems to be registering a Portfolio Items custom post type of it's own. It's frustrating I now see 2 "Portfolio Items" in the dashboard.
Ideally the block would use the existing portfolio CPT, but short of that, there at least ought to be a user friendly way to disable the duplicate without resorting to code.
At the very least it should go away when the portfolio block itself is disabled in the block manager. I don't think that's a very discoverable or expected way to get rid of it, since I suspect most people wouldn't even know the source of it was AB Blocks Pro, but I guess it's an option.
FWIW, yes
remove_action( 'init', 'atomic_blocks_pro_register_portfolio_post_type' );
works but really seems like to technical a hurdle for most on something like this.
The text was updated successfully, but these errors were encountered: