I think this could use some work from c5's perspective.

Currently, it stores all versions. And there might be 10 "drafts" for every published version. MOSS has a decent system where published versions get whole numbers and drafts are points (so 1 and 2 and 3 were visible to users, while 1.1 - 1.274 were unpublished). Deleting the points and keeping the whole numbers is trivial -- it might even happen automatically after some time.

I'm not aware of that requirement for govt agencies, but I guess it would be possible to save to another database before deleting. The lack of foreign keys makes a lot of hacks like that pretty easy.

There are areas in all products that challenge users. Not all of us use C5 for the same purpose. I will likely go in to the database and kill previous versions to solve the problem. On a few other sites that I maintain, I have configured Varnish Cache with fairly long TTL's to maximize page load times.

C5 still kicks a**!

I wrote an article about Varnish Cache and C5 athttp://nwlinux.com/configure-varnish-cache-for-concrete5-cms/....

rbuky,

Per:
"I will likely go in to the database and kill previous versions to solve the problem."

Were you successful in removing old page versions in the data base? Could you let me know what you did and where you did it (file etc.)? Would be greatly appreciated. Thanks!

A feature to do mass old version delete will be in the next version of
concrete5.

best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz

Franz, Again, much appreciated! Probably a dumb question, but, will the current C5 version upgrade to version 5.5 without major disruption? When do you think it will be available? Saw the team's video and looking forward to stacker, short cuts, etc. Nice features added in speeding up development! Please excuse my persistence on trying to find a solution for bulk version delete, it has been one of the few issues I have been unable to resolve, and really need to speed up an eCommerce site I am working on . Thanks Much! Tim

End of this month, and yes you will be able to upgrade.

best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz

Check this thread:
http://www.concrete5.org/developers/pro-accounts/community-leaders-...

It's rather ugly and I don't recommend to use it, certainly not without creating a backup first. I tried to use the API but things were super slow which is why we've ended up with that ugly SQL.. Worked fine for us, but again, think about this query a few times before you use it!!

Remo, Appreciate your input! Understanding your level of expertise, sure looks like a suicide mission for me! Based on Franz's reply regarding 5.5 being able to handle this, and your advice, will forgo attempting unless someone comes up with a less risky solution in the meantime. Thanks, Tim

hey, I currently have a script to remove old versions in the mp submission queue. going to be free, so i'll post it here. Just upload to root/packages and install through dashboard. go to the jobs page to run.

Jack, Fantastic! Any documentation you can send me as to where to stick the files? Will try on backed-up test site first. Any precautions such as orphan blocks etc.? Thanks! Tim

the unzipped file just goes in the root c5 install/packages. Uses the api, so it should be safe.

Jack, Thanks for the add-on, should have read your full post before asking you the dumb question you already had answered! Not very good at multitasking between trick or treat tasks.

I installed on 2 sites, activated and engaged. It's been a couple hours and the throbber.gif continues to spin without any indication that any pages have been deleted. One site has 100 versions with 5 total approved pages and the other 400 with 10 pages. Don't know if this is part of the routine or not. Considering it would take me more than a month to delete old pages off the site that has over 10,000 versions, if it takes a day or more to delete no problem, but guessing something may not be right. Tim

Tim, I'm afraid but I'm not surprised. As I wrote above, I tried to achieve this using the API but never had much success due to these performance issues. It didn't take me a month but that might also because my server has a ton of power..

I think a script to kill all but the 10 most recent versions for every
page in a site would be a valuable addition to the core. If anyone
wants to submit something via GIT, we'd be very thankful.

best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz