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

User Invalidation Not Respecting `qcAC` #401

Closed
jaswrks opened this issue Jan 19, 2015 · 2 comments
Closed

User Invalidation Not Respecting `qcAC` #401

jaswrks opened this issue Jan 19, 2015 · 2 comments
Assignees
Labels
Milestone

Comments

@jaswrks
Copy link

@jaswrks jaswrks commented Jan 19, 2015

In Quick Cache Pro, the qcAC variable is not respected properly whenever a URL contains a query string and a user is currently logged into the site. If a site owner or plugin developer wants to pass ?qcAC=1 to explicitly allow the URL to be cached (even though it contains a query string), this should be honored with user-specific caching also.

Currently, what happens is that qcAC is ignored if user caching is enabled and a user is logged into the site with a URL that contains qcAC=1. It's an edge case, but it was preventing me from completing a portion of my work to bring ZenCache compat. in AJAX queries performed by WPKBA.

@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 19, 2015

Next release milestone:

  • Bug Fix (Pro): Fixed a bug where the qcAC variable (used to force-enable/disable GET Request caching) was not respected properly whenever a URL contained a query string and a user was currently logged into the site. Props @jaswsinc. See #401.
@raamdev raamdev closed this Jan 19, 2015
@raamdev raamdev removed the ready to merge label Jan 19, 2015
@raamdev
Copy link
Contributor

@raamdev raamdev commented Jan 30, 2015

The fixes applied from this issue have been released today with v150129:

  • Bug Fix (Pro): Fixed a bug where the qcAC variable (used to force-enable/disable GET Request caching) was not respected properly whenever a URL contained a query string and a user was currently logged into the site. Props @jaswsinc. See #401.

See the v150129 announcement post.


This issue will now be locked to further updates. If you have something to add related to this Issue, please open a new GitHub Issue and mention this one (#401).

@wpsharks wpsharks locked and limited conversation to collaborators Jan 30, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants