Wiki docs

0 views
Skip to first unread message

paron

unread,
Jul 15, 2005, 10:38:15 AM7/15/05
to cherry...@googlegroups.com
I can't find the "edit" link on these pages in the wiki, so I hope it's
not too off-topic to post here.

http://www.cherrypy.org/wiki/ConfigSystem21 says:

"This example is in the CherryPy source directory
tutorial/tutorial.conf, or on-line at
http://www.cherrypy.org/file/trunk/cherrypy/tutorial/tutorial.conf"

Neither phrase of that is true. There is no "tutorial.conf" in the
CherryPy source directory in the 2.1 beta, and the online listing
differs from the example by about three settings.

http://www.cherrypy.org/wiki/Filters21 says:

"For instance, if you want to enable EncodingFilter? (using utf-8) on
all the site and DecodingFilter? for everything under /dir1 (using
latin-1), all you have to do is put this in your config file:

[/]
encodingFilter.on = True

[/dir1]
decodingFilter.on = True
decodingFilter.encoding = "latin-1"

The "standard" filters are currently: baseurlfilter, cachefilter,
decodingfilter, encodingfilter, gzipfilter, logdebuginfofilter,
staticfilter, tidyfilter, virtualhostfilter, xmlrpcfilter"

I am confused -- does capitalization matter? Usually in python, it
does. If so, is it 'encodingFilter' like it says in the code box, or
'encodingfilter' like it says in the text? If it matters, but the
inconsistencies are needed because of the way wikis treat CamelCase,
then where can I find the correct capitalization for the xmlrpcfilter
setting ? Of course, it could be a moot point if XmlRpcFilter isn't
working in 2.1 yet!!

Robert Brewer

unread,
Jul 15, 2005, 11:31:22 AM7/15/05
to cherry...@googlegroups.com, cherryp...@googlegroups.com
paron wrote:
> I can't find the "edit" link on these pages in the wiki, so I
> hope it's not too off-topic to post here.

That's fine. We were getting too much spam on the Wiki, so anonymous
editing is disabled while we research other options. However, if you
have further comments, you should probably move them to cherrypy-users
(which I'm cc'ing).

> http://www.cherrypy.org/wiki/ConfigSystem21 says:
>
> "This example is in the CherryPy source directory
> tutorial/tutorial.conf, or on-line at
> http://www.cherrypy.org/file/trunk/cherrypy/tutorial/tutorial.conf"
>
> Neither phrase of that is true. There is no "tutorial.conf" in the
> CherryPy source directory in the 2.1 beta, and the online listing
> differs from the example by about three settings.

Thanks. I've updated that Wiki page to reflect the most recent
tutorial.conf. I'm a bit confused by your other comment, that you cannot
find "tutorial.conf". I find it present both online (at the link
provided), and in the 2.1-beta download. Perhaps "setup.py" doesn't know
about it...?

> http://www.cherrypy.org/wiki/Filters21 says:
>
> "For instance, if you want to enable EncodingFilter? (using utf-8) on
> all the site and DecodingFilter? for everything under /dir1 (using
> latin-1), all you have to do is put this in your config file:
>
> [/]
> encodingFilter.on = True
>
> [/dir1]
> decodingFilter.on = True
> decodingFilter.encoding = "latin-1"
>
> The "standard" filters are currently: baseurlfilter, cachefilter,
> decodingfilter, encodingfilter, gzipfilter, logdebuginfofilter,
> staticfilter, tidyfilter, virtualhostfilter, xmlrpcfilter"
>
> I am confused -- does capitalization matter? Usually in python, it
> does. If so, is it 'encodingFilter' like it says in the code box, or
> 'encodingfilter' like it says in the text? If it matters, but the
> inconsistencies are needed because of the way wikis treat CamelCase,
> then where can I find the correct capitalization for the xmlrpcfilter
> setting ? Of course, it could be a moot point if XmlRpcFilter isn't
> working in 2.1 yet!!

Capitalization matters; however, that capitalization is different
depending on where you are referencing the name. Within the config file,
I believe all names are camelCase with a lowercase first letter. The
XmlRpcFilter uses the config setting, "xmlRpcFilter.on".


Robert Brewer
System Architect
Amor Ministries
fuma...@amor.org
Reply all
Reply to author
Forward
0 new messages