• State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 137 subscribers
  • Views 2792 views
  • Users 0 members are here
Options
Related

Configuring XMetaL 11 support in SDL Tridion Docs

CMS Administrators2

I'm trying to configure support for custom XMetaL 11 macros in an SDL Tridion Docs R13 environment. The OOTB ClientConfig.xml in /Web/Author/ASP/ClientConfig.xml has no configured editors. Can anyone give me an example of how ClientConfig.xml might look with XMetaL 11 configured?

I guessed that I would add the following syncgroup - when I added other "common syncgroups" from a previous version of the CMS, they didn't seem to work.

                <syncgroup ishcondition="ClientExe='xmetal.exe'">

                                <syncfolder serverfolder="XMetaL/11.0-CRCL/Editor" clientfolder="%EDITORLOCATION%" />

                                <syncfolder serverfolder="XMetaL/11.0-CRCL/LocalStorage" clientfolder="%DATASOURCEAPPDATA%/Config" />

                                <syncfolder serverfolder="XMetaL/11.0-CRCL/RoamingStorage" clientfolder="%LOCALSTORAGEROOTPATH%/../../AppData/Roaming/SoftQuad/XMetaL/11.0" />                                

                </syncgroup>

                </syncinfo>

 

Many thanks for any help you can give.

Paul Masalsky

McAfee
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Dear Paul,

    The support for synchronizing editor specific files is not provided through the ClientConfig.xml file but through the SyncInfo.xml file. This file is located in the same folder (<drive-letter>:\Infoshare\Web<project-suffix>\ASP\ClientConfig).

    Within the SDL Tridion Docs R13 environment, this 'SyncInfo.xml' file contains support for XMetaL 11 as it contains sections to synchronize files for XMetaL 10 or later. (see snippet below from file).

    ...
    <syncgroup ishcondition="ClientExe='xmetal.exe' and ClientExeVersion>=10.0">
    <!-- The files in this group are synchronized in case the editor is 'XMetaL 10.0' or later -->
    <!-- Implements the XMetaL Content Repository Connection Layer (Repository Adapter) -->
    <!-- Following line will synchronize the DTD related files below the Program Files\XMetaL\Author folder if this is allowed by security -->
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-CRCL/Editor/" clientfolder="%EDITORLOCATION%/" />
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-CRCL/LocalStorage/" clientfolder="%DATASOURCEAPPDATA%/Config/" />
    </syncgroup>
    <syncgroup ishcondition="ClientExe='xmetal.exe' and ClientExeVersion>=10.0 and ClientEdition='J'">
    <!-- The ClientEdition ishcondition is only available for XMetaL and is used to synchronize Japanese server files for XMetaL -->
    <!-- The files in this group are synchronized in case the editor is 'XMetaL 10.0 J' -->
    <!-- Implements the XMetaL Content Repository Connection Layer (Repository Adapter) -->
    <!-- Following line will synchronize the DTD related files below the Program Files\XMetaL\Author folder if this is allowed by security -->
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-J-CRCL/Editor/" clientfolder="%EDITORLOCATION%/" />
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-J-CRCL/LocalStorage/" clientfolder="%DATASOURCEAPPDATA%/Config/" />
    </syncgroup>
    ...

    So extending or adding similar syncgroup elements with similar conditions will allow you to configure your own custom macros to be synchronized.
    You can off course also tweak the condition or add a condition to the (new) syncgroup element so that it will only work for version 11 of XMetaL and not for anyone connecting with XMetaL 10.


    I hope this helps.
    Kind Regards,

    Raf
Reply
  • 0
    Dear Paul,

    The support for synchronizing editor specific files is not provided through the ClientConfig.xml file but through the SyncInfo.xml file. This file is located in the same folder (<drive-letter>:\Infoshare\Web<project-suffix>\ASP\ClientConfig).

    Within the SDL Tridion Docs R13 environment, this 'SyncInfo.xml' file contains support for XMetaL 11 as it contains sections to synchronize files for XMetaL 10 or later. (see snippet below from file).

    ...
    <syncgroup ishcondition="ClientExe='xmetal.exe' and ClientExeVersion>=10.0">
    <!-- The files in this group are synchronized in case the editor is 'XMetaL 10.0' or later -->
    <!-- Implements the XMetaL Content Repository Connection Layer (Repository Adapter) -->
    <!-- Following line will synchronize the DTD related files below the Program Files\XMetaL\Author folder if this is allowed by security -->
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-CRCL/Editor/" clientfolder="%EDITORLOCATION%/" />
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-CRCL/LocalStorage/" clientfolder="%DATASOURCEAPPDATA%/Config/" />
    </syncgroup>
    <syncgroup ishcondition="ClientExe='xmetal.exe' and ClientExeVersion>=10.0 and ClientEdition='J'">
    <!-- The ClientEdition ishcondition is only available for XMetaL and is used to synchronize Japanese server files for XMetaL -->
    <!-- The files in this group are synchronized in case the editor is 'XMetaL 10.0 J' -->
    <!-- Implements the XMetaL Content Repository Connection Layer (Repository Adapter) -->
    <!-- Following line will synchronize the DTD related files below the Program Files\XMetaL\Author folder if this is allowed by security -->
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-J-CRCL/Editor/" clientfolder="%EDITORLOCATION%/" />
    <syncfolder serverfolder="~/ClientConfig/XMetaL/10.0-J-CRCL/LocalStorage/" clientfolder="%DATASOURCEAPPDATA%/Config/" />
    </syncgroup>
    ...

    So extending or adding similar syncgroup elements with similar conditions will allow you to configure your own custom macros to be synchronized.
    You can off course also tweak the condition or add a condition to the (new) syncgroup element so that it will only work for version 11 of XMetaL and not for anyone connecting with XMetaL 10.


    I hope this helps.
    Kind Regards,

    Raf
Children