January 2008 - Development - lists.drupal.org

How to start new module
by Marolijo - Pol maresma 18 Jan '08

18 Jan '08

Hello, I'm a newbie on module development... I readed the Module Creator Guide, but I need to do a special thing and don't know where to start. I need a simple module to make a csv (or xml) of a content type with cck field, including images. I tried Views Export but doesn't work with images. (i need to put the image url on the csv) Can someone tell me where to find a guide on how to do the selectes on the database, and how to output a file to the browser on a specific path? Thank's for all! Pol Maresma / pol(a)polnetwork.com PolNetwork.com / Serveis d'Internet msn: marolijo

2 1

Supporting PostgreSQL schema level
by Jean-Michel Pouré 18 Jan '08

18 Jan '08

Dear friends, First of all, thank you for developing Drupal. I plan to use Drupal for my community site (2.000.000 pages a month) and would like to contribute some code as regards PostgreSQL support. You can find here a detailed HOWTO written for PhpBB community, but I guess it applies for Drupal too : PostgreSQL query optimisation HOWTO : http://area51.phpbb.com/phpBB/viewtopic.php?f=3&t=29292 Now, a question about my first contribution: I would like to add support for PostgreSQL schema. A schema is a separate logical space in a database. I would like to allow the following syntax: $db_url = 'pgsql://username:password@localhost/databasename/schemaname'; Conditions: 1) Old syntax still valid $db_url = 'pgsql://username:password@localhost/databasename'; connects to public schema and is still valid. 2) SQL required The proposed changes only means that we run a single SQL query after connecting to the PostgreSQL database: if (isset($url['port'])) { $conn_string .= ' port='. urldecode($url['port']); } $schema=''; if (isset($url['schema'])) { $schema .= urldecode($url['schema']); } // pg_last_error() does not return a useful error message for database // connection errors. We must turn on error tracking to get at a good error // message, which will be stored in $php_errormsg. $track_errors_previous = ini_get('track_errors'); ini_set('track_errors', 1); $connection = @pg_connect($conn_string); if (!$connection) { require_once './includes/unicode.inc'; _db_error_page(decode_entities($php_errormsg)); } if ($schema !== '') { @pg_query($connection, 'SET search_path TO ' . $schema); } This does not change other queries. Now, I would like your opinion on these changes. Would you like a patch supporting PostgreSQL schema in Drupal code? Kind regards, Jean-Michel

5 6

Committed to Drupal + PostgreSQL development
by Jean-Michel Pouré 18 Jan '08

18 Jan '08

Dear friends, I am a PostgreSQL fan, completely new to the Drupal community. My site recieves 600.000 visitors every month and serves 3 million pages. Our non-profit organization based in France. We are migrating to Drupal. Our choice was mainly decided because Drupal supports PostgreSQL. We are committed to support Drupal PostgreSQL development and contribute to the community, mainly with my work. It might take me some time to understand Drupal internals, but whenever you need information on PostgreSQL, feel free to contact me on this list. I am at your service and also serving the PostgreSQL free community. Kind regards, Jean-Michel Pouré

2 1

Need Help With Drupal Widget
by Matthew Farina 17 Jan '08

17 Jan '08

Netvibes contacted me about helping them put together a drupal aggregator widget. These widgets work on nevibes, OS X, in Windows Vista, on igoogle and more. You can find an example at http://eco.netvibes.com/widgets/229787/the-chronicle-of-higher-education I'm looking to put together a list of up to 15 feeds to put in the widget. 4 are tabs with up to an additional 11. In the example if you click the down arrow on the tab you are on you can see all the possible feeds you can read in the widget. Anyone have any suggestions for feeds to use in the widget? My initial list was the drupal planet and the feeds for the drupal homepage and the groups homepage. What others should we list? They contacted us because of www.netvibes.com/drupal. Matt

4 4

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