Porting 1.1.6 to 1.2.3


#1

In porting an application from rails 1.1.6 to 1.2.3, I discovered that
the image directory has become the images directory. But also some
other aspects of the map.image had to be changed.

Is there one central place where all these changes are listed so that I
could systematically port all aspects that are required?

Thanks


#2

The directory was always images. As for other changes I don’t know of
any listing of all the changes (you could of course browse through the
changelogs). I’ve ported a number of apps over from 1.1.x to 1.2.x
and not run into any significant changes. There were a few things
marked deprecated that I ran into like start_form_tag/end_form_tag,
but those were easy to clean up and didn’t break anything.

1.2.2 had an issue with functional tests needing strings instead of
symbols for the session hash, but 1.2.3 fixed that.


#3

On 5/5/07, Ra PM removed_email_address@domain.invalid wrote:

In porting an application from rails 1.1.6 to 1.2.3, I discovered that
the image directory has become the images directory. But also some
other aspects of the map.image had to be changed.

Is there one central place where all these changes are listed so that I
could systematically port all aspects that are required?

Each Rails lib (ActiveRecord, ActionPack, etc) has a CHANGELOG file for
this.


Rick O.
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com


#4

It would be helpful to see not just what’s being generated but also the
rhtml and any other useful bits you can contribute. It seems url_encode
is being called on the string passed as the ‘src’ attribute. By the way
h() is a shortcut for url_encode, so if you are used to writing <%=h
@image_src %> that’s your problem.

Ra PM wrote:

Well Ive made a little progress. I found that the rails version could be
set in config.rb. And so by switching between 1.1.6 and 1.2.3 I can
work out whats changing where. Laborious but reading changelogs is
worse :slight_smile:

The html generated with 1.2.3 (which is not working) is

Woodruff Avenue

The html generated with 1.1.6 (which is working) is:

Woodruff Avenue

Any clues which rails internal function is generating this? Its
something that image_tag drills down into.

Thanks


#5

Well Ive made a little progress. I found that the rails version could be
set in config.rb. And so by switching between 1.1.6 and 1.2.3 I can
work out whats changing where. Laborious but reading changelogs is
worse :slight_smile:

The html generated with 1.2.3 (which is not working) is

Woodruff Avenue

The html generated with 1.1.6 (which is working) is:

Woodruff Avenue

Any clues which rails internal function is generating this? Its
something that image_tag drills down into.

Thanks