Drupal 4.7.x

I'm trying to create a node type to which the user can attach multiple images. When the user is first presented with the Submit form, I want them to see a fixed number of image input fields. See the diagram below which has three such fields. (The number of images per node would be a set on the settings page.)

When the user clicks the 'Browse...' button, the standard file selection dialog box opens. When they select a file and the dialog box closes, I would like the image to immediately be uploaded. In the diagram, 'tn' means thumbnail and this would initially be an empty graphic. After the file uploades, I'd like that to be replaced with a thumbnail derived from their uploaded image.

And, I want various information to be associated with each image. In the example, this would be the make and model of cars. I'd store this information in its own table: the image location, the description, the make, the model, etc.

I've tried to put something like this together by modifying the upload module in 4.6, but it has a few undesirable features. For one, the user has to press the 'Attach' button and that refreshes the page. Even in 4.7 with jsupload.js, they still need to press that button. And, the upload module doesn't allow the same exact image to be associated with a node twice. And, you need to add a new image one at a time. In 4.7, the upload module is also even more difficult to understand than in 4.6.

I just upgraded my drupal site from 4.6.5 to 4.7 CVS today. I am working the example tutorial listed on http://category.greenash.net.au/multiple_root_menus

I created a container and a category in the container. When I go back to edit the category, no matter what I do, when I submit, I get the following error at the top of the page (I get this error if I change nothing and hit submit):

An illegal choice has been detected. Please contact the site administrator.

I've been working on an idea.

Mission

To move my development modules into 4.7, without losing compatability with my establised 4.6 client installations.
We will not be commiting to 4.7 for a while (if ever) but the features I'm developing deserve to be forward-looking.

Problem

To even get the old modules to work in 4.7 requires a significant rewrite.
Doing so would branch the code, then make added features (developed under 4.7) harder to apply in parallal to the target 4.6 implimentations

Experimental solution - a hybrid 4.6/4.7

I'm converting my modules to 4.7 but adding the bits of the forms API that I need as a conditional library that will bring the 4.6 site up-to-date enough to be able to handle it.

anyone can help me?

Hi, I'm just wondering how hard it would be for Drupal to dynamically choose a theme based upon the browser that people are using. I mean there are a lot of themes that include advanced javascript and AJAX and stuff that don't work as well with older IE browsers and Mozilla browsers and I was just curious if there were any way for Drupal to detect this and then use a simpler less fancy theme. This might also work out well for people who are still using dial-up, such as me at the moment :(

Hi,

I'd like to have a field in my user profile: 'Position' for staff members.

Obviously I don't want any old user of the site to be able to edit this, so is it possible to set up a profile field that is publicly viewable but that only the administrators can edit?

Thanks,

James