timepatternanalysis

I think you are right. I have not taken into account that with an active blog the preloading-process interferes with caching caused by normal traffic (users and robots). I made a test now: It needed 22 minutes to see the newest 17 posts in the cache. This is more or less what one should expect (four pages per minute; cron every five minutes).
Sorry for your extra work caused by me!
So my ?wishlist“ is reduced now by having the option to control the number of preloaded items (e.g. posts) (before preloading restarts, if selected).
Thank you for your help!

Hm, the behaviour on my site is different. Preload starts with the newest post, but then it switches to a post of the year 2012 and then to one of 2021. It doesn’t seem that this is a fixed sequence. Restarting the whole thing, the sequence differs from that before.

I think it is useful as explained earlier to limit the number of preloaded items (posts). So after for instance 200 preloaded posts preloading will stop (and restart if enabled). Therefore you have the most recent posts (with DESC order) in the cache and restart preloading sooner. That way a normal user gets the information on the sidebar (widget area) updated more often than if you are preloading the whole content.

Good to hear.
And if you would implement an option for max. no of items to be preloaded that would be even better.
Thank you!

If you will work on the preload issue I think it would be a good idea not only to establish a descending order of scanning posts but also let the customer decide how many posts should be scanned. The older a post is the less likely it will be accessed by anyone. The oldest posts need not to be cached and so you are saving processing-power and memory.

Concerning the comment issue: In my environment while having the option for logged-in users enabled (fourth from the top) the comments as well as the output of some plug-ins are not fresh (option widget-cache not enabled). I had to use a work-around by your exclude-functionality to get them all fresh. In my opinion when logged-in as administrator one should see the page completely un-cached (no CSS, no JS, no html). For logged-in ?simple’ users this might be different.

If you once have implemented the preload-functionality as described this would be a perfect plug-in for my needs.

It seems that a comment is displayed if the user is not registered (o.k.). But this is not the case for a registered user – to see the comment the cache has to be deleted first. Any suggestion?

Good, I am looking forward.
Once upon a time I programmed a tool loading all the posts in a time-descending order but for some reason it is not working anymore.
Meanwhile I will purchase the Pro-version.

Thank you for your effort!
Meanwhile I have switched back to the former version of your plugin which is working fine (3.2).
If I find out the reason why the new version of your plugin don’t work properly I will let you know.

Thank you for your answer.
The former version of your plugin worked nicely and in the meantime I haven’t changed anything in my blog.
Have you changed the way to handle the rating block in the actual version of your plugin?

Hi,
thank you for your help. It is working now.
What was wrong (or why it was necessary to start from scratch)?
Klaus