Okay. Mea culpa on this one (sort of). I had been playing with
ActiveRecord last week, and inserted a couple of puts statements to
understand what was going on. These were still in there, and did
absolutely no harm within ActiveRecord when using it standalone.
Within Rails it''s another story--stdout is, I think, the path that the
cgi output takes.
Would it be a reasonable change to fiddle ActionPack to do some
remapping so that writing by the application (or some library) to
stdout/stderr would go (harmlessly) to a log?
I''m not sure where stderr is going--I suppose it depends, right now,
on the environment--but I think it wouldn''t be surprising to encounter
a library somewhere that uses "warn" and friends.
Just a thought,
Bob
On Sat, 4 Dec 2004 17:49:56 -0800, Bob Sidebotham
<bob.sidebotham-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> Also with the todo tutorial, scaffolding does not work fully for me.
> The actions show, list, edit, and new all work, but destroy, create,
> and update all get "Not Found" errors (with error strings like
> "`/todo/create'' not found"). It does actually seem to do
the
> action--just doesn''t redirect, i.e. it seems to be looking for a
page
> with the same name as the action, but should probably be redirecting
> to list or show.
>
> This is with rails 0.8.5 with WEBrick 1.3.1 and ruby 1.8.2.
> Out-of-the-box. No changes except to edit the config file, run the two
> scripts to create the model/controller, and add the require to the
> controller.
>
> I do remember seeing somewhere that rails was not tested with 1.8.2...
>
> Bob
>