-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.X EE, 6.2.X EE, 7.0.0 Alpha 2
-
Fix Version/s: 6.2.X EE, 7.0.0 Alpha 2
-
Component/s: Portal Configuration, Portal Configuration > Custom Fields
-
Labels:
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:9
-
Fix Priority:2
-
Git Pull Request:
Steps to reproduce:
[ On 6.1.X EE ]
- Go to Control Panel
- On left menu, go to the Portal section and click on Custom Fields
- Edit the Page resource
- Add a Custom Field of type Date with any name
- Edit this created Custom Field and set a default value to it
- On left menu, go to the second section (usually named Liferay) and click on Site Pages
- Click on Export
- Import the LAR file created by the export of the previous step
[ On 6.2.X EE ]
- In the Dockbar, go to Admin > Control Panel
- On the Configuration section, click on Custom Fields
- Edit the Page resource
- Add a Custom Field of type Date with any name
- Edit this created Custom Field and set a default value to it
- Go back to Control Panel
- On the Sites section, click on Sites
- Click on the site named Liferay
- Click on Export
- Import the LAR file created by the export of the previous step
[ On Master ]
- Open the left menu and click on Control Panel
- Click on Configuration > Custom Fields
- Edit the Page resource
- Add a Custom Field of type Date with any name
- Edit this created Custom Field and set a default value to it
- Again, on the left menu, click on Sites
- Click on the site named Liferay
- Click on Publishing Tools > Export/Import
- Click on Export
- After the export is finished, click on Publishing Tools > Export/Import
- Import the LAR file created by the export
Expected result:
The date custom field displays the default value configured before the import process.
Actual result:
The date custom field displays a default value different from the one configured before the import process.
- relates
-
LPE-14408 After import process, the date custom field displays a wrong default value
-
- Closed
-