Please suggest user experience improvement patches for: managing large list of items, and discovering Drupal administration settings
Hello, there are hundreds, possibly thousands of available patches in the queue for head. If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well. These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report. Cheers, Kieran
Kieran, Here's my contribution: http://drupal.org/node/87700 It makes the "Configure Permissions for $module" link on the admin/by-modules page link directly to the relevant permissions for that module. Do you have any more feedback about doing the testing as part of a Denver Drupal User Group meeting? I'd like to find some space and advertise the event so we can get maximum participation. Thanks, Greg Kieran Lal wrote:
Hello, there are hundreds, possibly thousands of available patches in the queue for head.
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report.
Cheers, Kieran
-- Growing Venture Solutions | Denver, CO | 720-320-8748 Technology Solutions for Communities and Small Businesses http://growingventuresolutions.com/
On 10/14/06, Greg Knaddison - GVS <greg@growingventuresolutions.com> wrote: My apologies - that was supposed to go direct to Kieran. But if anyone else wants to look at that patch, go ahead :) Regards, Greg -- Greg Knaddison | Growing Venture Solutions Denver, CO | http://growingventuresolutions.com Technology Solutions for Communities, Individuals, and Small Businesses
Kieran, Sorry if this is OT, but I think it sorta makes sense to say this on this thread. I think the #1 problem Drupal faces is this: Difficulty to upgrade. I'm sure I'll get flamed for this, but... I think there should be a button, or something in the admin section that says goes something like the following: Upgrade - Configure when your Drupal software is upgraded 1. Status Upgrade is pending - Somewhere something should say: Upgrade pending! No Upgrades present - Same place it should say: No Upgrades Needed. (wording is off, but you get the idea) other? 2. When are your upgrades to be run? [Nightly] [Monthy] [Only when security releases are available - does this poll drupal.org? heh] [Never] 3. Level of upgrades [Email UID 1 (or whoever is specified) when something is done or available ] Simple Notification Download update but don't install Install upgrade but perform only when UID1 logs in and approves Automagic upgade with no user intervention needed. Heh, Ok, I know I'm probably smoking crack here, and none of this is possible, BUT, from a "newbie" Drupal Administrator, this would be a MAJOR plus on helping keep things maintained. I'd personally select the Automagic upgrades. That way I wouldn't have to worry about things. There is a LOT more thinking that has to go into something like this, and I know it's probably a 6.0 feature, but... it would really make managing a Drupal site a complete and utter breeze. Trae On 10/14/06, Kieran Lal <kieran@civicspacelabs.org> wrote:
Hello, there are hundreds, possibly thousands of available patches in the queue for head.
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report.
Cheers, Kieran
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
On Oct 15, 2006, at 5:29 PM, Trae McCombs wrote:
Kieran, Sorry if this is OT, but I think it sorta makes sense to say this on this thread.
I think the #1 problem Drupal faces is this:
Difficulty to upgrade.
Yes, it is off-topic. Yes, you are right. Upgrading was listed as the hardest task in the Drupal administration survey, as of right now. Survey results are subject to change.
I'm sure I'll get flamed for this, but... I think there should be a button, or something in the admin section that says goes something like the following:
Upgrade - Configure when your Drupal software is upgraded
1. Status Upgrade is pending - Somewhere something should say: Upgrade pending! No Upgrades present - Same place it should say: No Upgrades Needed. (wording is off, but you get the idea) other?
2. When are your upgrades to be run? [Nightly] [Monthy] [Only when security releases are available - does this poll drupal.org ? heh] [Never]
3. Level of upgrades [Email UID 1 (or whoever is specified) when something is done or available ] Simple Notification Download update but don't install Install upgrade but perform only when UID1 logs in and approves Automagic upgade with no user intervention needed.
Heh, Ok, I know I'm probably smoking crack here, and none of this is possible, BUT, from a "newbie" Drupal Administrator, this would be a MAJOR plus on helping keep things maintained. I'd personally select the Automagic upgrades. That way I wouldn't have to worry about things.
There is a LOT more thinking that has to go into something like this, and I know it's probably a 6.0 feature, but... it would really make managing a Drupal site a complete and utter breeze.
Most of the basics to solve this are being done by Derek right now. The basic assumption is that we need a release mechanism for contributed modules in order to do official releases that need to be pushed out to sites. However, I do think there are even harder parts of upgrading that we should explore like API changes, and teaching effective upgrading procedures to administrators. Cheers, Kieran
Trae
On 10/14/06, Kieran Lal <kieran@civicspacelabs.org> wrote: Hello, there are hundreds, possibly thousands of available patches in the queue for head.
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report.
Cheers, Kieran
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
On 10/15/06, Kieran Lal <kieran@civicspacelabs.org> wrote:
On Oct 15, 2006, at 5:29 PM, Trae McCombs wrote:
Kieran, Sorry if this is OT, but I think it sorta makes sense to say this on this thread.
I think the #1 problem Drupal faces is this:
Difficulty to upgrade.
Sorry, the rest looks good, feel free to let me know if there is any way I can help in testing this. As I agree it's our #1 problem and want to help out where I can. Peace love and bananas! Trae Yes, it is off-topic. Yes, you are right. Upgrading was listed as the
hardest task in the Drupal administration survey, as of right now. Survey results are subject to change.
I'm sure I'll get flamed for this, but... I think there should be a button, or something in the admin section that says goes something like the following:
Upgrade - Configure when your Drupal software is upgraded
1. Status Upgrade is pending - Somewhere something should say: Upgrade pending! No Upgrades present - Same place it should say: No Upgrades Needed. (wording is off, but you get the idea) other?
2. When are your upgrades to be run? [Nightly] [Monthy] [Only when security releases are available - does this poll drupal.org ? heh] [Never]
3. Level of upgrades [Email UID 1 (or whoever is specified) when something is done or available ] Simple Notification Download update but don't install Install upgrade but perform only when UID1 logs in and approves Automagic upgade with no user intervention needed.
Heh, Ok, I know I'm probably smoking crack here, and none of this is possible, BUT, from a "newbie" Drupal Administrator, this would be a MAJOR plus on helping keep things maintained. I'd personally select the Automagic upgrades. That way I wouldn't have to worry about things.
There is a LOT more thinking that has to go into something like this, and I know it's probably a 6.0 feature, but... it would really make managing a Drupal site a complete and utter breeze.
Most of the basics to solve this are being done by Derek right now. The basic assumption is that we need a release mechanism for contributed modules in order to do official releases that need to be pushed out to sites.
However, I do think there are even harder parts of upgrading that we should explore like API changes, and teaching effective upgrading procedures to administrators.
Cheers, Kieran
Trae
On 10/14/06, Kieran Lal <kieran@civicspacelabs.org> wrote:
Hello, there are hundreds, possibly thousands of available patches in the queue for head.
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report.
Cheers, Kieran
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
Kieran Lal wrote: > Hello, there are hundreds, possibly thousands of available patches in > the queue for head. > > If there are patches available that address managing large lists of > items (users, nodes, comments, groups, blocks, menus) then please help > identify them. > Also, if there are patches that help in the discovery of Drupal > settings for administrators please help to identify those patches as > well. 1. [Users] - Some mass user operations just went in from http://drupal.org/node/89323. I've got a small usability fix for that at http://drupal.org/node/89356 that could use a review. 2. [Common] - There really needs to be a common select all / deselect all for user/node operations. Since we can filter what we want, you could create a list, hit select all and be done with it. http://drupal.org/node/84961 looks like the jQuery issue for that. We should have this on node, user, comments, and permissions pages. Shouldn't be too difficult to do. -Rob
Rob Barreca wrote:
2. [Common] - There really needs to be a common select all / deselect all for user/node operations. Since we can filter what we want, you could create a list, hit select all and be done with it. http://drupal.org/node/84961 looks like the jQuery issue for that. We should have this on node, user, comments, and permissions pages. Shouldn't be too difficult to do. Could somebody give http://drupal.org/node/84961#comment-146002 a glance. I put a patch for select / deselect all and want to make sure I'm on the right track. I think this is a much needed usability enhancement.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com
On 14 Oct 2006, at 18:33, Kieran Lal wrote:
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
1. I'm not sure there is a patch for it, but managing URL aliases can be a bit of a pain (eg. URL aliases for taxonomy terms -- and folksonomies in particular). 2. The watchdog is a really large list of events that is hard to consume. Really large lists of items need a search functionality: users, nodes and comments have a search functionality, but there is no such thing for path aliases or watchdog events. Hope that helps, but chances are this was rather obvious. ;-) -- Dries Buytaert :: http://www.buytaert.net/
Watchdog could use some stronger filtering as well as search. I get tons of not found hits from spiders looking for links to its pre-drupal heritage. -----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Dries Buytaert Sent: Tuesday, October 17, 2006 2:52 AM To: development@drupal.org Cc: Kieran Lal Subject: Re: [development] Please suggest user experience improvement patches for: managing large list of items,and discovering Drupal administration settings On 14 Oct 2006, at 18:33, Kieran Lal wrote:
If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well.
1. I'm not sure there is a patch for it, but managing URL aliases can be a bit of a pain (eg. URL aliases for taxonomy terms -- and folksonomies in particular). 2. The watchdog is a really large list of events that is hard to consume. Really large lists of items need a search functionality: users, nodes and comments have a search functionality, but there is no such thing for path aliases or watchdog events. Hope that helps, but chances are this was rather obvious. ;-) -- Dries Buytaert :: http://www.buytaert.net/ -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.4/476 - Release Date: 10/14/2006
participants (7)
-
Dries Buytaert -
Greg Knaddison - GVS -
Greg Knaddison - GVS
-
Kieran Lal -
Rob Barreca -
Trae McCombs -
Walt Daniels