Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-1310

Better logging for failing import for initializeNodecontent

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • None
    • 2.01.00m06.3
    • None
    • None

    Description

      If I have log level on warn, and I get an error during initialization, I cannot see at all which import file failed. I then have to run the import again, now on info level, so see at info level which file did not succeed:

      So, is it ok to add to the method the location of the file that is loaded, such that we can print the failing file when an exception is caught? Would be nice to see the failing file

      Attachments

        Activity

          People

            aschrijvers Ard Schrijvers
            aschrijvers Ard Schrijvers
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 30 minutes
                1h 30m