-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.X, 7.1.X, Master
-
Fix Version/s: 7.0.0 DXP FP81, 7.0.10.12 DXP SP12, 7.0.X, 7.1.3 CE GA4, 7.1.10 DXP FP11, 7.1.X, Master
-
Component/s: Adaptive Media, Staging
-
Branch Version/s:7.1.x, 7.0.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
Sprint:023 - Ekans
-
Git Pull Request:
Reproduction steps:
0.) Use the latest master bundle
1.) Make sure the Adaptive Media plugin is deployed. When the system has started please verify it in Control Panel → Configuration → Adaptive Media.
2.) Create a new site and enable local Staging.
3.) Go to Content → Web Content, here create a basic web content and from alloy editor select and image and publish it.
4.) Make a Staging publication.
Checkpoint: Everything should work as expected.
5.) Go back to Content → Web Content, edit the article created in step 3 and change the image to source view. Manually delete the fileentryid value (you should see ‘data-fileentryid=""’) and publish it.
Checkpoint: It is a bit strange that the article can be published without any warning messages. This isn't the most relevant part of the use case.
6.) Make the Staging publication.
Result: You will get a java.lang.NumberFormatException: For input string: "" on the UI and detailed log it attached to the LPP.
Also tested:
master @ commit (ff37027c5444b07f828061372960853cdb22199c) reproduced