January 2008 - Development - lists.drupal.org

possible bug in FAPI 5.6 (query string killed)
by Ivan Sergio Borgonovo 14 Jan '08

14 Jan '08

I'm trying to have a form that has a query string other than q/clean path. eg. $form['#action'] = url($_GET['q'],$query); going somewhere like /obj/action/?id=37 Avoiding to specify #action doesn't pass the additional query string. $form['#action'] = url($_GET['q'], drupal_query_string_encode($_GET,Array('q'))); This put in the <form action what I'd expect but later browser get redirected to the path without the additional query. So somehow it is impossible to pass a non positional parameter. whatever is returned from add_item_form_submit get encoded. Am I missing something? Is there a way to handle non positional parameters? thx -- Ivan Sergio Borgonovo http://www.webthatworks.it

3 5

Latest BBCode release not shown as an Official release
by naudefj 14 Jan '08

14 Jan '08

Hi, I've created a new BBCode release (bbcode 5.x-1.3) - see http://drupal.org/node/209418 Problem is that it doesn't show under "Official releases" on the project page (http://drupal.org/project/bbcode) Please help! Frank

4 6

Fwd: [jQuery] Re: Birthday is coming
by Larry Garfield 14 Jan '08

14 Jan '08

Does jQuery time is releases by when Drupal has theirs? :-) Seriously though, jQuery 1.2.2 is supposed to be just a bug-fix release. Given that we're in RC status, should we be upgrading as well, to keep the bug count down, or avoiding it because OMG that would be changing code in an RC? Or put more pragmatically... Were someone to write a 1.2.2 patch for Drupal 6, would it be considered? ---------- Forwarded Message ---------- Subject: [jQuery] Re: Birthday is coming Date: Friday 11 January 2008 From: "John Resig" <jeresig(a)gmail.com> To: jquery-en(a)googlegroups.com Yep - that's the current plan! --John On Jan 11, 2008 11:12 AM, Cloudream <cloudream(a)gmail.com> wrote: > > is 1.22 going to be release on Jan,14? Seems lots of bugs were fixed. > ------------------------------------------------------- -- Larry Garfield AIM: LOLG42 larry(a)garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson

5 5

Re: [development] Multiple user aliases - Multiple user node, ownership
by Scott Reynolds 13 Jan '08

13 Jan '08

My approach did not involve just the node_access table, it used the og table (to determine if the user is an admin of the group). Just get rid of the og stuff and put in your node_uid table So revised using node_uid table like as follows hook__node_access_records() // add the admin access row $grants[] = array( 'realm' => 'node_author', 'gid' => $node_uid_record->nid, 'grant_view' => 1, 'grant_update' => 1, 'grant_delete' => 1 ); return $grants;* * hook_node_grants() foreach ($node_uid_records as $node_uid_record) { $grants['node_author'] [] = $node_uid_record->nid } return $grants I have done the same in the ejournal module, but what is not possible > with this approach is to track ownership or assign rights to > individual users (as opposed to groups). Think of it in this way: > access rights may be rebuild by other modules, if you do not keep > track of node-authors relationships, you are not able to recreate the > rights using information from node_access table only (using drupal > hooks) because access rights are deleted before being refreshed. > The proposed approach of node_uid table would solve this and many > other related problems. > > I am struggling with the multiple authorship issue since the very > beginning, ie. D4.6, there are potentially a lot of modules who would > benefit from this functionality. I am sorry, that it is probably too > late for D6. > > roman > On Jan 13, 2008 6:32 PM, Scott Reynolds <sdrreynolds at gmail.com<http://lists.drupal.org/listinfo/development>> > wrote: > >* Heres how I have allowed multiple users to be able to edit one node. > Custom* > >* node_access module* > > > >* hook__node_access_records()* > >* // add the admin access row* > >* $grants[] = array(* > >* 'realm' => 'og_admin',* > >* 'gid' => $node->group,* > >* 'grant_view' => 1,* > >* 'grant_update' => 1,* > >* 'grant_delete' => 1* > >* );* > >* return $grants;* > > > >* then..* > >* hook_node_grants()* > >* foreach ($account->og_groups as $group) {* > >* if ($group['is_admin'] == 1) {* > >* // grant this user admin priv over all nodes in group* > >* $grants['og_admin'][] = $group['nid'];* > >* }* > >* }* > >* return $grants* > > > >* Then hook_enable()* > >* node_access_rebuild();* > > > >* Its simple and it works. I may have some typos in there but thats the > basic* > >* idea. Same trick can be applied to roles. So you can have editor roles > that* > >* can change any node on the site.* > >* --* > >* Scott Reynolds* > >* Senior Developer and Engineer* > >* MothersClick* > >* scott at mothersclick.com<http://lists.drupal.org/listinfo/development> > * > > -- Scott Reynolds Cell: 630-254-2474 http://www.scottreynolds.us

1 0

Re: [development] Multiple user aliases - Multiple user node, ownership
by Scott Reynolds 13 Jan '08

13 Jan '08

Heres how I have allowed multiple users to be able to edit one node. Custom node_access module hook__node_access_records() // add the admin access row $grants[] = array( 'realm' => 'og_admin', 'gid' => $node->group, 'grant_view' => 1, 'grant_update' => 1, 'grant_delete' => 1 ); return $grants; then.. hook_node_grants() foreach ($account->og_groups as $group) { if ($group['is_admin'] == 1) { // grant this user admin priv over all nodes in group $grants['og_admin'][] = $group['nid']; } } return $grants Then hook_enable() node_access_rebuild(); Its simple and it works. I may have some typos in there but thats the basic idea. Same trick can be applied to roles. So you can have editor roles that can change any node on the site. -- Scott Reynolds Senior Developer and Engineer MothersClick scott(a)mothersclick.com

2 1

Re: [development] Multiple user aliases - Multiple user node ownership
by Moshe Weitzman 13 Jan '08

13 Jan '08

I think this is pretty much a moot point. You can easily add a multiple valued text field and display that everywhere, including Views. On 1/12/08, John VanDyk <jvandyk(a)iastate.edu> wrote: > I have long thought Drupal's assumption that a node has a single > author to be erroneous. > > >I've had several requests to: (i) To be able to have nodes that can be > >(owned) edited/deleted by multiple users (group posts); (ii) To be able > >to post under aliases - without logging into multiple accounts. > > > >Obvious answers: (i) Something nasty with Node Access; (ii) CCK field to > >be displayed replacing the the usual user field, trouble of having > >reusable or identifiable aliases as well. > > > >(in/sane?) answer: Write module that - (i) Creates a (blocked) user to > >register 'nicks' (ii) Links 'nicks' with user(s) 1->1 or 1->many (iii) > >uses nodeapi to add 'nick' to node form (iv) adds edit/delete to nodes > >that relate to user 'nick's (just skipping and adding different access > >control to present node functions). > > > >Just a check if I'm looking the wrong way, or if I'm just hanging out in > >the marginal 20% as usual. > > > >ekes > >http://drupal.org/user/10083 > >

2 1

Re: [development] Multiple user aliases - Multiple user node ownership
by Karen Stevenson 13 Jan '08

13 Jan '08

Actually, we really do need a core solution for this because of the fact that users are tied to nodes in so many ways other than what they display to the end user. What happens to a node that is authored by several people but 'owned' by only one when the owner's record is deleted or inactivated? There's no way to transfer ownership to the other authors, because we don't know who they are. If we have a way to link to multiple authors, if one goes away the links to the others remain. I do think this may be an example of what CCK in core might do in D7 -- the node author becomes a multiple value userreference field instead of a single value field. Also, for whatever it's worth, whether you need this at all depends on your environment. In the blogging world, the people who write the blogs are the authors and the current system works fine. When you talk about tracking issues, again, the people who write the issues are the authors, and there's a one-to-one relationship that works fine. But when you start talking about books or when you're publishing material in the business or academic world, 'authorship' and 'ownership' of nodes needs to be more flexible. Either way, this is clearly something that won't happen until D7, but it's good to discuss. My two cents :) Karen ----- Original Message ---- From: Moshe Weitzman <weitzman(a)tejasa.com> To: development(a)drupal.org Sent: Sunday, January 13, 2008 7:17:40 AM Subject: Re: [development] Multiple user aliases - Multiple user node ownership I think this is pretty much a moot point. You can easily add a multiple valued text field and display that everywhere, including Views. On 1/12/08, John VanDyk <jvandyk(a)iastate.edu> wrote: > I have long thought Drupal's assumption that a node has a single > author to be erroneous. > > >I've had several requests to: (i) To be able to have nodes that can be > >(owned) edited/deleted by multiple users (group posts); (ii) To be able > >to post under aliases - without logging into multiple accounts. > > > >Obvious answers: (i) Something nasty with Node Access; (ii) CCK field to > >be displayed replacing the the usual user field, trouble of having > >reusable or identifiable aliases as well. > > > >(in/sane?) answer: Write module that - (i) Creates a (blocked) user to > >register 'nicks' (ii) Links 'nicks' with user(s) 1->1 or 1->many (iii) > >uses nodeapi to add 'nick' to node form (iv) adds edit/delete to nodes > >that relate to user 'nick's (just skipping and adding different access > >control to present node functions). > > > >Just a check if I'm looking the wrong way, or if I'm just hanging out in > >the marginal 20% as usual. > > > >ekes > >http://drupal.org/user/10083 > >

1 0

Re: [development] Multiple user aliases - Multiple user node ownership
by Karen Stevenson 13 Jan '08

13 Jan '08

I think this would be a step in the right direction. But even a revision might have multiple authors. Take the case of a group of people that has been working together to solve a problem and publish the results. They all ought to get credit as authors, instead the credit will go only to the person who input it into the system (who might even just be an assistant and not one of the authors). The new 'add more' AHAH button in D6 could be useful here to build a list of authors. Karen ----- Original Message ---- From: FGM <fgm(a)osinet.fr> To: development(a)drupal.org Sent: Sunday, January 13, 2008 2:08:02 AM Subject: Re: [development] Multiple user aliases - Multiple user node ownership Actually, I'd be tempted to say that in most cases, nodes should not have one author, but revisions should, and nodes be characterized by the set of the authors of the revisions. This is actually probably best for intellectual property issues. This would credit actual contributors more efficiently than the current system, where all goes to the latest modifier, as exemplified by the recent problem with the handbook reorganization, in which lots of authoring credit was thus lost. ----- Original Message ----- From: "ekes" <ekes(a)aktivix.org> To: <development(a)drupal.org> Sent: Sunday, January 13, 2008 2:47 AM Subject: [development] Multiple user aliases - Multiple user node ownership > I've had several requests to: (i) To be able to have nodes that can be > (owned) edited/deleted by multiple users (group posts); (ii) To be able > to post under aliases - without logging into multiple accounts. > > Obvious answers: (i) Something nasty with Node Access; (ii) CCK field to > be displayed replacing the the usual user field, trouble of having > reusable or identifiable aliases as well. > > (in/sane?) answer: Write module that - (i) Creates a (blocked) user to > register 'nicks' (ii) Links 'nicks' with user(s) 1->1 or 1->many (iii) > uses nodeapi to add 'nick' to node form (iv) adds edit/delete to nodes > that relate to user 'nick's (just skipping and adding different access > control to present node functions). > > Just a check if I'm looking the wrong way, or if I'm just hanging out in > the marginal 20% as usual. > > ekes > http://drupal.org/user/10083 > >

2 1

i18n active language
by Idan Arbel 13 Jan '08

13 Jan '08

Hello, I'm need to find the active language for a module I'm writing, anyone know where this information is stored? Idan

2 1

Forms API and Array
by David Metzler 13 Jan '08

13 Jan '08

Does anyone know whether FAPI can create repeating input fields of the form: <input name="myfiled[]"/> <input name="myfield[]"/> Or some such equivalent. I'd like the stuff returned in a $form_values['myfield'] variable as an array of values I'm thinking about doing a custom helper function to accomplish this but would love to hear best some ideas about how to approach this. Dave

4 4