Many admin pages are wide and overlap with the  RHS blocks so I've disabled the blobs for the admin  section.

It wasn't on before because the test failed but I guessed that the problem might be the RewriteBase so checked the root Drupal .htaccess and changed it to /drupal (where Drupal is installed).

When the site goes live we want the urls not to include /drupal. I don't know what the difficulties with that will be.

The model tag pages, e.g. Fractals, are empty but filtering by tags works fine. The blog tag pages work OK.

Could you have a look Mark?

We at Simulistics have decided  that it is high time to give Simulistics.com a make over.

I've found the recent comments list useful but replies come up in the list out of context and very short titles like "yes" and "done" don't mean much. Descriptive titles that stand on their own would make the list more useful.

The FCKeditor being used to edit settings will be a recurrent problem unless we find a way to prevent it. It is a problem because it wraps text in <p></p> tags.

The FCK editor setting allow for disabling it for certain fields or paths. Conversely it can be enabled only for certain fields or paths. Perhaps we should try the latter. I don't know whether using fields or paths would eb better.

Do we still see the preg-replace errors?

Pathauto makes urls for content pages (nodes) according to rules administrators set up. But it gave a bunch of error messages when I posted blog entry Added tagaldelic module and gave it the url http://www.simulistics.com/drupal/?q=content that is rubbish. So, I've disabled the module.

This is wanted for Tagging for blogs and Added tagaldelic module to give tag clouds.

http://drupal.org/project/tagadelic

Particularly, I'd like to use it with the Model catalogue but it should be useful anyway.

Tag cloud blocks can be assigned by roles (user groups) initially but this isn't very flexible. Showing associated  tag clouds when viewing content is desirable. (E.g. a Model tag cloud when viewing the model catalogue.) To do this we need urls that catagorise content and so need the pathauto model.