[MGNLSTK-974] SearchResultModel is not Channel-aware Created: 18/Jun/12  Updated: 02/Aug/16  Resolved: 02/Aug/16

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: templates
Affects Version/s: 2.0.2
Fix Version/s: 2.0.x

Type: Bug Priority: Neutral
Reporter: Matt Dertinger Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: channels, search_results, stk, stk2, templates
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File search-results-screenshot.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Hi,

Currently, it does not appear that info.magnolia.module.templatingkit.search.SearchResultModel is channel-aware. Therefore, if a particular page is set to exclude a particular output channel (i.e. smartphone), the excluded page will still show up in search results. Additionally, clicking the link will return a 404 error.

Steps to Reproduce:

  1. Log into the demoauthor site as superuser
  2. Navigate to website/demo-project/news-events and click Open Page
  3. Click on the Properties button to open up the Page Properties dialog
  4. Click on the Output Channels tab, then check the Desktop checkbox to exclude the page from the Desktop channel
  5. Click the Save button
  6. Browse to the demo-projects Home page, then click the Preview button, to preview the site in Desktop mode
  7. Enter news and events in the search field, then click SEARCH
  8. On the Search Results page, note that the News and Events page is displayed in the results even though the page has been excluded from the desktop channel (see attached screenshot)
  9. Click on the News and Events link in the Search Results, note that a 404 Error is returned

Please let me know if you have any questions.

Cheers,
Matt



 Comments   
Comment by Milan Divilek [ 19/Jun/12 ]

Thanks for the report. Added to the changelog for next release.

Comment by Michael Mühlebach [ 02/Aug/16 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:32:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.