Upgrade to version 1.4 from version 1.3

Follow below steps:

a.Any custom site schema having a gs:compute section for the attribute modifiedDate should be corrected and the attribute should be computed as follows:

<xsl:attribute name="modifiedDate">

<xsl:choose>

<xsl:when test="$context/oc:OperationContext/@Kind='Upgrade'" >

<xsl:value-of select="nav:modified/nav:actionDesc/@Time"/>

</xsl:when>

<xsl:otherwise>

<xsl:value-of select="$context/oc:OperationContext/@UtcNow"/>

</xsl:otherwise>

</xsl:choose>

</xsl:attribute>

This change requires the s_objectTable. modifiedDate to be filled.

The SQL query to fill the table is available here: http://forum.teradp.com/topic.asp?whichpage=0.62&TOPIC_ID=219&#3521.
Run the query AFTER THE STEP 3 IS COMPLETE.

b.The new build allows inheritance of the gs:compute section, you can take advantage of it . See http://forum.teradp.com/topic.asp?TOPIC_ID=808.

c.A new computed attribute folderKind is available for folderObject.
Basically you can mark a folder with a kind (wires, archive, editorial) and this value will be inherited by the folder object. This field is full text indexed, allowing to make searches filtering for wires or archive kind. Previously you had to select a folder and subfolders to restrict searches to wire (or tark) stories or images), and this was a very slow search. This change requires the folderKind values to be filled. You must run (and eventually customize) the SQL query described in the following post: http://forum.teradp.com/topic.asp?TOPIC_ID=219#3575.
Run the query AFTER THE STEP 3 IS COMPLETE.

d.The justDef scripts element has been dropped in 1.4. If you exported style libraries from gn3 using gn3export, the exported files won’t import in 1.4 because not compatible to the new schema.
Please download and use the newest version of gn3export (http://tech.teradp.com/daily/GN3/main/bin/gn3export.zip), or fix already exported files by deleting the scripts elements.

e.When the properties VariantTypeIds and VariantTypeNames of the Variant activity are not set, then we consider the pubDest parameter varianttypeids which is read from the attribute pubDest.variantTypes and automatically injected to the parameters passed to the publishWF. There was a bug due to the fact that the pubDest.variantTypes attribute may feature variantTypes designed for different object types, and we used to apply them all whatever the type of the object being published. This bug has been fixed in the following way: a new computed attribute variantType.typeRef indicates the type of the objects a variantType is designed for, and among the values features by the varianttypeids pubDest parameter, only the ones that match the object being published are considered. Note that the new attribute variantType.typeRef defaults to 'folderObject' (which means that it is compatible with any object type that derives from folderObject, and so it does not affect current installations). In order to make the fix effective, it is necessary to set correctly the value of the variantType.typeRef attribute in the compute section of the various object type deriving from variantType. It has been done for the demo schemas GN4.xsd and Tark4.xsd. Please note also that if the compute of the various object types deriving from variantType are updated AFTER the introduction of the variantType.typeRef attribute (and not in the same time), then it will be necessary to MANUALLY recompute that attribute (either with the command cmd4 recompute or by editing and saving the variant types through the administrative web interface).

f.If using a schema different than the standard ones - i.e. that does NOT include the standard Tark4Include.xsd, it is necessary to add to it these declarations:

<xs:attributeGroup name="userGapExtra">

<xs:annotation>

<xs:documentation>

Additional attributes of the 'userGap' object type that are rendered as XML attributes

</xs:documentation>

</xs:annotation>

</xs:attributeGroup>

<xs:group name="userGapExtra">

<xs:annotation>

<xs:documentation>

Additional attributes of the 'userGap' object type that are rendered as XML element

</xs:documentation>

</xs:annotation>

<xs:sequence>

</xs:sequence>

</xs:group>

Note

Use a merge utility to see all the other minor changes and additions to the standard schemas, against the schema files you customized.

Use a merge utility to see all changes and additions to the standard configuration files, against those you customized.

This is the list of new files in version 1.4, list extracted comparing the 1.3 and 1.4 versions of the editorial_installconfig, it is strongly recommended to do the same check against you current install or upgrade configuration:

Data files (to be imported using cmd4 import)

User calendars: http://forum.teradp.com/topic.asp?TOPIC_ID=80.

<DataFile>Data\GapReasons.xml</DataFile>

Updated font related files

<DataFile>Data\GN4\fontLayout_Unicode.xml</DataFile>

<DataFile>Data\GN4\fontLayout_Dingbats.xml</DataFile>

<DataFile>Data\GN4\fontLayout_Symbol.xml</DataFile>

<DataFile>Data\GN4\fonts_Data.xml</DataFile>

New Config files (to be imported using cmd4 config)

Changes to back4 data sources

<ConfigFile>Global\wf_EditBack4DataSource.xml</ConfigFile>

<ConfigFile>Global\wf_EditBack4DataSourceTemplate.xml</ConfigFile>

<ConfigFile>Global\wf_NewBack4DataSource.xml</ConfigFile>

<ConfigFile>Global\wf_ReloadBack4DataSourceConfig.xml</ConfigFile>

<ConfigFile>Global\wf_SpikeBack4DataSource.xml</ConfigFile>

Adobe integration:

<ConfigFile>Global\GN4\Adobe\feed_AdobeEditions.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_DisplayExtDocJumpPart.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_ExtDocJumpPart.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_InDesignJumpContinueFrom.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_InDesignJumpContinueOn.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_InDesignJumpPart.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_LinkedExtDocs.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_txtToArticle.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\feed_txtToExtDoc.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\search_AdobeEditions.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\search_extDocJumpPart.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_InDesignCreateJumpPart.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_InDesignSetContinueFrom.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_InDesignSetContinueOn.xml</ConfigFile>

<ConfigFile>Global\GN4\Adobe\wf_InDesignUploadJumpPart.xml</ConfigFile>

Page preview:

<ConfigFile>Global\GN4\ppopt_Info240px.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Info480px.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview120dpi.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview240px.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview480px.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview72dpi.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview80px.xml</ConfigFile>

<ConfigFile>Global\GN4\ppopt_Preview96dpi.xml</ConfigFile>

Misc:

<ConfigFile>Global\GN4_Tark4_Common\feed_XamlDisplay.xml</ConfigFile>

<ConfigFile>Global\GN4\feed_TToFlowDocument.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4\gnpc_WebParts_browse.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4_Tark4_Common\gnpc_WebParts_reports.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4_Tark4_Common\gnpcInt_Webparts_docTypes.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\GN4_Tark4_Common\gnpcInt_WebParts_publications.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_home.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpc_WebParts_userCalendars.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpcInt_WebParts_home.xml</ConfigFile>

<ConfigFile Scope="WebParts">Global\gnpcInt_WebParts_userCalendars.xml</ConfigFile>

<ConfigFile>Global\GN4\feed_FormatStyles.xml</ConfigFile>

<ConfigFile>Global\GN4\feed_TToFlowDocument.xml</ConfigFile>

<ConfigFile>Global\GN4\feed_TypeIdName.xml</ConfigFile>

<ConfigFile>Global\GN4\html_Home.xml</ConfigFile>

<ConfigFile>Global\GN4\html_HomeInt.xml</ConfigFile>

<ConfigFile>Global\GN4\search_Formats.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_CreateImageVariants.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_processMultiCropOutput.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_ReplaceArticleContent.xml</ConfigFile>

<ConfigFile>Global\GN4\wf_SetFormat.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_CreatePreviewThumbnail.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_CreatePreviewThumbnailImg.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\wf_ImportPdfDocuments.xml</ConfigFile>

<ConfigFile>Global\GN4_Tark4_Common\xsl_xaml.xsl</ConfigFile>

New Icon files (to be imported using cmd4 icon)

Import all the icons listed in tark or editorial installconfig, as many are new, and some already existing were modified.

•The FlowDocumentPreviewControl in various configuration, particularly InfoPanel for article will no longer work. It must be replaced with EdFlowDocumentPreviewControl from the namespace http://www.teradp.com/schemas/GN4/1/EdWinUI, e.g.

<Grid HorizontalAlignment="Stretch"

xmlns:edWinUI="http://www.teradp.com/schemas/GN4/1/EdWinUI">

...

<edWinUI:EdFlowDocumentPreviewControl

l:Highlights.IsHighlightTarget="True"

VerticalScrollBarVisibility="Disabled"

IsSliderVisible="False"

ObjectId="{Binding Path=DataContext[article.id],

RelativeSource={RelativeSource AncestorType={x:Type l:ArticleView}}}"

TxtObjectType="{Binding Path=ObjectType}"

TxtFormatId="{Binding Path=[txt.contextRef]}"

TxtXsltName="TToFlowDocument"

TxtXml="{Binding Path=[txt.tText]}"/>

The standard configuration have been updated, but if you have a configuration using l:FlowDocumentPreviewControl with any TxtXXXX properties being assigned to, you need to change l:FlowDocumentPreviewControl to edWinUI:EdFlowDocumentPreviewControl and define the namespace in the surrounding markup as edWinUI in the example above.

•Starting from build 1.4.1473.0 EditorialXsltExt.dll has been deleted by GN4 project (replaced by the same class name EditorialXsltExtensions in EditorialServer.dll).

The default configuration has no more references to EditorialXsltExt.dll

In case of custom ServerConfig.xml, remove from the configuration the reference of EditorialXsltExt.dll

</XsltExternalClasses>

and the EditorialXsltExt.dll class from bin directory.

•Starting from 1.4.1446.0, a new computed field folderKind is added to the folderObject, and the value is computed on a new attribute of the folder (folderKind). It is used for making faster full-text searches,as the new attribute, now hidden in many searchObjectUis (client and browser) allows searching for the object story or image in "wires" folders or "archive" folders, instead of searching hardcoding or selecting the folder tree (that is a slow operation).

IMPORTANT - We recommend to update using the -nocompute switch of the srv4 dbupdate command, as the computation could be VERY slow on systems even with few thousands of objects. Use the following sql query to update the database with the proper values, instead. The query sets the folderKind to folders, and consequently to folderObject

Note:

Even If you run the update without the -nocompute, the folderKind will be in any case empty. So you will have to run the query to populate the new fields of folder and folderObject, otherwise some searches may not return any result.

Moreover, be sure to set the proper folderKind value to any new folder you will create after the upgrade.

Here's the query:

--

-- Customize the s_path fragments to set the proper folderKind

-- In the following we assume the wires are in subfolders of /Wires/

-- and archived objects in subfolders of /Archive/

-- if you changed these folders, you need to replace the correct names

-- the folders not "archive" or "wires" are considered and marked as "editorial".

-- So if you want to include in wires or archive other folders, update their s_folderKind accordingly

-- (0=wires,1=archive,2=editorial)

update s_FolderTable set s_folderkind = 0

where

s_path like '/Wires%'

update s_FolderTable set s_folderkind = 1

where

s_path like '/Archive%'

update s_FolderTable set s_folderkind = 2

where

(s_path not like '/Wires%' and s_path not like '/Archive%')

update s_FolderObjectTable set s_FolderObjectTable.s_folderKind =

(select ft.s_folderKind from s_FolderTable ft

left outer join s_folderobjecttable fot on fot.s_id =s_FolderObjectTable.s_id

where ft.s_id = fot.s_folderRef)

The change requires the re-definition of Exalead configuration (and a full rebuild).

Follow the following post for the procedure: http://forum.teradp.com/topic.asp?TOPIC_ID=330#3435

If after the update and restarting back4 you get the following error:

Index process: Exalead indexing failed. Error: 'Exception type: InvalidConnectorNameException

... the possible reason may be that the Exalead source name for document object has changed, and there are documents to be indexed in the gn_indexqueuetable referring to the old config.

Please clear the content of the gn_indexqueuetable:

truncate table gn_indexqueuetable

before reindexing your data.

Note also that reindexing could take long time (hours).

Note:

•If you customized the searchObjectUis of the portal and client application, update them to use the new folderKind attribute instead of the folderRef.

•Remember to set the folderKind for new folders you will create.

•Moved Private Function ConfirmReassign and Private Function ConfirmUnassign to UtilsBase class of Ted.VB, so if you used them in your custom code, replace all occurences of ConfirmReassign with UtilsBase.ConfirmReassign and of ConfirmUnassign with UtilsBase.ConfirmUnassign.

It is important to upgrade the database with the srv4 –nocompute switch, to avoid automatic computation of modifieddate and folderKind attributes introduced in this build.

The compute could, in fact, take hours on a medium/large sized database.

See above (1.a and 1.b) for the required sql query to run after the upgrade, in order to populate manually the new database columns.

If you maintain an editorial or tark4 update or installconfig, you can at the same time import the new/modified config/data/icon/strings files using the:

srv4 dbupdate -config [configfile] -nocompute

Otherwise, run the:

srv4 dbupdate -s [master schema file] -d "" -nocompute

If you do not maintain an update or install config file, you will have to manually import all the updated and new files :

See the step #2 "New files in version 1.4" for the list of new files.

1.Locate the files you customized in the version 1.3 and compare them with the files supplied with the version 1.4. Do all needed adjustments to keep your changes and add what’s new/changed.

2.Import using the appropriate command (import, config, icon, strings) :

othe new files;

othe files you compared and modified;

oall the other files listed in the released installconfig (that we may have modified from 1.3 to 1.4).

The files import order is important, see the released installconfig for the proper order.

At least one of the following CMYK profiles must be installed on the server: "Photoshop 5 Default CMYK.icc", "RSWOP.icm" or "U.S. Web Coated (SWOP) v2.icc". For a manual deploy the profiles can be found into the ICCProfiles.zip on the daily/main FTP folder.

Explanation of the bug fix: When the parser finds no color profile in the original image, it tried to set the default RGB profile (on a CMYK), with unexpected results. Now it sets a standard CMYK profile before the RGB conversion.

Due to changes in the Exalead index definitions (document connector renamed documents), delete all existing entries in the gn_indexqueuetable with the following SQL query:

truncate table gn_IndexQueueTable

Due to the changes in spell-checkers management (share settings between Web and Windows client spell-checkers), the configuration sections (in EditorialConfig.xml) and (in ServerConfig.xml) have been standardized, merged and moved to a new section in GlobalConfig.xml. The distributed GlobalConfig.xml file is auto-documented.

Look at yours GlobalConfig and modify it in the same way as distributed GlobalConfig.

Moreover, due to the those changes, the personal preferences about which spell checker to use are deleted, and the drop-down list in the Language... on the Spell checker tab of the Preferences dialog on the Articles main tab will be empty after the upgrade.

Therefore, the users will need to reselect the spell-checker manually.

In GNPortal, instruction strings were not encoded before being displayed. It has been changed in version 1.4.
However, some people were used to take advantage of this bug in order to insert break lines in instruction strings, like this:

Now, if you want to insert line breaks into instructions, you need to use the "\r\n" sequence, i.e. the configuration above must be written like this:

This applies only if upgrading to 1.4.1517.x or newer!

This version uses $credit, $summary and $authors as names for placeholders in image captioning configuration instead of credit, summary, authors (as it was before). Thus, you need to adjust all personal preferences on all sites that use 1.4 before upgrading to 1.4.1517.x.

An alternative is to use captions defined on the global level, instead on the personal preferences (introduced in 1.4.1517.x or newer). The priority is the “global” caption, if defined. By default it is empty, therefore, if you don’t define the global one, the personal ones will be used.

To enable it the global preference for the caption, add the line to your EditorialConfig such as:

<Item Name=" glbAFPCC_PCFields " Value=" >credit<$credit^>pie1<$summary" />

That corresponds to the personal preference:

>credit<credit^>pie1<summary