How to upgrade codeigniter from version 1.0 to recent version?
I have downloaded the recent version of codeigniter and have a sample project which is written in version 1.0. When i try to run it. I am receiving various kinds of errors for using deprecated functions.
You would have to go through http://ellislab.com/codeigniter/user-guide/installation/upgrading.html and make appropriate changes.
Alternatively, you can just battle the errors as they come up until they're all gone.
It might be easier to just re-write the thing.
Related
I upgraded to php7.4 on my dev box and am receiving a lot of deprecated errors with Propel 1.7.2. I see there is a closed thread in the support channel indicating fixes are in master, but they sure haven't made it to Propel 1.7.3 at http://propelorm.org/Propel/download.html. Does anyone know if/when the Propel folks are going to release a 1.7.x that is compatible with php74 (php 7.4)?
I wouldn't expeced to much from propel. The Project is more or less dead as of March 21.
As of their official github-page propel1 is outdated and unmaintained. See: https://github.com/propelorm/Propel
Current stable (and outdated and unmaintained) version of Propel -
Please use v2 https://github.com/propelorm/Propel2
Propel2 on the other hand is still in alpha. See: http://propelorm.org/download.html
Note: The version 2 of Propel is still under development. Please visit
http://propelorm.org/Propel/ if you want to use a stable version.
There is also Propel3. Which is not even in alpha yet. See: https://github.com/propelorm/Propel3
Propel3 is an open-source Object-Relational Mapping (ORM) for modern
PHP 7.1+. Version 3 of Propel ORM replaces Propel2, which is not
maintained anymore.
Maybe also see the discussion here: https://github.com/propelorm/Propel3/issues/92
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.
The Wiki page lists and links to version 2.2 of event drag library (threedubmedia.com).
However, the examples point to version 2.3, hosted in 6pac.github site.
What is this version about? Where does it come from? Can anybody give some information about it?
It's my repo. So for v2.3, we (#lfilho did these changes I believe) simply took 2.2 and updated it to be compatible with jQuery 2 and 3.
ThreeDub weren't involved, and the 2.2 version remains the latest release from them.
I have been tasked with fixing a bug found in a legacy app written in version 2.4.0 or 2.6.0 of STS.
After spending the better part of 2 days trying to port it to 3.6.2 without success I need to get my hands on either of these older releases to see if this even works or if there is something wrong with the app code base. I have spent the better part of an hour searching STS Spring for previous versions but can't find anything on the site. Where are previous versions of STS or why have they been stashed away?
OS Target: Window 7 - 64 bit
Thanks
Having a look at this post and the filename of the current version, you come up with: http://download.springsource.com/release/STS/2.6.0.SR1/dist/e3.6/springsource-tool-suite-2.6.0.SR1-e3.6.2-win32-x86_64.zip
Very strange that they are not linking the old versions even though they are still available.
I have a gantry template for Joomla 2.5 and I converted this template to make it Joomla 3.0 compatible.
The Joomla 2.5 to 3.0 upgrade was successful, but template does not work, why? .
I get the following error:
500 - JHtmlBehavior::mootools not found
Somewhere in your template, you are using:
JHtml::_('behavior.mootools');
or
JHtmlBehavior::mootools();
This has been removed as of Joomla 3 and therefore needs to be changed to:
JHtml::_('behavior.framework');
Instead of trying to fix the extensions the following plugin can be used (and it will provide the JHtml::_('behavior.mootools') API call): J25 Legacy plugin for Joomla 3.X
I agree with denis post above. I had this same problem with upgrading from j2.5 to j3X and used j25 legacy plugin from pluginaria. Found here: http://www.pluginaria.com/j25-legacy.html and got rid of the error for me. There may be a better way.... Find and replace plugin to the change code? But this is a quick and easy way to solve this issue. Make sure to activate the plugin under plugin manager after you install.... and of course make sure you have a backup before upgrading from 2.5 to 3. You should expect their to be problems.