AEM 6.0, no content in editor.html window

Question

I recently migrated a development site from AEM 5.6 to 6.0. When I click on the edit icon, in Touch UI mode, a blank page loads without a user interface. The Url sample in this mode looks like this: localhost: 4502 / editor.html / content / mypage.html

If I switch the URL to the classic content search engine, my page and all its content show: local: 4502 / cf # / content / mypage.html

If I click on the page properties, this URL loads and is completely styleless, this is a long list of links for the AEM user interface, including my user settings, but not the page settings. local: 4502 / LIES / WCM / core / content/sites/properties.html/content/MyPage

Has anyone experienced this? Does editor.html (Touch UI) have a different set of permissions or page properties that are not in Cf # (Classic UI)?

Answer 1

Verify that the sling: resourceSuperType page is set to / foundation / components / page. It inherits the dialogue and dialogue cq :. This will most likely solve problems with editor.html and page properties.

Answer 2

Its just a copy-paste from one of the adobe sites explaining the differences between Touch and Classic UI

The dialog box created for the Touch user interface is defined using nodes of type un: structured. You determine the type of control in the Touch UI dialog by setting the node sling: resourceType property. For example, to define a text field in the Touch UI dialog box, set the sling: resourceType property to granite / ui / components / foundation / form / textfield.

Note: When creating a dialog for the Touch UI view, you determine the type of control (for example, a text field) by setting the sling: resourceType property. In contrast, when building a dialog for a classic view, you determine the type of control by setting its xtype property. You set both properties in the following sections. See the Granite Link section for a list of all granite objects.

The following figure shows the JCR nodes of the component that was created in this development article.

As you can see in the previous illustration, there are two JCR branches that are associated with the component dialog:

/ applications / mywebsite2 / components / herotext2 / nh: dialog / Applications / mywebsite2 / components / herotext2 / dialog

Both of these dialogs are required when developing the AEM component. The first branch defines the component dialog used in the Touch UI environment. The second branch defines the component dialog used in the classic AEM view. Therefore, to use the component in both AEM views, you need to create JCR node branches.

So ... in summary, you need to define two dialogs if you want them to work with both user interfaces.

Answer 3

There are minor changes in accordance with AEM 6.1. Make sure your sling: resourceSuperType page component is set to wcm / foundation / components / page . You need to add this property to the page component. It inherits the dialogue and dialogue cq :. This will most likely solve the editor.html and page properties problems. I hope he decides!