Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Rahat-Pagecode/gitbook-competitions/llms.txt

Use this file to discover all available pages before exploring further.

As your competition platform grows, your database accumulates millions of ticket and order records that are rarely — if ever — accessed again. The Archiver plugin tackles this head-on by automatically moving aged data out of your live database and into a separate dormant store, keeping every new order as fast as the very first one you ever processed.
Archiver is an add-on plugin specifically designed for high-volume or older sites. Contact your account team to have it enabled and configured for your platform.

Why You Need the Archiver

Every ticket sold writes rows to your live database. That database is queried on every single order — so the more historical data it holds, the slower each query becomes. Two common scenarios accelerate this bloat:
  • Long-running sites — years of ticket sales pile up even at moderate volumes.
  • Penny prize competitions — orders regularly contain hundreds of tickets each. A single penny prize competition with 100,000 max tickets can add millions of rows in a matter of months.
Left unchecked, the symptoms are hard to miss: progressively slower checkout pages, orders that take longer and longer to fulfil, and customer complaints about a sluggish ordering experience.
If your website has become noticeably slower over time and order fulfilment is lagging, a bloated database is almost certainly the cause — especially if you run frequent penny prizes.

How the Archiver Works

1

Automatic off-peak scheduling

The Archiver runs automatically during non-peak hours (8 am to 1 pm). It scans your live database for records older than your configured threshold and moves them to a separate dormant database, freeing up space without any manual intervention.
2

Choose what to archive

You can configure the Archiver to move orders, tickets, or both. This gives you fine-grained control over which data leaves the live database first.
3

Set your time threshold

Pick a timescale — for example, 12 months. Any records older than that threshold are automatically migrated to the dormant database on the next scheduled run.
4

Access archived data when needed

The dormant database is always accessible via a dedicated lookup table in your admin panel. Click View on any archived order to see full order details: tickets purchased, billing information, and all standard order data — exactly as it appeared when the order was live.
The Archiver is normally configured by the platform team on your behalf. The options described above are shown here for reference so you understand what each setting controls.

What Customers See

Archiving is entirely transparent to your customers. Winners and previous entrants can still view their competition history and any prizes they have won from their My Account page — the Archiver never removes data that customers need access to.
Customers will always be able to see their wins on their My Account page, regardless of whether the underlying order has been archived.
The Archiver plugin is actively developed. New configuration options and capabilities are added over time — check back on this page for the latest details.

Build docs developers (and LLMs) love