Consider making 'guest-authors' CPT private

[danielbachhuber]

It doesn't need to be public, I don't think, and causes problems when it does: https://github.com/facebook/wordpress/issues/390

[alpha1]

@danielbachhuber I have come back to this problem as it still bugs the hell out of me, and this seems to work as a solution.

'public' => false, //changing to false
'show_ui' => true, //adding this

Simply changing public to false, I am unable to add a new guest-author, but this removed the facebook metabox, does not post to facebook.

[rebeccahum]

The link from the original post doesn't work anymore. Does anyone have any context on this issue?

[TheCrowned]

So, the CPT for Guest Authors is basically already private. The value of public has the function of indirectly setting a the following other arguments: exclude_from_search, publicly_queryable, show_in_nav_menus, show_ui. We are already giving a value explicitly to all of them, except show_ui.

Thus, currently changing the value of public only has the effect of setting show_ui. So yes, we could get rid of the public arg and set show_ui explicitly to true, but this would not affect the behavior of anything in any way :)

(register_post_type documentation)

[GaryJones]

I agree with:

'public' => false, //changing to false
'show_ui' => true, //adding this

Right now, "Guest Authors" appears as a post type that one can configure Yoast SEO for, for instance:

Making the change removes that, since it's only querying for public post types.

I'd suggest adding a filter to the registration args so that if someone did want to and them (like making them publicly_queryable for some reason), they can.