Highlighted

How to suppress the console XML log

Mentor ,
Sep 23, 2015

Copy link to clipboard

Copied

Hi, I am attempting to upgrade to FM2015. I have a structure app (not DITA) that includes an XSLT stylesheet. Every time I save an XML file, the console pod pops up with something like the following:

Save as XML Log

Source Document: C:\documentation\command_manuals\tl1_source\a.xml

Destination Document: C:\documentation\command_manuals\tl1_source\a.xml

XSLT Processor Messages

Transformation Successful.

Can I stop this from happening? I don't need to know that there weren't any problems. The console is intrusive and interferes with my work.

This behavior started in FM12 and actually caused me to stay with FM11. It is incredibly aggravating and a show-stopper for any serious XML author in my situation. You can size down the pod and nearly hide it somewhere, but then you miss any error messages that are important. I really hate the idea of remaining stuck on FM11 again due to this issue.

Thanks,

Russ

Hi Russ,


Hope you are doing well…!


The issue reported by you has been fixed in FrameMaker latest update i.e. FrameMaker 2015 update 2 ( 2015.0.2)


You can update it by going to Help menu > updates or can also update it manually by going to the following link -

https://www.adobe.com/support/downloads/detail.jsp?ftpID=5996


Let me know how it goes at your end.


Regards,

Raj

FM Team

TOPICS
Structured

Views

588

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

How to suppress the console XML log

Mentor ,
Sep 23, 2015

Copy link to clipboard

Copied

Hi, I am attempting to upgrade to FM2015. I have a structure app (not DITA) that includes an XSLT stylesheet. Every time I save an XML file, the console pod pops up with something like the following:

Save as XML Log

Source Document: C:\documentation\command_manuals\tl1_source\a.xml

Destination Document: C:\documentation\command_manuals\tl1_source\a.xml

XSLT Processor Messages

Transformation Successful.

Can I stop this from happening? I don't need to know that there weren't any problems. The console is intrusive and interferes with my work.

This behavior started in FM12 and actually caused me to stay with FM11. It is incredibly aggravating and a show-stopper for any serious XML author in my situation. You can size down the pod and nearly hide it somewhere, but then you miss any error messages that are important. I really hate the idea of remaining stuck on FM11 again due to this issue.

Thanks,

Russ

Hi Russ,


Hope you are doing well…!


The issue reported by you has been fixed in FrameMaker latest update i.e. FrameMaker 2015 update 2 ( 2015.0.2)


You can update it by going to Help menu > updates or can also update it manually by going to the following link -

https://www.adobe.com/support/downloads/detail.jsp?ftpID=5996


Let me know how it goes at your end.


Regards,

Raj

FM Team

TOPICS
Structured

Views

589

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Sep 23, 2015 0
Advisor ,
Sep 23, 2015

Copy link to clipboard

Copied

Hi Russ...

I'd like to know this as well. I have avoided FM12 and FM2015 for this reason as well. I thought that there was some discussion about providing a switch to turn it off, but don't know if that was implemented.

Here's hoping!

...scott

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 23, 2015 0
Mentor ,
Sep 23, 2015

Copy link to clipboard

Copied

Scott, thanks for the moral support. It really is a big productivity issue. It's so ridiculous that such a thing was implemented in an advanced, high-end application to make everything else seem unusable. The error messaging is good... it's the non-error messaging that just makes no sense. Anyway, in lieu of a fix, I wrote a script that warns me of certain errors that might appear, so I can just tuck the pod away but not miss the important stuff. It is so silly that I have to do this.

var activeDoc;

InitializeNotifications();

//Examines the console pod for keywords to alert

//if there was an error with an XML action.

//This is a workaround to the inability to suppress

//non-error messages from popping up the console.

//With this function as a sentry, you can hide the pod

//out of the way but still be alerted to error messages.

function HandleConsoleXmlLog()

{

    var error = false;

   

    //these are the strings/keywords to use to detect an error

    var keywords = new Array(0);

    keywords.push("error");

    keywords.push("invalid");

    keywords.push("xsl transformation not applied");

    var consoleText = app.FMConsoleString;

   

    if(consoleText == "") return;

   

    for(var i = 0; i < keywords.length; i++)

    {

        if(consoleText.toLowerCase().indexOf(keywords.toLowerCase()) > -1)

        {

            error = true;

            i = keywords.length;

        }

    }

    //One fallback... we really want to see the "transformation successful" message.

    if(consoleText.toLowerCase().indexOf("transformation successful") < 0) error = true;

   

    //If an error, report.

    if(error) alert("The XML action appears to have generated an error. The message "

        + "reported to the console was:\n\n"

        + consoleText);

       

    //We always clear the console then.

    app.FMConsoleString = -1;

   

    //Make sure we've returned focus to the active document.

    app.ActiveDoc = activeDoc;

    activeDoc.IsInFront = true;

}

   

function InitializeCmdsAndNotifications()

{

    Notification(Constants.FA_Note_PostOpenXML , true);

    Notification(Constants.FA_Note_PreSaveXML , true);

    Notification(Constants.FA_Note_PostSaveXML , true);

}

//Notifications

function Notify(note, object, sparam, iparam)

{

     switch (note)

    {

        case Constants.FA_Note_PostOpenXML:

       

            //alert("Opened XML");

            activeDoc = app.ActiveDoc;

            HandleConsoleXmlLog();

               

            break;

 

        case Constants.FA_Note_PreSaveXML:

       

            //alert("Pre saved XML");

            activeDoc = app.ActiveDoc;

               

            break;

 

        case Constants.FA_Note_PostSaveXML:

       

            //alert("Post saved XML");

            HandleConsoleXmlLog();

               

            break;

     }

}

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 23, 2015 0
Advisor ,
Sep 23, 2015

Copy link to clipboard

Copied

Nice. I'll give this a test drive.

Yes .. it is a little crazy that you have to go tall this effort to get rid of a completely unnecessary message.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 23, 2015 0
Adobe Employee ,
Nov 27, 2015

Copy link to clipboard

Copied

Hi Russ,


Hope you are doing well…!


The issue reported by you has been fixed in FrameMaker latest update i.e. FrameMaker 2015 update 2 ( 2015.0.2)


You can update it by going to Help menu > updates or can also update it manually by going to the following link -

https://www.adobe.com/support/downloads/detail.jsp?ftpID=5996


Let me know how it goes at your end.


Regards,

Raj

FM Team

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Nov 27, 2015 0
Mentor ,
Dec 01, 2015

Copy link to clipboard

Copied

Hi Raj,

As best I can tell, you have fixed it. Thank you very much. This was a serious usability issue.

Russ

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Dec 01, 2015 0