[
http://www.jahia.org/jira/browse/JAHIA-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergiy Shyrkov resolved JAHIA-2469.
-----------------------------------
Resolution: Fixed
Resolution: prevent the whole container from being activated if at least one
field is not valid for activation
> SP3: URL integrity checking: currently validate the full page ... excepted
> the bad field (should be at least the full container)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JAHIA-2469
> URL: http://www.jahia.org/jira/browse/JAHIA-2469
> Project: Jahia Content Management Server
> Issue Type: Bug
> Components: Workflow, Notifications and Publishing
> Affects Versions: 5.0 SP4
> Environment: Sp3 18805
> Reporter: Stephane Croisier
> Assignee: Sergiy Shyrkov
> Priority: Critical
> Fix For: 5.0 SP4
>
>
> 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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
