Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Pathfield search not working properly on AEM 6.3

davidt30874028
Level 1
Level 1

Hi community,

I'm currently working on a site implementation with AEM 6.3. We have a dialog that is using granite/ui/components/coral/foundation/form/pathfield, this is how the code looks like:

<multifieldcollection

sling:resourceType="granite/ui/components/coral/foundation/form/multifield"

fieldDescription="Click + to add a new page/asset"

fieldLabel="Add new Page/Asset for static entries"

jcr:primaryType="nt:unstructured"

composite="{Boolean}true">

<field

sling:resourceType="granite/ui/components/coral/foundation/container"

jcr:primaryType="nt:unstructured"

name="./staticPathsConfig">

<items jcr:primaryType="nt:unstructured">

<linkurl

sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"

fieldLabel="Page/Asset Path"

jcr:primaryType="nt:unstructured"

                                             filter="nosystem,hierarchyNotFile"

rootPath="/content"

name="./path" />

</items>

</field>

</multifieldcollection>

When the user tries to use the search for the pathfield, seems like on the results is showing jcr and metadata nodes which is not correct for an author user. We are expecting to see only pages and assets as a results of the search:

Screenshot 2017-11-02 12.57.44.png

Are we missing something here or this is how the widget is supposed to work? If that the case how can we configured it to only display assets and pages?

Thanks,

David.

23 Replies
mjb54261515
Level 5
Level 5

Can you pls remove filter and try. something like this 

<linkurl

   jcr:primaryType="nt:unstructured"

   sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"

   fieldLabel="Link Url"

   name="./path"

   rootPath="/content"

   suffix=".html"/>

remove suffix if not needed.

reference:

PathField — Granite UI 1.0 documentation

https://techrevel.blog/tag/multifield/

davidt30874028
Level 1
Level 1

I tried that before, but it was producing the same behaviour. Filter does not make any difference on how the search is working for pathfield. You can check the code if you want.

davidt30874028
Level 1
Level 1

What do you mean smacdonald2008​? I'm using the coral 3 granite UI component there.

mjb54261515
Level 5
Level 5

I tested for 6.3 button component with following snippet path filed in it  

               <linkTo

                        jcr:primaryType="nt:unstructured"

                        sling:resourceType="granite/ui/components/coral/foundation/form/pathfield"

                        fieldLabel="Link to"

                        name="./linkTo"

                        rootPath="/content"

                        suffix=".html"/>

regular select path works fine but whe we search for a title its showing jcr:content in results too

1339735_pastedImage_2.png

smacdonald2008​ pls look into this

davidt30874028
Level 1
Level 1

Exactly, that's what I mean. I think search is now working correct on the Pathfield, you should be able to find only pages or assets as an author user (not child nodes as jcr or metadata nodes).

smacdonald2008
Level 10
Level 10

I just tested on AEM 6.3 - i get:

APAthField.png

The value is persisted in the dialog --

APAthField2.png

If you use this in your project - you will not have any issues - granite/ui/components/foundation/form/pathbrowser

smacdonald2008
Level 10
Level 10

I am also looking for other examples too that will help you.

davidt30874028
Level 1
Level 1

Thanks smacdonald2008​, but that's a different component. You will see that the one that I'm using on my example has the ability to search which is a key once you are working with a big number of assets.

smacdonald2008
Level 10
Level 10

Yeah - I see that difference - i am searching for an example that uses that Coral data type. I have always used the one in my example and never had issues.

yellar5366253
Level 2
Level 2

Hi David,

Did you get any solution of this issue, even i'm also facing same issue in my project , if you know the solution could you please share solution to me.

Even i tried with filters also it's not working. Share solution.

Thanks

Arun_Patidar
Community Advisor
Community Advisor

If you need this only for assets you can use assets selectors as a picker source.

Vish_dhaliwal
Employee
Employee

Hello Everyone,

The product team is currently working on this issue. The internal reference number is GRANITE-15894 and GRANITE-26358.

This has been classified as an enhancement to the product.

Regards,

Vishu

aalfarocr
Level 2
Level 2

Any updates on this ISSUE ??? , it looks like a product BUG ! Very annoying by the way ...

Arun_Patidar
Community Advisor
Community Advisor

This behavior is no longer exists in 6.4,

you can contact Adobe for hot fix.

aalfarocr
Level 2
Level 2

Hi arunpatidar26​ , no is not, we're using AEM 6.4 and this is still an issue , same issue is reported here -> https://forums.adobe.com/thread/2578650