We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, we hack our way around WP_Query to prevent it from doing the database query.
WordPress 4.6 added a new filter (https://developer.wordpress.org/reference/hooks/posts_pre_query/) that lets you hook in and skip the query by passing in the necessary post objects. This could simplify the Advanced Post Cache code quite a bit.
The text was updated successfully, but these errors were encountered:
I've a long flight tomorrow, which seems a perfect opportunity to work on this.
Sorry, something went wrong.
Since this is open issue is quite old, I'm wondering the same as #12 .. Is this plugin safe to use or will I run into issues like #11?
I'm looking to maybe implement this on a multi-site (running most notably Event Espresso which makes use of extra DB tables).
No branches or pull requests
Right now, we hack our way around WP_Query to prevent it from doing the database query.
WordPress 4.6 added a new filter (https://developer.wordpress.org/reference/hooks/posts_pre_query/) that lets you hook in and skip the query by passing in the necessary post objects. This could simplify the Advanced Post Cache code quite a bit.
The text was updated successfully, but these errors were encountered: