On Aug 10, 6:35 pm, Yorick Peterse <
yorickpete...@gmail.com> wrote:
> John,
>
> I've taken a quick look at the helper but I doubt this is the actual cause of
> the problem. The reason the helper is named UserHelper and not User is
> because the latter is a common name for models (and other general classes). I also
> think that if this were to be an actual bug in Ramaze more people would've
> reported it as the helper is quite popular as far as I can tell.
This is what I thought, but I can't argue with what I'm seeing over
here. The above line change fixed everything :-/
I sort of have the hunch that you are right, but I'd like to find out
really why so.
> Is it possible for you
> to supply a small test case that reproduces the error?
>
I think I better do that
btw is there an easy way to find out which helpers are loaded with
their respective load paths?
> About the upgrading, I personally think the safest way to upgrade Ramaze is
> to do it in a separate RVM gemset and merge it once everything is working
> again. If you're using a VCS similar to Git I also recommend doing it on a separate
> branch so you can easily revert your changes.
>
Well, there is no RVM here I'm afraid, just a server-wide Ruby
installation for all apps to use ;-(
and 'sudo gem update ramaze' doesn't seem to cut it I think.
/pagojo