website

working on understanding xtemplate and tools like quanta. the background
image was adequate but needed(s) to be lightened, certainly the green
squares.

remember now that i've seen the xtemplate.inc that this is based on a
generic php templating engine. understanding that should help. see
xtemplate at sourceforge. it draws it's ideas from another template engine
called quicktempalte.

the basic approach seems to have a temptlate html layout that contains
variable names that are then defined with content.

seems to go like this. each object type on the page has a name, eg. node.

http://www.htmlgoodies.com/beyond/cssbg.html

Background images on webpages are easy to deal with.

http://drupal.org/book/print/274

how to do multiple sites in drupal, also good for clean site nameing. just
name the config file with your site name, eg: http://mysite.org/subir
would have the config file includes/mysite.org.subdir.php

[textile]

Just a test to see what's really in the node if textile filtering is in place

there was a stray = in the conditional check of user_access() that was
returning very inconsistent results for the role permissions query or
skipping it entirely. taking this out has fixed all the posting issues.
they question is: how did it sneak in?

testing

testing

it seems that when mailhandler rejects a post it just drops the message in
the bit bucket. it should at least have an option to put the content in
the approval queue for manual accept/reject.

and example of the rejection comes if you post a blog with some command
headers but don't include the type: blog header. while this should be
optional it's ommission causes the blog to be rejected with permission
denied error.

Seems there was a bug in the blogapi.module. It was testing for the old(?) permission "maintain personal blog" which now seems to be "edit own blog". Whatever, that was the magic string that let's me in.

this desktop blogging is nice. I can see how it would be addictive. pretty much what I was looking for.

The site has been upgraded to the 4.4.0 version of Drupal. This was a fairly painless upgrade. This release has lots of nice little improvements that make navigating the site easier. It also promises some updated module support to offer features we've been wanting to see. Keep your eyes open.

This was a fiarly painless upgrade. All content should be as it was before. The biggest problem to deal with were in the most heavily modified area of the the drupal code: the theme. The new xtemplate them was a little bit troublesome to migrate to since we had just hacked away at the old one. Nonetheless, we've got our atlab template in place and should be able to proceed nicely. You shouldn't notice but the some slight visual differences, which stem mainly from my unfamiliarity with CSS (and my unwillingness to change that). ;)