User login

Fragment

MacBook buying advice

and on MacBooks:

Site update order of operations

updating the big D.O:

killes
:
hunmonk: actually, make it: take down site, , clear sessions, dump db

(don't clear your own session, apparently)

Resolution

Interesting date warning to keep in mind

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.

Form munging, nothing figured out

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:

Action set organic group as passed through subform versus standalone

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

Interim almost have ability to add onto a form before post

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.

Standalone versus embedded action set (organic group) submissions

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):

Making forms redirect like they're supposed to even after complex hacking

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"

Subform limitations: errors in subform not noted or highlighted the same as main form

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:

Syndicate content