FairShare Release Notes - Ver. 1.01

Release Date: 02-03-2026


Data Protection and API Security

  • Removed service token credentials from API outputs (unless explicitly scoped)
  • Added partial data masking for sensitive information in logs (in progress)
  • Truncated sensitive keys in activity logs for safer auditing
  • Removed legacy/sample login functionality
  • Disabled automatic login on demo dashboards


Activity Logs Overhaul

The Activity Log system has been significantly upgraded to improve visibility, usability, and performance.


New and Improved Logging

  • Logs migrated to a React-based interface
  • Added before and after state tracking for clearer audit trails
  • Expanded log detail visibility, including richer event data
  • Reactivated and improved brand-level logs

Filtering and Search

  • Added date range filtering
  • Improved search functionality for faster log discovery
  • Introduced pre-search optimisation for performance


UI and Usability

  • Fully functional log popups with detailed views
  • Pagination and total counts now accurate and responsive
  • Added ability to clear logs
  • Improved handling of large log entries (consistent detail display regardless of size)


Reliability Improvements

  • Fixed issues with logs appearing in incorrect contexts (e.g. app pages)
  • Added cache key handling to ensure logs refresh correctly after new activity
  • Prevented stale or duplicate activity entries via improved validation checks


Additional Improvements and Fixes

  • Fixed long-standing brand page sidebar issue
  • Improved handling of brand edits (no longer includes blank images)
  • Added dedicated handling for image-related events
  • Framework updates to better support domains with ports
  • Improved async handling with longer timeout support
  • General internal refactoring and consolidation of logging functions

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article