Mattiave

You are fantastic!!

Love from Venice. All the best for you and your work

thank you

shure:

most files belong to posts, here an sample:
this is a file inside folder cache/all
adam-brody-e-leighton-meester-si-sono-sposati

and this is relating to the post
https://www.lavocedivenezia.it/adam-brody-e-leighton-meester-sposati-in-assoluto-segreto/
that have date 19/02/2014

Thanks friend!! Your script works perfectly. I cleared all caches, re-activated the plugin, it worked for two days and then it stopped and the space consumed on the server no longer increased. I will give you great publicity and tell everyone about the excellent quality of your work!
One last curiosity: in the cache/all folder there are still some post files with name of posts of a few years ago, what could this depend on? From some error in our CMS? Thank you again and we send you a big hug

• This reply was modified 11 months, 1 week ago by Mattiave.

I have about 10 thousand posts (not pages),
every day we publish news (new posts),
the posts have permalinks https://www.mysite/namearticle,
I need the plugin make cache of the news of the last month (30 days) and then stops (not doing cache of the older news),
and then need cache each new news that is published in new day (because it is inside last month of date )…
in this way the space occupied on the server will be 1% of the current one…
and for the older news it doesn’t matter: they have very few visits, it doesn’t matter if they will be slower to load without cache…
you’ll see that many other users will thank you if you manage to set the function like this
a big hug

it can’t work, if I want the cache to be created only on the posts of the last week (because these are the news items that have the most visits) I have to insert that function in every single other post URL in the archive, i.e. around 10 thousand pages…

yes, I had already seen it, thanks, but unfortunately you cannot create a rule if you have https://www.sitename/postname , and there is no function that says: “cache only the latest posts more recent than a month (or 2-3 months, or six months) …

because if a site is medium-large it must be able to choose, it makes no sense to create folders on the server to cache posts from 5-6-7 years ago… since they consumes space…

if you can put this suggestion in future features if possible…

thank you for your work

I tried to downgrade for 2-3 versions but the defect persisted. Then I jumped to 1.5.10 and things were back to normal. I think I’ll keep this old version. The only thing we have changed in the last few days is that we have updated wordpress..

Thanks for the information, I will look for the solution and then report back to you. Strange though that the site isn’t reachable, the ttfb controls seem fine to me…

https://prnt.sc/0kBeQWAJAJBJ

of course: we discovered the problem today, I can’t say exactly how many days ago the problem started. What is certain is that two days ago we updated to 1.5.28, and on 5/04 we updated to 1.5.26 (we skipped 1.5.27). The last time we are sure it working perfectly was early April and the version was 1.5.25 or 1.5.24…

Got it, thanks. Latest information:

the biggest folder is cache/all ,

then there is another one almost the same very big size called : ai1wm-backups

Can this be removed by any chance? Are these temp or backup files that can be deleted?

thank you

unfortunately the permalinks only have the titles…

I will have now to delete some folders via ftp in wp-content/cache/all that contains the caches of the older posts because the malfunctions begin…

Can I can suggest inserting the option (for example) to cache only the last two years o something like that? Otherwise old sites with many posts won’t be able to use this plugin and it’s a shame, because the space runs out naturally…

I really don’t know,

I have wp-content/cache/tmp that is empy,

then I have wp-content/cache/all that is full of directories of dates, also of today with old posts inside, if I understand plugin is caching old posts after do his work of caching recent posts… maybe to stop caching is enough…

old post do not have many visits…

our site has 20 years and 35k posts about…

what do you think?

thank you for help

talking about the practical phase:
I placed the code in function.php
I cleared the cache
I put the split by year
Do you think I should already see the results? because on sitemap.xml I still see the old years…

Yes, it does… it was our initial theory, seeing that the number of non-indexed pages is increasing, it seems to me that it is a good compromise ??

you got the point: it’s precisely because there are conflicting opinions on the matter that we can’t decide…

Thanks again, a hug