[
http://www.jahia.net/jira/browse/JAHIA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Croisier reopened JAHIA-2071:
--------------------------------------
Assignee: Thomas Draier (was: Sergiy Shyrkov)
The problem of independancy on a per language validation workflow is sill
present.
Clearly speaking we should extend read-only lock on a per language basis and
not only on a per container basis. It should be possible to validate a page in
its main language while translators are still doing their job in staging mode
in other optional language, which is not possible yet. This gives any
translation work quite difficult.
The same is true with "deletion" of content where it is not possible to delete
one lang only (because you validate too fast a language for example but the
master language is correct). You have to validate your whole page in all
language. Quite a shame. And you also have no manner to put some time based
publishing on a per language basis... so no way to hide a wrongly validated
language excepted deleted the whole page or section in all languages.
Certainly something for Barbarella if we do not have the time to refactor a bit
locks and granularity of validation on a per object AND per language basis.
> Sp3 Workflow in multilang: possible to refuse a page waiting for validation
> in one language only - all lang should be interconnected or a waiting for
> validation lock per lang should be implemented
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JAHIA-2071
> URL: http://www.jahia.net/jira/browse/JAHIA-2071
> Project: Jahia Web Content Management Server (WCMS)
> Issue Type: Bug
> Components: Workflow, Notifications and Publishing
> Affects Versions: WCM 5.0 SP2
> Environment: Sp2 17629
> Reporter: Stephane Croisier
> Assignee: Thomas Draier
> Priority: Major
> Fix For: WCM 6.0 (Andromeda)
>
> Attachments: screenshot-1.jpg
>
>
> It is currently possible to refuse a workflow for a page for one language
> only. So one lang is in yellow state and the other is back in the red state.
> However the "waiting for validation" lock is currently valid for all
> languages.
> So I would suggest:
> 1) for the SP2 to put back in staging mode (red) all the lang of a page even
> if you only select one lang to refuse
> 2) for SP3 to work on a refactoring of the waiting for validation lock in
> order to support the new read only engine on a lang per lang basis so that
> each lang could have a different validation process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/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
