Level 2

Pathfield search not working properly on AEM 6.3

Forum|Forum|8 years ago
November 2, 2017
3 replies
13110 views

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:

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

manoj_devapath

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/

D

davidt30874028Author

Level 2

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.

smacdonald2008

Level 10

Try to use the Grainte Pathfield.

manoj_devapath

Level 5

regular select:

search select:

smacdonald2008

Level 10

I just tested on AEM 6.3 - i get:

The value is persisted in the dialog --

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

D

davidt30874028Author

Level 2

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.

Hi smacdonald2008, Do you have any findings? Do you think this is a bug?