Skip to main content

Fixes Overview

This section contains documentation for fixes and solutions implemented in OpenRegister to address specific issues and improve system stability.

Available Fixes​

Entity __toString() Magic Method Fix​

Issue: Object entities could not be saved due to string conversion errors when the framework attempted to convert entity objects to strings.

Solution: Added __toString() magic methods to all entity classes and fixed organisation handling logic in the SaveObject service.

Impact: Resolves object entity saving errors and prevents similar string conversion issues across all entity operations.

Organisation Default Fix​

Issue: Import functionality failing on production with missing default organisation methods.

Solution: Added missing methods to OrganisationMapper, enhanced Organisation entity, and created migration for is_default column.

Impact: Resolves production import errors and ensures proper multi-tenancy support.

Folder Deletion Fix​

Issue: Import errors when reusing UUIDs due to orphaned folders from previous deletions.

Solution: Enhanced hard delete process to clean up folders, improved multiple folder handling, and added foundation for automated cleanup.

Impact: Prevents import errors with reused UUIDs and ensures complete resource cleanup.

Fix Categories​

Database & Migration Fixes​

  • Schema updates and migrations
  • Data integrity improvements
  • Multi-tenancy enhancements

File System Fixes​

  • Folder cleanup and management
  • Orphaned resource handling
  • Import/export improvements

Service Layer Fixes​

  • Missing method implementations
  • Error handling improvements
  • Performance optimizations

Contributing to Fixes​

When implementing fixes, please:

  1. Document the problem clearly with error messages and context
  2. Explain the root cause and why it occurred
  3. Detail the solution with code examples and file changes
  4. Include testing scenarios to verify the fix works
  5. Add deployment instructions for production rollout
  6. Update this index with new fix documentation

Fix Documentation Template​

Use the following structure for new fix documentation:

# [Fix Name]

## Problem Description
[Describe the issue and error messages]

## Root Cause
[Explain why the problem occurred]

## Solution Implemented
[Detail the changes made]

## Files Modified
[List all files changed]

## Testing
[Describe how to test the fix]

## Deployment
[Instructions for production deployment]

## Impact
[Summary of improvements]