-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 DXP FP71, 7.0.X, 7.1.X, Master
-
Fix Version/s: 7.0.0 DXP FP74, 7.0.10.11 DXP SP11, 7.0.X, 7.1.10 DXP FP8, 7.1.10.2 SP2, 7.1.3 CE GA4, 7.1.X, Master
-
Branch Version/s:7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Story Points:0.25
-
Fix Priority:4
-
Git Pull Request:
AssetPublisher is imported without configuration in case of an Exception during export/import operation.
Root cause of the issue:
- A try...catch of any Exception was added during portlet staging data handlers modularization to osgi (see
LPS-56496) - In 6.x there was no try...catch there
Steps to reproduce
- Create a new site
- Activate local staging
- Go to Staging environment:
- Create a page and add an Asset Publisher
- Publish to live
- Execute select * from Group_ where liveGroupid <> 0 and get the staging groupId of your site
- Execute following SQL update in order to cause an Exception. Note: replace <<GROUPID>> with your staging groupId
update set preferences='<portlet-preferences><preference><name>anyAssetType</name><value>99999999999999999</value></preference></portlet-preferences>' where plid in (select plid from Layout where groupId = <<GROUPID>>) and portletId like 'com_liferay_asset_publisher_web_portlet_AssetPublisherPortlet_INSTANCE_%'
- Go to Control Panel => Configuration => Server Administration => Resources and clear all Liferay caches
- Go to Staging and try publishing to Live:
- Expected behavior: An error is produced and Asset Publisher changes are not published to live
- Wrong behavior: A warn trace is written to log and changes are published to live
- Expected behavior: An error is produced and Asset Publisher changes are not published to live