[ 
http://jira.nuxeo.org/browse/NXP-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58564#action_58564
 ] 

David commented on NXP-3495:
----------------------------

I think that the same problem is in older version of nuxeo 5.1.6.
I am using admin rights , so I have not permission problems.
I have one published document version 1.0 in a section called "test" and I have 
this document in workspaces but with the version 1.1.
When I try to publish the document version 1.1 over the section called test 
(where is the document with version 1.0) the version is still 1.0.
Ok I can do it by unpublish and later try again with publish tab and works ok, 
but It should update the document.
But when I try to do the same thing with a normal user with read rights in 
sections and write rights in workspaces I cannot do that.



> Fix version number increment when versions are snapshotted
> ----------------------------------------------------------
>
>                 Key: NXP-3495
>                 URL: http://jira.nuxeo.org/browse/NXP-3495
>             Project: Nuxeo Enterprise Platform
>          Issue Type: Bug
>    Affects Versions: 5.2 M4
>            Reporter: Florent Guillaume
>            Assignee: Florent Guillaume
>            Priority: Major
>             Fix For: 5.2 GA
>
>
> When you publish a document, the current document's version number isn't 
> changed, which means that if you then modify it and republish it, another 
> version with the same version number will be created.
> It's not acceptable to have two versions in the archives with the same 
> version number.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to