Quick Cache caches user info so new login is hooked to someone else's account.

[Marfisk]

I support an eStore/eMember Word Press site, and my client added the Quick Cache plugin to increase load times. Almost immediately, she had reports of people logging in, being authenticated, and having someone else’s name on the Welcome bar, and even worse, someone else’s information in the Profile page. Since she hadn’t told me about adding the plugin, I had to figure this out backwards until I found the plugin and asked her when she added it. However, two things:

1) It would be great if an update could prevent the userinfo from being used across sessions (perhaps by storing a session key and validating the user info against it?)

2) Is there a place where incompatible plugins are listed with level of severity? Once I knew the answer, I was able to find other issues with Quick Cache, but none that specified the sharing of user information (the profile reveals their email, which is not a good situation)

[kodeexii]

Salam n Hola Marfisk,

I am also using Quick Cache.

Here is what I have added in the No Cache URI patterns setting for Quick Cache.

/wp-content/plugins/wp-cart-for-digital-products

/wp-content/plugins/wp-affiliate-platform

/wp-content/plugins/wp-eMember

This should prevent any caching of pages coming from the above urls.

Try it out. It might solve your problem.

[blogviet]

[Marfisk]

Thanks, kodeexii. My client decided to turn off the caching software, but I’ll keep this solution in mind if that changes. Sorry for the late reply.

[Author]

Posts