Drupal 7.x

My limited understanding of Drupal is that while multiple revisions of a node can be saved, only one can be published at any given time. The problem I need to solve is how to give my site's users the ability to view arbitrary versions of a particular node based on a time value.

E.g., assume node 123 was originally published on January 1, 2012. Further assume that node was revised on February 1, 2012. I need for a request to:

example.com/node/123/2012-01-15

to return the original version of node 123, while a request to:

example.com/node/123/2012-02-15

In my ongoing evaluation of Drupal7 as a solution for our needs, I've come to the matter of distributed workflow, staging & backup.

We're wading through a number of threads discussing the issues.

So far, I've found far more unanswered questions and frustration with the current state of affairs, than testimony to & evidence of solutions that end users are satisfied with.

A large part of this confusion seems to arise from the lack of a clear definition of the problem & requirements. Or, perhaps more appropriately, a consistent one ...

For our use, we target 4 site stages,

1 live production, offiste, in the cloud
1 staging for pre-production QA, onsite
1 master development for pre-staging testing, onsite
numerous individual development sites, @ desktop & roaming

We require the ability to sync the code, data, and code across these sites.

In particular, we need to provide our developers the ability to rebase their local environments to closely sync to current live production config, data & content.

Their individual, distributed development contributions need to be managed in appropriate version control, with full push-forward, roll-back capbility.

Master development must have the ability to integrate those distributed contributions in prep for eventual push to staging and production.

On an existing site, I can access pages WITHOUT the word "admin" in the url path:

I have a form that has two text fields that for most users will be filled identically- let's call them 'foo' and 'bar'. So when a user fills out 'foo', I want 'bar' to be automatically filled with the same value.

I am attempting to create a newsletter in my Drupal 7 setup using simplenews. The newsletter content type contains a select field that allows the user to choose from a list of event editions (October 2011, September 2011, etc). I want their selection to be passed to the ViewField and filter the content to display only Events of the chosen edition. Is this possible? Thank You!

I am trying to update a value during the validate phase of a node-form, i.e. if the custom validation error is fired, just empty one of the fields.

for the last 60 hours I am trying to make sense of the drupal api, but I am giving up. I just do not seem to get the idea what the different values mean.

the function is: form_set_value($element, $value, &$form_state)

now i understand that the last value is simply the $form_state, that I am having through the validate function. but what about $element and $value?

I was trying a lot and apparently the desired value resides in $form['field_name']['und'][0]['value']['#value'] and only there.

but when I am trying form_set_value($form['field_name']['und'][0]['value']['#value'],'foo',$form_state) it raises

Recoverable fatal error: Argument 2 passed to drupal_array_set_nested_value() must be an array, string given, called in /includes/form.inc on line 2436 and defined in drupal_array_set_nested_value()

and when I am trying:

$newvalue = $form['field_name']['und'][0]['value'];
$newvalue['#value']='foo';
form_set_value($form['field_name']['und'][0]['value'],$newvalue,$form_state);

it raises:

Warning: mb_strlen() expects parameter 1 to be string, array given in drupal_strlen()

Thanks for any help!

P.S. my function currently looks as this: