Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-38756

content.cleaner.errors.logged property is wrong in docs and doesn't work

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0
    • Fix Version/s: 10.6
    • Component/s: Kernel
    • Labels:
      None
    • 10 status:
      Resolved
    • Previous Issue Keys:
      KNL-1376
    • Test Plan:
      Hide

      The test plan for this would be
      Set the sakai property content.cleaner.errors.logged=true
      Leave content.cleaner.errors.handling the default (which is notify) start up Sakai.

      You should have detailed errors in the logs when there is a formatting error (like if you add the <script></script> tag to a rich text area)

      Show
      The test plan for this would be Set the sakai property content.cleaner.errors.logged=true Leave content.cleaner.errors.handling the default (which is notify) start up Sakai. You should have detailed errors in the logs when there is a formatting error (like if you add the <script></script> tag to a rich text area)

      Description

      There was a property added "content.cleaner.errors.logged" which in the documentation is referred to by a non-existent property content.cleaner.errors.display. In addition, unless you have the value of

      content.cleaner.errors.handling=logged set it doesn't do anything anyway

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  k1team KERNEL TEAM (Inactive)
                  Reporter:
                  jonespm Matthew Jones
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration