Hi and thanks so much for your efforts as a Drupal dev.

I am trying to figure out whether Solace API will work with the Acquia Search service, which ApacheSolr Search Integration can use to provide a SOLR server. From the following:

"we don't use the search module, but only the main API module as our indexer and SolR instance interface"

... it seems likely but before I try it I thought I would ask - if I have ApacheSolr Search Integration working with the Acquia Search service, can you think of any reason why it would not be possible to just install Solace API and related modules, or would I need my own SOLR server to use Solace API and related modules?

If Solace API and Acquia Search service will (or may) work together via ApacheSolr Search Integration, is it possible for users to search within results of their searches with your Solace Node Reference and/or Solace Search?

Thanks again.
CDB

Comments

pounard’s picture

pounard
Primary language French
commented

If apachesolr modules can reach the SolR server, then this module should work great. The goal of using apachesolr as underlayer is that if it can speak to SolR, then us too!

butler’s picture

butler commented

Thanks very much pounard... I seem to have this working, which would mean that your API/modules don't require that people set up their own SOLR server.

FYI for anyone trying to get this up and running - the current recommended ahah_helper.module, rev 1.4, appears to have implemented the patch mentioned in Solace documentation (the os x terminal app patch program says the patch has been applied, and it appears to be there minus one line). The patch is for rev 1.3, a release I can't find anywhere.

Perhaps I missed this in documentation but, how does one go about adding Configured fields? pounard it looks like your API may provide some possibilities I have been trying to get at for weeks - thanks so much for your efforts!

butler’s picture

butler commented

Addendum - found the following in documentation for assistant_ref.module (Developers.txt):

" - assistant_ref : Main feature, this module handles saving of a filters list
for any (Node Reference field / node) couple. " and:

"user configurable filters is implemented through
the 'Solr Assistant' (assistant_api) filters form, accessible which the menu
system. Save, delete or any other crud operation will be done in the form submit
function."

Having installed and enabled further dependencies discovered during module installation or mentioned in documentation:

feeds-6.x-1.0-beta10
ctools-6.x-1.8
job_scheduler-6.x-1.0-beta3

... and the freestanding module also by pounard which (I am pretty sure) is a dependency for assistant_ref.module:

daemoncli-6.x-1.0-beta4

... I still can't find any sort of UI for "'Solr Assistant' (assistant_api) filters form". Anyone know where/whether I should see this filters form?

Thanks...

pounard’s picture

pounard
Primary language French
commented

I must admit the documentation needs a good revamp.
First of all, the main module "Solace API" will provide a form, but it's being displayed nowere.

Feeds is not mandatory, but it can help if you plan to import content from the outside. Ctools is not a dependency, and won't ever be, except if you use other contrib modules that needs it (Feeds, ..).

Daemoncli is not required, but it should be I suppose, because you won't do anything without it, it will trigger the Solace Node Reference queue operations in the background.

Once you enable Solace Node Reference, you can configure node reference fields to use it by configuring the field itself (some fields are being added to the field configuration form). You must enable the feature on a per-field basis in that form. UX is not great on this, you have to enable the feature in the field, then reload the form and check out some new options in it.

Once it has been activated for at least one field, You'll notice a new tab on existing nodes pages which is called "Assistant", you can access node specific configuration (queue delai and some others) as well you access the form from a button on this tab.

Hope it helps.

butler’s picture

butler commented

And thanks again pounard. Apologies if I'm being obtuse, but for clarification, when you write above:

"Once you enable Solace Node Reference, you can configure node reference fields to use it by configuring the field itself (some fields are being added to the field configuration form)."

... do you mean I should see a UI on the site where I've installed Solace API+related modules, resembling this screenshot (field configuration UI?):

http://drupal.org/node/739520

... or is that screenshot an example of something that must be created on my end using your API? I tried creating a test content type with some node reference fields thinking that might cause a fields configuration form to become available somewhere but still can't find such a thing. If this form should be available could you post an example URL?

Likewise, I can't find anything resembling this screenshot:

http://drupal.org/node/739518

... should I see something like that available from my site's menu system?

Maybe I can help with documentation? I have somewhat outdated PHP skills (still getting up to speed w/ OO PHP and Drupal programming generally) and would probably have to ask you a lot of questions, but if an english speaker who can write reasonably well would be helpful, I would love to lend a hand.

pounard’s picture

pounard
Primary language French
commented

The screenshot is a part of the existing UI, once you enabled the assistant feature on a node reference field, you should be able to access it from the node tabs that uses this same field.

To activate the assistant, go to "Administer > Content > Content Type > some type > Manage fields" from there, choose a node reference field in the list, and click the "configure" link. You have to create the node reference field of course. Once you are on the node reference field edit form (if you are creating it, create it, save it, then go again on the configure form) you will see a new "Assistant" fieldset on the top of the form. Check the "enable" box; save again, and go to a node for which you have sufficient rights to edit, you should see the tab right here.

If the tab isn't, attempt to clear your cache (this shouldn't be necessary by the way). If it still does not appear, and you are *really sure* you activated the Assistant (you can check it by going to "Administer > Structure > Solace|Assistant" (can't remember the exact menu entry, but there is) you will see a list of enabled fields in it containing the field you just enabled), then it's a bug, please open a bug report.

If you find the first one (the node tab) then you are good. The "save and edit filter" button will redirect you on the filter form you can see on the second screenshot.

If not, please open a bug aside and I'll attempt to find out why.

Vertical tabs are rendered by the vertical tabs module (optional dependency) if you don't enable it, the form will appear, but using fieldsets instead of tabs.

pounard’s picture

pounard
Primary language French
commented
Status: Active » Closed (won't fix)

Abandonned project.

jason.fisher’s picture

jason.fisher commented

Did you find a different way to provide this type of custom build-a-search in Drupal 7? Or an alternate setup that provides similar functionality using different components/engines/software? I believe this is/was to be a powerful and useful interface for power users building custom searches for libraries of many content types and fields.