Nabble - Drupal - Dev

Re: Doing hook_update_N() when module is installed

2009-11-23T13:42:01Z

On Fri, 13 Nov 2009 Randy Fay wrote:

> Thanks for your comments on this!
>

You're welcome. Let me apologize for being late in responding. Other
duties kept me off list for quite a while.

> While you're right that the original intent of hook_install() is to do a *
> schema* setup and the original intent of hook_update_N() it to update that
> when change occur down the line, they are both actually and widely used to
> set up the Drupal configuration in non-schema ways so that it's ready for
> the module. You yourself mentioned in a later message a variable_set()
> which is a configuration change, not a schema change.
>

I do understand that hook_install and hook_update_N have been misused
to help a package maintain sanity. It is that misuse that needs to be
addressed by providing either updated documentation for hook_install
and hook_update_N to allow for the unintended use or to provide
instruction for how to control the variable default values of a
package during install and upgrade phases.

> I *think* that the reality is that these two functions are often used in a
> variety of ways to make sure configuration is correct for the current
> version of the module, not just in terms of schema.
>

Yes, I agree that they have been used this way but shouldn't be.
Perhaps a specialized menu callback that is created during the install
or update phases that can is then executed on first use and removed
from then removed from the router table is what is needed for this.
Only the install or update phase would create the menu callback within
the menu router table.

> You mention the idea of setting up something for cron to do... but that
> would be a privately implemented hook_update_N, woudn't it?
>

No, a variable can be reset outside of the install/update phase so
that it can be executed manually if desired. In D7 hook_update_N will
only be allowed to be executed once.

> In my case, which is a bit extreme, I'm writing a module whose only job is
> to do one-off configuration changes to staging*.drupal.org. There are 10 of
> these machines, and their configuration is slightly different from
> Drupal.org, but they are occasionally reinstalled with D.o's database. That
> means that the install needs to work to set the config correctly, and also
> that when a config change is introduced, hook_update_N (or a similar
> technique) needs to take care of it. We're trying to avoid reconfiguring
> everywhere.
>

The thing I dislike about this is you are requiring a installation of
an update to your module just to make a configuration change. If
instead you put the changes in a INI file type and create a hook_cron
(or even a hook_init if the code doesn't take very long) to check for
a new file date you can make the configuration changes without
shutting down the site for update.php.

> As others have mentioned, this pattern is quite common.
>

INI files are for configuration. It makes sense to use what is
already available for configurations and PHP can read them for you to
the point that it returns an associative array of values. You can
even have a hierarchical tree array.

> A valuable discussion. I'm interested in hearing more.
>

Yes, I agree and I would like to hear more as well.

--
Earnie
-- http://r-feed.com/ -- http://for-my-kids.com/
-- http://www.4offer.biz/ -- http://give-me-an-offer.com/

Re: creating a new usermanagement things

2009-11-23T11:24:10Z

May be you should have a look at CiviCRM: http://www.civicrm.org

Joop

-----Oorspronkelijk bericht-----
Van: development-bounces@... [mailto:development-bounces@...]
Namens Kees Scherpenhuijzen
Verzonden: maandag 23 november 2009 18:29
Aan: development@...
Onderwerp: [development] creating a new usermanagement things

Hey all,

When using drupal for a site where users can register themself for a
event; what is the best way to store the data when you have different
modules to manipulate them?
By manipulating i mean:
- Managing some fields like if the person have payed.
- Managing multiple users to assign them to groups
- Just show lists of users
- Printing lists of each user data

I'm right now looking a the module profile which is provided by drupal
it self. but is see it is data stored in a separate table. Is it then
the best way to create code which uses the "API" from profile? Is
there anyone who has more experience with this?

TIA,
--
Kees

Re: Creative querying

2009-11-23T10:24:10Z

On Mon, Nov 23, 2009 at 8:51 AM, Brian Vuyk <brian@...> wrote:

> Jeff Greenberg wrote:
>
> Brian Vuyk wrote:
>
> 1.) We are including extra data from the users table (wasn't central to the
> question, so I omitted it to simplify)
> 2.) How would you structure this exactly with subquery?
>
> Create a second table where the role id's have a weight for their capability
> level
>
> Ah, right, I get it now!

There's a module for that - http://drupal.org/project/role_weights

#rule35

Cheers,
Greg

--
Greg Knaddison | 303-800-5623 | http://growingventuresolutions.com
Mastering Drupal - http://www.masteringdrupal.com

Re: creating a new usermanagement things

2009-11-23T09:58:33Z

On 2009-11-23, at 12:29 PM, Kees Scherpenhuijzen wrote:

> Hey all,
>
> When using drupal for a site where users can register themself for a
> event; what is the best way to store the data when you have different
> modules to manipulate them?

It sounds like you need to investigate some contrib modules - much of this doesn't require coding at all. Look up CCK, Views, Content Profile, Organic Groups at the least.

I would suggest not using the core Profile module unless your requirements are very simple. Using CCK fields is far more flexible.

--Andrew

smime.p7s (3K) Download Attachment

creating a new usermanagement things

2009-11-23T09:29:26Z

Hey all,

When using drupal for a site where users can register themself for a
event; what is the best way to store the data when you have different
modules to manipulate them?
By manipulating i mean:
- Managing some fields like if the person have payed.
- Managing multiple users to assign them to groups
- Just show lists of users
- Printing lists of each user data

I'm right now looking a the module profile which is provided by drupal
it self. but is see it is data stored in a separate table. Is it then
the best way to create code which uses the "API" from profile? Is
there anyone who has more experience with this?

TIA,
--
Kees

Re: Creative querying

2009-11-23T08:12:50Z

Also be aware that, at least on MySQL, subqueries in a WHERE clause get
executed for every otherwise-matching record. Depending on your dataset
that could eat up a lot of time. Subqueries in a SELECT or FROM clause
are only executed once, so those are fine.

With a proper join against a weighting table, though, the subquery
shouldn't even be necessary.

--Larry Garfield

Ken Winters wrote:

> select * from users where uid in (select uid from users_roles where rid
> in (4,5,6,7,8));
>
> Note that I dropped the rid column from the results, but your query
> didn't provide all that useful results for it to start with (picked
> one). If you actually need it then you may still need a join, and also
> might need something like group_concat.
>
> - Ken Winters
>
> On Nov 23, 2009, at 10:41 AM, Brian Vuyk wrote:
>
>> 1.) We are including extra data from the users table (wasn't central
>> to the question, so I omitted it to simplify)
>> 2.) How would you structure this exactly with subquery?
>>
>> Brian
>>
>> Ken Winters wrote:
>>> On Nov 23, 2009, at 10:18 AM, Brian Vuyk wrote:
>>>>
>>>> SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN
>>>> {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid =
>>>> 5 OR rid = 7 OR rid = 4 GROUP BY uid;
>>>>
>>>> Brian
>>>
>>> 1) Why are you doing a join when all the info you are selecting is in
>>> the users_roles table? If you don't need it for some other reason,
>>> problem solved.
>>> 2) I've found it's generally better to use subqueries (where X in
>>> (select Y from Z)) rather than join and group.
>>>
>>> - Ken Winters
>>
>

Re: Creative querying

2009-11-23T07:54:09Z

select * from users where uid in (select uid from users_roles where rid in (4,5,6,7,8));

Note that I dropped the rid column from the results, but your query didn't provide all that useful results for it to start with (picked one). If you actually need it then you may still need a join, and also might need something like group_concat.

- Ken Winters

On Nov 23, 2009, at 10:41 AM, Brian Vuyk wrote:

1.) We are including extra data from the users table (wasn't central to the question, so I omitted it to simplify)
2.) How would you structure this exactly with subquery?

Brian

Ken Winters wrote:

On Nov 23, 2009, at 10:18 AM, Brian Vuyk wrote:

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid = 4 GROUP BY uid;

Brian

1) Why are you doing a join when all the info you are selecting is in the users_roles table? If you don't need it for some other reason, problem solved.

2) I've found it's generally better to use subqueries (where X in (select Y from Z)) rather than join and group.

- Ken Winters

Re: Creative querying

2009-11-23T07:51:54Z

Jeff Greenberg wrote:

Brian Vuyk wrote:

1.) We are including extra data from the users table (wasn't central to the question, so I omitted it to simplify)
2.) How would you structure this exactly with subquery?

Create a second table where the role id's have a weight for their capability level

Ah, right, I get it now!

Re: Creative querying

2009-11-23T07:48:58Z

Brian Vuyk wrote:

1.) We are including extra data from the users table (wasn't central to the question, so I omitted it to simplify)
2.) How would you structure this exactly with subquery?

Create a second table where the role id's have a weight for their capability level

Re: Creative querying

2009-11-23T07:46:52Z

PS: Please do standard SQL (in previous post, mine was, I think).

Re PS: Do not rely on MySQL performance, they are sometime even better
when you disable MySQL internal optimizer :D

This was a FLAAAAAAAAAAAAAAAAAAAAAAME,
Pierre.

Re: Creative querying

2009-11-23T07:41:06Z

1.) We are including extra data from the users table (wasn't central to the question, so I omitted it to simplify)
2.) How would you structure this exactly with subquery?

Brian

Ken Winters wrote:

On Nov 23, 2009, at 10:18 AM, Brian Vuyk wrote:

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid = 4 GROUP BY uid;

Brian

1) Why are you doing a join when all the info you are selecting is in the users_roles table? If you don't need it for some other reason, problem solved.

2) I've found it's generally better to use subqueries (where X in (select Y from Z)) rather than join and group.

- Ken Winters

Re: Creative querying

2009-11-23T07:39:29Z

On Mon, 2009-11-23 at 10:18 -0500, Brian Vuyk wrote:
> SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur
> ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid
> = 4 GROUP BY uid;

If the order is an arbitrary order, you'll have somewhere to create a
new table, containing rid and an order column, then join it with rid in
your request, and finally order with the order field.

SELECT DISTINCT(u.uid), ynst.rid FROM {users}
JOIN {users_roles} ur ON ur.uid = u.uid
JOIN {you_new_shiny_table} ynst ON nst.rid = ur.rid
ORDER BY ynst.order DESC
GROUP BY u.uid

If this does not works (I did not tested it, I think the GROUP BY clause
will override the ORDER BY one, maybe with more than one ON clause it
may work) try a subquery in the result clause:

SELECT DISTINCT(u.uid), (SELECT ynst.rid
FROM {you_new_shiny_table} ynst
WHERE r.rid = ur.rid
ORDER BY ynst.order DESC
LIMIT 1
) AS rid
FROM {users}
JOIN {users_roles} ur ON ur.uid = u.uid
GROUP BY u.uid

Note: you can even easily create somewhere a form to order your roles
(or altering the existing one) to add a dragtable to order them.

Pierre.

Re: Creative querying

2009-11-23T07:38:22Z

Yep, that will do it too.

Thanks for the suggestion!

nan wich wrote:

Brian Vuyk wrote:

> SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid = 4 GROUP BY uid;

You might find something like this easier to maintain (think about an array, which could also map the levels):

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid IN (6, 8, 5, 7, 4) GROUP BY uid;

Nancy E. Wichmann, PMP

Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

Re: Creative querying

2009-11-23T07:37:06Z

On Nov 23, 2009, at 10:18 AM, Brian Vuyk wrote:

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid = 4 GROUP BY uid;

Brian

1) Why are you doing a join when all the info you are selecting is in the users_roles table? If you don't need it for some other reason, problem solved.

2) I've found it's generally better to use subqueries (where X in (select Y from Z)) rather than join and group.

- Ken Winters

Re: Creative querying

2009-11-23T07:31:51Z

Brian Vuyk wrote:

> SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid = 4 GROUP BY uid;

You might find something like this easier to maintain (think about an array, which could also map the levels):

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur ON ur.uid = u.uid WHERE rid IN (6, 8, 5, 7, 4) GROUP BY uid;

Nancy E. Wichmann, PMP

Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

Creative querying

2009-11-23T07:18:48Z

Hello all.

I am trying to write a MySQL query for users and roles, and could use a
little help along.

Basically, I need to compile a list of users who have certain roles. On
this site, users can have 4-5 roles which represent ascending privilege
levels, and we need to find the highest privilege level a user can get.

The problem is, the highest privilege level in terms of functionality
isn't the highest numerically by role id.

In essence, as output, I am trying to get results that show a user id in
one column, and rid 6 if they have it, otherwise rid 8, otherwise rid 5,
otherwise 7, otherwise 4.

Edit:

As I was typing this, I thought of another thing to try, and it seems to
have worked:

SELECT DISTINCT u.uid, ur.rid FROM {users} u RIGHT JOIN {users_roles} ur
ON ur.uid = u.uid WHERE rid = 6 OR rid = 8 OR rid = 5 OR rid = 7 OR rid
= 4 GROUP BY uid;

This depends on MySQL's query evaluation to stop on the first match from
the OR'd conditions that apply. Without the GROUP BY condition, this
still returns a list of all uid / rid combinations...

Since this email was already written, I thought I would send it along
with the solution I have both so that:

1. If anyone else is trying to do something similar, they can see what I
did.
2. It goes into the list archives for the same reason as #1.

Brian

Re: Drupal way of doing onchange

2009-11-22T16:23:04Z

Jamie Holly wrote:

> That isn't even valid - having the <div> not inside a <td> or <th>.
> That could lead to problems, but you might want to try:
>
> $("#{field_id}").parent().prev('.generalclass');
>
Yeah, it's pretty ugly...but that worked! Thanks, Jamie.

Re: Drupal way of doing onchange

2009-11-22T15:38:39Z

That isn't even valid - having the <div> not inside a <td> or <th>. That
could lead to problems, but you might want to try:

$("#{field_id}").parent().prev('.generalclass');

Like I said it might not even work considering the markup you are
showing is invalid in HTML and XHTML.

If for some reason you missed the <td></td> surrounding the div then try
this:

$("#{field_id}").parents('td').prev('.generalclass');

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

Jeff Greenberg wrote:

> Jamie Holly wrote:
>
> > $("#{field_id}").prev('label') will give you the label
> Might have worked if the label were encased in <label> tags, but it's
> really ugly...like this
>
> <tr>
> <td class="generalclass">labeltest</td>
> <div>field</div>
> </td>
> </tr>
>
> don't know why it was done that way. I tried prev("td"),
> prev("td.generalclass") and prev("tr") ... nada
>
>

Re: Drupal way of doing onchange

2009-11-22T15:28:42Z

Jamie Holly wrote:

> $("#{field_id}").prev('label') will give you the label
Might have worked if the label were encased in <label> tags, but it's
really ugly...like this

<tr>
<td class="generalclass">labeltest</td>
<div>field</div>
</td>
</tr>

don't know why it was done that way. I tried prev("td"),
prev("td.generalclass") and prev("tr") ... nada

Re: Drupal way of doing onchange

2009-11-22T15:14:43Z

Unless it is added inline with a defer then you do risk loading problems:

<script type="text/javascript">
$("#edit-cc").change(edit-cc-function);
</script>
<script src="/path/to/edit-cc-function.js"></script>

Without the defer, edit-cc-funciton will be undefined.

Even though this scenario is most likely for private use, something else
that should be considered in contrib modules as well as core (and
possibly added to the JS coding standards) is the use of event
namespaces. That way you can easily disable any bound events later on in
the code without having to rewrite the original JS. Something like:

$("#edit-cc").bind("click.myccmodule",edit-cc-function);

Now if I want to unbind that function all I got to do is:

$("#edit-cc").unbind("click.myccmodule");

Want to unbind every event that module binds to?

$("#edit-cc").unbind(".myccmodule");

It really adds a nice new layer of extensibility.

http://docs.jquery.com/Namespaced_Events

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

Scott Reynen wrote:

> On Nov 22, 2009, at 2:25 PM, Greg Holsclaw wrote:
>
> > Of course, from a JavaScript purists mindset, you should attach all
> > the
> > event handlings later, but that is a completely different topic.
>
>
> I'll bite. One might argue that inline JS violates Drupal coding
> standards:
>
> http://drupal.org/node/172169#jscodeplacement
>
> That could be read with a more narrow meaning (i.e. event function
> bindings are okay, nothing else), but is there any actual benefit to
> doing inline JS? It's not as if it's more difficult to select an
> element and apply an event handler in jQuery.
>
> $('#edit-cc').change(some_js_funtion);
>
> Doing things the "purist" (right) way seems to be both easier and
> better for modularity, so why not do it?
>
> --
> Scott Reynen
> MakeDataMakeSense.com
>
>
>
>

Re: Drupal way of doing onchange

2009-11-22T14:57:21Z

$("#{field_id}").prev('label') will give you the label

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

Jeff Greenberg wrote:

> Greg Holsclaw wrote:
>
> > A quick way to do this is to use the attributes as you mentioned. Any HTML
> > attribute can be added into the attributes array as follows:
> >
> Thanks. That's what I've done for now, until I figure out how to make
> CTools work. Frustratingly, the field has an ID, but neither the label,
> the cell they're in or the row that the cell is in have ID's. So without
> doing more work than is warranted, the field disappears but not its
> label. So when the field disappears, I replace it with a string 'Not
> applicable.'
>
>
>

Re: Drupal way of doing onchange

2009-11-22T14:34:09Z

Greg Holsclaw wrote:

> A quick way to do this is to use the attributes as you mentioned. Any HTML
> attribute can be added into the attributes array as follows:
>
Thanks. That's what I've done for now, until I figure out how to make
CTools work. Frustratingly, the field has an ID, but neither the label,
the cell they're in or the row that the cell is in have ID's. So without
doing more work than is warranted, the field disappears but not its
label. So when the field disappears, I replace it with a string 'Not
applicable.'

Re: Drupal way of doing onchange

2009-11-22T14:32:38Z

On Nov 22, 2009, at 2:25 PM, Greg Holsclaw wrote:

> Of course, from a JavaScript purists mindset, you should attach all
> the
> event handlings later, but that is a completely different topic.

I'll bite. One might argue that inline JS violates Drupal coding
standards:

http://drupal.org/node/172169#jscodeplacement

That could be read with a more narrow meaning (i.e. event function
bindings are okay, nothing else), but is there any actual benefit to
doing inline JS? It's not as if it's more difficult to select an
element and apply an event handler in jQuery.

$('#edit-cc').change(some_js_funtion);

Doing things the "purist" (right) way seems to be both easier and
better for modularity, so why not do it?

--
Scott Reynen
MakeDataMakeSense.com

Re: Drupal way of doing onchange

2009-11-22T13:59:25Z

FYI if you do the 'onChange' and have your site set to XHTML strict it
won't work. Change it to 'onchange' and you'll be fine. I see a lot of
people get caught by that one.

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

Greg Holsclaw wrote:

> A quick way to do this is to use the attributes as you mentioned. Any HTML
> attribute can be added into the attributes array as follows:
>
>
> $form['cc'] = array (
> ...
> '#attributes' => array(
> 'onChange' => "some_js_funtion();"
> ),
> ...
>
> You can include Jquery directly there instead of the function if you simply
> need to hide a div, or you can use:
>
> drupal_add_js(path_to_file);
>
> Of course, from a JavaScript purists mindset, you should attach all the
> event handlings later, but that is a completely different topic.
>
> If you have a callback to get more information from a menu callback, then
> AHAH or CTOOLs is definitely the way to go, but for simpler affects this way
> might be sufficient.
>
> Greg
>
> -----Original Message-----
> From: development-bounces@... [mailto:development-bounces@...]
> On Behalf Of Jeff Greenberg
> Sent: Sunday, November 22, 2009 10:38 AM
> To: development@...
> Subject: [development] Drupal way of doing onchange
>
> Haven't delved into AHAH yet, this might force the issue.
>
>
> Using an easy (=less typing) example. A credit card form. When the
> credit card type is selected from a select, the selection needs to fire
> a javascript function that will disable fields that don't apply to that
> card type (such as CVV).
>
>
> Normally, I would have an onchange event for the select, and noticed
> that in the form api, while there is an attribute section to add
> miscellaneous attributes, the doc doesn't mention events as examples.
> And if putting an event there is legitimate, there isn't a mention of
> how to include the responding js function in the form.
>
>
> If AHAH is the way I'm supposed to handle this, I'd appreciate being
> pointed to a good similar example, because I'm a bit unclear from the
> AHAH entries in the form reference docs, for example, how to relate the
> myhandler/js entry to a physical location of the function, and how the
> function gets there.
>
>
> Thanks!
>
>
>
>

Re: Drupal way of doing onchange

2009-11-22T13:25:11Z

A quick way to do this is to use the attributes as you mentioned. Any HTML
attribute can be added into the attributes array as follows:

$form['cc'] = array (
...
'#attributes' => array(
'onChange' => "some_js_funtion();"
),
...

You can include Jquery directly there instead of the function if you simply
need to hide a div, or you can use:

drupal_add_js(path_to_file);

Of course, from a JavaScript purists mindset, you should attach all the
event handlings later, but that is a completely different topic.

If you have a callback to get more information from a menu callback, then
AHAH or CTOOLs is definitely the way to go, but for simpler affects this way
might be sufficient.

Greg

-----Original Message-----
From: development-bounces@... [mailto:development-bounces@...]
On Behalf Of Jeff Greenberg
Sent: Sunday, November 22, 2009 10:38 AM
To: development@...
Subject: [development] Drupal way of doing onchange

Haven't delved into AHAH yet, this might force the issue.

Using an easy (=less typing) example. A credit card form. When the
credit card type is selected from a select, the selection needs to fire
a javascript function that will disable fields that don't apply to that
card type (such as CVV).

Normally, I would have an onchange event for the select, and noticed
that in the form api, while there is an attribute section to add
miscellaneous attributes, the doc doesn't mention events as examples.
And if putting an event there is legitimate, there isn't a mention of
how to include the responding js function in the form.

If AHAH is the way I'm supposed to handle this, I'd appreciate being
pointed to a good similar example, because I'm a bit unclear from the
AHAH entries in the form reference docs, for example, how to relate the
myhandler/js entry to a physical location of the function, and how the
function gets there.

Thanks!

Re: Drupal way of doing onchange

2009-11-22T13:11:07Z

Obviously doing something wrong with Ctools (latest version enabled in D6)

Here is the form field that should disappear when the option selected in
the edit-cc-type field is Other. The Ctools parameters are the last two.

$form['cc_cvv'] = array(
'#type' => 'textfield',
'#title' => t('CVV'),
'#default_value' => $_SESSION['clear_cc'] ? '' : $default_cvv,
'#attributes' => array('autocomplete' => 'off'),
'#size' => variable_get('uc_credit_amex', TRUE) ? 4 : 3,
'#maxlength' => variable_get('uc_credit_amex', TRUE) ? 4 : 3,
'#process' => array('CTools_process_dependency'),
'#dependency' => array('edit-cc-type'=>
array('Visa','Mastercard','Discover','American Express')),
);

Changing the selected option has no affect on this field.

Jeff

Re: Drupal way of doing onchange

2009-11-22T11:47:46Z

Earl Miles wrote:

>
> You wouldn't use AHAH. CTools as a tool called 'dependent' that will
> help you do this kind of behavior without having to write any javascript.
>
>
Thanks everyone. Earl, coincidentally, I started working on another
site last night, and had installed CTools and was looking forward to
trying them out. More so now!

Re: Drupal way of doing onchange

2009-11-22T11:33:36Z

Great to hear about CTools 'dependent', Earl!

Can you point us to information about it, or give us an example of how we'd use it, or point us to related code?

Thanks for all you do!

-Randy

On Sun, Nov 22, 2009 at 2:07 PM, Earl Miles <merlin@...> wrote:

Jeff Greenberg wrote:

Haven't delved into AHAH yet, this might force the issue.

Using an easy (=less typing) example. A credit card form. When the credit card type is selected from a select, the selection needs to fire a javascript function that will disable fields that don't apply to that card type (such as CVV).

Normally, I would have an onchange event for the select, and noticed that in the form api, while there is an attribute section to add miscellaneous attributes, the doc doesn't mention events as examples. And if putting an event there is legitimate, there isn't a mention of how to include the responding js function in the form.

If AHAH is the way I'm supposed to handle this, I'd appreciate being pointed to a good similar example, because I'm a bit unclear from the AHAH entries in the form reference docs, for example, how to relate the myhandler/js entry to a physical location of the function, and how the function gets there.

You wouldn't use AHAH. CTools as a tool called 'dependent' that will help you do this kind of behavior without having to write any javascript.

--
Randy Fay
Drupal Development, troubleshooting, and debugging
randy@...
+1 970.462.7450

Re: Drupal way of doing onchange

2009-11-22T11:07:41Z

Jeff Greenberg wrote:

> Haven't delved into AHAH yet, this might force the issue.
>
>
> Using an easy (=less typing) example. A credit card form. When the
> credit card type is selected from a select, the selection needs to
> fire a javascript function that will disable fields that don't apply
> to that card type (such as CVV).
>
>
> Normally, I would have an onchange event for the select, and noticed
> that in the form api, while there is an attribute section to add
> miscellaneous attributes, the doc doesn't mention events as examples.
> And if putting an event there is legitimate, there isn't a mention of
> how to include the responding js function in the form.
>
>
> If AHAH is the way I'm supposed to handle this, I'd appreciate being
> pointed to a good similar example, because I'm a bit unclear from the
> AHAH entries in the form reference docs, for example, how to relate
> the myhandler/js entry to a physical location of the function, and how
> the function gets there.
>

You wouldn't use AHAH. CTools as a tool called 'dependent' that will
help you do this kind of behavior without having to write any javascript.

Re: Drupal way of doing onchange

2009-11-22T10:53:09Z

AHAH is generally more for submitting something and changing the form,
this doesn't really sound like your example. ie. submitting a file
like in the d.o issue queue.

Generally the "Drupal way" is the jQuery way in the simple case you
described. It doesn't add javascript directly to anything html
elements and uses the jQuery event handlers in a javascipt file added
to the page. This ends in much more manageable code, less html, etc.

http://docs.jquery.com/Events/change

On Sun, Nov 22, 2009 at 12:37 PM, Jeff Greenberg <jeff@...> wrote:

> Haven't delved into AHAH yet, this might force the issue.
>
>
> Using an easy (=less typing) example. A credit card form. When the credit
> card type is selected from a select, the selection needs to fire a
> javascript function that will disable fields that don't apply to that card
> type (such as CVV).
>
>
> Normally, I would have an onchange event for the select, and noticed that in
> the form api, while there is an attribute section to add miscellaneous
> attributes, the doc doesn't mention events as examples. And if putting an
> event there is legitimate, there isn't a mention of how to include the
> responding js function in the form.
>
>
> If AHAH is the way I'm supposed to handle this, I'd appreciate being pointed
> to a good similar example, because I'm a bit unclear from the AHAH entries
> in the form reference docs, for example, how to relate the myhandler/js
> entry to a physical location of the function, and how the function gets
> there.
>
>
> Thanks!
>
>

Re: Drupal way of doing onchange

2009-11-22T10:47:14Z

As long as you don't change form elements, you can use traditional javascript/jquery. So it would be OK to hide/show or disable/enable the CVV field in your example.

If you change them (for example, by adding in a CVV field, or by changing the options in a select) then form validation will fail. That's the case where you're forced into AJAX(D7)/AHAH.

If you find you need to do AHAH, there are working examples in the Examples module (http://drupal.org/project/examples), and there is a tutorial at http://randyfay.com/ahah, which also has references to other information.

-Randy

On Sun, Nov 22, 2009 at 1:37 PM, Jeff Greenberg <jeff@...> wrote:

Haven't delved into AHAH yet, this might force the issue.

Using an easy (=less typing) example. A credit card form. When the credit card type is selected from a select, the selection needs to fire a javascript function that will disable fields that don't apply to that card type (such as CVV).

Normally, I would have an onchange event for the select, and noticed that in the form api, while there is an attribute section to add miscellaneous attributes, the doc doesn't mention events as examples. And if putting an event there is legitimate, there isn't a mention of how to include the responding js function in the form.

If AHAH is the way I'm supposed to handle this, I'd appreciate being pointed to a good similar example, because I'm a bit unclear from the AHAH entries in the form reference docs, for example, how to relate the myhandler/js entry to a physical location of the function, and how the function gets there.

Thanks!

--
Randy Fay
Drupal Development, troubleshooting, and debugging
randy@...
+1 970.462.7450

Drupal way of doing onchange

2009-11-22T10:37:56Z

Haven't delved into AHAH yet, this might force the issue.

Using an easy (=less typing) example. A credit card form. When the
credit card type is selected from a select, the selection needs to fire
a javascript function that will disable fields that don't apply to that
card type (such as CVV).

Normally, I would have an onchange event for the select, and noticed
that in the form api, while there is an attribute section to add
miscellaneous attributes, the doc doesn't mention events as examples.
And if putting an event there is legitimate, there isn't a mention of
how to include the responding js function in the form.

If AHAH is the way I'm supposed to handle this, I'd appreciate being
pointed to a good similar example, because I'm a bit unclear from the
AHAH entries in the form reference docs, for example, how to relate the
myhandler/js entry to a physical location of the function, and how the
function gets there.

Thanks!

Re: Drupal, SimpleTest and Continuous Integration

2009-11-22T09:25:25Z

Hi Yannick,

Are you using SimpleTest or Drupal's SimpleTest? I'm not sure of the
exact differences myself, but I know that they are not the same thing.

As for using continuous integration there a number of scattered
articles/resources around the place, and it seems that a lot of people
using Drupal like the Hudson CI engine (myself included).

Here are a few I can think of:
Paris presentation:
http://paris2009.drupalcon.org/session/continuous-integration-and-drupal
Getting Simpletest results into Hudson:
http://www.computerminds.co.uk/hudson-and-simpletest
http://www.lullabot.com/drupal-voices/drupal-voices-52-stew-robinson-continuous-integration-deployment-economistcom
http://www.archive.org/download/DrupalCampUK/ScalingDrupalDevelopment_512kb.mp4

Regards
Steven Jones
ComputerMinds ltd - Perfect Drupal Websites

Phone : 024 7666 7277
Mobile : 07702 131 576
Twitter : darthsteven
http://www.computerminds.co.uk

2009/11/22 Yannick Warnier <ywarnier@...>:

> Hi there,
>
> I'm the lead developer of a GPL e-learning system called Dokeos, and
> occasional contributor to the Dokeos-Drupal module [1].
>
> A few (12) months ago, we (Dokeos team) had to choose between PHPUnit
> and SimpleTest to cover our system with unit tests. As the Drupal
> community was in the same situation at that time, only a few weeks
> ahead, we decided to follow and chose SimpleTest.
>
> Unit Testing is not our final goal, and we want to implement something
> like Xinc [2] or PHPUnderControl [3] to have Continuous Integration, as
> it's called (a way to check when new code introduces regressions,
> basically).
>
> However, both seem to support better PHPUnit (I haven't tried
> PHPUnderControl, but I have broken a few teeth on SimpleTest + Phing +
> Xinc already, mainly because of conflicting versions of SimpleTest and
> complexity of the configuration files for Xinc).
>
> To get to the point, I would like to know if anybody has already
> configured that type of combination in the context of Drupal and would
> be so kind as to give me a link to some kind of report, examples or
> plain documentation about this.
>
> In any case, I will be looking at the problem myself (so far it's been
> only team members) and report here if it works, so it can be used with
> Drupal too (but the question is more like if Drupal has a few weeks in
> advance on our investigation there as well).
>
> Cheers,
>
> Yannick
>
> [1] http://drupal.org/project/Dokeos
> [2] http://code.google.com/p/xinc/ (LGPL)
> [3] http://www.phpundercontrol.org/about.html (not OSI license)
>
>

Drupal, SimpleTest and Continuous Integration

2009-11-22T09:04:04Z

Hi there,

I'm the lead developer of a GPL e-learning system called Dokeos, and
occasional contributor to the Dokeos-Drupal module [1].

A few (12) months ago, we (Dokeos team) had to choose between PHPUnit
and SimpleTest to cover our system with unit tests. As the Drupal
community was in the same situation at that time, only a few weeks
ahead, we decided to follow and chose SimpleTest.

Unit Testing is not our final goal, and we want to implement something
like Xinc [2] or PHPUnderControl [3] to have Continuous Integration, as
it's called (a way to check when new code introduces regressions,
basically).

However, both seem to support better PHPUnit (I haven't tried
PHPUnderControl, but I have broken a few teeth on SimpleTest + Phing +
Xinc already, mainly because of conflicting versions of SimpleTest and
complexity of the configuration files for Xinc).

To get to the point, I would like to know if anybody has already
configured that type of combination in the context of Drupal and would
be so kind as to give me a link to some kind of report, examples or
plain documentation about this.

In any case, I will be looking at the problem myself (so far it's been
only team members) and report here if it works, so it can be used with
Drupal too (but the question is more like if Drupal has a few weeks in
advance on our investigation there as well).

Cheers,

Yannick

[1] http://drupal.org/project/Dokeos
[2] http://code.google.com/p/xinc/ (LGPL)
[3] http://www.phpundercontrol.org/about.html (not OSI license)

Possible to create nodereference field in Form API?

2009-11-20T09:09:39Z

I'm creating a form via Forms API in a module, and I need to create a
nodereference field. Is there a way to do that, or can nodereference
only be used as part of a CCK form?

Thanks.

Steve