yoav.aner

Thanks for keeping me posted. I’ll try to update the FAQ to reflect this, so others can avoid this.

Ajaxize adds a div around the data that your function returns, so any styling issues can be corrected by CSS rules.

I did notice that your function returns some empty space around the span with the actual data. Perhaps that’s the reason you’re seeing some padding?

In any case, this is not something that I can help much with. Take a look at the actual page using your browser development tools (inspector on chrome etc), and see which tweaks to either the data that your function returns or to CSS rules would fix this problem.

Thanks for the info.

If you already have a certificate installed, I would personally recommend using SSL everywhere across your website. It increases security and gives people confidence with your website, without really affecting performance as much as people might think.

Just my 2 cents.

Hi joshuaiz,

As far as I know this plugin should work seamlessly with HTTP/HTTPS. Perhaps the reason you see the enqueued scripts served via http because of some kind of caching?

Cheers
Yoav

Hi evo252,

Nice to hear from you again, and thanks for your kind and positive message.

Unfortunately I don’t think what you’re trying to achieve is very easy with Ajaxize. As you said, it ajaxifies the function and the function is shared across all posts. Ajaxize does not support passing any parameters for a variety of reasons, and I don’t plan to have this feature since it will make things much more complicated. Simplicity is one of my goals, even if it means less functionality.

So, it looks to me like you’ll need to write some custom javascript / php code to achieve what you want, or use a counter plugin that supports ajax better. I can’t think of a simple solution to this unfortunately.

Cheers
Yoav

Thanks for the detailed report!

I’ve come across this as well, but it’s tricky to reproduce exactly in order to try to resolve. I’m away on holiday at the moment, so not sure when I’ll have time to address this.

I’m guessing the caching that W3TC applies makes some browsers cache the page longer than necessary, which invalidates the CSRF value. Why it happens only/mostly on Windows/W3TC is an interesting question.

I might remove the CSRF protection entirely, but it’s not the ideal solution for security reasons (although this extra ‘security’ is something debatable since most functions exposed by ajaxize are harmless or not applying any changes, and also parameters are limited making it a difficult targets for attacks anyway).

Alternatively, there might be a more optimal cache settings that avoids this problem, but I haven’t found it. I believe that CSRF tokens expire after 12 or 24 hours. Setting the page to refresh the cache more frequently could resolve this in theory. If you are able to experiment with some cache settings, you might be able to help.

Otherwise I’ll try to take a closer look, but unfortunately I can’t promise exactly when.

Thanks! 🙂