Properties at jcr:content doesn't get stored in form of items as it does at component level. it is storing as String array and could not read the values back from it.

Though I go from editor.html or sites.html, it opens : /mnt/overlay/wcm/core/content/sites/properties.html?item=pagePath.

Its both the ways. While creating the page and editing the page property after a page is created.

It is available as we are using the multifield dropdown or any combination of fields at component level and those work fine.

Please find the part of the xml which renders multifield dropdown.The same xml is used across component level and works fine. The configuration is stored node wise and renders correctly on opening the dialog but when used for page properties level, stores the configuration as string array and doesn'...

Hi,Thanks for the solution. It worked but to add new plugins to the inline toolbar, there are some issues.When I tried adding plugin - #edit  and #misctools (#plugin name) to the inline property and added new node to support features under the popover node like edit (node) with property edit#cut and...

Hi,Thanks for the suggestion.I tried using the sling rewriter and able to rewrite the links for clientlibs and dam assets.Now the assets are being rewritten as :http://localhost:4502/company/global.csshttp://localhost:4502/company/abc.jsBut I am not able to render them as AEM is not resolving it.I e...