In an effort to clean up the Admin UI, module config menu items should probably find a home under a parent item in configuration. Spamicide Config menu item should probably be moved to /admin/config/content

Thoughts?

Comments

lipcpro’s picture

Status: Active » Postponed (maintainer needs more info)

Is this a community wide effort (effort to clean up the Admin UI), you don't cite any issues with other modules or core. I believe I'll upset my users if I do this without some explanation. Please cite a community initiative and I'd be glad to comply. Frankly I don't see that it fits there at all. Captcha adds itself to admin/config/people and Mollom adds itself to /admin/config/content, so there doesn't seem to be a standard for spam prevention tools at all.

pixelsweatshop’s picture

It was a part of the information architecture and usability improvement effort for D7. See http://drupal.org/node/549094 under "Configuration". (admin/config/content was merely a suggestion, put it under what you feel is appropriate. It just shouldn't be it's own parent item in config.)

Configuration

The Configuration section is for all configuration. Any module which exposes configuration should be placed here. The category for a module's configuration should be chosen carefully.

Avoid creating new categories. Instead, consider placing your module's configuration near a related module. If possible, add the module's configuration under one of the following categories:

People
System
Development
Content authoring
Regional and language
Search and metadata
Media
Web services
User interface

danchadwick’s picture

Title: Spamicide Config menu item should be moved to /admin/config/content » Spamicide Config menu path should be /admin/config/system/spamicide
Status: Postponed (maintainer needs more info) » Active

I concur that the Spamicide admin is in the wrong place. However, I disagree that content is the right home. admin/config/content (aka "Content authoring") is the home of input formats, editor settings, etc. These items relate to authoring content, which spamicide does not help with, except in the secondary sense of preventing comment spam (as comments are content that is authored).

Other anti-spam modules, such as spambot are under system. I therefore suggest changing admin/config/spamicide to admin/config/system/spamicide, and updating relevant help text, read me, etc.

It is inappropriate to pollute the parent configuration menu with an individual module's settings, much less one as relatively minor this (compared to, say, user or views). If the maintainer doesn't care for system, then content would be fine. Anything but the parent config menu, please.

If you need a patch, I'd be happy to provide one. Great module. Thank you very much!

lipcpro’s picture

Assigned: Unassigned » lipcpro
Status: Active » Needs review

I've moved the spamicide to under people

lipcpro’s picture

Issue summary: View changes
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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