- Development - lists.drupal.org

Re: [development] Docs about Drupal + CVS: reminder and call for help
by Michelle Cox 17 Jan '08

17 Jan '08

On 1/17/2008 2:28:48 PM, Ivan Sergio Borgonovo (mail(a)webthatworks.it) wrote: > I think previous exposure to any rcs should be a prerequisite to > anyone contributing to drupal code (core or contrib). I hope you're joking. That would be a crazy requirement and knock out a heck of a lot of contributors. Michelle

1 0

So why we do support postgresql?
by Karoly Negyesi 16 Jan '08

16 Jan '08

Hi, Still there are no testers. I want to reiterate my plea: make postgresql support somewhat optional. If there are testers, great, if not, go on with life. You can flame me, but this is already the state of affairs just noone wants to admit. Just see http://groups.drupal.org/node/6980 . Greg spoonfeeds you. I know we will get testers for the rest of the week because of this letter and then they will move away as it happened uncounted times. I wonder what people will say. "Monoculture is bad" -- tick, do not bother with this answer. "You are evil" -- tick, do not bother either. "There are testers, but" -- surely there are just they have hidden themselves really well. What about answering something constructive? I *am* bored by needing this raised every month. Regards Karoly Negyesi

16 22

Free to good home: modules
by Mark Fredrickson 16 Jan '08

16 Jan '08

Hey all, Like the miser I am, I've been greedily hoarding my collection of precious modules. Well, I've turned over a new leaf. I'm now accepting as many co-maintainers as I can find for the following modules: http://drupal.org/project/betterdate http://drupal.org/project/fieldactions http://drupal.org/project/jquery47 http://drupal.org/project/nodeasblock http://drupal.org/project/nodecloud http://drupal.org/project/og_actions http://drupal.org/project/referertools http://drupal.org/project/submitagain http://drupal.org/project/viewfield Several of these are actions modules that should probably be rolled into the real modules now that actions is hitting core. jQuery4.7 will probably be "end-of-lifed" at the 6 release (unless someone wants it). I think nodeasblock, nodecloud, and viewfield are pretty sweet, but I don't have time to give them the love they deserve. I'll still try to get some work done on them when I can, but I don't want my lack of time to hold any one else back. Also, if people are interested, I've got a project in CVS that doesn't have a node: http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/aclfield/ It's a module to add access control permissions via a CCK field. It defines its own hook for "widgets." Other modules can hand out keys and the field decides which keys apply to a given node with which permissions. Of course, it's also compatible with other access control methods. I wanted to get it in better shape before I created an official project, but again, that hasn't happened. If you want in, let me know and I'll create a project. If you can wrangle a CVS account, email me back and I'll add you to any of these projects. Cheers, -Mark

2 1

"Final call" for new GHOP tasks
by Angela Byron 16 Jan '08

16 Jan '08

There's less than one week left for students to claim GHOP tasks. We still have 74 slots available. Modules need porting? Documentation need written? Videos need making? Patches need coding? Tests need writing? Submit 'em as task ideas: http://drupal.org/node/add/project-issue/ghop Or, help refine someone else's great idea into a task: http://drupal.org/project/issues/ghop -Angie

2 1

$form #tree issue
by Alessandro Feijó 15 Jan '08

15 Jan '08

I'm building a dynamic filter system, my user will be able to add as much criteria he wants Here a tiny example of my current aproach: $form['criteria'] = array( '#type' => 'fieldset', '#title' => t('Criterias'), '#collapsible' => TRUE, '#collapsed' => FALSE, '#tree' => TRUE, ); for ($i=1; $i<=variable_get('beginer_criteria', 3); $i++) { $form['criteria'][$i]['table[]'] = array( '#type' => 'select', '#options' => $tables, '#value' => $load[$i]['table'], '#description' => $load[$i]['table'], '#attributes' => array( 'class' => 'edit-table', ), ); } The form will start with X sets of fields (2 combo, 1 editfield) I set jQuery to clone any of those criteria, adding more Here the problem begin, any cloned, will have the same name of the original one. My $form_values does not return the cloned fields. my HTML is: <div class=qz-tablefield><div class="form-item"> <select name="criteria[1][table[]]" class="form-select edit-table" id="edit-criteria-1-table[]" ><option value="0">Select an option</option><option value="6">criticality</option><option value="2">group</option><option value="4">origin</option><option value="3">position</option><option value="5">priority</option><option value="1">reason</option><option value="7">status</option></select> </div> <div class="form-item"> <select name="criteria[1][field[]]" class="form-select edit-field" id="edit-field1" id="edit-criteria-1-field[]" ><option value="0">Select a table</option></select> </div> <div class="form-item"> <input type="text" maxlength="100" name="criteria[1][value[]]" id="edit-criteria-1-value[]" size="30" value="" class="form-text" /> </div>Note the criteria[1], the next set will be criteria[2]The cloned criteria will to be 1 ! the $form_values ignore the new fields.What can I change in my $form to solve that? Thanks a lot Feijó

3 7

Multiple user aliases - Multiple user node ownership
by ekes 15 Jan '08

15 Jan '08

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

6 6

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