User login

Drupal Development

Merging forms for usability: creating nodereference or organic groups nodes within a node

UPDATE: Agaric did manage to do this. The working code is in our custom wsf_action module used on wsf2008.net. Some related notes are as follows:

Storing lots of little pieces of data for a module: best practices? Interim practices?

How to store a bunch of little variables?

Location.module does it this way, a separate, dynamically produced variable for every field and node type. The value is either 0 (don't display), 1 (display), or 2 (required)

      $workflow_setting = variable_get('location_'. $field_name .'_'. $node->type, $field_name == 'country' ? 1 : 0);

Cool looking countdown block

drupal theme countdown block

drupal graphical countdown

drupal text to graphic

drupal clock

Present an Action

Resolution

action_group_node_form data dump

action group node form before setting the weight down

so form data added by translation modules wouldn't be there

Form ID: action_group_node_form

Array
(
[#id] => node-form
[nid] => Array
(
[#type] => value
[#value] =>
)

[vid] => Array
(
[#type] => value
[#value] =>
)

[uid] => Array
(
[#type] => value
[#value] => 1
)

Language and translation miscellaneous notes

(not useful ultimately)
getting the language flags to show node to node translations
http://drupal.org/node/65182#comment-131795

Absolute Priorities

Just posting this for hysterical posterity... this is the task list that sunk our deadlines:

Dear Ben, Dan,

I have been in Rome all day and came back home late.
I went on the site and was surprised to find that our main priorities are still very behind.

So, to be clear, I am listing them again and would like an answer for each:

1- creation of country "portals" accessible from the home page with country button or other method.
They should be as described in the first powerpoint we sent you, with a map, list of actions, etc.

Drupal forms: don't forget your tree

    $form['place_taxonomy']['#tree'] = TRUE;  // this was so important and so easy to overlook

Community tagging solutions for Drupal, a comparision

From Gábor Hojtsy:

if you need real folksonomy support (per user tagging, editing of own tags, personal tag clouds but still powering a common tag set), you need to look into a contributed module. Interestingly there are two similar solutions for the problem: the community_tags module and the taxonomy_user module. Since I need this functionality for a project, I needed to look at them, so here is a rundown of the differences I see from looking at their implementation.

Syndicate content