Upgrade to version 1.6 from version 1.5

The following changes can potentially cause problems on your system:

•POSSIBLE PROBLEM: CHANGE IN PS/PDF FILE NAME: &e variable in version 1.5 refers to the edition descName attribute, while in version 1.6 refers to the edition name only. SOLUTION: update all your print presets with appropriate variables.

•POSSIBLE PROBLEM: YOU CANNOT CONNECT a result Web part to a publishing destination: since build 1.6.1672.0 it is no longer possible to connect a result Web part to a publishing destinations provider to display the content of the publishing destination. It is still possible to connect a result Web part to a pub. dests. provider in addition to a search or object ids provider to be able to use the 'Publish' icon (as it is done in the 'Publish' page in the standard GN4/Tark4 configurations).

•POSSIBLE PROBLEM: The xml returned by the 'ReferencingExt' option changed from "refs" to "extRefs". See http://forum.teradp.com/topic.asp?whichpage=1&TOPIC_ID=440#3665. SOLUTION: update all your custom XSLT.

•POSSIBLE PROBLEM: since build 1.6.1713 the XML export options used by the search REST call: ../do.ashx?cmd=search&name=...&feed=.... specified with the 'feed' URL option - are considered only when starting a new search - i.e. when 'from' is zero or not specified. Any subsequent call to get more pages of results of the same search uses the same XML export options used in the first call, regardless of what is specified by the 'feed' URL option. Previously the XML export option could be specified at any call.

•POSSIBLE PROBLEM: CRASH OF SCHEMA ON STARTUP. Due to the optimization in the computation of objects' descriptive names, schemas with descriptive name XPaths referencing non-existing attributes are no longer valid - they cause an error on loading, previously such schemas were accepted as valid (but then the descriptive name was not computed correctly of course. SOLUTION: modify your schema so XPaths do not reference non-existing attributes.

•POSSIBLE PROBLEM: WRONG NAMESPACE ON LOADING CONFIGURATION!

•POSSIBLE PROBLEM: If you execute a SQL search, and then after a long period of time switch to another page of results, the listed content may not reflect the actual status. For more details see About paginated searches in version 1.6 or newer. The purpose of the change was to speed-up the searches and lower the server load. SOLUTION: No solution for this change.

•POSSIBLE PROBLEM: When printing pages, changed the way to consider the bleed in printing. All the object in page were cut at the level of page size, but now are cut on the paper size. No differences in print configuration. Now the bleed behavior is equal to GN3 Postscript printing. SOLUTION: No solution for this change, and probably not needed as the behavior is now appropriate.

•POSSIBLE PROBLEM: The AuditCopyTo function has been removed. This can affect your custom add-ins if you used such function. SOLUTION: make changes in your custom add-ins avoiding to use AuditCopyTo function.

•POSSIBLE PROBLEM: The configuration items, defined in EdAdmin4 and Admin4, but used in Ted4 or Fred4 are not available anymore. This is due to the revision of loaded configurations. This can affect your customized configurations. See Order of loading configurations on startup. SOLUTION: Move the Ted4/Fred4 shared items from EdAdmin/Admin4, typically pubdest and calendarobject UI.

•POSSIBLE PROBLEM: AFTER UPGRADE, YOUR PRINTED PAGES CHANGED SIZE. This is due to fixes of some rounding problems in application and print processing. Your old masters pages may change their size. The same is with the paper size: if the width and height were manually adjusted to obtain correct page dimensions in presence of the rounding bug, after the fix you have to put them to the appropriate correct values. SOLUTION: Adjust master page size and paper size in print preset if needed.

•Replaced GNPortalConfig/@UsersFolderPath by GlobalConfig/@UsersFolderPath.