Active
Project:
Smartqueues for Organic Groups
Version:
5.x-1.2
Component:
User interface
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2008 at 15:05 UTC
Updated:
12 Nov 2008 at 02:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
ezra-g commentedThat was an intentional design decision to force the user to specify which batch action to perform, in order to prevent accidental batch actions on large sites.
Comment #2
ezra-g commentedI suppose we could add a 'save this choice' type of checkbox, but I wonder if that would clutter up the design.
Comment #3
foxtrotcharlie commentedAah, sorry. I didn't read it properly, so didn't understand the functionality of it. On reading that whole field with less haste, I think it's clear enough, and it's good to reset the values :-). I also think that having a save this choice would clutter up the design.
One thing in this particular UI that I found confusing was the text above the checkbox "Create new NodeQueues" - "For Users of the above-specified roles who do not yet have user NodeQueues:". (see attached screenshot). I realise now that this creates new nodequeues for any existing group nodes which don't have a subqueue, but to me the text above the checkbox refers to users and not groups. Unless I'm missing something again, I can't figure out what is meant by "user NodeQueues".
Comment #4
ezra-g commentedGood catch, thanks. I fixed that text.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
moshe weitzman commentedFYI, that text still appears on the screenshot for this project. I zoomed in to read everything :)