February 2008 - Development - lists.drupal.org

SQL To D6 Schema Conversion Script?
by Mike Cantelon 05 Apr '08

05 Apr '08

Does anyone have a script that automates conversion of table creation SQL to a Drupal 6 schema definition? If not, maybe I'll see if I can cook something up as it seems like a lot of work otherwise. ;) Cheers, Mike

8 8

Views 2 UI
by Keith Smith 03 Mar '08

03 Mar '08

I recently promised merlinofchaos that I would help with the Views 2 documentation. I'm glad that I did. In reviewing Drupal 6 reviews posted across the web, I'd recently read the "Views preview" section of the post http://tek4dpipol.blogspot.com/2008/02/look-at-drupal-6-core-features-2.html, complete with screenshot. I'd seen various Views UI related posts on g.d.o, though I didn't follow any of them closely. I'd seen UI-related discussion scroll past in IRC. I assumed I was pretty well on top of "state of the art" Drupal interface designs. I was so very wrong. I checked out Views 2 over the weekend, in order to get a feel for how I might could help with strings and documentation. It is fair to say that the new interface "blew me away." It is not evolutionary, but revolutionary. Thomas Kuhn would call it a paradigm shift. It's damn sexy. Earl, what I've seen so far is just fantastic. You -- and everyone who has helped you with this -- have made something special here. I think I want to be you when I grow up. --ks

8 13

RTBC is now "reviewed & tested by the community"
by Karoly Negyesi 03 Mar '08

03 Mar '08

Hello world, After Daniel F. Kudwien pointed at http://drupal.org/node/156637 (rename RTBC) in my other RTBC thread, the issue saw a flurry of activity and, much to my delight, I was able to rename this status to something which much better reflects what it actually is. Thanks to: * fajerstarter for the new name * webchick for rerolling my small patch to make the issue state accomodate the longer name. * hunmonk for commiting and applying it on drupal.org. Enjoy! Karoly Negyesi

12 16

Best practice for update_sql?
by Kieran Parsons 29 Feb '08

29 Feb '08

I am wondering how best to change update_sql commands for Drupal 6 modules. I know that update_sql does not to %-placeholder substitution (although previous patches suggest that it was considered and rejected -- eg http://drupal.org/node/36324) but now we also need to remove literals from db_query (http://drupal.org/node/114774#db-query-standard) and so in effect from update_sql as well. This seems to make update_sql much less useful. I looked through how the core modules deal with this and they do not seem consistent to me, and also do not seem to be following the dq_query change either. Some examples from system.install: $ret[] = update_sql("UPDATE {profile_fields} SET category = 'Account settings' WHERE LOWER(category) = 'account'"); $ret[] = update_sql("UPDATE {permission} SET perm = '$renamed_permission' WHERE rid = $role->rid"); In many other cases the update is done using db_query and then something like: $ret[] = array('success' => TRUE, 'query' => "My query"); is used. But if the db_query failed this will still appear as a success and the only error message will be in the normal error message (which presumably may only be logged and not displayed in some cases). What is the best way to deal with this? Thanks, Kieran

4 4

2 Forms
by Konstantin Kroner 29 Feb '08

29 Feb '08

hi, i have 2 form on 1 Site, they needed by 1 module. I render them with drupal_get_form() in my template, that works fine. When i look at firbug i have 2 forms on this side. Form 1 runs after submit in my _submit function. But form2 ignore my _submit total. I set on the submit Button '#submit' => array('mycallback'), but drupal ignore that total. Any have i idea how my second form can find his callback Konstantin

2 1

your issues mail
by bert boerland 27 Feb '08

27 Feb '08

Hi A long time ago <?> I got a monthly mail with a list of all the issues I filed. This was a great way for me to clean old feature request and bug reports and helps developers to have a more clean issue queue. Since some time I do not get these mails anymore. I understand that sending out bulk mail towards every person that ever filled a bug report is causing a high load on different servers, but I would love to get these mails again every month. Is this possible? -- groets, bert boerland -- my rants on my weblog ---- ------ http://boerland.com/ --

1 0

Tooltips for api functions.
by Paco 27 Feb '08

27 Feb '08

This week on irc some developers were talking about integrating tooltips on api.drupal.org, the idea is to show parameters while browsing function lists. This is the patch to api module 5.x. http://drupal.org/node/227007 What's your opinion?, can you review/test it? theBorg

2 1

A Git mirror for Drupal CVS
by Mikkel Høgh 27 Feb '08

27 Feb '08

Forgive me my shameless self-promotion, but I'd like to draw attention to my newly created Git-mirror of cvs.drupal.org Git ( http://git.or.cz/ ) is a great version control system that I use to keep my Drupal-sites up-to-date, so a complete mirroring of Drupals CVS with tags and branches and all is a great step forward - for me at any rate. I've made a longer blog post about it here: http://mikkel.hoegh.org/blog/2008/a_git_mirror_for_drupal_cvs The repository is here: http://git.lion47.com/cgi-bin/gitweb.cgi Kind regards, Mikkel Høgh <mikkel(a)hoegh.org>

15 32

Drupal 6.x uses translations/ instead of po/
by Tobias Toedter 26 Feb '08

26 Feb '08

Hi, I think that the list of changes between Drupal 5.x and 6.x for module developers ("Converting 5.x modules to 6.x", <http://drupal.org/node/114774>) is missing the renaming of the po/ directory to translations/. Could this still be added? Regards, Tobias -- Tobias Toedter | Dyslexics have more fnu. Hamburg, Germany |

2 1

Module developers, please do *proper* releases !
by Xavier Bestel 25 Feb '08

25 Feb '08

Hi, I'm writing a little rant about modules. I know it's tempting when you start your module to call it a "development version", because it doesn't work so well yet or it's not finished. But many modules never leave that state, and e.g. now that the official Drupal version is 6.x and that version 5.x is just a bugfix release, there are still many modules with only a 5.x-1.x-dev release. There's also the case where you have a concurrent -dev and numbered release, but only the -dev release has the features and the bugfix to make it usable. This isn't just a cosmetic problem. As all releases have the same name, it's very inconvenient to store different versions, e.g. to go back in case of problem. Also it doesn't work so well with the update module (even if it tries to workaround that). So please, do proper releases. If you need to work on features, do a parallel 1.n and 2.n version, but avoid using -dev in code which should really be used. Thanks, Xav

22 57