Quick Cache

Hello,

I am wondering if one of your free products will continue to be updated & available, either paid or otherwise? We have been long time users of your Quick Cache plugin for WordPress & noticed that it has not been updated since 2011 & has begun to cause problems on one of our sites. However, in an article on s2member, it would seem that Quick Cache will continue to be supported (http://www.s2member.com/primothemes/).

So, will Quick Cache continue to be updated & supported & if so, will it be included in one of your paid packages or will it still be free? Any info you could shed on this would be appreciated & if I’ve posted in the wrong forum, please just let me know. Was torn between pre-sale & community :-)

Thanks for your time.

Hello Joe,

Yes, the plan is to update them of course, but the thing is, Jason is currently with his head deep in the new s2Member development, so right now they’re giving that all the priority. The rest I leave it to a support rep. ;)

Hope this helps. :)

Thanks Eduan,

So, will a support rep reply here or should I post this in the community forum as well? A similar question was asked months ago by another user, to which you graciously replied, but a support rep never responded.

Thanks again!

You can expect an answer here, since the support reps do check this forum, if I’m not mistaken, the other post was made in the community forums. ;)

Hi Joe.

Yes, Jason intends to keep supporting QuickCache, as far as I know. He probably isn’t aware of any problem with it, and hasn’t released any updates because of that. It’d be good if you could provide more info on the problem you’re having so I can forward it to him to look at.

Thanks. :)

Hi Cristian,

Thanks for the reply. So will Quick Cache become a paid product or remain free?

In regards to the problem I experienced… I am not 100% sure if the problem is with QC or WPTouch(mobile theme), or how they are interacting. Long story short, my mobile theme was displaying on my desktop and clearing the cache remedied the problem. Considering that QC hasn’t been updated since ’11 and isn’t necessarily compatible with the newer versions of WP and other plugins, I was thinking that the problem stemmed from an issue with QC, rather than WPTouch.

WPTouch confirmed my theory, stating that the problem is not with WPTouch, suggesting that I try another caching plugin.

Anyway, this issue drew my attention to the fact that QC hasn’t been updated in a while and there is no longer WP forum support. So, my problem may stem from QC needing an update, or it may not! It would seem that caching played a part in my problem. I am very happy to hear that QC will continue on, in one form or another, I just hope it gets updated soon! That will alleviate my concerns, and I am sure others as well, judging by comments in the WP forums. Thanks so much for your help!!

• This reply was modified 4 years, 4 months ago by  Joe S.

I emailed Jason asking him that. I’ll let you know when I hear back from him. :)

Thanks for the heads up on this thread.

An updated version of Quick Cache will be released late this year, and it will include a paid upgrade as well. That’s all the details I have at the present time.

Regarding the WP Touch issue. Can you please provide me with (or a link to), the details regarding this. Thanks!

Hi Jason,

So good to hear that you’ll be updating Quick Cache!! Thank you for the FREE plugin!! Look forward to checking out the paid version!

Funny you replied this morning as I again woke up today to our site loading the mobile theme on a laptop!

Not sure what’s happening but I am guessing that Quick Cache is not properly ignoring the rejected mobile user agents & therefore rendering cached pages of the mobile site on a desktop, or, perhaps there are other mobile user agents to be added to the list of rejected, that are not presently there, which are being cached by Quick Cache.

I just deactivated the plugin until I can get some sort of resolution. I also ran my thoughts by the folks over at WP Touch about possibly needing additional mobile user agents to reject. Their initial opinion was that QC wasn’t properly rejecting the mobile user agents. We’ll see what they say about my missing mobile user agent thoughts…

I would rather not post any personal site info here, but if you would like, I would be more than happy to email you a few screenshots of the mobile site loading on my laptop, that I took this morning, including page source info. If there is anything else that I can do to help diagnose, please don’t hesitate to ask, it’s the least I can do considering that I have been using your plugin free of charge! I prefer the simplicity & performance of your caching plugin to all others & would like to use it on all of my sites. I need to get some form of caching going again on my main site, as it does receive a decent amount of traffic.

Thanks & let me know if you want me to send you my site info. BTW, here is the list of the rejected mobile user agents that we were using, just in case you were wondering:

w3c_validator
iphone
ipod
ipad
pre
pixi
iemobile
aspen
incognito
webmate
android
dream
cupcake
froyo
blackberry9500
blackberry9520
blackberry9530
blackberry9550
blackberry 9800
blackberry 9780
blackberry 9850
blackberry 9860
webos
s8000
bada

Hi,

I have an update…

WPTouch’s list of mobile user agents was not up to date & did not include the following:

iemobile/7.0
googlebot-mobile
adsbot-google

It would seem that only the ie user agent could impact the caching, but all it takes is one! So, I reactivated QC & updated the mobile user agents. Now, I wait & see if that did the trick. I will let you know if it did not. If you would prefer I post future additional info elsewhere, just let me know!

Thanks for your support, to all involved! I look forward to your QC updates.

Thanks for the update! Yes, please keep us posted. :)