E-mail
This page is designed to be an index of the problems users commonly encounter when using Pylons and how they are resolved.
If you ran into any difficulties when using Pylons which you were able to resolve please add a child page below explaining the problem and its resolution.
 | Please do not use this page for reporting bugs. Suspected bugs can be discussed on the mailing list or reported via the ticket system. |
Comments (6)
Mar 03, 2007
Ben Bangert says:
This sounds like the FAQ (Frequently Asked Questions) section?This sounds like the FAQ (Frequently Asked Questions) section?
Mar 03, 2007
James Gardner says:
Well not really, I want this section for reporting obscure things that probably ...Well not really, I want this section for reporting obscure things that probably shouldn't be in the FAQ but are still worth documenting in case someone else has a similar issue. Have a look at the page I've just added, that's the type of thing I envisaged going here. What do you think?
Mar 03, 2007
Ben Bangert says:
It looks like a Question, then an Answer, and I'd imagine it might pop up somewh...It looks like a Question, then an Answer, and I'd imagine it might pop up somewhat frequently... generally all the Cookbooks we have at O'Reilly cover recipes for doing things, rather than fixing things or resolving issues.
On a side-note, if you have a style for a page that repeats, you might want to take a look at creating a Template for it so that people can ensure they're adding new pages of that style properly. I'm assuming there's a page somewhere on creating Confluence templates.
Mar 03, 2007
James Gardner says:
The thing is I don't really want to pollute the FAQ with obscure thingsbut I wou...The thing is I don't really want to pollute the FAQ with obscure thingsbut I would rather they were documented somewhere than not at all. Perhaps it needs its own space. Shall we just see how it goes for a bit and then make a decision based on what it eventually gets used for (or remove it if it isn't used)?
I'll take a look at the template, thanks for the tip.
Mar 03, 2007
Ben Bangert says:
Agreed, I've seen this kind of stuff elsewhere as a "Troubleshooting" section.Agreed, I've seen this kind of stuff elsewhere as a "Troubleshooting" section.
Mar 03, 2007
Ben Bangert says:
I'm actually now thinking that these things should be in a section at the end of...I'm actually now thinking that these things should be in a section at the end of the chapter covering it. For example, Troubleshooting issues with Paster should be at the end of the Paster chapter, along with Tips and common Pitfalls.
This way more content on the topic is brought in one spot, rather than someone reading about Paster in the book, then having to jump over to the cookbook to see Common Pitfalls and Troubleshooting of Paster (which is good to see right after you've read about Paster so you can try and head off the trouble in advance).