There is some non-functional code in hook-install for creating/saving initial facet blocks.

This needs to be reworked to integrate with facet API module instead.

Comments

paulgemini’s picture

paulgemini commented

Ok - I've just started using it and can't get many of my facet blocks to show up. Perhaps you're talking about the same thing?

[Update 4-15-2010] Nevermind. Was another issue on my side.

pwolanin’s picture

pwolanin commented

This issue is just about trying to enable some of the facet blocks by default.

paulgemini’s picture

paulgemini commented

subbing

cpliakas’s picture

cpliakas commented

I am of the opinion that Acquia Search shouldn't try to enable any facets by default. Different sites will have different data models and configuration requirements, so I would argue that we shouldn't be assuming any defaults and handle the automatic configurations like this are better suited for installation profiles in distributions such as Acquia Search Drupal. (Sorry for typo)

pwolanin’s picture

pwolanin commented

ok, so should we just rip this code out? The idea was that the "typical" person trying out this combination of module would expect to see facets working.

In what context do we then provide the pre-configured test experience?

cpliakas’s picture

cpliakas commented

I am having second thoughts about what I posted. I am going to take a step back and think about this some more.

The more I think about it, we should have a way for people to get a search experience OOB. However, I still don't think we should explicitly set it up in hook_install(). To me some sort of simple wizard, like a one page "Do you want facets? Which ones?" would be helpful. That way people could get a clean install if they are heavily using panels / context, but could easily have an OOB experience by selecting a few checkboxes.

danepowell’s picture

danepowell commented
Issue summary: View changes
Status: Active » Closed (won't fix)

This branch of Acquia Connector is no longer supported, per the version policy on the project homepage. As such, I'm tentatively closing this issue.

If this issue still applies to a supported branch (currently 7.x-3.x, 8.x-1.x, or 8.x-2.x), please reopen and select the new target version. Thanks!