![]() ![]() It was possible to configure Autosave in a way that would cause Helix to hang at the end of the day, if left running all night. Autosave no longer hangs just before midnight.The error - when attempting to modify structure without having first supplied this parameter - referred to it as the ‘modify’ parameter. To make changes to that structure, the ‘modifying allowed’ parameter must also be passed. Helix 6.0 increased the maximum collection size from 2GB to 4GB, and introduced support for collections as large as 64GB. When a collection is in User Mode (or open with Helix Server) the script must ‘login’ as a user with Design Mode access to the collection structure. Text of an Apple event error message now refers to a parameter by its proper name.Users who wish to experiment with extended file size collections may do so only with new collections by modifying the HxAppFRTL2Val preference before creating one. Although tools to modify existing collections to support extended file sizes are not available in Helix 6.2.4, bugs in the underlying code have been fixed. Helix 6.0 increased the maximum collection size from 2GB to 4GB, and introduced support for collections as large as 64GB. Structure Check Failure Dialog enhancement.(By default, the SC Log records just the most recent structure check.) See Editing Helix Preferences for more details on changing this preference. To accumulate SC Log data over time, the HxSCAppendLog preference must be set to true. Whether the needed maintenance was actually done.Which Helix application (and version) was used.How the check was invoked (Open, Close, Autosave, Manual save, Apple event, other).In order to gather more information about this issue, additional information - which is useful in and of itself - is now recorded in the SC Log: However, these misleading reports of damage are disconcerting, and must stem from some source. But after studying the code thoroughly, we have concluded that a manual save can not trigger maintenance when maintenance is prohibited. The speculation was that a manual save would somehow bypass the normal rules and trigger maintenance that would subsequently appear as a false report of collection damage. I have returned to the original 6.2.4 collection and opened it in 7.0.1 but get same behaviour after conversion - in fact RADE crashes before the collection is fully open. Originally reported as ‘Server reports structure damage on manual save’ with a note that closing and reopening the collection would ‘fix’ the damage. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |