Closed (fixed)
Project:
Facet API
Version:
7.x-1.0-rc4
Component:
Custom Search Blocks
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 May 2012 at 12:38 UTC
Updated:
10 Jul 2012 at 01:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
cpliakas commentedYes, because of the way CTools export plugin UI works, you have to hard code one permission. I chose "administer search", but that is not available when you are not using the core Search module. We can either implement a hook_menu_alter() to use the same permissions scheme as facets, or we can implement a new permission for administering the current search blocks. I am leaning towards leveraging the facetapi_access_callback() since most current search blocks have facet data, but I would be curious to get your take.
Thanks for reporting,
Chris
Comment #2
Zahak commentedAh I see, was suspecting something like that. I think that facetapi_access_callback() makes sense. Don't really see a need for a new permission.
Comment #3
cpliakas commentedThe attached patch changes the access callback for the Current Search administration pages to facetapi_access_callback() as discussed.
Thanks,
Chris
Comment #4
cpliakas commentedSame patch, changed text in comments.
Comment #5
cpliakas commentedHm, I switched the logic. The pattern will match admin/config/search/current_search_foo, which is not the intended behavior. It should match admin/config/search/current_search, but not admin/config/search/current_search_foo.
Comment #6
cpliakas commentedResolved logic error.
Comment #7
Zahak commentedGreat, looks good!
Comment #8
cpliakas commentedBased on #7 and this being a somewhat minor change, marking as RTBC.
Comment #9
cpliakas commentedCommitted to all 7.x versions of Facet API.
Backported to 6.x-3.x version of Facet API.