Module development and code questions

Is this module intended to be used long term or it is a temporary fix? The download contains a patch for taxonomy.module which is rather dubious. It also only includes a .mysql but not a .pgsql file. I am hesitant to implement this module with it's new database requirements if the functionality is being considered for inclusion in the core in the future, even though it is needed now.

I am considering developing a module that regularly (using cron) checks a Drupal site (all or part) against various validation schemes such as the W3C's Markup Validation Service, CSS Validator, and Web Content Accessibility Guidelines 1.0, and the U.S. Section 508 Guidelines. The Drupal core and most of the essential modules already validate nicely against these tests, but obviously any user-submitted code would be at risk.

I have a highly formatted document which I would like to render in htmlarea as close as possible to the way it is rendered in Microsoft Word. I found that a simple cut and paste of the formatted text doesn't achieve my goal, so I figured I would go into htmlarea's "text mode" and insert straight HTML. I used Word's "Save As.. web page" to generate the HTML.

Hi.

Is it possible to have it so that when a user signs up they get a taxonomy term to themselves, that only them can post content to but anyone can view?

Like their own corner of the site.

Any help much appreciated.

Mr Maggoo

Required fields aren't marked in the quick reg form, and the UI doesn't indicate what the meaning of "required" is... I deduced that it refers to the quick reg form... not sure if it also refers to ?q=user/register.

Also, in Firefox 1.0 (but not in IE6), placing the cursor in the quick reg form (in any field) causes ?q=user/register to open in the browser. I can't imagine that's the intended behavior. Very disorienting, even though the user is conveniently tranplanted to the full registration form.

A site that I'm working on requires one 'create content' page for all file based content types. So, rather than clicking on "create content" and then selecting "image" or "upload file" there would be one option called 'upload'. Using this option, users would be able to upload 1 file of any type (i.e. any of the various image, audio, video, etc. file formats) OR 1 zip file containing any mix of these files.

I've searched around the forums and CVS repository but have yet to find modules or code that handles any of these requirements. Before I began working on this myself, I wanted to ask around and see if there is existing code to handle this or similar functionality, and if not I would appreciate feedback on the idea/best approach...

There is a subset of options/inputs that are consistent across the various modules that implement these types (image, filestore2) which is all I need/am interested in: title, n taxonomies, file upload, and description.

I would like to use as much of the existing modules/code as possible. Error handling the batch upload process might prove tricky, but I'm hoping that with minor changes to the existing modules, and little additional development, I can accomplish this project in a day or three.... I'm thinking the best (or least quickest) way to approach this is to create a new module which would present the above listed subset of options via an input form, and then based on the file that was uploaded, broker the request(s) / call the appropriate module(s) to validate and process the information/file(s)... however extending filestore2, to include the image module (or vice versa) in the additional functionality described above is an alternative approach that I'm considering (i.e. it seems logical that the filestore module should handle all files)