Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-2469

SP3: URL integrity checking: currently validate the full page ... excepted the bad field (should be at least the full container)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • xCM 5.0 SP4
    • xCM 5.0 SP4
    • None
    • Sp3 18805

    Description

      I activated the url integrity checking in the Admin Center (HTML settings panel). Then I made a href in a big text on a sub-page which was never validated yet (should be great that such pages are listed in red (as it was the case on the 5.0.0) if there were never validated yet - this ease selection of "valid" published pages).

      So I am getting an error. I accept to bypass such an error. Then I validate this page (and not the sub-page). The title of my main_content container is validated without the big text. This does not make any semantic sense. The Jahia granularity is at the container level. So either we do not validate the full container or the full page, but not all the fields excepted the bad ones... then you have some title without any content in live mode...

      Xavier worked on that previously. Previously the full page was blocked for validation while the link was not corrected. This was perhaps a bit too "hard". So we decided to put such a validation check at the ctn level. But never at the field level. Ideally such an option (block validation at the full page or at the container level) should be turn on and off through an option in the jahia.properties file (which is not the case currently), so that each site could decide if, if there is an integrity error, on the page, this blocks the full page or only the guily container. Otherwise we could add such an option in the workflow engine (in the error/warning pop-up) to let the validator decides if he wants to validate the rest of the page without this container, or the oppsite.

      Finally, when editing the guilty container from the workflow engine error pop-up, this only opens the guilty big text field (without the title or other field). So here again this is quite hard to understand which content object we are currently editing in order to modify the text accordingly. So we need to launch the full container (and perhaps position the container to the guilty field).

      TestRail: Results

        Attachments

          There are no Sub-Tasks for this issue.

          Activity

            People

              shyrkov Sergiy Shyrkov (Inactive)
              scroisier Stephane Croisier (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      xCM 5.0 SP4