search for: timocratic

Displaying 5 results from an estimated 5 matches for "timocratic".

Did you mean: democratic
2008 Jan 30
2
Testing a call to super
Did any further discussion ever come of this? I take it is officially not supported currently? I just get an odd error when I try it (it throws a "0 expected 1 received", no matter what stubbing/expectation combo I use), so came looking around on google, and finally the mailinglist. Here''s my stripped down example: http://pastie.caboo.se/145603 (it fails with expects too)
2007 Jul 22
2
500 error while trying to run Camping on Dreamhost
I''ve tried setting up an Hello World app with Rails (no database), on a Dreamhost account. I used the configuration I found here http://www.mail-archive.com/camping-list at rubyforge.org/msg00114.html with the proper paths. But I keep getting Internal Server Errors (500). On the error.log I found this [Sun Jul 22 15:32:07 2007] [error] [client 82.154.48.138] FastCGI: comm with (dynamic)
2007 Jul 07
0
logging errors
Looking over the ServerError code there is no built in way to tell camping to log its errors is there? I suppose the answer it to instantiate a logger, inherit ServerError, call super and pass the return into the logger? If we using fcgi on production, does the ServerError get called, or only the server_error in fcgi.rb? Mainly I''m wondering if there is just one place I can handle
2007 Mar 24
0
Stability and usability of SuperRedCloth - particularly break handling
I was just wondering if I should upgrade to using SRC, as it sounds like it is going to be what becomes RedCloth 4. Reading the wiki and the announcements it''s supposedly under very active development, nearing release, and the breaking options are next on the list. Since there hadn''t been an update in a little while, I was curious where it stands now. The break handling in
2007 Mar 15
2
simply_helpful's form_for not respecting default_url_options (only_path)
Looking over the discussions and Trac tickets am I correct in assuming that the simply_helpful''s form_for not respecting the default_url_options (specifically only_path) is a side-effect of some other default behavior choices? Personally, I set only_path to true as my default as I think except were you are dealing with https it makes life much easier (especially in testing) and is just