5.0 R39 Pt2 DP Regression Test (ACE-2834)

[ACE-2777] "Upload new version" for edited document uses incorrect link to refresh the page Created: 16-Sep-14  Updated: 28-Nov-14  Resolved: 02-Oct-14

Status: Closed
Project: Alfresco One Platform
Component/s: Document Library
Affects Version/s: Cloud 38
Fix Version/s: 5.0

Type: Feature Bug Priority: Critical
Reporter: Dmitry Yukhnovets [X] (Inactive) Assignee: Closed Issues
Resolution: Fixed Votes: 0
Labels: FoHL
Remaining Estimate: 0 minutes
Time Spent: 2 days, 1 hour
Original Estimate: Not Specified

Cloud2 myAlfrescoHead5.0 build 676 stable-rel39rc1 DP, Layer7

Issue Links:
Test In: DP
Build Location: ftp://pbld01.alfresco.com/nightlybuilds/Enterprise-5.0/5.0.0/build-00154/
Regression Since:
Sprint: Rel 5.0 R39 Pt2 (WAT1 & PLAT1)
Cloud or Enterprise: Cloud and Enterprise


1. Create any site
2. Upload any document
3. Execute "editing offline" action for the document
4. open document details for the doc
5. Upload new version for the doc.

Expected: page should be refreshed, working copy for the document will be removed, version for the document should be updated.
Actual: At the moment after uploading new version of content - the page is refreshed (please see the fix for the ACE-2578, it uses the function window.location.reload(); but in this case it should the redirect to original document, instead of refreshing page for working copy).
so as a results page will be refreshed, but document will not be displayed because it still uses working copy instead of original document.

Comment by Brian Remmington [ 16-Sep-14 ]

This appears to be a problem with the fix for ACE-2578, which works for documents that are not checked out but fails in the case of the document being checked out.

Comment by David Draper [X] (Inactive) [ 25-Sep-14 ]

The proposed fix doesn't seem to make any sense, we're already updating the URL to be completely different because the nodeRef has changed... e.g:

NOTE: that we have a different request parameter, what seems to be happening is that either the window location update is not being honoured or something else is restoring the window location.

Can you please investigate this, even if the fix you're proposing does work I suspect it is not for the reason you suggest.

Generated at Thu Jul 09 09:19:39 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.