[MGNLPER-180] RootPath is not used for findBar results Created: 26/Nov/21 Updated: 19/Dec/22 Resolved: 14/Dec/22 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | 1.2.6, 2.0.0 |
| Fix Version/s: | 2.0.0, 1.2.7 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antonio Tuor | Assignee: | Miguel Martinez |
| Resolution: | Fixed | Votes: | 7 |
| Labels: | VN-Analysis, VN-Testing | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 1d 0.5h | Time Spent: | 1d 0.5h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||
| Issue Links: |
|
||||||||||
| Sub-Tasks: |
|
||||||||||
| Template: |
|
||||||||||
| Acceptance criteria: |
[ ]*
RootPath is used to create the link for find-bar results
[ ]*
Item is highlighted when the find-bar result is clicked and the app is opened
|
||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||
| Bug DoR: |
[X]*
Steps to reproduce, expected, and actual results filled
[X]*
Affected version filled
|
||||||||||
| Release notes required: |
Yes
|
||||||||||
| Date of First Response: | |||||||||||
| Epic Link: | AuthorX Support | ||||||||||
| Sprint: | AuthX 23 | ||||||||||
| Story Points: | 2 | ||||||||||
| Team: | |||||||||||
| Work Started: | |||||||||||
| Description |
Steps to reproduce
subApps:
browser:
datasource:
rootPath: /myRootPath/
Expected resultsThe url contains the full path of the node, to highlight/select it correctly: Actual resultsThe url does not contain the rootPath, and therefore the node path is not absolute and the item is not preselected/highlighted: WorkaroundDevelopment notes |
| Comments |
| Comment by Anne Meister [ 25/Feb/22 ] |
|
This issue has been open for a while and is a real problem for our client. Could we get this prioritized? |
| Comment by Anne Meister [ 01/Mar/22 ] |
|
We now have another DX Core client with the same problem, which makes some content apps absolutely unusable for them as they can't use the search function. Please prioritize and fix this issue. |
| Comment by Jonathan Ayala [ 01/Mar/22 ] |
|
When executing info.magnolia.admincentral.findbar.operation.InternalNavigationOperation.execute(InternalNavigationRequest) the value of request.path is relative to the configured root path of the app, i.e. it doesn't contain /myRootPath as explained in the description. |
| Comment by Rajeev Singh [ 24/May/22 ] |
|
Hello, What's the priority and status of this issue? Thanks for your feedback Regards, |
| Comment by Rajeev Singh [ 30/May/22 ] |
|
Hello, |
| Comment by Rajeev Singh [ 08/Jun/22 ] |
|
Any updates on the prioritization of this ticket? |
| Comment by Rajeev Singh [ 14/Jun/22 ] |
|
Hello, In which version this will be released? @gabriele.piras@magnolia-cms.com Regards
|
| Comment by Jonathan Ayala [ 14/Jun/22 ] |
|
Hello, We are currently working on fixing this issue. Unfortunately, we don't have a specific date for the release yet but we'll let you know as soon as we have more information. Regards. |
| Comment by Rajeev Singh [ 15/Jun/22 ] |
|
Hello, Since when team has been working on this topic? --> Affects Version/s:6.2.13, 6.2.17 (Created:26/Nov/21 10:32 AM) PS: plz note that we are still running production with the 6.2.18- |
| Comment by Laura Delnevo [ 17/Jun/22 ] |
|
Hi rajeevsingh, I am Laura, PM for Author Experience. Thanks for your comments. As Jonathan mentioned, we are looking at the problem. I will be posting an update with the expected release as soon as we can. |
| Comment by Rajeev Singh [ 17/Jun/22 ] |
|
Many thanks for the update, Laura. |
| Comment by Jonathan Ayala [ 06/Oct/22 ] |
|
Hello rajeevsingh, atuor, We are working on this issue and found the behaviour in the latest releases is slightly different when using the 6UI syntax. In order to make sure we cover all the scenarios we'd like you to provide us with the complete content app descriptor that is causing the issue in your instances. Regards,
|
| Comment by Michail Botas [ 07/Oct/22 ] |
|
Hi Jonathan, I will send you one of our custom apps today. I will simplify it having only 1 custom node type and I will provide you also customNodeTypes.xml to have also same custom node type.
Thanks, Michail |
| Comment by Michail Botas [ 07/Oct/22 ] |
|
Hi Jonathan, You can check persons-app.yaml Thanks, |
| Comment by Jonathan Ayala [ 19/Oct/22 ] |
|
Thanks Michail, The issue is reproducible with given app and node type. Steps to reproduce
|
| Comment by Antonio Tuor [ 09/Nov/22 ] |
|
Hi Jonathan, Sorry for the late response, I was on vacation. Best regards, |
| Comment by Laura Delnevo [ 19/Dec/22 ] |
|
Hi, please note that the fix is being released on 6.2.27. Release notes will follow up shortly |