Updating files w/o setting original document type causes metadata to be lost
Description
causes
relates
Activity
Show:
Oriana Tham July 24, 2012 at 3:45 PM
Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 1c3e587467e77199b0677cbc05da6aca718c37ed.
Tomcat 7.0 + MySQL 5. Portal 6.2.x EE GIT ID: 28e769a890b3cf3b25c3a42f69edf916f28c9dd1.
Metadata is no longer lost after updating files
Michael Saechang July 23, 2012 at 4:19 PM
Committed on:
Portal 6.1.x CE GIT ID: 55048b3593e59190976a032e400706bd585c8a5b.
Portal 6.2.x GIT ID: 711000f17887eec9d77529423b9ae32ee07273ec.
Fixed
Details
Assignee
Oriana ThamOriana Tham(Deactivated)Reporter
Dennis JuDennis Ju(Deactivated)Labels
Branch Version/s
6.1.xBackported to Branch
CommittedFix Priority
4Git Pull Request
Components
Affects versions
Priority
Medium
Details
Details
Assignee
Oriana ThamReporter
Dennis JuLabels
Branch Version/s
6.1.x
Backported to Branch
Committed
Fix Priority
4
Git Pull Request
Components
Affects versions
Priority
MediumZendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created July 6, 2012 at 2:45 PM
Updated June 24, 2023 at 3:51 PM
Resolved July 18, 2012 at 10:23 PM
Updating files (whether through the JSON web service API, WebDAV, etc) will lose all metadata (Document Type).
Solution: in an update, if we upload null metadata, we should keep the existing metadata.