[MAGNOLIA-3772] Magnolia-internal search (website workspace) does not work as specified: page name not considered. Created: 01/Aug/11 Updated: 04/Aug/15 Resolved: 04/Aug/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Maximilian St√∂rzer | Assignee: | Philipp Bärfuss |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Testcase included: |
Yes
|
| Date of First Response: |
| Description |
|
The Magnolia-internal search (website workspace) does not work as specified. From http://documentation.magnolia-cms.com/usermanual4/managingpagesinadmincentral.html#search_function: Search Levels Magnolia's search function operates simultaneously on four levels. Before returning your search results, the search function searches through:
Example: Page name ist not searched. Tested both local Magnolia EE as well as Demo instance (http://demo.magnolia-cms.com/.magnolia/pages/adminCentral.html) |
| Comments |
| Comment by Philipp Bärfuss [ 02/Aug/11 ] |
|
The name of a page can't be queried with JCR 1.0. Except one queries the path which doesn't allow a pattern matching on a single node. We had to copy the name into a property or wait for JCR 2.0, which we use in 5.0 (or in a potential 4.5 version). |
| Comment by Michael Mühlebach [ 04/Aug/15 ] |
|
We're closing this issue as outdated as it was reported for 4.4.x or earlier versions which are no longer supported. Don't hesitate to reopen or create a new ticket in case this is still relevant and you'll experience it on 4.5.x or later versions. |