| Converting Codeigniter 2.0.1 HELP ! |
|
I have a site that was build for my company using 2.0.1 the site is up and running but breaking down and we want to update to current version of codeigniter, I have read how to do it, replace all system files with 2.0.2 replace index.html I guess then put that we have done back on top of the code in these files? Doesnt seem to work....and are we going to have to upgrade from 2.0.1 all the way to 2.2 with every upgrade or is there an easier way?
Thanks 
Adice from me but not tested cause my old projects use old version but leave it too lazy upgrade it !
1. Just move whole your Model, Controller and View to current version dont to your Old Codiegnter. every name controller should be Start with Upper case also with model 2. You should setting manually in config
Hey Justin,
Your version of CI (2.0.1) is so old, it has dino poo on it...  .This means that installing version 3; copying your controller, model and view folders and renaming your classes filenames isn't going to cut it. You don't have to upgrade to every newer version, but if your site is using certain files you maybe have update a couple of times. You should read the following links taken from the user guide about updating: http://www.codeigniter.com/user_guide/in...=upgrading http://www.codeigniter.com/user_guide/in...=upgrading http://www.codeigniter.com/user_guide/in...=upgrading These links describe what has to be done to update to a newer version. Updating from such an old version can mean you have to move some files around or change code because of deprecated functions or what not. Good luck! -Roger
I would recommend upgrading to v2.2.4 (the latest 2.x release), first. In a development environment, you should be able to clear out your system directory and put in the files from the 2.2.4 system directory, then check to see if you need to change any of your application files (I generally just use a diff program, like Meld, or WinMerge if you're using Windows, to check the new files against my existing files, so I can keep my changes but take into account any new entries or options). You'll still have to review the upgrade instructions for every version from 2.0.1 to 2.2.4 to see what changes have to be made to your own code, but you don't have to change the system files 9+ times in the process.
Once that's working, you can upgrade to v3.0.1 following the same process. The upgrade from 2.2.4 to 3.0.1 might take more work than 2.0.1 to 2.2.4, depending on your application, which is one reason I recommend the interim 2.2.4 upgrade first. Additionally, if you get everything working under 2.2.4, you can upgrade the production site to the current (more secure) version of CI 2.x before you get started on the (potentially longer) process of upgrading to 3.0.1. |
| Welcome Guest, Not a member yet? Register Sign In |
