Skip to main content
S
Sherri_McCue
Participant
February 14, 2017
Question

Validation Error Messages Not Logged In Console Window (FM12)

  • February 14, 2017
  • 1 reply
  • 2010 views

When I save a structured documents as XML (File -> Save As – XML), messages and errors appear in a Console Pod but are not reflected in the Console Window or in consfile.txt

Any help appreciated.

This topic has been closed for replies.

1 reply

S
shoose
Known Participant
March 11, 2017

I have this problem also -- I need to capture the validation errors somewhere, but they are not logged to consfile.txt.  Is there a setting somewhere that controls what is written to consfile?

I am using FrameScript also, and have not yet found a way to capture these validation errors from the console pod and copy them to a file somewhere.

This seems like a serious bug or issue in Frame, that errors just disappear and are not logged anywhere, unless there is a workaround.

I'm now on FM 2015.

Thanks much,

Shelley

W
Wiedenmaier
Inspiring
March 14, 2017

I'm never used the console.txt file for error handling in all the years.

XML messages that appear are validation issues mostly. So you can check the root element if structure is valid after document is opened or before it is saved.

Other issues are due to an inconsistent environment, XML application. So once your Setup is correct, there is no need anymore to check console.txt.

Markus

S
Sherri_McCueAuthor
Participant
March 14, 2017

Shelley,

I'm with you, and I think this is a "bug" in FM 2017 (not before) which should be fixed in FM. So that all messages which appear in FM Console are written to console.txt in the same way. Perhaps Adobe's listening :-)

But as there is no solution and I have no idea, I think you have to find a way around that. I understand that users (as we all) are  making mistakes and this leads to invalid XML files und to problems within publication processes.

To solve this issue and as you are alread working with ExtendScript/FrameScript you can catch these errors easily.

1. Get the highest level element from MainFlow

2. Get the FP_ValidationFlags property of the element. If it's 0, everything is OK otherwise to some error handlings

For more Information see the FDK Programmers Reference and search for "Element validation properties". If you don't have the reference you can get it from here Framemaker Developer Center | Adobe Developer Connection .

If your EDD and XML environment is consistent, this should solve your problems with invalid structures.

My be you will have problems with missing graphics referenced in your XML file. IMHO FM logs this also to this console and not to console.txt. To check this loop the documents for all Graphics of type FO_Inset and check if file is existing.

I don't know of any other problems reported when XML files are opened and your enviornment is setup correctly.

This all can be part of your Validation functionalität. One part of it greps console.txt and the other parts check the document. And in Adobe fixes this issue in future, you can simply remove your code and grep console also for these kind of problems.

But as already said; I always validate the document and don't care console output. One reason is: so I'm sure that what I check is correctly and the other reason is I have not to worry if Adobe changes the log text in any release.

Hope this helps

Markus


I concur that it is a bug that makes automation (machine-driven) validation more difficult than it should be. What is the point in having a console pod that has errors that never get to the console and more importantly console.txt. Adobe please fix.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices