[MGNLPER-111] JcrSearchResultSupplier does not use the enabled property Created: 31/May/19  Updated: 18/Jun/19  Resolved: 01/Jun/19

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by DOCU-1925 Periscope page needs a section on how... Closed
relation
is related to MGNLUI-4930 Disabling search result supplier does... 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

 Description   

In some cases it might be useful to turn off search for a workspace. Findbar can have the side effect of making larger implementations slow as search is performed as soon as you login. You have to wait for it to finish before you can do anything else.

It would also be nice if search results lazy loaded. The home page won't load into the search is finished. It might be better of the page loaded and then the searchedswere performed one-by-one. Also, as a user of Magnolia, I don't use search that often. For it to be my landing page doesn't help me. I would rather see apps first. I think we already have a ticket for configuring the landing.


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