What happens is the “new” variable starts out as a boolean. When Kid gets ahold of it to send it out on the web, it turns into a string (eg “True”). So, it comes in to CherryPy as the string “True”, which is what I check for in the screencast. (It wouldn’t work properly otherwise…)

In the written version of the “20 Minute Wiki”, I use a validator to convert the value to a real boolean.

Amusingly enough, the written tutorial says that you can “add are belong to us” if you feel you must

The written “20 Minute Wiki” includes a trivial default method so that you can go to /PageName as you would in a normal wiki. I chopped that bit out and a minor validation usage in order to avoid the 20 Minute Wiki ballooning into the 25 Minute Wiki.

Glad you enjoyed the screencast!

One thing I noticed in particular is the use of: input type=’hidden’. If you switch the URL scheme to use /pname/edit instead of /edit?pagename=pname, you can completely do away with the hidden input elements. Now, that does mean using a default method in your controller, which is probably too advanced to explain in a short tutorial. But if TG provided a base class which used the virtual path (pname), looked up the item (Page object) for you based on that ID (pname), and then dispatched based on the rest of the path (/edit -> self.edit), that would be VERY cool. That’s essentially what I do, but with CP plus Dejavu, my own ORM.