Project

General

Profile

I am not able to upgrade redmine from 1.2.1 to 2.4.2

Added by Mastan Prasad Chinni about 10 years ago

I am also not able to update from 1.2.1 to 2.4.2. I have followed the steps as shown in the below link :
http://www.redmine.org/projects/redmine/wiki/RedmineUpgrade?version=53

I had followed the steps in the document.

Steps:
1> I have taken the files, mysql and sqlite backup.
2> Downloaded the Redmine 2.4.2 zip file and extracted to a folder redmine 2.4.2.
3> Copied the config/database.yml into the new config directory.
4> Copied the files directory content into new installation folder.
5> I don't have the session_store.rb file, so i had generated the file using "rake generate_session_store" command.
6> Copied the public/themes into newly created directory.
7> Executed the database upgrade command "rake db:migrate RAILS_ENV=production".
8> Executed the plugins upgrade command "rake db:migrate_plugins RAILS_ENV=production".
9> Cleared the cache and session data.
10> Restarted the application server. Restarted all the redmine services.

After that i have check the version of Adminstration/Information page, still it is showing the old version - 1.2.1 stable.
It looks, it is using old version only.

Now can you please tell, what i had missed the steps of upgrade?

Thanks in advance.


Replies (1)

RE: I am not able to upgrade redmine from 1.2.1 to 2.4.2 - Added by d s over 1 year ago

Funny to update a question about 8 years later.
As this page was found in a Google search with the criteria I was using to solve my issue, and because unanswered problems are so frustrating, here I am.

I am in no way 100% certain this will solve all similar issues, but in the official guide on Redmine upgrade as in the comments above, I've always been surprised to read instructions to create a new folder to uncompress the newer app, then work in it, but never see a point at which the Web server is "made aware" that Redmine should now work in this new folder.

The way I solved my own issue was to backup the older folder locally, and then rename the new folder to /redmine/ where the old one was.

So if after apparently following all requirements for a Redmine upgrade you still seee the older versions, make sure you have either :

1/ Overwritten the directory in which your application resides, or made a symlink between your older path (ex /apps/redmine/) and your new directory in which you did the upgrade process (ex /apps/redminev5/)

OR

2/ Updated the Virtual Host path in your Web (Apache, Nginx) server, so that the domain name if for example now served from /apps/redminev5/htdocs/ and not /apps/redmine/htdocs/ which is the older version.

I hope this helps.

Pierre.

    (1-1/1)