Skip to main content

Event System

This page covers day-to-day operation of the local R100 Event System and the yearly reset/import process.

R100 Tools​

R100 Tools is the core bridge between production and the locally running system. This facilitates the connection between the website and the local system.

Primary functions:

  • Event import: Done once a year and will pull of of the current year's events from the production website.
note

Event import logic can be found in the production site's codebase.

Printing​

The bulk priting tool is used to print out registrations with the printer hardware.

Printing is handled by a local service chain:

  1. Local PHP site generates label PDFs into uploads/r100-labels.
  2. The site calls local Windows service R100.printer.
  3. R100.printer forwards the job to Foxit.
  4. Foxit sends output to Zebra printers.

Key notes:

  • Foxit is a local windows service to facilitates the printing process
  • All prints will have associated log files

Score Export Workflow​

Scores can be viewed locally on the event system and on the production site.

  • Local toool is setup by the event: auto exports from local site into the online production site.
note

Score Export logic can be found in the production site's codebase.

R100 Settings Reference​

  • Special Shoots: Legacy area, no longer used.
  • Sponsors: Manages sponsor logos.
  • Pricing:
    • Used to update the range data and label for registrants
    • Pricing used to be controlled via this setting - it is now controlled through the Shoot Selections product
  • Printing: Maps local proxy IP and printer assignment.

Reports​

  • General reports support operations and admin tasks.
  • Duplicate Registrants report is especially useful for cleanup and reconciliation.

Product and Registrant Behavior​

Each event is considered to be a product (composite products)

  • Products can have components
  • These are normally configured through the R100 site, but can be tweaked/modified via the local site

When registrants and events are imported

  • They have a tie between them
  • All registrants have an event id associated with them
    • Local site registrants will not auto update to new event id on a reimport
    • If you need to reimport you will need to bulk update the event id on the registrants

Tablet Operations​

Function through the iOS proxy settings on the tablets

Proxy uses the IP of the primary laptop and the default Squid Server Tray port (Port: 3128)

  • Proxy runs as a background Windows service - should auto start, but can be seen in the running services

Common Troubleshooting Checks​

  • Tablet registration fails: Verify proxy settings and laptop service status.
  • Labels not printing: Verify r100-labels output, R100.printer service, Foxit, and Zebra connectivity.
  • Missing registrants: Use R100 Tools counts and details panel to compare expected versus imported records.
  • Status drift: Confirm custom status transitions through test registration and score entry.

Annual Reset and Import​

This runbook is typically executed at the beginning of each year to archive prior-year data, reset local operational records, and import current-year events and registrants.

Scope and Safety​

Before any destructive action:

  • Confirm exports are complete and verified.
  • Confirm database backup exists and is stored safely.
  • Confirm stakeholders know reset timing.

Step 1: Export Registrants​

Use All Export Pro with the prebuilt template:

  • Template name: Registrations - Master Export.
  • Export format: CSV.
  • Validate CSV using Ron's Editor.
  • Deliver copies to R100 team via email or Google Drive.
  • Attach copy to ticketing system for traceability.

Step 2: Create Full Database Backup​

Use phpMyAdmin via XAMPP.

  • Create full database dump before deletion.
  • Store backup at Desktop/Misc/Site Backup.

Step 3: Delete Prior-Year Operational Data​

Use Bulk WP and manual product cleanup.

Deletion order:

  1. Registrants by post type, permanent delete.
  2. Orders by post type.
  3. Dated event products only.

Product deletion safeguards:

  • Move products to bin first.
  • Confirm selection excludes base products.
  • Empty bin only after review.
important

Do not delete these base products:

  • Registration - Base Product.
  • Shoot Selections.
  • SUPER TEN (special shoot).

File cleanup:

  • Remove old label files from uploads/r100-labels.

Step 4: Import Current-Year Events and Registrants​

Connect the laptop to the public network

Then run the import events process

  • once done spot check a few products
  • should come in with components and as composite product

Via the R100 Tools, run a test run of the event:

  • this screen will also show you stats on how many registrants have been pulled vs how many still need to be imported
    • view details - opens a debugging window of the registrants for that event
    • Quick way to see the data without logging into the live site
  • They handle importing the registrants each week
    • Run import for first of the year's event to test all functionality
note

Orders on the live site sit in the processing status until they are imported into the local site

Once done, clean up order and registrants from testing.

Step 5: Functional Testing Checklist​

After imports and before go-live checklist:

  • Register from tablet.
  • Print labels successfully.
  • Enter scores via tablet.
  • Verify scoreboard reflects new scores.
  • Validate status progression:
    • Pending Payment.
    • Paid.
    • Printed.
    • Score Entered.

Step 6: Cleanup Test Data​

After testing:

  • Remove test orders.
  • Remove test registrants.
  • Reconfirm operational counts and event readiness.

When Remote Help Is Needed​

If on-site direct access is unavailable:

  • Remote support can be done with TeamViewer.
  • Operational assistance can be provided over phone.