Drupal 4.7.x

Not sure if this is the right place to post this question but...

I am using Drupal 4.7 beta 3 and have installed the 4.7 version of flexinode.

When I try to add an image to a content type I get the following error message

Fatal error: Cannot use object of type stdClass as array in /raid/sites/www.lfshosting.co.uk/www/drupal/drupal-4.7.0-beta3/modules/flexinode/fie... on line 137

I am using PHP 5.1.

How can we create multiple nodes using a single module?

It is urgent.
Thank in advance.

The contact module allows registered users to send an email to another user. Can this be set to act as a contact page for an unregistered user to contact a registered user?

For nodes with images, I would like the thumbnail version of a specified image to appear in the teaser, but a larger (preview sized) version to be shown in the node (verbose) view.

I've ported William Pramana's fine Golden Gray Wordpress theme to Drupal 4.7 for a site I'm creating. It was a quick job so there are likely issues but it works reasonably well. It has been tested with Firefox 1.5, Opera 8.5, and IE 6 on Drupal 4.7.0-beta3 with a modicum of modules (forum, blog, image, and other core modules) enabled.

Known issues include:

Almost every table definition I've evaluated so far could be rewritten into portable code. That is, most MySQLisms I have come across are pointless and outdated - and could easily be avoided, making Drupal a much more cross-database solution than it currently is. That is, we should develop some essential database coding guidelines!

The boringly obvious point is of course to use standard SQL statements only - the MySQL and PostgreSQL documentation usually state whether a statement is compatible to standard SQL. As many people will rarely look up whether the statements they have been using for years are deprecated, here are a couple of recommendations to start with:

• do not copy&paste your table definitions from a dump, or you will end up with the particular backends' database specific view of your design, often with some obsoleted indices and columns from discarded design stages thrown in. Design is a result of planning and consideration, not a snapshot from a trial-and-error process. Rethink, reorder and rewrite your code to be concise, logical and generic...
• use standard generic data types, that is, integer rather than int(x). And choose text over varchar(y) unless you have very good reasons to use the latter
• don't force table types - "MyISAM" won't only annoy people using other databases, but also the InnoDB users...
• " and ` are not ' - portable SQL string literals are in single quotes (') only.