May 2006 - Development - lists.drupal.org

AJAX SIG meeting: May 18th at 18:00 UTC / 11am PST / 2pm EST / 20:00 CEST
by Konstantin Käfer 18 May '06

18 May '06

Hi, I want to invite everybody who is interested in Drupal and AJAX within Drupal to join us in #drupal-ajax. You can also join the SIG at http://groups.drupal.org/ajax-developers. timcn

1 0

Drupal Curriculum Meeting today.
by Adrian Rossouw 18 May '06

18 May '06

Just a reminder that there is a Drupal Courseware meeting today at 12:00pm PST. The meeting was moved 2 hours earlier to facilitate more people in other time zones to be there. If you have an interest, please join us on #drupal-courseware today. The agenda and volunteer todo's will be placed on http:// groups.drupal.org/curriculum soon. -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com

1 0

sess_write() and PHP processes
by Nic Ivy 18 May '06

18 May '06

Is sess_write() called by the same PHP process that handles page requests? I'm working with dado to debug node_import.module (see http:// drupal.org/node/63581) node_import.module uses a $_SESSION variable to control the workflow state, which is something I've not seen often. Simply put, the workflow progresses normally for some people (e.g. dado) and not for others (e.g. me). For me, some variables in $_SESSION are effectively not updated. I say "effectively" because $_SESSION is written twice. The second write uses old values. At one point, I have the following debugging statements: <?php watchdog('debug', 'Before'); $_SESSION['node_import'] = $edit; // NOTE: sess_write() calls watchdog ('debug', 'Writing'). watchdog('debug', 'After'); ?> The logs consistently show, in reverse chronological order: Writing After Before What's going on? Nic

2 2

IRC #drupal re: project not publishing nodes, flexibility
by Derek Wright 18 May '06

18 May '06

Topic for #drupalDrupal Development Chat | Use #drupal-support or http://drupal.org/support for support questions. Theming discussion is on #drupal-themes. | Digg: http://www.digg.com/software/ Two_videocasts_about_the_new_Drupal | Do not talk of consultancy fees here. Thanks. | We have a #drupal-soc channel now. irc: Shakur has joined drupal irc: SC-RM has left drupal irc: adrinux has joined drupal irc: kitt has joined drupal irc: R_engel has left drupal irc: X_x has joined drupal Derek: seen nedjo? Druplicon: nedjo was last seen in #drupal-ecommerce 5 days 21 hours ago saying 'Thanks, I'll try to get a first draft patch posted tomorrow.'. irc: Itkovian has left drupal irc: port has joined drupal Amazon: dww: nedjo's best found via email Derek: we exchanged some this morning... i was just wondering if he was around, that's all. ;) Derek: thanks for the pointer, though... Derek: seen osinet? Druplicon: osinet was last seen in #drupal 1 hours 21 mins ago saying 'thanks for your help, anyway'. irc: Freso has left drupal irc: vIkSiT has joined drupal irc: eighty has left drupal irc: malexmedia has joined drupal malexmedia: hey all... how can my module get a complete list of all NIDs that match a given taxonomy classification? malexmedia: i'm looking at taxonomy_select_nodes at the moment, but it is only giving me the top N results irc: s1mon has left drupal irc: j^ has joined drupal irc: JonBob has left drupal irc: TobiasFar has left drupal irc: bpuccio has left drupal irc: erikhopp has left drupal irc: erikhopp has joined drupal irc: Heine has left drupal irc: erikhopp has left drupal killes: dww: hi, did you see my recent comment? Derek: no sorry, where? Derek: http://drupal.org/node/64100 ? Druplicon: http://drupal.org/node/64100 => project shouldn't publish/ unpublish nodes automatically based on releases irc: Nand0 has left drupal killes: yeah killes: merlinofchaos: ping Derek: why don't we make a new signup administrative page that shows pending, unpublished projects? irc: scyrma has joined drupal irc: R_engel has joined drupal Derek: sorry, project admin, that is... killes: yeah, we could do that killes: another idea: irc: Aw0L has left drupal irc: Nomad411 is now known as Nomad411_Away killes: auto-publish projects that have a corresponding entry in cvs. Derek: well, it seems somewhat silly to try to do fork/duplicate filtering on the account requests, but then nothing once they're inside the gates. ;) killes: ie, if people proceed according to your recipe then their new projects will be published from the start killes: why? killes: nobody really checks new projects now anyway. killes: no reason to change that. Derek: i guess the premise is once we trust them enough w/ an account in the first place, we trust them to never attempt to start doing duplicate work in the future... killes: I rather unpublish one inappropriate project once a year rather than publish five a week Derek: sure. killes: makes sense, doesn't it? Derek: but what good is unpublishing it if project will republish it at the next cron run? ;) killes: also, we should limie creation of projects to people with a cvs account. killes: limit Derek: *that* seems like the real solution. killes: well, the cron stuff should go away of course Derek: then all projects should just be published immediately. irc: d-f-g has joined drupal killes: yes Derek: i was thinking the same thing... killes: cool Derek: i guess we'd just want to make a role for this, which had whatever cvs-related perms we wanted, and "create projects" perm irc: geilhufe has joined drupal killes: hmm irc: hunmonk has joined drupal killes: can't the access hook in project check for the cvs account? Derek: i dunno if we'd want to have cvs.module automatically messing with roles. killes: no roles Derek: well, we don't really want to have "project" show up as an option on "create content", do we? killes: just if $user->cvs-account killes: right killes: so you check the global $user for the cvs info. killes: maybe to a user_load if neccessary killes: do killes: killes sips from his stein. Derek: a) if we do this, we should make it a project setting to enable this behavior -- i still have illusions in the idea of being able to use project somewhere *other* than d.o. ;) killes: heh, I don't :p killes: you can do a if module_exist(cvs) Derek: b) i'd have to look at the project code to figure out if what you're saying is possible... i suspect it is... killes: yeah killes: easily Derek: yeah, furthermore, i have illusions in the idea that you could enable both project and cvs somewhere other than d.o. ;) irc: drob has joined drupal Derek: i'd still make it a setting, not just module_exist(). ;) killes: function project_project_access($op, $node) { webchick: killes, say... the vote up/vote down package... is that you who keeps marking it as unpublished? and if so, is it because of the commercial thing? or is there some bug in project module? killes: settings suck killes: webchick: no killes: webchick: the gremlins do it webchick: Ah, the gremlins. :) Derek: webchick: we suspect bugs in project's auto publish/unpublish code. killes: I've no idea why it gets unpublished webchick: Ok, just making sure I wasn't stepping on any toes by publishing it again. Derek: which is why killes and i are talking about how to completely rid project of all such code. killes: I suspect the regexp in project_cron webchick: Oh. I should pay attention. :) Derek: 'tis ok. ;) killes: webchick: I did that several times myself killes: yeah killes: Kjartan likes the code, but Kjartan shows up once every half a year. webchick: Yeah that makes sense. I just got nervous when I saw your name thinking it might've been a licensing conflict or something. mozillaman: seen Dries_ Druplicon: Dries_ was last seen in #drupal 1 days 3 hours ago saying 'webchick: pm?'. killes: webchick: no, I was just trying to help Derek: killes: why do you think settings suck? killes: and gave up killes: dww: it is a general consensus :p Derek: is that not a good way to keep a module flexible enough to be used for different things by different people? malexmedia: hey all... am looking for a way to get a list of _all_ nids that match specific tids mozillaman: seen craq Druplicon: craq was last seen in #drupal 5 hours 1 mins ago saying 'dww: that was the same thing for me that i hated about it too'. killes: dww: well, it you can't do without a setting, go ahead. killes: dww: but I generally prefer the "do what I think" approach malexmedia: taxonomy_select_nodes is great, except it seems to be only giving me the top N nids Derek: killes: i refuse to give in to the "project should only run on d.o".. killes: malexmedia: do a join on term_node killes: or just a select •: malexmedia looks Derek: one of the main reasons i'm making so many improvements to it is because i want to use it for other things, too. killes: dww: that's ok. webchick: seen moshe_home Druplicon: moshe_home was last seen in #drupal 3 hours 37 mins ago saying 'i am not updating groups site with this new og code. thats suicidal. views would need to be rebuilt'. webchick: seen moshe_work Druplicon: moshe_work was last seen in #drupal 55 days 3 hours ago saying 'chx: i would accept it but i am not release manager. i think it will be tough'. Derek: you think it's hard finding people to keep project working and getting better already? killes: dww: I don't really want it to be resteicted to drupal.org malexmedia: killes: oh, so should I just do the db queries myself? killes: malexmedia: umm, yes. Derek: if it's so central to d.o, we should nurture as big a devel community as possible... malexmedia: ie, there's no 'right' way to do it with the drupal api malexmedia: cool, thanks Derek: and that means getting other people to use it... killes: malexmedia: there might be a function in taxonomy.module Derek: and that means leaving it flexible, without so many assumptions about how we need it to work on d.o... irc: clouseau has left drupal killes: dww: yeah, ok, stop it. :p malexmedia: killes: i was looking, and taxonomy_select_nodes seems to be the closest candidate Derek: </soapbox> Derek: ;) malexmedia: but it's not 100% perfect :-P killes: malexmedia: I think that's not really what you want killes: yeah Derek: webchick, can i get an amen? ;) killes: so do you own select nid from term_node where tid = %d webchick: Wait. amen? what am I amening? Derek: my rant about project. ;) Derek: forget it. webchick: Oh probably. :D webchick: If I ever get a huge chunk of freetime webchick: I have a big interest in project module malexmedia: killes: works for me, thanks webchick: but... Derek: i just meant my last 5 messages in here, roughly... webchick: until then I will do my best to help it get working on d.o, :) irc: malexmedia has left drupal webchick: And I think making it flexible is a godo thing webchick: good thing* webchick: So does that qualify as an amen? :) Derek: indeed. Derek: killes, i'll create a project issue about what we were talking about and assign it to myself. Derek: the code will in fact be easy, even with the setting. ;) Derek: but, i'd want to test it locally a lot, first. irc: vIkSiT has left drupal Derek: so i can't just finish it right now... killes: dww: no hurry Derek: ok. killes: webchick: try casetracker :p webchick: so i hear. ;) Derek: *sigh* ;) killes: at least if you don't need the cvs/tarball integration Derek: was i just being dense when i tried it, or does case tracker not allow you to move "cases" from one project to another? killes: dww: let me try irc: adrinux has left drupal Derek: (yeah, sorry, i don't have a local test site for casetracker setup at the moment) killes: dww: you can edit the case and re-assign killes: well, I do killes: :p killes: non-local Derek: yeah, i figured. killes: but testsite Derek: but there's no way for non-admins to move cases? killes: not sure Derek: i.e. you need admin nodes perms? Steef: seen nedjo Druplicon: nedjo was last seen in #drupal-ecommerce 5 days 22 hours ago saying 'Thanks, I'll try to get a first draft patch posted tomorrow.'. Derek: yeah, that's a serious failing IMHO... killes: dww: no, you can change that from a comment Derek: oh, ok, great. killes: yep, works Derek: killes, i guess i should just followup to http://drupal.org/ node/64100 instead of making a whole new feature request about it. ;) Druplicon: http://drupal.org/node/64100 => project shouldn't publish/ unpublish nodes automatically based on releases killes: dww: right irc: s1mon has joined drupal irc: hunmonk has left drupal irc: Shakur is now known as Flk irc: drob has left drupal irc: tobias_maier has left drupal irc: obicke has left drupal irc: s1mon has left drupal irc: eaton has left drupal irc: gordonh has joined drupal

1 1

[ANN] OpenID module version 1.1 for Drupal 4.7
by Jonathan Daugherty 18 May '06

18 May '06

JanRain, Inc. is pleased to release version 1.1 of the Drupal OpenID module to enable consumer support in Drupal 4.7. This module depends on the JanRain PHP OpenID library, version 1.1.0. Enjoy! http://www.openidenabled.com/software/drupal/drupal-consumer-module http://www.openidenabled.com/openid/libraries/php/ -- Jonathan Daugherty JanRain, Inc.

5 9

Drupal hook_user 4.6
by Trevor Mckeown 17 May '06

17 May '06

hey all, A quick questsion on drupal hook_user in 4.6. If I am attempting to add a user through the approiate web pages, and let's say the user is already registgered, would the hook_user still be fired? In case of errors on the page are hooks still excuted? -Trevor

1 0

OT: Google Tool Kit allows AJAX development in Java
by Khalid B 17 May '06

17 May '06

Google released their Google Web Toolkit. It allows AJAX development in Java (yes, you read that right!) http://code.google.com/webtoolkit/ Slashdot discussion http://developers.slashdot.org/article.pl?sid=06/05/17/127214 Digg http://digg.com/programming/New_Google_tool_compiles_Java_to_AJAX

4 5

Sessions and non-logged-in users
by Nick Wilson 17 May '06

17 May '06

Hi everyone, I have to store some item id's (a little like a cart) for anon users. I can of course set a cookie with the id of the items, but i was wondering if there were any built in ways to manage this kind of thing? many thanks -- Nick Wilson http://performancing.com/user/1

3 5

Freezing the Drupal API
by Richard Archer 17 May '06

17 May '06

Hi all, Recent discussions on the Consultants list has raised the issue of the cost of doing business using Drupal, notably the high cost of upgrading existing installations due to the ever-changing nature of Drupal's API. I wonder if there would be any interest in forming a group to tackle this by identifying where the current API has potential for improvement and perhaps even writing some code! My aim would be that as of Drupal 5.0 with CCK, the published API would be treated as "stable" and changes to it would be resisted strongly. IMHO, if this could be achieved it would give Drupal a much more mature look and make it more attractive to large users. It would also increase the manpower available to work on future Drupal development because right now extra resources are being wasted maintaining the 4.5 and 4.6 trees, simply because the API changes between releases makes it impractical for many users to upgrade to 4.7. ...Richard.

26 51

RFC: Candidate 'premium' modules
by Karthik 17 May '06

17 May '06

Premium modules are those that are: a) release-critical - A new version of Drupal cannot be released unless these are up-to-date. b) quality controlled - these will be 'core modules' in all but name. c) well maintained - HEAD, current release and previous release should all be maintained preferably by a number of maintainers. Candidate modules: ---------- actions casetracker cck ecommerce event flexi* i18n image og project sections (when it is done) subscription trackback views voting api If it doesn't find its way into core, this list should also include a JS and XML API. Any modules being used on Drupal.org (simplenews etc.) will also need to be included. Conversely, any of these modules should be safely usable on drupal.org. ---------- Unsure about the following: workflow Access control modules : taxonomy_access/na_arbitrator? HTML editors? links module? Media/gallery modules ---------- Critical themes and translations should also be added to the list. Thanks, -K

17 20