WSF2008

Caused by Event.module:

2048 date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead

basically i think it's saying event.module does not follow date best practices

Date thing filed for future reference.

Wasted a lot of time trying to compare the results of two drupal_set_message print array wrapped in pre tags, copied out of the browser.

Various text editors treated it as having multiple lines (around 3,000 lines, in fact) but FileMerge insisted that it was one giant line. I tried saving, again with multiple editors, to Unix line ending type. I do use Unix-style line breaks by default ("LF") but this had no effect.

Anyone have any experience/advice on this?

FileMerge uses diff, and it doesn't work in diff either.

function
file: line
arguments
warning: Invalid argument supplied for foreach() in /var/www/wsf2008/modules/contributed/devel-5.x-1.x-dev.tar/devel/devel.module on line 1033.
devel_query_table
/var/www/wsf2008/modules/contributed/devel-5.x-1.x-dev.tar/devel/devel.module: 501
,
devel_shutdown

Queries taking longer than 5 ms and queries executed more than once, are highlighted.
ms
#
where
query

Using devel and getting this error?

This, in the [#post] array of $form that resulted directly from drupal_execute, makes it look like it would be so easy to modify before final submit:

case 'validate':


drupal_set_message('

' . print_r($node, TRUE) . '

');

Differences are uid, name: zero and blank in the subform, rather than set to the current user.

A couple places on the subform that are blank, rather than zero on the standalone form: promote, sticky, og_register

Resolution

Actually, Agaric can add onto the form before submitting with this code in form_alter, action_node_form hook, to catch and stop repeats of drupal_execute.

Important differences:

The differene already noted in the #node comparison-- no node author name.

$form['#node']->name = 'Username'

And the same username difference, but in a different place:

$form['author']['name']['#default_value'] = 'Username'

blank in embedded

standalone:
$form[#action] => /eng/node/add/action-group

embedded:
$form[#action] => /eng/node/add/action

standalone (embedded subform has NO token information):

wsf_action ben$ svn commit -m "that's drupal_goto, not drupal_go_to"

wsf_action ben$ svn commit -m "drupal_goto prevents form submission... how to make redirect work????"

wsf_action ben$ svn commit -m "despite not saying so, drupal_execute does return a redirect"

Note: Elements of a subform aren't included in the list of 'this is required' if there are main form errors triggered. Furthermore, the wrong element can turn red. In this case, the Title text is red, but it's the group title (renamed Action set name) that's blank.

Title field is required.
Description field is required.
Country field is required.
Province/State field is required.
Town field is required.

Where's the Action set name required?

Well, if you leave only it out you get the error:

Drupal content type description won't change

aha:

http://drupal.org/node/112132
http://drupal.org/node/113652

it is a story type renamed to news, and the Description changed, and it somehow got stuck as this:

News stories have a title, a teaser and a body (the teaser is part of the body and can be separated by <!--break--<). News stories must belong to an action set.