Closed (fixed)
Project:
Module Filter
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
1 Feb 2012 at 21:00 UTC
Updated:
21 Jul 2012 at 01:31 UTC
Jump to comment: Most recent file

Comments
Comment #1
petsagouris commentedI'd rather have that on the top right.
This is the button that will be pressed 80% of the times you are visiting this page.
The whole "save button, module filter area, table headers" area should be actually made sticky.
Please take a look at the mockup:
Suggestions that are not in the mockup:
Comment #2
rogical commentedI have the same issue while I enable a field module, the list is too long, I have to find the 'Save xx' in button, that's not good.
Some users may not want to use another module, so is it possible just make a patch to module filter to set the place of action?
thanks,
Comment #3
klonosI was thinking that perhaps the old chunk of code should stay in place and get wrapped around an if statement to check for existence of the page_actions module. If found use that, else use the old code. This would help provide an out-of-the-box experience for users (IOW without "forcing" them to add and enable yet another module). At the same time this method would allow for people that find the page_actions useful and use it in their sites anyways to use that instead ;)
Comment #4
greenskin commentedThe module will now utilize page_actions if it exists, otherwise the previous functionality to page_actions is available (namely the dynamic positioning of the save button).
http://drupalcode.org/project/module_filter.git/commit/f0d8192509adacff1...
Comment #5
klonosPerfect! ;)
Comment #6.0
(not verified) commentedFixed incorrect dev date.