It took me a solid 2 days to move from 1.2.3 to 2.1.0 and I had to do
that point release by point release.
I would suggest you take on your Javascript issues head-on and only move
to newer versions as a last resort, unless, of course, you have a lot of
time to upgrade.
Wes
On 5/31/11 1:31 PM, Jeff Luckey wrote:
I have a legacy Rails app (Rails 1.2.3& Ruby 1.8.6) that uses
ActiveScaffold that has been in production for almost 5 years. Now, when
executing an insert in an AS grid, it throws javascript errors in FireFox 3
and greater and IE.
I've tried upgrading to AS 1.1.0-stable but when I do, the app won't even
present the Index page (errors out w/ Error 500).
I've read thru many postings on the AS Group& some other people have had
this issue but there doesn't seem to be satisfactory solution. In fact,
some of the threads just end w/o resolution. I gather from this situation,
that very few people are using this older, legacy environment w/ AS. Since
trying to fix the problem appears to be a dead-end, how to proceed, is now
the question.
Options:
1. Upgrade the app to Rails 2.* and use a newer, non-deprecated version of
AS.
2. Something else?
Questions:
1. Which version of Rails 2.* should I move to?
2. How much pain is associated w/ moving from Rails 1.2.3 to 2.*?
3. Other possible solutions?
TIA
--
You received this message because you are subscribed to the Google Groups
"ActiveScaffold : Ruby on Rails plugin" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/activescaffold?hl=en.
