-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: 7.3.10 DXP FP2
-
Fix Version/s: None
-
Component/s: Fragment Administration, Fragments Toolkit
-
Labels:None
Steps to reproduce:
- Create a React example fragment with the Fragment Toolkit
- Import it to a Liferay DXP 7.3 FP2 running instance
- Drag and Drop the fragment into a page by editing that page
Expected result: The React Component should be rendered
Actual result:
- Only the HTML is rendered
- In JS Console you get the following error
A require() call has failed but no failure handler was provided. Note that even if the call stack of this error trace looks like coming from the Liferay AMD Loader, it is not an error in the Loader what has caused it, but an error caused by the require() call. The reason why the Loader is in the stack trace is because it is printing the error so that it doesn't get lost. However, we recommend providing a failure handler in all require() calls to be able to recover from errors better and to avoid the appearance of this message. Some information about the require() call follows: - Require call id: 2 - Required modules: (2) ['[email protected]/render.es', '[email protected]/fragmentEntryLink/41081']0: "[email protected]/render.es"1: "[email protected]/fragmentEntryLink/41081"length: 2[[Prototype]]: Array(0) - Missing modules: (n/a) Error: Unsatisfied dependency: __REACT_PROVIDER__$react found in module [email protected]/fragmentEntryLink/41081