EasyCatalog 21.0.8
- Bug fixImage URL cache treats trailing slash path as folder instead of filename
When an image URL ends with a trailing slash after a real path component, the URL cache should use the final path component as the filename.
For example:
https://www.apple.com/1/2/1234/should be stored as a file named:
1234not as a folder named
1234with no filename. - Bug fixIf the user has changed the default image frame object style to include text wrap, the human-readable text in a barcode will be overset
- Bug fixFixes issue where tabular fields created by GROUPSCRIPT would be lost when updating custom fields
- Bug fixImage previews were not being shown in the Record Viewer panel when FIELDSTR(FIELDNAME()) was used in the image location path
- Bug fixUpdate Panel with Page Numbers doesn't find fields if their names have changed case
- Bug fixFixed crash updating furniture when a tabular field with no content was used as an Action
- Bug fixFixed issue when a combined custom field referred to placeholder fields that did not exist
- Bug fixHidden boxes can cause a collision in the centre of the page
Boxes hidden using the Layers panel can cause guide-based pagination to believe there's a box in the centre of the page.
- EnhancementImproved ECLink documentation
- Bug fixCrash in CREATERANGES custom field function
Crash in CREATERANGES custom field function when some of the values contain strings, some contain numbers. There is also a potential issue when there are values in the 'values' parameter that are not the 'possible values' parameter.
- Bug fixFields are being incorrectly flagged as dependencies when using the XREFFIELD command with an external data source
Dependencies are incorrectly flagged — which can result in erroneous circular dependencies — if the XREFFIELD custom field command references an external data source. This will be the case when the external data source contains fields of the same name as those in the custom field's data source.
- Bug fixWhen evaluating some custom fields, a 'field not found' error will be incorrectly reported
Using the v2 parser, sometimes it will report that a field can not be found. This only seems to affect custom fields used in certain locations, such as the "Location" text edit box.