Ensure front-end hooks are only registered on main query #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
It has been reported that the Benevolent Pro theme makes a sub-query prior to the main query. This unsets the value of
get_query_var( 'page' )
and thus the CiviCRM basepage fails to render CiviCRM content. Given that other themes might do something similar, we should accommodate this sort of behaviour. The solution is to ensure that front-end hooks are only registered on main query.See the issue on Lab for further details.
Before
Making a sub-query prior to the main query unsets the value of
get_query_var( 'page' )
and CiviCRM content fails to render.After
Making a sub-query prior to the main query no longer unsets the value of
get_query_var( 'page' )
and CiviCRM content renders as expected.Steps to reproduce
Add this to a plugin or
functions.php
file:Boom.