"Open in FrameMaker" option not working

[tsherman1]

The "Open in FrameMaker" option in our AEM Guides instance is showing up fine -- and it used to work for me. But lately (I think since upgrading versions of Guides and FrameMaker (to 2020), when I click "OPen in FrameMaker" to open either a .dita file or .ditamap file in FrameMaker, the screen just sort of blinks and then nothing happens. This happens to one of my coworkers as well, but is working properly for a handful of my other coworkers. I've checked that .dita and .ditamap files are set to open in Adobe FrameMaker 2020 by default on my system. I tried to allow pop-ups for our aem production instance. Any other ideas on why the OPen in FrameMaker option is not working for me and how to fix it? Thank you!

[DivrajSingh]

@tsherman1 : Since this is working for some of your coworkers and not working for few including you - so AEM Guides upgrade should not be an issue as I understand. Probably the "Open in FrameMaker" action is not able to find the FrameMaker application to launch on your system.

Can you check if you have multiple versions of FrameMaker installed on your system? or if FrameMaker registry is valid? - you may reach out to FrameMaker support for steps on this.

[tsherman1]

Thank you for your quick response Divraj! I've entered a FrameMaker support case to see if they can help me fix it. It's a very handy option! And to answer your first question, I no longer have two versions of FrameMaker installed, but I did when this issue first started happening. I now only have 2020 installed, I removed 2019 a few weeks ago. Thanks! 

[Beaula123]

How to disable this open in framemaker option from Guides. We disabled this in XMLEditorConfiguration, but still appearing after recent Guides upgrade to 4.6.0 and showing the empty page.

[DivrajSingh]

@Beaula123 : was this earlier changed directly on server?

Probably if the config is added to the code and deployed then the upgrades should not overwrite that.(read more)

I hope that is the case, if not would it be possible to share the config "com.adobe.fmdita.xmleditor.config.XmlEditorConfig" committed to code?

[Beaula123]

Hi @DivrajSingh ,

Thank you for the quick response. Below are the XMLEditorConfiguration 

[DivrajSingh]

@beaubeau : we would need the config file committed to code (if it is available). 

You can share this in a inbox message or reach out to us directly on Adobe email or support to share above code file.

[saidineshch]

Hi @DivrajSingh I have shared the code file with you in the chat. Could you please check and let us know your comments on the same. Thank you!

[Beaula123]

@DivrajSingh , Below is the code we have in code reposirty

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"

    jcr:primaryType="sling:OsgiConfig"

    fmdita.hide.oldmapeditor="{Boolean}true"

    fmdita.useapproval="{Boolean}false"

    process.label="Xml Editor Configuration Manager"

    xmleditor.autocheckout="{Boolean}false"

    xmleditor.autosave="{Boolean}true"

    xmleditor.autosaveinterval="{Long}1800"

    xmleditor.checkin="{Boolean}false"

    xmleditor.classes="topic, section, table, simpletable, fig, image, ul, ol, note"

    xmleditor.openinframebuttonshow="{Boolean}false"

    xmleditor.openinsametab="{Boolean}false"

    xmleditor.pattern="${elementName}_${id}"

    xmleditor.preventcheckedoutcontentdeletion="{Boolean}false"

    xmleditor.replaceall="{Boolean}false"

    xmleditor.savenewversion="{Boolean}true"

    xmleditor.tabs.baseline="{Boolean}false"

    xmleditor.uniquefilenames="{Boolean}false"

    xmleditor.uuid="{Boolean}true"/>

[DivrajSingh]

Thanks @Beaula123 @saidineshch : I assume that this is same as the other open thread you have raised. We will share updates on the other thread only as this page was related to a different issue originally

 I will analyze the files you shared and give an update soon