- Development - lists.drupal.org

Re: [development] form_builder and the $form['#type'] .'_value' callback.
by Darrel O'Pry 07 Feb '07

07 Feb '07

I started asking chx about this in IRC last night. I've been working on a few custom form elements for handling files. I need a chance to save files locally before #validate is reached. Chx, suggested #after_build, but I am having issue with my #after_build being called from my element prototype(the default #type values returned from hook_element). While looking through form.inc and trying to figure out why my #after_build function wasn't being called when triggering a submit button on the page I notice there is a large select in form_builder for some default element types, to assign their values from edit/_POST. The _value callback is for defining default values according to chx, and is a rarely used function. I thought it might be a neat idea to move this hard coded select out of form_builder and use the _value callback to assign the #value in form_builder and set the #needs_validation if a value is return from the _value callback. Otherwise use the #default_value defined in the form or the element prototype. I think the behavior would make it easier to build form_elements that don't return a value (type=file ad unchecked type=checkbox are the only ones I know of) and need to generate their value from contextual data. .darrel.

2 1

Fwd: [drupal.org] How to add co-mainteners?
by Boris Mann 07 Feb '07

07 Feb '07

I *think* we can go forward with Kevin as main maintainer of 5--2-0 and Allie/Steve as maintainers of 5--1-0. Who wants main ownership of the TinyMCE project? ---------- Forwarded message ---------- From: Drupal Indonesia <support(a)drupal-id.com> Date: Feb 6, 2007 10:45 PM Subject: How to switch the Maintener? To: Boris Mann <boris(a)bryght.com> Borris Mann, I would like to switch my right as Main Maintener to other, and I just a co-maintener. How to do it? Regards, Jonathan. ---------- Forwarded message ---------- From: Drupal Indonesia <support(a)drupal-id.com> Date: Feb 6, 2007 10:09 PM Subject: Re: [drupal.org] How to add co-mainteners? To: Boris Mann <boris(a)bryght.com> > Yes, cvs access is co-maintainers. You've now added a ton of them, > without communicating about direction. what direction need to comminucate? and how? > Does that make sense? Since we had no response from you, we had to > start another project... > FYI, 12 Jan 2007: Heini reports that my email broken 18 Jan 2007: I give respond 30 Jan 2007: Heini and you come back and report that email still error 7 Feb 2007: I have fixed the email problem. On 30 Jan 2007 I still receive email from other company like CodeGear, that's why I didn't think that I have email problem. What exactly happen is the MX Records point to my other email server. But... clever Kevin directly contact me via website and I see the problem. Thanks Kevin! > There are many folks that need the 4.7 functionality brought to 5. > Ideally, you could move your codebase to DRUPAL-5--2-0 and we could > maintain the extension of the existing base at DRUPAL-5--1-0. > I am not familiar with CVS. I am using Tortoise-CVS. Could you tell me how to create DRUPAL-5--2-0 ? Regards, Jonathan. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com

1 0

The array argument in hook_user: can we get rid of it?
by Nedjo Rogers 06 Feb '07

06 Feb '07

Unlike our other object hooks (e.g., hook_nodeapi, hook_taxonomy), hook_user passes two arguments by reference. Both are representations of the user object, one in array and the other in object format. There's a lot of interest in streamlining our object handling. I've been working on a set of generalized object handling methods that build on our current ones in http://drupal.org/node/113435. As I dig into this, I'm finding that hook_user's difference from our other hooks is one of the main barriers. Maintaining this double pass by reference would force all other object types to do the same, even though they don't have data they need to pass. Hence my question: can we change hook_user to behave like the other object hooks, passing a single argument (the user object) by reference? Pitfalls? Looking at the implementations in user.module, this double passing looks to be mainly a matter of convenience--separating out what are parameters to match (user_load()) or extended user attributes (user_save()) from the base user object. My hunch is, if they're user data they're user data as far as hook implementations are concerned, so it shouldn't matter much if they're passed in a single object. But maybe this is wishful thinking. I'm thinking a patch to change hook_user to pass a single argument by preference may be a necessary prior patch to getting a generalized set of methods in. Thoughts?

4 3

special filter behavior for teaser
by Dave Cohen 06 Feb '07

06 Feb '07

I have a client using img_assist to add inline images. They want thumbnails of images to appear in teaser views, and larger images to appear when the entire node body is shown. Others have requested the same sort of thing here: http://drupal.org/node/107801. I was hoping to accomplish this by hacking the img_assist filter to change its behavior when a teaser is being generated as opposed to a full body. But this information (whether a teaser is being generated or not) is not available in hook_filter. Is there any way for me to accomplish this? I cannot think of a clean way so I wonder, should more parameters be passed to the check_markup and hook_filter functions? Apologies if this is a FAQ, and thanks for any advice, -Dave

4 5

Reduce number of DB hits in bootstrap
by Earnie Boyd 06 Feb '07

06 Feb '07

http://drupal.org/node/116488 Comments appreciated. Earnie

2 1

workflow.module not setting actions properly
by [K2] 06 Feb '07

06 Feb '07

Hi, I have Drupal 5.1 and was trying to setup the actions and workflow to have a "flow of submitted stories edited before publishing" feature. However, with the latest actions and workflow modules in place, I can't get the actions setup for different states of a work flow. Any action which I add, ends up with the first state. If I apply more than one, they are preprended (above) to present actions. What can I do to get this thing sorted out? Thanks, KS. PS: Is this the right mailing list to post to or should this be sent to support mailing list?

3 2

settings.php broken after last commit
by Tadej Baša 05 Feb '07

05 Feb '07

In case you don't know this already (it's been in CVS for 5 days now), after the last commit to settings.php the installer doesn't work anymore. line 93 reads $db_url = 'mysql://drupal:drupal@localhost/drupal'; instead of $db_url = 'mysql://username:password@localhost/databasename'; -- Tadej

1 0

Is there any drupal module for creating Multisite configuration?
by Pushparajan V 05 Feb '07

05 Feb '07

Hi all, Is there any drupal module for creating multisite configuration ? I tried provisionator. It is not that maintained and not working in my environment. Is there any other module which can do the job? Thanks, Pushparajan V. -- Pushparajan V http://www.vprajan.org - - - - - - - - if(others(love)>=life) { noends=true; lifetime=others(love).length(); } - - - - - - - -

5 4

CVS branch work best practices?
by Bèr Kessels 05 Feb '07

05 Feb '07

Hello, I've recently started using the "new" CVS ways on Drupal.org but ran into some difficulties. I am not sure if I simply don't understand it, or if I expect too much from the 'tools'. Here is the case: Foo module has the following tree | |--- DRUPAL-4-7 |--- DRUPAL-5 | |- tag DRUPAL-5--1-0 | | lots of hard work and patches applied | |- tag DRUPAL-5--2-0 | HEAD. What one would expect (or at least, what the CVS handbooks tell me to expect) is that HEAD is always the latest-greatest-thingy. So it should include all the cool stuff that was added during the 'lots of hard work and patches applied' phase. Yet with the curent practice it is not, or seems to me, not to be. In order to let it be that latest-greatest, I *seem to* have to apply all patches twice, at least, I could not find any way to make this easier then by copy-pasting files, changes and patches around. I seem to have to syncronise the changes made during 'lots of hard work' every single time. This is quite a lot of work. And I feel it as a waste of time when the 'tools' I use require me to 'waste' time that i could have spent on development. Is there some way, I missed, or misunderstood, or whatever, that allows this process to work without lots of extra work? Is it just me who wants HEAD to be he latest-greatest? Bèr NB: I asked the same question on Drupal's IRC channel, yet people tought I was whining, or complaining; I've tried to rephrase it in this mail, it is just a concern of me, and a question for others about how I (and others, facing the same issues) can drive up my productivity. It is by no means meant as critique on the new release system. It is simply a question for us all to improve the way we use our "tools" :) -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl

16 35

Intro + sql abstraction
by Philippe Jadin 05 Feb '07

05 Feb '07

Hello, I hope this is the right mailing list to introduce myself as a "willing to be" contributor. I'm new to Drupal, but not to the world of content management. I wrote quite a few systems, the latest is available on http://www.thinkedit.org (this is the result of 2 years of work). It has some features in common with Drupal (node system, custom content types, trees, etc...) but we lack a community (the goal was to create one when I decided to opensource it a year ago) and community building features. Two weeks ago, I started to wonder if I wasn't reinventing the wheel (it's never too late isn't it ?), and when I looked again at Drupal, it was clear that something special is happening here :-) So, I hope I'll be able to contribute to Drupal and maybe contribute a few module/ideas. I will try to avoid "why don't you do it like this?" posts. Looking at recent discussions, like how to abstract the sql used to create tables in the install/update system, here's how we do it (not that it's the best way, but it works with a minimal amount of code) This is for example the default sql table definition file : http://svn.berlios.de/wsvn/thinkedit/trunk/config/tables-dist.php?op=file&r… >From this, we can install and upgrade the database at any time : the installer checks if a table is missing, and adds the required fields. (it is not possible to delete fields by design, to avoid trouble). If this file is updated, when you run the installer again, the corresponding fields are added. This way, you can use versioning on this file and thus on your sql schema (sql schema migration is a pita). The "create table" and "alter table" are created on the fly, by comparing the existing database and the requested schema. We can also build forms on the fly with validation, scaffolding (there is an "active record" object) Nothing new under the sun, but using data oriented programming seemed powerful. Using php arrays to store this is very straightforward and can be directly used by the language. I hope to bring some of those ideas to Drupal (if they are not yet there, which seems unlikely) My 0.02, as an intro :-) Philippe Jadin

1 0