Keeping Task Session up to date is one of the most important things you can do as a self-hosted user. Updates bring new features, performance improvements, and — critically — security patches that protect your data and your clients’ data.
This guide covers how to prepare for an update, run the update process, verify that everything works afterward, and handle situations where something goes wrong.
Who this guide is for: Admins (System Owners) responsible for maintaining the Task Session installation.
What you will need: Admin-level access, access to your server (via cPanel, SSH, or FTP), and a recent backup of your database and files.
Security updates are urgent: Task Session’s changelog has included security patches (including SQL injection fixes). When a security update is released, apply it as soon as possible. Delaying security updates leaves your installation and your clients’ data vulnerable.
Why Updates Matter
Every update falls into one or more of these categories:
| Update Type | What It Includes | Urgency |
|---|---|---|
| Security patches | Fixes for vulnerabilities that could be exploited by attackers. Examples include SQL injection fixes, XSS patches, and authentication hardening. | Apply immediately. |
| Bug fixes | Corrections for issues reported by users — broken features, display errors, calculation problems, or workflow glitches. | Apply within a week. |
| New features | Additions to the platform — new modules, UI improvements, enhanced permissions, better mobile support. | Apply at your convenience. |
| Performance improvements | Optimisations that make the application faster, reduce server load, or improve the user experience. | Apply at your convenience. |
Check the Task Session changelog regularly to see what each release includes. This helps you assess urgency and plan your update schedule.
Before You Update: Preparation Checklist
Never update without preparing first. A failed update without a backup can result in data loss or extended downtime.
- Back up your database. Export a full copy of your MySQL/MariaDB database. This is your safety net. If the update breaks something, you can restore this backup and return to your previous state. See the Backing Up Your Task Session Data article for detailed instructions.
- Back up your files. Download a copy of your entire Task Session directory from the server, including any uploaded files, custom configurations, and the .env or config file.
- Check the changelog. Read the release notes for the version you are updating to. Look for breaking changes, new requirements (such as a higher PHP version), or migration steps that need manual action.
- Verify server requirements. Some updates may require a newer PHP version, additional PHP extensions, or updated MySQL/MariaDB. Confirm your server meets the requirements before proceeding.
- Notify your team. Let team members and active clients know that a brief maintenance window may occur. Updates are usually fast, but it is professional to communicate ahead of time.
- Choose a low-traffic time. Run the update when your team and clients are least active. Early morning, late evening, or weekends are typically safest.
Golden rule: Always back up before updating. Always. Even if the update is minor. Even if you updated successfully last time. Backups are your insurance policy against anything going wrong.
How to Update Task Session
Task Session advertises one-click auto updates. The exact process depends on your version and hosting setup, but the general flow is as follows.
Method 1: One-Click Update (Recommended)
- Log in to Task Session with your Admin account.
- Navigate to System Settings or the Updates section.
- If an update is available, you will see a notification with the new version number and a button to start the update.
- Click Update (or the equivalent button).
- Wait for the process to complete. Do not close the browser, navigate away, or restart your server during the update.
- Once finished, you should see a confirmation message with the new version number.
Method 2: Manual Update (If Auto-Update Is Unavailable)
- Download the latest version files from your Task Session account at tasksession.com/account/.
- Upload the new files to your server via FTP, SFTP, or cPanel File Manager, overwriting the existing files.
- Important: Do not overwrite your configuration file (.env or equivalent) or your uploaded files directory. These contain your settings and user-uploaded content.
- If the update includes database migrations, visit the migration URL or run the migration command as specified in the release notes.
- Clear any application cache if instructed by the release notes.
- Log in and verify the new version number in the admin dashboard.
After Updating: Verification Steps
Do not assume everything works just because the update completed without errors. Verify the key areas:
- Check the version number. Confirm the dashboard or system settings show the new version.
- Test login for all roles. Log in as Admin, then test with a Staff account and a Client account (or use incognito windows). Verify each can access what they should.
- Open a project. Navigate to a project, check the Kanban board, open a task, and verify everything displays correctly.
- Check the Client Portal. Log in as a test client and confirm the portal loads, projects are visible, and invoices display correctly.
- Test invoicing. Create a test invoice (or open an existing one) and verify the payment link works if you have a gateway configured.
- Test email notifications. Trigger a test notification (assign a task, send a test invoice) and confirm the email arrives.
- Check integrations. If you use Google Login, Google Drive, or payment gateways, verify each integration still works. OAuth redirect URIs and API connections can sometimes be affected by updates.
What to Do If Something Goes Wrong
If the update causes problems, do not panic. Here is how to handle common scenarios.
| Problem | Likely Cause | Fix |
|---|---|---|
| White screen or 500 error after update | PHP version mismatch, missing extension, or file permission issue. | Check server error logs. Verify PHP version meets new requirements. Reset file permissions to 755 for directories and 644 for files. |
| Database errors or missing data | Migration did not run or failed midway. | Check if a database migration script needs to run. If data is missing, restore from your pre-update database backup. |
| Login not working | Session or cache conflict after the update. | Clear browser cache and cookies. Clear server-side application cache if available. |
| Integrations broken (Google Login, payments) | API endpoints or redirect URIs changed. | Reconfigure OAuth redirect URIs and payment callback URLs. Check integration settings for fields that need updating. |
| Features missing or behaving differently | Breaking changes in the new version. | Check the changelog for documented changes. Some features may have moved to a different location or been renamed. |
If you need to roll back: Restore your pre-update database backup and your pre-update files. This returns your installation to the exact state it was in before the update. Then investigate what went wrong before attempting the update again.
Recommended Update Schedule
Security updates: Apply the same day they are released, or within 24 hours at most.
Bug fixes: Apply within one week of release.
Feature updates: Apply at your next maintenance window. Review the changelog first to understand what is changing.
Routine check: Log in to your admin dashboard at least once a week and check for available updates. Subscribe to the Task Session changelog or follow their announcements to stay informed.
Frequently Asked Questions
Will updating erase my data?
No. Updates modify the application code and may run database migrations to add new tables or columns, but they do not delete your existing data. However, always back up before updating as a precaution.
Do I need to notify my clients before updating?
For most updates, no. Updates are usually fast and clients may not notice. For major updates or if you expect any downtime, a brief heads-up is professional courtesy.
Can I skip versions?
This depends on the update. Some updates can be applied directly from older versions. Others require stepping through intermediate versions. Check the release notes or contact Task Session support if you are several versions behind.
Does the one-click update require my licence key?
It may. Some update mechanisms verify your licence before downloading the update. Make sure your licence is active and properly configured.
How do I know if a security update has been released?
Check the Task Session changelog at tasksession.com/changelog/ regularly. Security-related updates are typically flagged prominently in the release notes.
