When you press "Import from Catalog" on the List Settings page, the server-side catalog is merged into your local database.
If anime you added have not been promoted to the catalog by the admin (i.e. they are still your private entries), the sync does not touch them at all. All their fields are preserved.
Not automatic — only when you ask for it. Sync runs once each time you press List Settings → "Import from Catalog".
Separate from the catalog sync, the "how many episodes have aired" figure for still-airing anime is refreshed from AnimeSchedule. This runs by itself once a day in the background each time you open the List Settings page; you can also trigger it manually with "Sync Now".
+. Anime Tracker itself ships new releases from time to time. You can check whether a new version is available via List Settings → "Check for Updates". That section is only visible to the owner of a personal (single-user) install: on a multi-user site the operator updates from the source code, so a link to the project page stands there instead of a button.
If a new release is available, a one-click automatic update runs:
config.php, uploads/ and your watch data are preserved)Anime Tracker is open source and anyone can run it on their own server. That leaves the project no other way of knowing how many installations exist: a personal install never has to talk to the central catalog, and the update check only runs when its button is pressed. The install counter fills that gap with a number, nothing more: "how many installs".
Your install sends one small request to the project counter once only — after the first time the home page is opened. If the counter server cannot be reached at that moment it tries once more the next day; as soon as it succeeds it never sends again. The request carries three things:
settings table. It is not derived from your address, your database or you; its only job is to let the counter recognise a repeat (a retry, a restored backup) instead of counting it as a new install.define('INSTALL_PING', false); to config.php (new installs already have the line, set to true). From then on no request is sent; the rest of the application is unaffected. To reset, delete the install_id and install_ping_done rows from the settings table — your install then appears on the counter as a new one. Why does it exist? To know something nobody tells us: how many people the work put into the project actually reaches. The number is roughly right, not proof — installs that switch the counter off are invisible, one that resets its id is counted twice.
For further questions: more detailed technical information is on the project's GitHub page.
Help Contents