Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

get_supported_post_types() shouldn't fire on init #2

Closed
danielbachhuber opened this issue Sep 22, 2012 · 2 comments
Closed

get_supported_post_types() shouldn't fire on init #2

danielbachhuber opened this issue Sep 22, 2012 · 2 comments
Milestone

Comments

@danielbachhuber
Copy link

Because it does, $this->post_types becomes set without potentially additional post types that just happen to be registered after.

It doesn't look like that class variable is ever used, so it would probably be better to remove it altogether.

Also, the taxonomy should be registered with post types on late init to ensure all post types have been registered.

@brettshumaker
Copy link
Contributor

@sboisvert
I believe this was mostly addressed by a0beb6d which added a priority of 99 to the init hook that calls Zoninator->init().

It doesn't look like that class variable is ever used

Correct, I don't see a need to keep it around unless we're interested in keeping backwards compatibility for anyone who has code relying on that class variable being there.

Thoughts?

@sboisvert
Copy link
Contributor

unless we're interested in keeping backwards compatibility for anyone who has code relying on that class variable being there.

I guess folks could be using it.... If we don't need to change it let's not :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants