-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: Master
-
Fix Version/s: 7.1.10 DXP FP1, 7.1.1 CE GA2, 7.1.10.1 SP1, 7.1.X, Master
-
Component/s: Portal Configuration, Portal Configuration > Custom Fields, Staging
-
Branch Version/s:7.1.x
-
Backported to Branch:Committed
-
Fix Priority:4
-
Git Pull Request:
Steps to reproduce:
- Enable Remote Staging (Not reproducible in Local Staging)
- Navigate to Control Panel > Configuration > Custom Fields > Document
- Add new custom field for Document
- Add new file entry and fill the custom field for that file entry
- Export Custom Fields portlet on staging server, then import it to the remote live (this is a new step after the fix)
- Publish to Remote Live
- Assert document in live contains the custom field value
- Go back to staged site
- Delete the custom field you created in step 3
- Assert document does not have the custom field value
- Export Custom Fields portlet on staging server with deletions included, then import it to the remote live with the deletions included (this is a new step after the fix)
- Publish to Remote Live
- Navigate to document
Expected result: File entry does not have the custom field and value.
Actual result: File entry still displays the custom field and value.
Reproduced on:
Tomcat 8.0.32 + MySQL 5.6
Portal master GIT ID: c24a713afaa76290b098c57d0761cbb3479ea375