OptiPub 3.2.701 introduces new features, user experience enhancements, and important bug fixes. Read on for a summary of what's new and improved.
Release Notes 3.2.701
🚀 New Features
- Added support for setting and ensuring unique URL slugs for various item types.
- Implemented refresh tokens for authentication, allowing for longer sessions.
- Users are now notified when a new app version is deployed, prompting them to reload for the latest updates.
- Campaign efforts table now includes default columns and new data such as clicks and conversions.
- Message history can now be filtered by segments, thanks to new relationships between messages, mailings, and segments.
🛠 Improvements
- Snackbars (notifications) have been enhanced: multiple can display at once, progress bars indicate auto-hide timing, notifications can be pinned, and visual design is improved with icons.
- Improved Sentry integration for better error tracking and reporting.
- The new releases modal now retrieves data more efficiently via a direct API endpoint.
🐛 Bug Fixes
- Fixed the GTM form to allow old tags with 6-character suffixes.
- Resolved an issue where the template selection input on message forms did not fetch items if the associated publication template was invalid.
- Corrected an error that could occur when parsing app version numbers.
- Fixed the “submit feedback” button on error snackbars to properly send feedback.
🔧 Technical / Internal
- Provided the new app version to frontend scripts during build for improved version tracking.
- Included the current app version in task status responses for better diagnostics.
- Added support for cross-site requests on the resource contents endpoint.