V2: W3 Total Cache compatibility

Hello,
thanks for asking! In what way did latest versions break your site? Just to be sure not to commit the same mistake again!

Frankly, I don’t know what it takes to be compatible with W3 (if you know, please let me know, I’m eager to implement it). Anyway, I’ve made my best to make the plugin as lightest as possible, especially on the database side: the plugin doesn’t have a table of its own anymore and, most important, doesn’t store all data in the database but rather computes them on each page load. This may seem way slower at first, but counting words every time instead of querying the database (and updating it every time they’re changed) is far lighter.

It’s quite a challenge to make Post Pay Counter smooth and light because of the considerable amount of data it needs to handle, but I am really trying. I would advise you to wait version 2, it’s a matter of days now: common tasks should be quite faster!

Hope this helps.
Have a nice day,
Stefano

Hi Stefano,

frankly i dont know what it takes to be compatible with caching plugins. I hope i find some time on the weekend to investigate. Or someone else here has a clue.

I only use your plugin for the visit count and for the display of the results to the individual user that hast contributed posts. The calculation of the reward and handling of the payment is done in a custom made plugin (only based on visits of the posts, no word count, no fixed prices).
So maybe updating will not be all that easy for me, since you changed the database design that my custom made plugin relies on.

The earlier update broke the site because the plugin after a simple update via the repository gave some php errors. I did not do a lot of investigation since i had to get the live system up and running as soon as possible.

I am quite sure it is the hell of a challange to make such a plugin lightweight and still keep all the features.

Will it be possible to turn off “expensive” operations like word count if not needed (only keep the stats functionality)?

Thanks for your effort!

Regards,
Stefan

>So maybe updating will not be all that easy for me, since you changed the database design that my custom made plugin relies on

That is sure to happen, also because the plugin doesn’t have a visits counting system of its own and relies on other plugins (enough to specify the postmeta that holds the visits) or Google Analytics.

>Will it be possible to turn off “expensive” operations like word count if not needed (only keep the stats functionality)?
Indeed it will be. In this sense, the plugin will be much more modular.

To use your plugin, it will be necessary to install other plugins (that do the counting)?
Analytics through a plugin?

My theme has a counting also, maybe i can use that.

But the fact that it has no counting might raise the chance to be compatible with caching since no database operation is needed on post load. Right!?

But updating only would have been far too simple anyways :-))

No, no addons needed. There will be a PRO addon by me which will make Analytics and PayPal available.

One big piece of news is that from version 2 on the plugin will be extensible, so if you need to customize it you will be able to use actions and filters.

> But the fact that it has no counting might raise the chance to be compatible with caching since no database operation is needed on post load. Right!?
Well, I don’t really know. Anyway, it’s not that no database operation is needed, is more that LESS database operations are needed.

Thank you Stefano,
i will give it a try when the version 2 is out.

That is good news indeed ??

Version 2.0 is finally out! For the PRO still some days…

Good news and bad news. Means a lot of work for me ??

Will you talk to the guys from w3 total cache (https://www.w3-edge.com/contact/) about compatibility issues? If i do it might make less sense, since i dont know your code.
It is a really important point to me. Otherwise integrating your new version might be in vain. Think of all the blood sweat an tears ??

But of course! Filed a support request! ??

Hey ?? W3 developers ask me how I know the Post Pay Counter pages are not cached. In fact, I don’t. How do you know? You are sure?