#6 — allowedRolesAndUsers not indexed in Plone 3.3
| State | Resolved |
|---|---|
| Version: |
—
|
| Area | Functionality |
| Issue type | Bug |
| Severity | Critical |
| Submitted by | David Glick |
| Submitted on | May 02, 2009 |
| Responsible | Andreas Zeidler |
| Target release: | 1.0 |
Last modified on
May 04, 2009
by
Andreas Zeidler
I just got around to trying out collective.solr in Plone 3.3. Unfortunately the switch to using plone.indexer to get index values means that collective.solr is not getting an object wrapped in the extensible indexing wrapper....which means that nothing is getting indexed for the allowedUsersAndGroups index, and so no results are ever returned for a search.
The problem is that plone.indexer provides its extensible indexer as an adapter to a *different* interface (plone.indexer.interfaces.IIndexableObject adapting (context, catalog)) than the one that was used before (plone.app.content.interfaces.IIndexableObjectWrapper adapting (context, portal)), in order to be forwards-compatible with CMF 2.2.
I think what needs to happen is to modify collective.solr.indexer.SolrIndexProcessor.wrapObject to be more like the new Products.CMFPlone.CatalogTool.CatalogTool.catalog_object
I hope you don't mind me adding you to the cc list here, Martin...I wanted to make sure you see this, as my recollection of the changes on CMF trunk is hazy.
The problem is that plone.indexer provides its extensible indexer as an adapter to a *different* interface (plone.indexer.interfaces.IIndexableObject adapting (context, catalog)) than the one that was used before (plone.app.content.interfaces.IIndexableObjectWrapper adapting (context, portal)), in order to be forwards-compatible with CMF 2.2.
I think what needs to happen is to modify collective.solr.indexer.SolrIndexProcessor.wrapObject to be more like the new Products.CMFPlone.CatalogTool.CatalogTool.catalog_object
I hope you don't mind me adding you to the cc list here, Martin...I wanted to make sure you see this, as my recollection of the changes on CMF trunk is hazy.
Added byAndreas ZeidleronMay 04, 2009 07:27 AM
Issue state:
Unconfirmed
→
Resolved
Target release:
None
→
1.0
Added byAndreas ZeidleronMay 04, 2009 07:29 AM
oops, for some reason "resolve immediately" always sounds like a call to me, i.e. like "yes sir, i'm gonna resolve it immediately!"... :)
Issue state:
Resolved
→
Confirmed
Added byAndreas ZeidleronMay 04, 2009 09:54 AM
fixed in http://dev.plone.org/collective/changeset/85375Issue state:
Confirmed
→
Resolved
david, could you verify the fix works for you, please?
No responses can be added.
If you can, please log in before submitting a reaction.