Drupal 7.x

I would like to create a review site where users can create an account and begin submitting their own reviews. Where I have ran into some frustration is figuring out how to control certain aspects of the process.

The product is somewhat analogous to tea - different brands, different types of tea, various assortments of ingredients/flavorings, etc.

I'm guessing there could be as much as 500 different individual blends reviewed eventually. These are broken down by maybe 20 brands, around seven ingredients/components.

I have created a content type specifically for adding reviews, and it has check boxes for the ingredients, a text field for the brand name, and as it is the person could enter the specific name of the blend in the title... but I'm not entirely satisfied with this yet...

I would prefer being able to set things up so they could work down through a hierarchy to select the individual blend starting with brand name so to the user it would look something like this:

Create a review > Choose brand > Choose individual blend

The page created from that would have the individual blend name in the title, and hopefully the ingredients and manufacturer already filled in.

The reason I want it this way is so I can have these reviews searchable and browse-able by each of those criteria.

The Project:
After several months of focusing on building our ideas and platform, we have a great plan to create a simple and intuitive environment online for are members. We are currently designing a new Drupal installation for an existing financial institution.

I just upgrade site from drupal 6.20 to Drupal7 for 5 days and found that in Google search show 3 type of url for 1 node. For example

1. gma108.com/node/24

2. ns.gma108.com/node/24

3. mail.gma108.com/node/24

all link is workable just like case with www and without www.

Does anyone found the same issue ? and what is the best way to slove this problem ?

For the time being , i just edit .htaccess to redirect url with ns and with mail to without ns and without mail but I think it may not the right solution.

Please kindly advise.

What can cause a date inside a view to display different on different servers?

I created a view with a custom content type that contains a datetime field. When I display the field in my view it looks different on different servers. Both are running the exact same versions of everything Drupal related. PHP and MySQL are very close to same versions. All the settings on the view itself are identical for this date field.

Drupal 7.0-dev
Views 7.x-3.x-dev
Date 7.x-2.x-dev

My site allows users to comment on nodes on both the standalone node page, and on custom Views featuring multiple nodes (and multiple comment forms). I want to redirect users back to whichever page they commented from after their comment is posted.

The comment module's default submit function sets $form_state['redirect'], so I need to set the redirect after that default submit handler has fired to avoid having it overwritten.

To do this, I've tried calling hook_form_alter, adding an additional custom submit function, storing the current path in a form variable, and redirecting to that variable after submit.

Here's how I've tried to implement this:

function MYTHEME_form_comment_form_alter(&$form, &$form_state, $form_id) {
	$form_state['MYTHEME_redirect'] = current_path(); // NOTE: I've also tried drupal_get_path_alias() for this
	$form['#submit'][] = 'MYTHEME_comment_form_submit';
}

function MYTHEME_comment_form_submit(&$form, &$form_state) {
	$form_state['redirect'] = $form_state['MYTHEME_redirect'];

Unfortunately, what appears to be happening is that $form_state['MYTHEME_redirect'] is somehow being set to the value of $form['#action'] (at least I think that's where it's pulling from) and the form ends up redirecting to the comment reply page (IE 'comment/reply/17').

We’ve been following what other technologies are up to recently regarding deployment and hosting. Heroku, for Ruby on Rails, is clearly an awesome platform that has surely played an important role in getting RoR a wider acceptance. Lately some other clones for different technologies have appeared and, while some of them address PHP based deployments, there’s still no specific solution that handles Drupal the “right” way.