[Webware-discuss] 0.8 broke my Cheetah :-(

[Michael E. <men...@ka...>]

Hi

I've been scratching my head on this bug for the last few days.

I just upgraded one system to Webware 0.8 and I use Cheetah 
extensively.  I had no problems running the same code in Webware 0.7.

Basically what I have is give custom pages based on a users login 
preferences.  To handle this I store cheetah templates in a database 
that is pulled into a session variable for the person currently logged 
in.

In my other Cheetah templates I have a line like this:

#include source=$prefs.customerTemplate

Which causes cheetah to parse and insert the template into that part of 
the HTML output.

Since moving to 0.8,  this doesn't switch between users.   If a user 
logs out, and then another user logs in, the first users template shows 
up.   It's always the first user to view the page whose template gets 
"stuck".  The only way to make this go away is to restart the server 
(i.e., it doesn't appear to time out).  I also always cause 
session.invalidate() to ensure that there aren't any old preferences 
lying around.

Anybody have any ideas before I switch back to Webware 0.7 (which I'd 
rather not do due to the large number of other bug fixes that are in)??

I'm not sure that this is actually related to CHeetah but it seems like 
it is. I was using Cheetah 0.9.15a2 and just upgraded to Cheetah 0.9.15 
final to make sure it wasn't related to the older version of Cheetah.


Any help would be appreciated.

Thanks
Mike