A task to run over the complete database would be a nice feature to have. We have a lot of databases with a large number (over 1000) pages and cleaning those up with a single click would save a lot of time!

Hi, and thanks for the module, much cleaner db before deploying website ! Would it be possible to extend this module to safely truncate versions of not only SiteTree but also every class implementing Versioned ?

Fixes #3 and adds tasks for truncating on all pages at once and removing deleted pages.

Certainly some things that could be cleaned up but hopefully a good starting point.

Note that the way I've excluded 'protected' records currently will mess with the $version_limit as they're removed before the offset is applied, meaning you'll get at least one more record than you want left behind. Might be better to leave the DB query how you had it, then scrub the array of records to delete against a whitelist to remove any protected records.

Apologies if this module already does this as I haven't had time to test - but looking at the code I suspect it doesn't.

If you change the URLSegment of a page for example from 'about-us' to 'about', SilverStripe is normally able to automatically redirect users who try to access site.com/about-us to site.com/about. It does this by searching through previously published versions of pages for the old URLSegment, and if it finds it it redirects you to the URL of the current published version of the page.

If the old versions aren't there any more, naturally this functionality will be lost.

I propose a new configuration option preserve_url_history: true which if enabled (probably should be by default) ensures that at least one version record is left in the table for each unique URLSegment a page had.

Thanks for this module! I noticed you're using the full namespaced class path to get Config values:

Config::inst()->get('Axllent\VersionTruncator\VersionTruncator', 'keep_drafts');

Not aware if there's unforeseen downsides to this, but it might be more convenient to use the ::class property instead? (shorter, easier to refactor, plus most of the time you're already in the same namespace in case of related classes)

Config::inst()->get(VersionTruncator::class, 'keep_versions');

Or, shorter yet;

VersionTruncator::config()->keep_versions;

In the SilverStripe 3 branch one of the SQL select where clauses is "PublisherID" > 0. I believe this is meant to check "WasPublished" > 0.

I believe these two queries are first meant to fetch the latest x published versions and then the latest y draft version. If that is correct the queries should be targetting WasPublished > 0 and WasPublished = 1 instead of PublisherID.

Hello!

I'm helpful robot. I noticed you don't have a Scrutinizer config file. This one adds many code quality checks. If you are unsure of how to connect your repository to Scrutinizer, read the guide I wrote for you humans.

Have a nice day! [brrrrb, click]

See semver and SilverStripe supported module definition

Tagging releases is important to allow people to track your project without having to hook onto dev-master, which can be unstable and have unexpected consequences.

By adopting semver and an expected version numbering system devs can safely lock onto the correct versions on your software for their projects.

Hello!

I'm helpful robot. I noticed there were some deviations from PSR-2 in your code. The core committer team recently decided to transition SilverStripe Framework and CMS to PSR-2, and the supported module standard recommends following PSR-2. I've gone ahead and converted files in code and tests to PSR-2. If this sounds like something you'd like to merge then go right ahead! Feel free to ask questions or make suggestions for how I can help you more. I've been programmed with a wide range of responses.

Have a nice day! [gzzzzrrrkt]

This module does not work in combination with the SilverShop module. https://github.com/silvershop

The class SilverShop\Model\Variation\Variation is a bit weird. It is versioned but is does not have a _Live table.

See file: https://github.com/silvershop/silvershop-core/blob/master/src/Model/Variation/Variation.php

This causes issues:

ERROR: Uncaught Exception SilverStripe\ORM\Connect\DatabaseException: "Couldn't run query:  SELECT "Version" FROM "SilverShop_Variation_Live" WHERE "ID" = ?  Table 'mydatabase.SilverShop_Variation_Live' doesn't exist"

Is there a way to exclude a model from truncation?