|
|
| Product | |
| Support | |
| Everything Else | |
| BZ979: Collection damage reported after Apple events access | |
| Category |
Bug |
| The Problem |
Collections used with Helix Server or Helix Engine Preview Release versions 6.1 – 6.1.2 could leave internal data in a state that Update Collection 6.0.x considers wrong, resulting in a false report of collection damage. |
| Discussion |
Helix 6.1 no longer uses the ‘compiled form’ data that was used in Helix 6.0, but Update Collection is not aware of this. In cases where Apple event access users neglected to close a process, this obsolete data would not be cleared properly. Because Update Collection is backward compatible with Helix 6.0, it considers this a problem and reports collection damage. In reality there is no damage; Update Collection is being overly sensitive. Helix 6.1.3 takes greater care to discard this obsolete data, keeping Update Collection from falsely reporting damage. Helix 6.1.3 also restores the original limitation of one open Apple event process per licensed seat. |
| Workaround |
To avoid this bug, close all Apple event external access processes before quitting Helix. |
| Scope |
This bug affects Helix Server and Helix Engine Preview Release versions 6.1 – 6.1.2. |
| Status |
This bug is fixed in Helix 6.1.3. |
| Attribution |
Special thanks to Greg Morin, Howard Sutherland and Christian Skeem for bringing this bug to our attention. |