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:
fieldDescription="Click + to add a new page/asset"
fieldLabel="Add new Page/Asset for static entries"
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?
Can you pls remove filter and try. something like this
remove suffix if not needed.
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.
I tested for 6.3 button component with following snippet path filed in it
regular select path works fine but whe we search for a title its showing jcr:content in results too
smacdonald2008 pls look into this
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).
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
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.
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.
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.
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.
This behavior is no longer exists in 6.4,
you can contact Adobe for hot fix.