Hi Jeffrey,
On 1 July 2011 00:36, jsman wrote:
> Today I tried to follow the instructions on
> http://radiantcms.org/download/
> to upgrade to the bleeding edge (1.0.0.rc2) in an existing 0.9.1
> project.
>
> On the rake db:migrate step I got the following output:
>
> $ rake --trace db:migrate
>
I've not seen this. Can you post some stats and some code to help figure it out?
Perhaps there were changes that only affect performance in a situation
like that of your site (however it is setup) and we're finding the
edge.
On Mon, Jul 4, 2011 at 11:16 AM, Johannes Fahrenkrug
wrote:
> Hi,
>
> w
Not sure if you solved this one yet or not but here's the link I used
to solve it:
http://stackoverflow.com/questions/6065015/undefined-method-name-for-systemtimerstring/6282459#6282459
Pete
Looks like a problem with rails trying to autoload a missing constant
that's already loaded. You don't mention the version of Radiant that
you're using, but the simplest fix is probably to load up the version
of Radiant that you're not using (rc 2 or .91) with a default template
and using RVM to cr
