February 2008 - Development - lists.drupal.org

Fwd: [droppies] [General inquiry (other)] Drupal Icon to Share with You and Drupalers
by Dries Buytaert 17 Feb '08

17 Feb '08

Begin forwarded message: > From: ben(a)contactben.com > Date: Sat 16 Feb 2008 23:58:49 GMT+01:00 > To: info(a)drupal.org > Subject: [droppies] [General inquiry (other)] Drupal Icon to Share > with You and Drupalers > Reply-To: ben(a)contactben.com, droppies(a)drupal.org > > DrupalB sent a message using the contact form at http://drupal.org/ > contact. > > Hello Drupal gang! > > I made a "Powered by Drupal" icon (inspired by the format you have > on the > Drupal.org site) and I wanted to make it available to other > Drupalers. I'd > appreciate it if you guys could host the file on your server, but > I've made > it available for you to download at > http://www.hershleder.com/powered_by_drupal_for drupal.psd.zip ~~ > It's a > Photoshop file, with all the separate layers to facilitate > customization; > and I made it large so it can be scaled to the user's needs. > > Thanks for all the hard work you guys do. Hopefully, in the future, > I can > contribute more than just a logo, but right now I'm doing a lot of > learning! > > Best, > Benjamin > _______________________________________________ > droppies mailing list > droppies(a)drupal.org > http://lists.drupal.org/listinfo/droppies -- Dries Buytaert :: http://www.buytaert.net/

3 2

Drupal 6.x FormAPI: validate and submit properties
by Ron Parker 16 Feb '08

16 Feb '08

Hard at work trying to upgrade my modules to 6.x. Looked at the Drupal 5.x to 6.x FormAPI changes here: http://drupal.org/node/144132 Particularly this regarding the validate and submit properties: http://drupal.org/node/144132#custom-params In Drupal 5.x, I've been using this format: <?php function og_user_roles_form_alter($form_id, &$form) { $form['og_user_roles_regcode_gid']['og_user_roles_regcoderole_value_' . $gid] = array( '#type' => 'select', '#title' => t('Role to assign'), '#options' => $roles, '#default_value' => variable_get('og_user_roles_regcoderole_value_' . $gid, 0), '#description' => t('Select the role you wish to use as the "registration code group role" for every new subscriber who subscribes to this group using one of the registration codes above.'), ); $form['#validate'] += array('og_user_roles_regcode_form_validate' => array($form_id, &$form)); $form['#submit'] += array('og_user_roles_regcode_form_submit' => array($form_id, &$form)); } ?> My question is: How do I write the #validate and #submit properties for the above in Drupal 6.x? My example above does not look like the ones used here: http://drupal.org/node/144132#custom-params So, would this be correct in Drupal 6.x?: <?php function og_user_roles_form_alter(&$form, &$form_state, $form_id) { $form['og_user_roles_regcode_gid']['og_user_roles_regcoderole_value_' . $gid] = array( '#type' => 'select', '#title' => t('Role to assign'), '#options' => $roles, '#default_value' => variable_get('og_user_roles_regcoderole_value_' . $gid, 0), '#description' => t('Select the role you wish to use as the "registration code group role" for every new subscriber who subscribes to this group using one of the registration codes above.'), ); $form['#validate'][] = 'og_user_roles_regcode_form_validate'; $form['#submit'][] = 'og_user_roles_regcode_form_submit'; } ?> Thanks for any information provided. -ron -- Ron Parker Software Creations http://www.scbbs.com Self-Administration Web Site http://saw.scbbs.com SDSS Subscription Mgmt Service http://sdss.scbbs.com Central Ave Dance Ensemble http://www.centralavedance.com R & B Salsa http://www.randbsalsa.com

1 0

Drupal 6.x hook_menu question regarding use of wildcards - Modified
by Ron Parker 16 Feb '08

16 Feb '08

You are absolutely correct! Gosh, why didn't I think of that? Made the modification. Thanks! -ron Message: 3 Date: Sat, 16 Feb 2008 00:37:41 +0100 (CET) From: "Karoly Negyesi" <karoly(a)negyesi.net> Subject: Re: [development] Drupal 6.x hook_menu question regarding use of wildcards - Resolved <?php function _agenda_list($node) { return agenda_list($node->nid); } ?> why not make agenda_list accept a $node instead of a nid and change inside? Why a whole wrapper? <?php function agenda_page_title($node, $text) { $return = $text . $node->title; return $return; } ?> -- Ron Parker Software Creations http://www.scbbs.com Self-Administration Web Site http://saw.scbbs.com SDSS Subscription Mgmt Service http://sdss.scbbs.com Central Ave Dance Ensemble http://www.centralavedance.com R & B Salsa http://www.randbsalsa.com

1 0

PostgreSQL 8.3 change
by Ken Rickard 16 Feb '08

16 Feb '08

All- This is ------NOT------- intended to open the database wars. However, please take note of http://drupal.org/node/220064. Drupaler drupallfm <http://drupal.org/user/194425> discovered a nasty (to us) little change from pgSQL 8.2 (which I test on) to 8.3. It only seems to affect one core query, but could bite any developer who uses JOINS where data types are not identical. >From the Postgres website: "Upgrade Warning...in version 8.3 we have cleaned up some of the data type conversions ("casts"). This refactoring may cause problems for some users..." What does it mean? It means that you cannot do a JOIN across different data types without casting your data. In older versions of pgSQL (and in MySQL) the database handled the conversion for you. pgSQL 8.3 does not, and throws an error. In D6, the only query that seems to be affected is http://api.drupal.org/api/function/block_box_get/6. pgSQL used to turn the interger and varchar into text strings for comparison. It no longer does, so an explict CAST is necessary. However, lets keep that in mind for D7 work on the db layer. -- Ken Rickard agentrickard -- -------------------------------------------------------------- DON'T MISS EARTH'S LARGEST GATHERING OF DRUPAL PROFESSIONALS! Drupalcon Boston 2008 · March 3-6, 2008 Learn more at http://boston2008.drupalcon.org Affordable sponsorship packages available --------------------------------------------------------------

3 2

Drupal 6.x hook_menu question regarding use of wildcards
by Ron Parker 16 Feb '08

16 Feb '08

I'm trying to figure out if I can use wildcards in this manner: <?php $items['node/agenda/list/%node'] = array( 'title callback' => 'node_page_title', 'title arguments' => array(3), 'page callback' => 'agenda_list', 'page arguments' => array(3)->nid, 'access callback' => 'user_access', 'access arguments' => array('view agenda'), 'type' => MENU_CALLBACK ); ?> Since array(3) represents node_load(arg(3)), can I use the statement array(3)->nid for the node id. Or, for that matter, array(3)->type for the node type? If not, what's the correct way? Would it be the old fashioned way (i.e., page arguments' => arg(3))? Thanks for any assistance. -ron -- Ron Parker Software Creations http://www.scbbs.com Self-Administration Web Site http://saw.scbbs.com SDSS Subscription Mgmt Service http://sdss.scbbs.com Central Ave Dance Ensemble http://www.centralavedance.com R & B Salsa http://www.randbsalsa.com

4 7

cutting through the input format clutter
by Gábor Hojtsy 16 Feb '08

16 Feb '08

Hey, Today, I reviewed four contrib modules to cut through the multiple input formats one sets up on a site: http://groups.drupal.org/node/8911 The approaches taken include defaulting to the last used format per user, turning off formats completely for some content types or defining defaults based on content types and user rules (but leaving the options intact). I think that Drupal 7 deserves better support for easily pickable input formats (eg. if the forum is supposed to be bbcode only, then offer that format only), so I'd like to help get some of this functionality into Drupal 7. Let me know if you have some additional / better insight, so we can get the best for all of us. On a related note, I also submitted a Drupal 7 patch to make input formats reorderable. This was not possible without DB changes (input formats were not reorderable before at all): http://drupal.org/node/222183 Testing/opinions welcome (it is just a simple DnD improvement using the already established APIs). Gabor

1 0

Minimum MySQL version
by Larry Garfield 14 Feb '08

14 Feb '08

This has been discussed in a few circles, but this seems the optimal place for it. I propose that for Drupal 7 we make MySQL 5.0 our minimum MySQL version. Justification: Active support for MySQL 4.1 has long-since ended[1]. It is in legacy/extended support status now only. The same is true of MySQL 4.0, which we've already left behind (fortunately). Now, let's be realistic. Drupal 7 is most likely a year away from release, give or take a month. Like previous versions, it will likely be the premiere release for a year or so. In that year, MySQL 4.1 will cease even extended support, at the end of 2009, just as MySQL 4.1 legacy support ends at the end of this year. That means by the time Drupal 7 ships, with PHP 5.2 as a minimum requirement, MySQL 4.1 will be about as modern as PHP 4.2. :-) What does MySQL 5 offer us? 1) SQL Views 2) Stored procedures 3) Perhaps most importantly, many many fewer minor versions each with their own bugs for us to have to work around. 4) The full changelog[2] I am flexible on which minor version of MySQL 5.0 to target, but a year from now there will be no point to keeping MySQL 4.1 around anymore. Let's plan ahead to make Drupal 7 the "all 5s" release. :-) [1] http://www.mysql.com/company/legal/lifecycle/#calendar [2] http://dev.mysql.com/doc/refman/5.0/en/news-5-0-x.html -- 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

10 10

OpenID for the masses
by Derek Wright 14 Feb '08

14 Feb '08

Sorry if this is old news to some, but I just saw this referenced in the SANS security newsletter and I thought the dev list might be interested: http://www.campustechnology.com/articles/58342 "Google, Microsoft, IBM, VeriSign, Yahoo Join OpenID Board" "In a move that could help deliver single sign-on to the masses, Google, Microsoft, IBM, VeriSign and Yahoo have joined a consortium that backs a common federated identity specification..." Cheers, -Derek (dww)

4 3

Invitation to join Students Hang Out from sanari9
by sanari9＠gmail.com 14 Feb '08

14 Feb '08

Hi You have been Invited to Join Students Hang Out by sanari9 To join Students Hang Out click on the following link: http://www.studentshangout.com/index.php?act=Reg&coppa_user=&termsread=1&co… Students Hang Out is one of the Top Students Site World Wide

1 0

Invitation to join Students Hang Out from sanari9
by sanari9＠gmail.com 14 Feb '08

14 Feb '08

Hi You have been Invited to Join Students Hang Out by sanari9 To join Students Hang Out click on the following link: http://www.studentshangout.com/index.php?act=Reg&coppa_user=&termsread=1&co… Students Hang Out is one of the Top Students Site World Wide

1 0