[Cheetahtemplate-discuss] #include source=template.tmpl problem

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

Hi,

I recently posted this to the Webware list but didn't get any responses 
so I'm checking here.

I recently upgraded to Webware 0.8 and as soon as I did the only that 
that stopped working in my current project was a cheetah template.

My site handles user preference templates that allow users to have 
custom pages displayed based on their settings.

I do this by having a line like:

#include source=$prefs.customerTemplate

which loads in a snippet of HTML template code that gets parsed by 
cheetah and displayed to the user.   In Webware 0.7 this worked fine.  
I could log in to the system as one user and his pages would look like 
he wanted to and then log out and log in as another user and the site 
would change to match his preferences.

But since upgrading to Webware 0.8, when I log in and then back out 
again, the template that gets displayed is always the initial template 
that gets shown for the first customer who logged in since the 
AppServer was started.   I hope that makes sense :-)

So what appears to be happening is that the per-user templates that are 
stored in a users preferences get cached by either Cheetah or Webware 
and then for all subsequent users they see the initial users web 
settings.

I've use in-Memory Sessions only and have modified the SessionMemory.py 
file to comment out the storeSessions() method so that sessions only 
stay in memory and never get written to disk (which is how I think it 
should be).   I've also tried switching browsers, computers and OS's so 
it's definitely occuring with the app server framework/cheetah 
framework but I have no idea where or why this would happen only upon 
upgrading to Webware 0.8.

If anyone has any pointers as to what part of the code could be the 
culprit I'd greatly appreciate it.

Michael


Michael Engelhart
http://www.eztrip.com/
Why not take it easy?