[PAGES-395] JS Errors in Page Editor when area inside a component Created: 20/Oct/16 Updated: 02/Dec/22 Resolved: 02/Dec/22 |
|
| Status: | Closed |
| Project: | Magnolia pages module |
| Component/s: | None |
| Affects Version/s: | 5.4.7, 5.4.9 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mercedes Iruela | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | maintenance, to-verify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Epic Link: | AuthorX Support | ||||
| Team: | |||||
| Description |
|
When there is a component that include inside an area in its freemarker template than overwrite the content variable leads to javascript issues in the editor and the editor stops working.
[@cms.area name="tabbedContentArea" content=content/]
Javascript Exception: info.magnolia.widgetset.MagnoliaWidgetSet-0.js:304 Wed Oct 19 10:39:43 GMT+200 2016 com.vaadin.client.ApplicationConfiguration SEVERE: Null widget handle. If you are creating a composite, ensure that initWidget() has been called.java.lang.RuntimeException: Null widget handle. If you are creating a composite, ensure that initWidget() has been called. at Unknown. If you are creating a composite, ensure that initWidget(Unknown) at Unknown.Error(Unknown) at Unknown.Ac(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.qs(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.ws(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.xs(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.N(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.Ejb(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.zjb(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.qib(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.jo(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.eval(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) at Unknown.eval(info.magnolia.widgetset.MagnoliaWidgetSet-0.js) Tested in Magnolia 5.4.9(magnolia-enterprise-pro-cp13n-demo) and magnolia 5.4.7(magnolia-enterprise-pro-stk). Attached you can find a simple module with the required templates and components to reproduce the issue. The component works as expected, but there seems to be a problem with page editor, it stop working and triggered actions over the editor are not sent to server(info.magnolia.pages.app.editor.PagesEditorSubApp) to update the page (f.e. action bar is not updated). The above JS error is written on the browser console and no request/triggered action is sent to the server to update the Editor App View In the support ticket you can see the required steps to reproduce the issue:
As soon as the 'embedded' content area (step 2) is clicked, the editor is broken and stop sending requests to the server to update the page. Only a reload of the editor-tab can fix this afterwards. |
| Comments |
| Comment by Laura Delnevo [ 02/Dec/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, The Magnolia Team |