Skip to content
New issue

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

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

Already on GitHub? # to your account

Conflict with jQuery Categories List Widget plugin #174

Closed
KTS915 opened this issue May 24, 2014 · 8 comments
Closed

Conflict with jQuery Categories List Widget plugin #174

KTS915 opened this issue May 24, 2014 · 8 comments

Comments

@KTS915
Copy link

KTS915 commented May 24, 2014

Quick Cache Pro will not cache anything when the jQuery Categories List Widget plugin (see http://wordpress.org/support/plugin/jquery-archive-list-widget) is activated. This is caused by two factors.

First, the jQCLW plugin makes GET requests, but this can be overridden by the setting for that purpose in QCP, so this is not really a problem.

Unfortunately, all that then happens is that the second problem manifests itself, for the message produced by QCP in View Page Source just changes to ""

I must admit I cannot see what in the jQCLW plugin is causing this problem. Any ideas?

@raamdev
Copy link
Contributor

raamdev commented May 26, 2014

@KTS915 I'm not able to reproduce any issue with the jQCLW plugin and Quick Cache.

Could you please provide me with a list of exact steps to reproduce this issue?

Also, have you tested this in a fresh WordPress install with no other plugins (to rule out another plugin causing the conflict)?

@KTS915
Copy link
Author

KTS915 commented May 26, 2014

Raam,

Thanks for getting back to me! These are the steps:

I am using a slightly modified version of the jQCLW plugin, together with Quick Cache Pro and s2Member Pro. In Quick Cache Pro I have selected the option to cache for logged-in users (maintaining a separate cache for each user).

When I look at View Page Source, I get the message I reported.

Just to be sure, before reporting this issue, I disabled all other plugins, and replaced my modified version of jQCLW with the current version available in wordpress.org. I got the same result. As soon as I disable jQCLW, caching works.

@raamdev
Copy link
Contributor

raamdev commented May 26, 2014

@KTS915 Here's what I did to try and reproduce this on a fresh install of WordPress (v3.9.1) with Quick Cache Pro (v140104) and jQuery Categories List Widget (v2.2.3), using the default Twenty Thirteen theme:

  1. Installed and activated Quick Cache Pro; enabled caching in Enable/Disable; configured Logged-In Users with "Yes, and maintain a separate cache for each user"; configured GET Requests with "Yes, I would like to cache URLs that contain a query string"; Saved Changes
  2. Installed and activated jQuery Categories List Widget
  3. In Dashboard → Appearance → Widgets I added the jQuery Categories List Widget to my sidebar, gave it a title and left the default options; clicked Save
  4. Logged out and visited my test site. Loaded several different pages, looking the source code for each one. On each page, I see exactly what I'd expect:

screen shot 2014-05-26 at 4 39 42 pm

@KTS915
Copy link
Author

KTS915 commented May 26, 2014

OK. I am running the Release Candidate of Quick Cache Pro (because that solved the Nav Menu Roles issue). Sorry, I should have made that clear.

When you say you logged out, I assume that you were viewing your page source as a logged-out user. I am using this on a membership site; it isn't possible to see any post where the jQCLW widget appears without being logged in.

I also think you need to try it with s2Member Pro because (a) this is what transforms the site into a membership site and (b) QCP should be working with s2Member's custom roles and not just WordPress's default roles. Perhaps it is the interaction between jQCLW, s2Member and the QCP Release Candidate that produces the problem.

@raamdev
Copy link
Contributor

raamdev commented May 27, 2014

@KTS915 writes...

it isn't possible to see any post where the jQCLW widget appears without being logged in.

So you were using s2Member when you were testing this? I ask because you previously stated that you "disabled all other plugins, and replaced my modified version of jQCLW with the current version available in wordpress.org." So I was working with the understanding that you were recreating this in a clean WordPress install, with only jQCLW + Quick Cache Pro.

I need to know exactly what steps are required to recreate this issue, that includes any mention of s2Member protecting content, etc.

I'll play around with this a bit more, this time adding s2Member to the mix, to see if I can recreate this. Any additional info you can provide would be helpful.

@raamdev
Copy link
Contributor

raamdev commented May 27, 2014

I have confirmed that this issue has nothing to do with the jQuery Categories List Widget plugin. As far as I can tell, it's actually an issue with s2Member.

s2Member is setting the QUICK_CACHE_ALLOWED constant to true when viewing a protected page. I'm not entirely sure why this is, if there's an actual good reason, or if it's a bug. I've opened a new issue on the s2Member repo (wpsharks/s2member#172).

@KTS915 Thanks so much for reporting this!

@raamdev raamdev closed this as completed May 27, 2014
@KTS915
Copy link
Author

KTS915 commented May 27, 2014

Thanks, Raam!

When I said above that "I disabled all other plugins," that was after I had said that "I am using a slightly modified version of the jQCLW plugin, together with Quick Cache Pro and s2Member Pro." I meant the "all other" to refer to all others apart from those three plugins.

I apologize for not being clear enough, and I really do appreciate your investigating this.

I must admit, though, that I am surprised by your conclusion because, for me, QCP will cache when I disable jQCLW but keep s2Member running, and it also caches on another site with s2Member running but which doesn't use jQCLW at all. On that one, mind you, it caches only posts and not pages, but I had assumed that that was expected behavior.

Anyway, thanks very much again!

@raamdev
Copy link
Contributor

raamdev commented May 27, 2014

The problem persisted for me even after I disabled jQCLW, so that tells me it's not jQCLW at all.

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

No branches or pull requests

2 participants