Simulistics

themes/garland/style.css,/drupal/sites/all/modules/fcked ...

comes up as the top "page not found" in the logs. It looks as if the "," either shouldn't be there (i.e. the comma plus what follows it shouldn't be there), or isn't being recognised. This isn't impacting on the site but it would be good if we could get rid of it. I'll look into it.

Could uninstall it.

• remove permissions
• disable the module
• uninstall

Then reinstall.

I've installed the projects module along with the project issuses module. I am hoping that it will deal with the Simile issues list we have been planning to make public. We could also have a wish list.

We have also talked of distributing helpers seperately from the main Simile installation (actually we for Simile version 3). Project releases would help us handled this and each released file could have an issues and a wish list.

I've updated our Drupal instsallsation to version 5.5 from 5.3. Mark was going to upgrade to version 5.4 the but problem with the Projects module prompted me to upgrade in the hope that it would fix those problems. It didn't.

Upgrading was a simple matter of following the instuctions in the upgrade package.

Performance: caching and CS aggregation and compression enabled in  Admin.

I was finding it inconvenient to have to the Create content menu hidden inside the Content menu so I've moved it up the hierarchy.

I've created a Web site admin group to contain Simulistics web site development and general administration information and discussion.

This groups replaces the sitedev blog tag in controlling access to web site development related blog entries. Instead of having to remember to enter sitedev in an empty tag box there is now  a set of check boxes in a new Audience section.  Content may be made available to any combination of groups and made public.

We could have a Simile project and even separate projects for helpers. Users could add them too. 

Problem adding a project though, even with some text in the "Full description" field, I get an error message telling me that a description is required.

Enable users to create and manage their own 'groups'. Each group can have subscribers, and maintains a group home page where subscribers communicate amongst themselves. They do so by posting the usual node types: blog, story, page, etc. A block is shown on the group home page which facilitates these posts. The block also provides summary information about the group. (More)

Mark pointed out that the logs weren't updating. I've found out why -- logging wasn't enabled! It now is.