TapNTable 0.9.13: backups and restores that survive hiccups
Backups that always finish
Creating a files or full backup could leave the window stuck loading forever, even though the backup was being created on the server. Creation now finishes visibly, the list refreshes on its own and any problem shows up as a clear message instead of an endless wait. The process is also more robust: folders without read permissions are skipped and logged instead of failing the whole backup.
Only genuine backups get in
When you upload a backup file - or import an orphaned file found on the server - the system now checks the actual content of the file before accepting it. A random zip with the right name can no longer pass as a backup: it is refused up front with an explanation, before anything touches your system. The backup type (database, files or full) is now recognized from the content, not the file name.
Restores that recover on their own
If a restore is interrupted midway - a network drop, a server limit or an accidentally closed page - the system now takes care of the rest:
- The “Resume Restore” notice disappears by itself once there is nothing left to resume.
- The “Restart” button really clears everything and leaves the system ready for a fresh restore, instead of refusing with an error.
- Resuming a restore shows progress in a popup again, with the real outcome at the end - a restore that never ran no longer shows up as completed.
- Leaving maintenance mode through the emergency console also clears the pending state, instead of leaving eternal notices behind.
No more looping update screen
After installing an update, the “Update complete! The page will reload…” screen could keep repeating forever. Fixed: the confirmation shows once and the page returns to normal.
Progress always in sight
Updates and restores now show their steps in a central popup with a clearly visible warning not to close the page, navigate away or minimize the browser until the process finishes. The popup cannot be dismissed by accident - only when the process ends or you choose an action.
A quieter, better-protected recovery console
The restore emergency console (/restore-recovery) now only exists while a restore is actually underway - otherwise it answers as a missing page, giving no hints to the curious. Repeated access attempts are now rate limited.
A note on file backups
Files-only backups are meant for downloading and restoring manually; restoring directly from them arrives in a future version. To restore everything in one click, use a full or database backup. The restore button now only shows where it makes sense.