For the admin/settings/opensearch page, we should use the 'administer search' permission provided by search.module instead of the way-too-general 'administer site configuration'.

Comments

avpaderno’s picture

Would to move the settings page inside the search settings page make sense? I think that most users would look into that page, when searching for the module settings (IMO); then, it would reduce the code that should not even implement hook_menu().

The con is that in this case it would not be possible to put the administration code into a separate file.

dave reid’s picture

Probably what would be best to create it as a local task under admin/settings/search. Make the search.module settings a default local task named 'Settings'.

dave reid’s picture

Title: Re-use the 'administer search' permission » Revamp the settings page
Assigned: Unassigned » dave reid

Seems the permission change slipped in with my coding cleanup patch, so I'm going to change this to cover the settings (and where the settings should be) retooling and revamping.

dave reid’s picture

avpaderno’s picture

There are some form fields that accepts more than 64 characters, and they are textfields; it would be better to make them textareas.

avpaderno’s picture

avpaderno’s picture

Assigned: dave reid » avpaderno

I have moved the settings page under /admin/settings/search/opensearch, and added a menu callback to make the search settings page added from search.module the default tab.

avpaderno’s picture

I changed the textfield form fields in textarea form fields. This has been done in consideration of a possible introduction of a new feature that would allow to execute PHP code.

avpaderno’s picture

Status: Active » Fixed

The code has been changed, and committed in CVS.

dave reid’s picture

Nice work!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.