-
Notifications
You must be signed in to change notification settings - Fork 383
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
Version 0.6 get_support_errors() filter? #867
Milestone
Comments
@ktmn I have written up a proposal for what I think would be a better solution than adding a new filter: #837 (comment) Please review. |
Looks good |
Works well, thank you |
@ktmn can you share your code that mutates |
Yeah that works, replaces my custom implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have previously provided support in a theme for having a chosen page as AMP front page by manually changing the global WP_Query, setting proper template and calling
amp_prepare_render()
when applicable.0.6 introduced a problem when trying to render an AMP front page that is also the main front page due to this code here:
It forces the AMP to be disabled in the metabox and redirects to canonical when visiting it.
I think if the
AMP_Post_Type_Support::get_support_errors()
return array had a filter I could just unset the'page-for-posts'
and'page-on-front'
error values and would be able to keep the support for front pages.The text was updated successfully, but these errors were encountered: