-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: Master
-
Fix Version/s: 7.1.X, 7.2.10 DXP FP1, 7.2.1 CE GA2, 7.2.X, 7.3.10 DXP GA1, Master
-
Component/s: Fragment Administration
-
Branch Version/s:7.2.x, 7.1.x
-
Backported to Branch:Committed
-
Fix Priority:5
-
Git Pull Request:
This piece of code when importing FragmentEntryLinks assumes that the FragmentEntryLink has a FragmentEntry in the database. There are times where it often is not the case, as when using contributed fragments.
Currently Contributed Fragments will not be importable (exporting is okay if you want to save the LAR for later).
Steps to Reproduce
- Activate Local Staging
- Add a Fragment Entry Link with no Fragment Entry ( Add a Contributed Fragment)
- Publish to Live
Expected Result
Fragment Entry Link present on live site
Actual Result
Fragment Entry Link not present on live site
Tested on Tomcat 9.0.10 + MySQL 5.7
Portal master GIT ID: 826a5b06994aa6d1cd2f0afc79023ad7e44f627b
- demands
-
LPS-98370 Create integration tests to test export/import fragmentEntryLinks with no fragmentEntryId (Contributed Fragments)
-
- Closed
-
- fixes
-
LPS-97991 Publishing to remote staging should take into account fragment configuration
-
- Closed
-
- is caused by
-
LPS-98038 Deactivating staging breaks connection between fragment entry links and fragment entries
- Closed
- is duplicated by
-
LPS-98379 Publishing content page contains category throws PortletDataException
- Closed