Operations
Troubleshooting
Use these checks when a Racinage page, tree action, public link, or deployment does not behave as expected.
Login problems
- Confirm the family code is correct.
- Try both username and email if the user is unsure which one was used.
- Check that the account is active and email verification is complete.
- Use password recovery when credentials are known to be stale.
Tree layout looks wrong
Use the reset control in horizontal view first. If the tree still looks wrong after adding or removing people, refresh the browser page and retry the action.
Large tree note: hide, show, mark dead, and mark alive update locally. Adding or removing relationships rebuilds the tree because connectors and branch positions need fresh structure.
Public link does not show expected details
Open the public share settings and confirm that the relevant fields are enabled. Public views intentionally hide data when privacy settings say they should.
Uploads do not appear
- Confirm the file type is supported.
- Check the upload folder permissions on production.
- Refresh the page after upload if browser cache keeps showing an older image.
Deployment checks
Deployment runs from the GitHub workflow after a push to main. If production does not update, check the workflow run, FTP secrets, and Hostinger target directory.
git status
git log --oneline -5
git push origin main
When to escalate
Escalate when database rows look inconsistent, a permission check blocks the correct user, or production deployment fails after the workflow has started.