[albatross-users] Upgrade problems to albatross 1.10pre2

[Andrew McNamara]

>OK, well that gets me past that error. Now I have to deal with the 
>fact that I've apparently got a problem due to setting session vars 
>before they exist in the local name space (which is an error now, and 
>didn't used to be).

Ah - yes. I'm sure this change seemed like a good idea at the time... 8-)

I think very strange things happened later in the application's life if
you forgot to set the session var. Rather than have albatross explode
in obscure ways, we're enforcing the requirement that variables be set
before they're registered.

>Also, there is now something weird with the way the headers are being 
>written, and the headers are appearing in my web page.

The header code had to have a revamp to allow arbitary headers to be set
by the application (content encodings and things like that). Are you
able to strip the application down to the simplest form that exhibits
this problem and forward the result to me?

>Thanks for your help so far. I don't think I would have figured out 
>the path problems with the page module on my own.

Sticking debug into albatross itself is a useful technique (albatross
should have more hooks for debugging). There's nothing sacred about the
module - we intend people to mess around inside it.

-- 
Andrew McNamara, Senior Developer, Object Craft
http://www.object-craft.com.au/