The Gallery Checker is located in Rotation > Settings > Gallery Checker.
The script continuously checks galleries in the database while limiting bandwidth usage. You can configure the maximum bandwidth in settings under “Max bandwidth to be used by checker (Kb/s)”.
Galleries are checked against Gallery Deletion Rules in the format domain|keyword. The script looks for a keyword in the gallery's HTML; if found, the gallery is marked as deleted. For example, if the keyword “Video deleted” appears in the HTML of a gallery on videos.com, the checker removes it.
A pseudo-domain named “default” applies to any domain that doesn't have specific rules.
To prevent accidentally deleting large numbers of galleries (for example, if you accidentally enter a word that appears in all galleries on a domain), use the Deletion Lock feature. Set a threshold, such as “Stop deletion if we delete more than 5 galleries in a row”. If the checker finds 5 consecutive galleries matching a rule, it locks that rule and stops deactivating galleries from that domain until you manually remove the lock in the admin panel. You can see which rules have locks in Rotation > Tube > Gallery Checker.
To skip checking a domain entirely, add a rule in the format skip|domain.com.
The config file uses a simple format:
domain|keyword
where domain is the gallery's domain, and keyword is the text to search for in the gallery's HTML. For example:
videos.com|Video deleted
You can also create a default rule that applies to any domain without specific rules:
default|Bad Request Page
You can even check for HTTP status codes:
default|http_code_0 default|http_code_404 default|http_code_502
To skip checking a domain entirely:
videos.com|skip
Before update 49, the Gallery Checker processed all galleries sequentially, which had drawbacks. As the checker worked through the database, older galleries at the “top” could be removed before they were checked again, leading to lengthy gaps depending on database size. Update 49 introduced a dual-queue system: one queue for the top 1000 galleries by CTR and a general queue for the rest. On each run, the checker selects galleries from both queues. Think of it as running two checkers in parallel: one constantly monitors the top 1000 galleries, while the other checks the full database. This ensures the highest-traffic galleries are always checked promptly.
If you run multiple sites with overlapping gallery databases, you can synchronize gallery deactivation across sites. When the checker on one site detects a deleted gallery, it can automatically deactivate that gallery on your other sites.
Here's how to set it up:
1. Enable the Gallery Checker on all sites 2. On each site, create a rotation template named deletion_list (or similar):
<thumb num=1-1000> <!--URL--> </thumb>
3. Verify the template works by accessing http://yourdomain/?force_template=deletion_list&order=date (or add &gallery_status=inactive to see only inactive galleries)
4. On each site, add an import set of type “Deletion” pointing to another site's deletion list: http://another_domain/?force_template=deletion_list&order=date&gallery_status=offline
That's all you need to do.
Note: This approach is not necessary for master-slave setups, since all slaves deactivate galleries directly in the master's database, so no data transfer between sites is needed.