- Development - lists.drupal.org

Incorporate RoleAssign module into User module?
by Thomas Barregren 20 Oct '06

20 Oct '06

Hi everyone, It has been suggested [1] to me that the RoleAssign module [2] of mine should be part of core. RoleAssign introduce the |assign roles| permission. While editing a user's account information, a user with this permission will be able to select roles for the user from a set of available roles. Roles available are configured by users with the |administer access control| permission. Thus, RoleAssign lets site administrators delegate assignment of selected roles. I see the point to incorporate this kind of functionality with the User module. So now I am wondering if there is any support for that idea. Regards, Thomas <http://drupal.org/user/16678> [1] http://drupal.org/node/89333#comment-147351 [2] http://drupal.org/project/roleassign

3 5

So you tought you get form API?
by Karoly Negyesi 19 Oct '06

19 Oct '06

Great! You can join me on Gliffy.com drawing flowcharts. A taste of things to come is http://www.gliffy.com/publish/1088709/L

2 1

Re: [development] [decisions-dev] Request for input: Decisions.module
by Anders 19 Oct '06

19 Oct '06

> I will initiate a discussion on drupal-dev when we are closer to that > point and have implemented more of Anders' quality improvements, which I > estimate is on the order of 1-2 months away. Thanks Chris, I really appreciate that you see that I'm trying to improve (or make you improve mostly... :) ) the overall quality of the code.I also agree that it might have been a bit early to involve Dries, but on the other hand it's never wrong to advertise the model and show that we are serious about producing quality code. There are currently some obvious coding standard things that could be improved upon, see http://drupal.org/node/318. Code dealing with theming (http://drupal.org/node/306) and FormAPI (http://jeff.viapositiva.net/drupal/dynamic-forms, http://api.drupal.org/api/HEAD/file/developer/topics/forms_api_reference.ht…) are also important areas where code could be improved. Also, but more complicated, is how to handle "mode-specific" code the best way, currently we mix this a bit, e.g the voting_algorithms in decisions_form() which I think would be better off separated from decisions.module and into their specific .inc files. It might even be possible to use hook_form_alter() for such things, I'm not shure. I of course know that development have been focused on implementing new features and I'm also keen on seeing new features implemented. It should be possible to have these two areas work together though (quality+feature implementation), and it will be even easier when we have improved the overall code quality. /Anders

1 0

Re: [development] Incorporate RoleAssign module into User module?
by Metzler, David 19 Oct '06

19 Oct '06

I would support this idea as well. Letting someone define "what a role can do" and "who's in a role" should be different privileges, IMHO. Dave -----Original Message----- From: development-bounces(a)drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Mark Hope Sent: Thursday, October 19, 2006 9:26 AM To: development(a)drupal.org Subject: Re: [development] Incorporate RoleAssign module into User module? I support the idea. Makes complete sense to me. I wasn't aware of the module - I'll take a look as I'm delegating that task right now. Mark On 19 Oct 2006, at 16:45, Thomas Barregren wrote: > Hi everyone, > > It has been suggested [1] to me that the RoleAssign module [2] of mine > should be part of core. > > RoleAssign introduce the |assign roles| permission. While editing a > user's account information, a user with this permission will be able > to select roles for the user from a set of available roles. Roles > available are configured by users with the |administer access control| > permission. Thus, RoleAssign lets site administrators delegate > assignment of selected roles. > > I see the point to incorporate this kind of functionality with the > User module. So now I am wondering if there is any support for that > idea.

1 0

hooks after hook_menu is called, but before page rendered
by _craig 19 Oct '06

19 Oct '06

I'm in the process of updating taxonomy_breadcrumb to work with 5.0 and as part of the upgrade I'm making a few improvements to the module. I want to have an opportunity to change the breadcrumb trail after hook_menu has been called, but before the page is rendered in the theme. I'm not able to find any way to do this. Any suggestions? It seems as if I need a hook added right at the end of menu_execute_active_handler() in menu.inc, after call_user_func_array (but before returning). Am I missing something? How can I have a function in my module execute after any other hook_menu's have been executed? In the rare case I'm not overlooking the obvious how to I begin the process of trying to get a new hook added? Thanks! Craig

3 8

RFC: version numbers for core translations?
by Derek Wright 18 Oct '06

18 Oct '06

i've discovered another potentially tricky issue with the new release system and version numbering schemes for contrib: what should we do about version numbers for core translation releases? request for comments (RFC): http://drupal.org/node/89969 thanks, -derek

1 0

module upgrade from 4.6 to 4.7?
by Chad Phillips 18 Oct '06

18 Oct '06

Hi, I am new to drupal. I need to upgrade a module from 4.6 to 4.7. It looks like a number of API changes where made. Is there a document that list the functions that were removed and what their replacements are? I looked at the document titled 'Converting 4.6.x modules to 4.7.x' http://drupal.org/node/22218, but it doesn't seem to have a complete list of removed functions. Some of the functions this module used in 4.6 are: form_item, form_button, form_submit,form_weight, etc.. All of these are listed in the 4.6 API documentation, but not in the 4.7 documentation. Is there a way to find out if they were replaced or just dropped? thanks chad

2 1

Drupal 5.0 beta 1: status update
by Dries Buytaert 18 Oct '06

18 Oct '06

Hello world, the current plan is to release a first Drupal 5.0 beta early next week. In order to succeed, we need you to help out in the issue queue as much as possible. We've quite a few bugs to tackle, some of which are critical [1]. So, if you could all review (at least) one or two bugs a day, we'd be able to get a ton of work done. Your help is appreciated. I'll be traveling next week, but Steven Wittens will coordinate the first Drupal 5.0 beta release. [1] http://drupal.org/project/issues? projects=3060&versions=10195,9902,9842,9753,9728,6487&categories=bug&pri orities=1&states=1,8,13,14 Thanks, -- Dries Buytaert :: http://www.buytaert.net/

3 2

Delicioius module maintainership
by Earl Miles 17 Oct '06

17 Oct '06

As a reminder, while I quickly found someone willing to take paging and masquerade, I'm still looking for someone who might be interested in taking over (and maybe even expanding) the delicious module. There's quite a bit of room for improvement there, so for a newish developer it could be an adventure. Although all it really NEEDS is for someone to fix bugs, make sure the 4.7 port really works, and bring it forward to 5.0 at some point. I know that there's a bug in the queue that the delicious API has changed and it needs to be updated for that.

1 0

Re: [development] Please suggest user experience improvement patches for: managing large list of items, and discovering Drupal administration settings
by Michelle Cox 17 Oct '06

17 Oct '06

On 10/17/2006 1:51:34 AM, Dries Buytaert (dries.buytaert(a)gmail.com) wrote: > 2. The watchdog is a really large list of events that is hard to > consume. I haven't used this module, so I can't vouch for it at all. I just remembered seeing it while looking at the modules: Log Search incidentist(a)civicspacelabs.org http://drupal.org/node/23883 I thought maybe it could be used as a head start on getting something in core if it's any good. Michelle

1 0