[MAGNOLIA-6666] Indexing configuration does not take components nested in areas into account Created: 03/Mar/16  Updated: 09/Feb/17  Due: 03/Mar/16  Resolved: 20/May/16

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 5.4.7, 5.5

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: 0d
Time Spent: 2.5h
Original Estimate: Not Specified

Issue Links:
Relates
duplicate
is duplicated by MAGNOLIA-6591 Create search index for nested compon... Closed
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
Release notes required:
Yes
Sprint: Basel 44
Story Points: 5

 Description   

So far the JR's indexing_configuration Magnolia provides by default since 5.4 would index text found at /page/area/component/ but not at /page/area/component/area/component level. A further index aggregate must be created for components too.


Generated at Mon Feb 12 04:16:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.