Incomplete

Drupal needs smarter packaging scripts.

If you get a module that depends on another module, they should both be delivered to you (and so forth).

But to do this Drupal needs to know what's on your system, so you have to be initiating the transfer from within Drupal. Drush could do this fairly securely.

We need to encourage the lots of small modules approach that everyone loves from the development and extensibility side, but which the difficulty of developing, maintaining, and using can drag down.

So we had these problems (at end of post). Fairly noticable.

Deleted everything we could find that could cause it (after making a hackish custom error message setting, see blockquote here)

<pre>function wsf_action_init() {
  set_error_handler('wsf_action_backtrace_error_handler');
}

nitrospectide
:
freeMoo3: http://www.amazon.com/CSS-Missing-Manual-David-McFarland/dp/0596526873/ref=pd_bbs_sr_1/103-5784009-9672607?ie=UT...
[
3:01pm
]
nitrospectide
:

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.

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.

You spend enough time in FAPI and it speaks to you. (UPDATE: but it speaks lies.)

The beginnings of a chance to catch material from the subform and duplicate it for the main form:

this should take care of prefilling places

What hasn't worked:

Not much more to say about that... but it would be somehow more human and real to have a changing assortment of pictures representing users on a site along with their posts, rather than a single, static, unchanging mug.

I guess instead or in addition to this concept making user pictures NON-retroactive would be part of the concept-- the picture of you with your three-year-old post should be you from three years ago, not two months ago.

Resolution

Not quite...

Content Taxonomy Options 5.x-1.x-dev Defines a option widget type for content_taxonomy for selects, radios/checkboxes

Here we go:

Option Widgets 5.x-1.6-1 Defines selection, check box and radio button widgets for text and numeric fields.

That's part of core CCK (a module that comes with content.module)

Question is... can it be translated?