Increased Version History Retention

Content can change dozens of times before it is ready, especially around season launches, programme updates, and fast-moving campaigns. Basker now keeps up to 100 recent versions for core content instead of 30, so editors have a longer recovery window when they need to look back or restore an earlier state. The extra history is available without changing how editors save.

100 versions retained

Raising the cap from 30 to 100 means a busy edit session is less likely to push useful history out of reach. If a page, event, post, person, venue, or related record changes several times in quick succession, earlier work stays available for longer. That matters when a final edit needs to be compared against what was approved the day before.

Useful for high-change periods

Launch weeks and late-stage programme edits are where version history matters most. A deeper history gives teams more room to compare changes, recover earlier copy, and understand how a record reached its current state without relying on separate notes or screenshots.