Adobe Experience Manager Sites & More

Afrem_Danaho · 7/25/17

I have included a component on a template so its on every page by default. But am unable to open the component's dialog box in touch UI (AEM 6.2).

The browser is throwing 500 error for the below path :

http://localhost:4502/mnt/override/apps/test/components/content/global/menu/_cq_dialog.html/content/...

Any Idea how to handle this?

VeenaVikraman · 7/26/17

Hi Afrem

You can add a path property dynamically. I have implemented something similar for one of my project . Please find below the syntax. You have to first assign that to a variable

In the below code, I am trying to create parsys in loop and so I have to give different path properties.

Here is the explanation for @format

Ref :- cq5 - Expression Option Sightly - Stack Overflow

Hope this helps

Thanks

Veena

View solution in original post

poojac_2204 · 7/26/17

is the edit dialog of this component is working properly if drag and dropped in page?

Afrem_Danaho · 7/26/17

Yes.. Dialog is working properly if drag and drop in a page.

poojac_2204 · 7/26/17

Hi Afrem,

I am not able to replicate the issue. Including component in template is working fine and I able to edit it and below is the path for getting dialog.html in browser

http://localhost:4502/libs/cq/gui/components/authoring/compat/content/dialog.html?dialog=%2Fapps%2Fs...

Can you share the sample content package with issue?

Afrem_Danaho · 7/26/17

Hi Pooja,

This works fine in Classic UI. I am facing this issue in touch UI (_cq_dialog).

Techaspect_Solu · 7/26/17

Hi Afrem Danaho,

I am not able to replicate this issue at my end.When a component is included in template I am able to edit the component dialog in page.

I have included the component using below syntax :

Hope you have followed the same to include resource in page.If you can share a sample package of it we can better help you out in fixing this.

Thanks,

Techaspect Solutions.

Afrem_Danaho · 7/26/17

Hi Techaspect,

Many Thanks,

I have include the component with 'dynamic path' with below syntax.

to store the component configuration in a common node.

Dialog works fine in classic UI. But in touch UI it is not working.

Please find the below link which discuss the same issue.

Re: How to include component with dialog box on template with sightly?

Do we have any workaround for this?

smacdonald2008 · 7/26/17

To make this work in AEM - seems that this syntax is what you need:

Looks like using dynamic path is not supported.

VeenaVikraman · 7/26/17

Hi Afrem

You can add a path property dynamically. I have implemented something similar for one of my project . Please find below the syntax. You have to first assign that to a variable

In the below code, I am trying to create parsys in loop and so I have to give different path properties.

Here is the explanation for @format

Ref :- cq5 - Expression Option Sightly - Stack Overflow

Hope this helps

Thanks

Veena

smacdonald2008 · 7/26/17

I tested this syntax --

You can open the dialog --

Afrem_Danaho · 7/27/17

Many Thanks Veena and Scott .

The solution provided works for page level components.

My component is a global component and its configuration is same across all the pages. For that I am using the below syntax

<sly data-sly-resource="${@ path='/content/myproject/hidden',resourceType='myproject/components/content/global/menu'}"></sly>

This way my component configuration gets stored in the node - '/content/myproject/hidden' and is available across all the pages.

This works fine in classic UI.

But in case of touch UI, the dialog is not opening and I can see 500 error (in browser console) for the following URL

http://localhost:4502/mnt/override/apps/myproject/components/content/global/menu/_cq_dialog.html/con...

I am getting a NullPointerException while navigating through this URL.

Cannot serve request to /mnt/override/apps/myproject/components/content/global/menu/_cq_dialog.html/content/myproject/hidden in /libs/cq/gui/components/authoring/dialog/dialog.jsp

Exception:

java.lang.NullPointerException

at org.apache.jsp.libs.cq.gui.components.authoring.dialog.dialog_jsp._jspService(dialog_jsp.java:348)

at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502)

at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:284)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:102)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:536)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491)

at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:546)

at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44)

at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:77)

at com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:96)