Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Publish to Live creates new versions of documents even if these haven't changed

Description

Steps to reproduce:

1. Create an structure which contains a Document from Docs and Media
2. Add a new Basic Document in the Document Library.
3. Add a new web content display in a page, and add a new web content using the structure from #1 and the document in #2.
4. Activate Staging --> Check the database, table dlFileVersion, you will have 1 version in live and another in staging
5. Publish to Live again --> still the same, this is ok
6. Edit the document in Staging (now you have version 1.1)
7. Publish to Live --> Now in the database, you have another version in live (2.0)
8. Publish to Live again --> Another version is created (3.0) and so on...

The main issue is that the DLPDataHandler is assuming the version is kept when publishing (see method isDuplicateFileEntry), but the version is not kept when publishing. We should use the dlFileVersion uuid to do this checking.

Activity

Show:

Pani GuiFebruary 19, 2012 at 6:11 PM

PASSED Manual Testing following steps in description.

Fixed on:
Tomcat 6.0 + MySQL 5. 6.0.x GIT ID: ed18320a0b381993cd2202799c88eac50c38ec20.

Pani GuiFebruary 16, 2012 at 6:23 PM

PASSED Manual Testing following steps in description.

Reproduced on:
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: 64641783b89b909a79c414009543703499ea9c38.

After publishing the edited document in staging, show another live document version(2.0) in dlfileversion table in database.

Fixed on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: 2fd025d089899db55f3622ba845222fa80410d2a.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: a2f490c1b9315b6d8010173097c7d56ba497afcf.

Live document version is same as staging document version in dlfileversion table after publishing.

Michael SaechangFebruary 10, 2012 at 10:15 AM

Committed on:
6.1.x GIT ID: 4b5059dd68d5cb8f85a6aa4259fb8bf0e0927260.
6.2.x GIT ID: ace6c30db11298f8588a8db7a7e86fb32471a5bb.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Branch Version/s

6.1.x
6.0.x

Backported to Branch

Committed

Fix Priority

3

Git Pull Request

Components

Fix versions

Affects versions

Priority

Zendesk Support

Created January 31, 2012 at 9:38 AM
Updated June 24, 2023 at 3:50 PM
Resolved October 3, 2012 at 5:19 PM