• Replies 3 replies
  • Subscribers 137 subscribers
  • Views 1162 views
  • Users 0 members are here
Options
Related

Issue with IshPublishCompare; Draft options not appearing in form

Mario Madunic

Hi I have the following code in "Publish plug-in XML settings"

<postprocess ishcondition="ISHOutputFormat.FDITAOTTRANSTYPE in ('transtype1', 'transtype2', 'transtype3', 'transtype4')">

...
   <compare handler="IshPublishCompare" ishcondition="ISHOutputFormat.FDITAOTTRANSTYPE = 'transtype3'">
      <parameters />
   </compare>

...

</postprocess>

The list of transtypes that will require compare to be available is quite large but have been testing with a single one currently.

The "Draft options" is not appearing for transtype3 or when I use the following:

ishcondition="ISHOutputFormat.FDITAOTTRANSTYPE in ('transtype2', 'transtype3')"

I've also tried creating individual <postprocess /> for each transtype and still no "Draft options".

This issue is happening in both Pub Manager and the Web interface, just incase that matters.

Also I've recycled the app pool before testing.

Any insight into this issue will be appreciaated

kr

Mario
Rate translation
×
Suggest better translation
×
Parents

  • Hey Mario,

    The 'Draft options' section in the webclient and/or client tools dialogs is not controlled by the postprocess element(s) in the 'XML Publish Plug-in Settings'.

    You need to update the metadataconfig.xml file available on the filepath <drive-letter>:\Infoshare\Web<project-suffix>\Author\ASP\ClientConfig.

    This xml file controls the dialogs which are used by the webclient / client tools.

    So in this file search for the following '<ishfrmgroup ref="PublicationOutput.DraftOptionsGroup" ' and extend the ishcondition attribute with the outputformat names for which the draft options should be available.

    After you have changed this file you need to:

    - recycle the apppools in order to see the change in the webclient.

    - close all of your client tools (Publication manager / Editors) and restart/reconnect so that the synchronization step will apply the change to your local system as well.


    Kind Regards,

    Raf
  • in reply to Raf Snijders

    Raf, thank you. I do have one more question then. What is the relationship between Publish plug-in XML settings and metadataconfig.xml?
  • in reply to Mario Madunic

    Hi Mario,

    Actually there is no real relationship between Publish Plug-In XML settings and the metadataconfig.xml apart from the fact that the items enable/supplied by one area can be used by the other.

    The metadataconfig.xml allows you to control and define the different dialogs that are used in our system.
    So this file allows you to enable the compare option for publication outputs. However if you do not provide a version to compare with value in the publication output object that gets published, the Publish plugin configuration will not execute the Compare routines.

    The Publish Plug-in XML settings xml content allow you to control and define the sequence of plugins that need to be executed in order to transform the published content into the final deliverable.
    So this configuration is targetting the transformation steps from xml to the final format. If the publication output object provides information about compare (so the option is set in the dialog) and the sequence has the compare option configured as step in the process, the actual compare will be triggered.

    But there is no relationship/dependency between both files


    Kind Regards,

    Raf
Reply
  • in reply to Mario Madunic

    Hi Mario,

    Actually there is no real relationship between Publish Plug-In XML settings and the metadataconfig.xml apart from the fact that the items enable/supplied by one area can be used by the other.

    The metadataconfig.xml allows you to control and define the different dialogs that are used in our system.
    So this file allows you to enable the compare option for publication outputs. However if you do not provide a version to compare with value in the publication output object that gets published, the Publish plugin configuration will not execute the Compare routines.

    The Publish Plug-in XML settings xml content allow you to control and define the sequence of plugins that need to be executed in order to transform the published content into the final deliverable.
    So this configuration is targetting the transformation steps from xml to the final format. If the publication output object provides information about compare (so the option is set in the dialog) and the sequence has the compare option configured as step in the process, the actual compare will be triggered.

    But there is no relationship/dependency between both files


    Kind Regards,

    Raf
Children
No Data