Ch3 in book: session_filter vs sessionFilter

19 views
Skip to first unread message

Magnus

unread,
Jan 10, 2006, 6:27:08 PM1/10/06
to cherrypy-docs
It might be a well-known issue, but I couldn't find any mention of it
here. Ch3 of the book describes how to use sessions. The recipe is

cherrypy.config.update({'session_filter.on' : True})

That will result in a "500 Internal Error" page because of a
SessionNotEnabledError. The line should read

cherrypy.config.update({'sessionFilter.on' : True})

With some pointers I'd be happy to provide a diff for the book...

/M

Remi Delon

unread,
Jan 11, 2006, 11:35:05 AM1/11/06
to cherry...@googlegroups.com
> It might be a well-known issue, but I couldn't find any mention of it
> here. Ch3 of the book describes how to use sessions. The recipe is
>
> cherrypy.config.update({'session_filter.on' : True})

Are you sure you're looking at the right version of the book for ?
(corresponding to the CP version that you use)

Remi.

Magnus Therning

unread,
Jan 12, 2006, 6:10:51 AM1/12/06
to cherry...@googlegroups.com

No, I wasn't. I followed a link Google gave me, so I didn't pay
attention to the 'trunk' in the URL. I should have used the 2.1.0
version.

Does this happen a lot?
I bet it's a nice thing for the authors of the book to have the trunk
published, but it is a possible cause of confusion as well.

/M

--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
mag...@therning.org
http://therning.org/magnus

Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

Some operating systems are called 'user friendly', Linux however is
'expert friendly'.

Wektor

unread,
Jan 25, 2006, 10:28:06 PM1/25/06
to cherrypy-docs

im using CP 2.1.1 and
cherrypy.config.update({'session_filter.on' : True}) -- doesnt work
cherrypy.config.update({'sessionFilter.on' : True}) -- does

i tried in CP 2.1 and its the same

i think its good idea to po point out which versions work which way
becouse its very nasty error and difficult to spot

Reply all
Reply to author
Forward
0 new messages