Problem/Motivation

When you are configuring a range facet using the range facet widget it is expected to work out of the box. However, currently the weights are defaulting to place the url processor below the range processor. The range processor requires the url on the result item, causing a fatal with the default ordering.

Proposed resolution

Change the default ordering. Patch included

Remaining tasks

Discuss if we should make a system to not allow dependencies of a certain processor to be placed after its execution in the specific build stages.

User interface changes

None

API changes

None

Data model changes

None

CommentFileSizeAuthor
#2 2983572.patch1.38 KBNick_vh
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Nick_vh created an issue. See original summary.

Nick_vh’s picture

FileSize
1.38 KB
Nick_vh’s picture

Title: Change default weights so that the sitebuilder experience when configuring a range facet works out of the box » Improve the sitebuilder experience when configuring a range facet so that it works out of the box
Status: Active » Needs work
borisson_’s picture

Status: Needs work » Reviewed & tested by the community

I think dependencies are a bit overkill to introduce together with this patch. It would be a good thing to do, but we always add that on later, we can do this in a non-bc breaking way. We can get this in, as it's already a good improvement.

Nick_vh’s picture

Sounds good for me - I'll create the follow-up

  • Nick_vh committed 28764cb on 8.x-1.x
    Issue #2983572 by Nick_vh: Improve the sitebuilder experience when...
Nick_vh’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.