Affects Version/s: Master
Component/s: Fragment Administration
Many times we assume the classNameId / classPK pair is correct when creating FragmentEntryLinks. It seems like better practice to validate that the classNameId / classPK pair is valid upon creation to prevent unexpected errors further down the road.
Steps to Reproduce
- Create a FragmentEntryLink with invalid classNameid / classPK combo (remote or local service), but with a valid FragmentEntryId as a reference.
- Check Usages for the Fragment Entry or Publish the Fragment Entry Link to live site
FragmentEntryLink not even allowed to be added with invalid classNameId/classPK in the first place
Because we tried fetching the FragmentEntryLink's className id / classPK and failed, we got an exception thrown
Tested on Tomcat 9.0.10 + MySQL 5.7
Portal master GIT ID: 826a5b06994aa6d1cd2f0afc79023ad7e44f627b