follow-up for import (needs to be optionally available when ctools is enabled)

The export function comes from ctools and the export array in hook_schema(). So you can export your configuration. But there is no way to (re-)import this configuration.

Possible solution: Do you know this issue? http://drupal.org/node/624018#comment-5278644

Basically it is one file (wysiwyg.features.inc) with some implemented features hooks. Especially the two functions wysiwyg_features_revert($module) and wysiwyg_features_rebuild($module) do the work of importing the wysiwyg configuration via a simple db_merge() and cache clear.

What do you think?

Possible steps:
- Get all defaults: features_get_default('apachesolr_search_page', $module).
- Write/merge array to database: apachesolr_search_page_save($search_page).
- Menu rebuild needed to pick up search path: menu_rebuild().

I'd love to see a patch for this! Please go ahead and try. Together we'll figure it out ;-)

Subscribing, linking from #1386750: Exportables not picked up

I'll come up with another patch which adds the ctools dependency and uses ctools' export ui.

If we could make the ctools optional for the apachesolr.module that would be great. I suppose it wouldn't be a big problem for the apachesolr_search module because that is the more visual side of the module. And since this is mostly coupled with facetapi it needs ctools anyway.

So my proposal for dependencies is to check if module exists and, if it does, provide export/import functionality.

I think that Apache Solr environment "variables" ($environment->conf) need to be exported along with the environment, rather than as separate exportables. Additionally, it makes sense to use the Apache Solr module's own CRUD functions rather than relying on CTools exportables CRUD, because it means that environments are always updated the same way, environment variables are maintained, and caches are properly cleared afterwards.

Here's a patch that updates environment exportables to include the variables, and implements importing. I've tested this with Features, and the patch doesn't provide a UI for exporting environments other than Features. Also, I suspect that this does not work with previously exported environments/environment variables--which really shouldn't be a big deal, because exports that come from the current implementation can't be diffed or imported.

This patch can be tested by using Features to export an Apache Solr environment. There are three things to test:

• the freshly installed feature should be reported by Features as being in the "default" state
• editing the environment through the Apache Solr configuration page should cause Features to report the feature as "overridden"
• reverting the "overridden" feature should restore the default (exported) settings

These should be tested when the feature is installed on the site it was created on, AND when the feature is installed on a site where Apache Solr has not been previously configured.

I'm not sure how to automate this sort of testing in a simpletest--maybe a test module that implements hook_default_apachesolr_environments(), and checks whether the default environments are present when apachesolr_load_all_environments() is called? (CTools would be required for this test).

Unfortunately, in my testing the feature is immediately reported as "overridden" when it is installed on a fresh site, even though Apache Solr picks up the settings correctly. I'm working on a fix right now.

I've reviewed this patch in a couple of different contexts and it appears to work as expected. I generated Features using local Solr configs and verified that these configurations were usable once enabled. I'm receiving a couple of SimpleTest failures, however, so I'm going to queue the latest patch for a re-test.

There seems to be some reset cruft in apachesolr_load_all_environments()

Awesome, thanks!

Please let me know if you see any problems, or if you can explain the failure of the built-in cools exporter.

I think that the problem with the built-in ctools exporter was that apachesolr itself only loaded environments from the database, and never from the ctools hooks, and that (before this patch) there were two separate types of exportables for environments and environment variables, instead of exporting all of the relevant configuration in one object. Technically data from two tables can be exported as one object with ctools by adding 'join' information to the hook_schema() 'export' configuration, but IMO it makes more sense to use a consistent load path.

Yeah, exactly.