SP4: File Integrity Checks: no coherent bypass rules
----------------------------------------------------
Key: JAHIA-3155
URL: http://www.jahia.org/jira/browse/JAHIA-3155
Project: Jahia Content Management Server
Issue Type: Sub-task
Components: Edition Pop-ups / Engines
Affects Versions: WCM 5.0 SP4
Environment: SP4 21008
Reporter: Stephane Croisier
Assignee: Xavier Lawrence
Fix For: WCM 5.0 SP4
There is no coherent and consistent bypass rules regarding files. We should try
to implement something similar to the workflow warnings, partial blockers and
blockers.
Sometimes you can bypass (e.g: ACL... but they are reinitialized to the old
value). Sometimes you can not bypass (ex: deleting a file whihc is used).
When there is some multiple select (e.g: selecting a directory which is using a
file in staging only and another directory with a file in live) the integrity
error mentions that we could suppress the directory (warning only)... but
finally it does not delete any of both directories. In such a case we should
have some partial error (deleting only the guilty directory).
We also need to decide who can bypass file integrity checks. I would add a new
role in the admin Center about it.
Of course root could always bypass all integrity checks (which is not the case
currently if you try to delete a file used in live mode).
--
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
