Fix: Messaging Centre Now Preserves Account Context on Redirect
Fix: Messaging Centre Now Preserves Account Context on Redirect
Release: v0.1.68
Overview
In v0.1.68 we fixed a routing issue where navigating to the messaging centre for a specific account — via the URL pattern /:company/:accountType/messaging-centre/:personOID — would redirect users to a generic messages page with no account pre-selected. The personOID that identifies whose inbox to show was being silently dropped during the redirect.
This release ensures the correct inbox is always loaded, with no extra steps required from the user.
What Was Happening
The route GET /:company/:accountType/messaging-centre/:personOID is designed to open a per-account, paginated inbox scoped to a specific person (personOID). Instead, it was issuing a 307 Temporary Redirect to /:company/messages — a generic messages page that has no awareness of which account to display.
The result: users following a deep link or notification to their inbox would land on an unscoped, unfiltered messages view, with no inbox pre-selected.
What Changed
1. Redirect updated to forward personOID
The redirect rule in next.config.ts has been updated so that the destination URL includes personOID as a query parameter:
Before:
destination: '/:company/messages'
After:
destination: '/:company/messages?personOID=:personOID'
This ensures the account identity is preserved across the redirect and is available to the messages page.
2. Messages page reads personOID to pre-select the inbox
The messages page (/:company/messages) has been updated to read the personOID query parameter on load and use it to automatically pre-select the corresponding account inbox. Users are taken directly to the right conversation view without any manual selection.
Who Is Affected
- Tenants, landlords, buyers, vendors, and contractors who follow deep links or notification URLs pointing to a specific messaging-centre inbox.
- Agency staff or systems that generate direct links to
/:company/:accountType/messaging-centre/:personOID.
Behaviour After the Fix
| Scenario | Before v0.1.68 | After v0.1.68 |
|---|---|---|
Navigate to messaging-centre URL with personOID | Redirected to generic /messages, no inbox selected | Redirected to /messages?personOID=…, correct inbox pre-selected |
| Deep link from notification | Lands on empty/default inbox | Lands on the correct account inbox immediately |
Direct URL without personOID | No change | No change — falls back to default messages view |
Notes
- The redirect remains a 307 Temporary Redirect; only the destination URL has changed.
- No changes are required from agencies or end users — the fix is transparent.
- The
personOIDvalue in the query string is the same identifier previously carried in the URL path segment.