Hey @nurbis,
I seen that before. The problem appears with caching with different plugins.
The encrypted passwords are saved in the database and a use some sort of transient caching (time based caching with automatic expiring), but If the page is fully cached (e.x the full page cache from W3TC) it get some trouble.
I will check that out, but can’t promise it’s available in the newest update.
There are actually so many features I have to rewrite that I can make 3 releases so :-D.
But the next update will add the new captcha solution, maybe you give it a try.
Thread Starter
Nurbis
(@nurbis)
OK, thank you.
And do you know if I can somehow exclude content protector from W3TC caching ? There are filters for paths and urls but I’m not sure what to type on them.
Thank you.
Thread Starter
Nurbis
(@nurbis)
Or is there any setting at Content protector that can help me ? Like Shared Authorization, store encrypted passwords etc. ?
Also if I may ask how it looks with new version of Passter ? 🙂
Hey @nurbis,
sorry for the delay.
You could exclude the page where you use Passster in W3TC.
Say, you include it in your portfolio page and the slug is maybe “portfolio”.
So you could exclude this page from the caching and passster should work fine.
new version:
It’s still in development. I try to add all requested feature AND solutions for several bugs. It should be a big release but take some more time to complete 🙂
Thread Starter
Nurbis
(@nurbis)
Thank for your answer.
You could exclude the page where you use Passster in W3TC.
Problem is I’m using it at almost all my posts :/
But I noticed that I’m having this issue even when I’m logged in (and so the page I see isn’t cached via WT3C), could it still be mixed from W3TC ?