I don't see why the mailhandler menu items should be split between the site building and content management menus. Further the way they are split seems backwards:
* creating the mailhandler mailboxes is filed under content management
* determining they types of nodes that can be created by mailhandler is filed under site configuration
If anything, these two should be reversed.
However, i would recommend that a mailhandler menu item be filed under site configuration and have two children, one for determining the content types, and the other for administering the mailhandler mailboxes.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | mailhandler-d7.png | 40.96 KB | ilo |
| #1 | mailhandler-d6-list.png | 21.83 KB | ilo |
| #1 | mailhandler-d6-settings.png | 16.02 KB | ilo |
| #1 | mailhandler_hook_help.patch | 9.8 KB | ilo |
Comments
Comment #1
ilo commentedIt is a Drupal Best practice to have module settings under site configuration, so I think it is not that bad, as long as we can provide contextual links from each page to reach the other.
The Drupal 7 UX helps a lot on this issue, because the final D7 admin interface include local actions (see attached image).
The attached patch cross-link both pages in the help section, so now you can jump from the mailboxes list to the global settings and back. I think this approach is less intrusive than menu changes, but it breaks translations as it introduces new sentences.
Comment #2
danepowell commentedSorry, Mailhandler 6.x-1.x / 7.x-1.x are no longer supported. Please upgrade to 6.x-2.x / 7.x-2.x and re-open if still an issue. Thanks!