Codeigniter version 1.0 to current - codeigniter

So my website is using Codeigniter version 1.0 - Im wondering what it would take to update it to the current version or even migrate it over to laravel ?
The website is quite large as it is a Directory however we have not launched just yet.
Thanks
Jonathon

Backup your files
Backup your database
Follow steps from the bottom to the top.

Related

Problem with migration Joomla 1.5.26 to 3.x with jUpgradePro

I need to migrate an old website witch is using Joomla 1.5 to Joomla 3.x.
I updated Joomla to 1.5.26 and I decided to buy and use tool jUpgradePro from https://matware.com.ar/subscriptions/jupgradepro-subscription.html .
I configured everything and I'm trying to start migration but there's one problem and I need Your help.
When I start using cmd of jupgradepro there's one error message after using command composer install.
Cannot update only a partial set of packages without a lock file present
What can I do with this problem, any Issue? I was trying to search something in web, but finally have to ask You for help.
One thing that I can say is that this example is a test so target domain is a subdomain (http://ernestdolowy.pl/projects/szpital/nowytest/) and source site has just empty test template, is that a problem? Joomla 3.x is well configured on subdomain.
Finally I need to migrate Joomla 3.x to Wordpress but right now I have to solve this problem.
Thank you in advance for your help :)
I got same problem, and found this solution on my local machine:
In Joomla site, xxx\administrator\components\com_jupgradepro I copied the composer.json file to composer.lock
I started composer install command from command line (in Windows, not in built-in jUpgradePro). It installed all dependencies, and in jUpgradePro command line window the check site command worked fine.
Solution:

Laravel Update 4.1.24 to 4.2

im currently working on an update from laravel 4.1.24 to 5.6 The problem is i got nearly no experience with laravel. My question is now, how do i properly upgrade. Should i first upgrade to 4.2 and then to 5.0 and so on or would it be better to upgrade directly to 5.6 and how should i do this? I mean there are so many changes that i think i could miss something.
Also the project is just in a github repository, so it's hard to check if it's still working after an upgrade because i dont got the old modules. Or would it be enough to go on laravelshift. com and just upload it there to go from 4.1 to 4.2, 4.2 to 5.0 and so on.
Best regards!
The Laravel documentation contains a whole list of breaking changes that can help you to upgrade your application to a newer version. Laravel Shift is a service that checks and updates these changes in your project.
However, there is no way of being sure that your project will still work after these upgrades. Especially if you are using external modules its very risky.
If it is not required, I would not recommend upgrading from 4.1.x to 5.6 unless you have a lot of time on your hands. A solution could be to set up a completely new 5.6 project and add the project code file by file and test the implementations.
Start from here and follow instructions to upgrade it to 4.2. Then go through your packages and update their versions accordingly. When done use dropdown list in the top-right corner to select next version (5.0) and repeat it until you are at 5.6.
You definitely need to be able to run your code and test it somehow after each step because there will be problems. From 4.1 to 5.6 is a big leap and a lot of packages might have breaking changes etc. I only migrated as far as from 5.1 to 5.6 and it took me whole day to fix everything.
As for automated upgrade you can try it as well, but as I already mentioned you need to be able to test your work because all packages need to be updated as well.

Magento upgrade from 1.5 to 1.7

I am upgrading magento version 1.5 store to magento version 1.7. Current store has more than 1000 products, more than 100 categories, more than 20 attribute sets, more than 500 customers,more than 500 orders and Database size is more than 600MB.
Above details are mentioned in order to have the idea of store size. Furthermore, I am trying it on local machine with wamp server installed.
Here are the steps involved to upgrade:
Export Current Database (Imported it in gzipped format with option "Disable foreign key checks" checked). As I was unable to export it in normal sql formate due to large size of database.
Created new database and imported the Database exported.
Downloaded fresh 1.7 stable version from magentocommerce.com
Tried to install this fresh magento 1.7 in newly created Database, in which exported database was recently imported.
Next steps were to install theme, copy extensions and copy media folders.
But when I tried to install magento 1.7, it always give me this error :
"This webpage has a redirect loop
The webpage at http://localhost/magento17/index.php/install/ has resulted in too many redirects. "
Here is the link to which I was following:
Link I followed
Note that my main focus is upgrading from 1.5 to 1.7, so much focus must be on that rather then resolving this issue if it is not the right way to do.
And If there is any better and proven way to upgrade to 1.7 from 1.5, kindly share it.
If you want to upgrade you dont need to install and move DB and theme.
Refer this link.
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/upgrading_magento
Note: If you followed best practices in Magento and didn't modify core code then upgrade should run smoothly.
Expected issues are that your Local and Community folder modules might need some fixes.

Should I upgrade Magento before changing the theme?

I have a Magento store running on 1.3.2.4 and the client wants to give the site a facelift. Would it be better to stay with the current version and just modify the current version or should I migrate to a newer version?
Additionally, is it possible to backup the existing store on ver. 1.3.2.4 and just do a fresh install of a newer version and restore?
Upgrading from 1.3.x to 1.6.x will not be as straight forward as you may think.
My suggestion is to setup a copy of your existing site, and attempt the upgrade BEFORE a redesign. Unless your client is okay with staying with the same version of Magento.
You can also create a copy of the database and upload the latest version of Magento, you'll then need to copy over your app/etc/local.xml file from your installation and modify it to use your duplicate database.
More reading:
http://www.nicksays.co.uk/2010/03/fool-proof-magento-upgrades/
http://magentoexpert.com/upgrading-magento-from-1-3-2-4-to-1-5-or-1-6/
http://www.magentocommerce.com/boards/viewthread/263068/#t355374
Would it be better to stay with the current version and just modify the current version or should I migrate to a newer version?
Modify the current version unless your client can pay you to perform the upgrade.
Additionally, is it possible to backup the existing store on ver. 1.3.2.4 and just do a fresh install of a newer version and restore?
Of course.
A bunch of stuff changed in 1.4 with regards to the layout/design system. We had to change several things to get the update right so I'd suggest you upgrade first.

Upgrading Magento from 1.1.8 to 1.5 stable

Am looking to upgrade Mangeto from version 1.1.8 to version 1.5.
This is a quite a leap I am taking I know, but and I have tried the following already (as some one else had suggested on another site):
dump v1.1.8 database, restore it in a new database.
install magento 1.5 pointing on the restored v1.1.8 database
let the upgrader run
add the old theme files
test that it all works.
When doing that, the upgrader kept saying some tables already existed.
Can anyone help me out?
Thanks
It's fine now, basically make sure you're using the same server environment.

Resources