= Reinstate missing image warnings in either generate.log or in a report = == Summary == When generating a project, ePublisher used to include warning messages in the generate.log file for any referenced images that were not present in the source. Current versions of ePublisher (2009.3) do not output these messages any more and there is no other way to determine whether any images are missing. We need this functionality to QA our large generated doc set - please reinstate! == Detailed Description == When I used 9.2 and 2008.1, ePublisher would output [WARN] or [Warning] lines for any referenced images that were not present in the source when generating output. It appeared in the Splits pipeline. The following excerpt shows the output, taken from a 2008.1 generate.log file: {{{ Processing pipeline 'Splits', 9 of 25. [WARN] Image file not found 'C:\DocsrootS\source\BusinessSuite_Guide\Graphics\Chap1Graphic1.bmp'. [WARN] Image file not found 'C:\DocsrootS\source\BusinessSuite_Guide\Graphics\Chap3Graphic1.GIF'. Processing pipeline 'Copy', 10 of 25. }}} After upgrading to 2009.3, I found this was no longer output, either in the generate.log file, or anywhere else. Webworks Support has confirmed that this was removed from the product. (I'm generating Webworks Help 5.0 but I think this is an issue common to any output format.) == Use Cases == If you are building a large doc set containing many books by multiple writers and utilizing a version control system like CVS or Subversion, it's easy for images to get lost in the mix. It's not practical to manually load each book in FrameMaker before each build to determine whether it has any missing images. It's also impractical to use a link checker to check the output (they typically have problems with Webworks Help 5 because it's so heavily controlled by Javascript). Having this back in the generate.log would work. It would also work to have this in the reports, either added to an existing one like the Links Report, or in a new report. ePublisher really should provide messages on basic problems with output like this. I'm not sure why these have been classified as warnings in the past since you would never want to ship generated output with missing images. ---- <>