I am trying to upgrade my laravel 4.1.30 project to laravel 5. But I searched instructions online many times, even official described not clearly.Please lead me to be able to upgrade step by step.
Yes, you can I'm also in a process of doing upgrade with a project from 4.0 to 5.
Currently I have upgraded from 4.0 to 4.2 and now gonna upgrade it to 5 as well.
What I figured out is that you have to follow all upgrade process step by step as described in the guide.
https://laravel.com/docs/5.3/upgrade
It means, you have to do all small upgrades as well for example, "Upgrading To 4.1.29 From <= 4.1.x" also needs to be done.
I hope it helps.
Related
actually i made a symfony webapp 3 years ago , i didn't use it, and now i am trying to deploy it on heroku but it says , that i need to use newer version
I am trying to resolve the deprecation before updating the version (5.1 and go progressively to 6) but i do not know how to do
i already made my research on internet but i did not find something that can help
You should migrate to Symfony 5 first tkans to the full doc here and after to Symfony 6 thanks to that !
Both explain how to fix your deprecations and a search for deprecations specific to your favorite search engine will also help!
I'm currently in the process of upgrading a Laravel 5.2 project (yes, I know, I know...) to the latest Laravel version (9 at the time of writing). This project uses Caffeinated/Modules to structure the code - currently on version 3.
On checking the compatibilities using Laravel Shift, it appears there is no version of Caffeinated/Modules compatible with Laravel 9. In addition, on checking the Modules project on GitHub, no updates have been made to it in the past year - which is slightly worrying.
So I'm wondering if this plugin is effectively obsolete? (or soon-to-be?)
Does anyone know if there are any plans to keep it going in the future? Or is it worth ditching it now?
(For background, I tried a single "shift" from 5.2 to 5.3, and so far have been unable to get the Module routes to work. I wonder if the Modules could be the biggest headache in the upgrade process).
Any insider knowledge/advice/experience gratefully received!
So I just took over a laravel 5.2 based project with some dependency hell.
The backend is build on a smarch/watchtower package which has been abandoned and laravel 5.3 is the highest version it supports.
tsawler/laravel-filemanager is one more abandoned package.
Now I would like to update the whole project to the latest version of laravel to enjoy the new features, bug fixes and security patches and add the possibility to use other packages.
What are the best practices in such a situation?
Should I go with hijacking the abandoned packages one at a time and update them,
find similar packages with strong community support and replace the abandoned ones,
build the whole project from the start on a fresh copy of laravel 6
or accept the truth and continue on the old version?
any other suggestions?
Links to abandoned packages:
smarch/watchtower
tsawler/laravel-filemanager
Typically, I use packages from vendors that I know will be kept updated (such as Spatie packages). In place of Watchtower, you could use [laravel-permission] https://github.com/spatie/laravel-permission. However, tsawler/laravel-filemanager did install on Laravel v6.x. Though it says use https://github.com/UniSharp/laravel-filemanager so I'd install that instead.
From there you can upgrade from 5.2 to 6.x yourself or have a service like Laravel Shift do it for you. I create a new laravel instance and diff the directories to see what files changed. Also, make sure you read the upgrade guide: https://laravel.com/docs/6.x/upgrade. This might help as well: https://laracasts.com/discuss/channels/laravel/laravel-52-to-6?page=1
How does one downgrade a Laravel 5 project to Laravel 4? If it's not that hard, it might work better for my team. Any changes in Eloquent, Controllers, views, and user logins would be the need-to-know. The primary reason we are looking to downgrade is host PHP support. 5.3/5.4 are what we'd need, so whichever version of 4 we use would need to go that far back - I guess I'm also looking for advice on which version of 4 would be good.
I am trying to update my project written in Symfony 2.0 into Symfony 2.2.
Moving source codes into 2.2 project ended with config.yml and security.yml incompatibiliy.
Is there way how to properly migrate Symfony 2.0 project into Symfony 2.2?
It better to wait until Symfony 2.3 before migrating. It will be released somewhere in May. It's the first LTS (Long Time Support) release, meaning that it's maintained for three years. So: You don't have to worry about BC breaks for 3 years!
For the migrating of Symfony 2.0 to 2.3: There is nothing you can do. Read the UPGRADE-*.md files (which are stored in the root of the symfony/symfony package) and fix anything that is in their in your code. Every BC break that's important for normal users will be put in those UPGRADE files.
If you can't solve it after the fixing everything in the UPGRADE files, you should take a look at the CHANGELOG.md files in the root of the package (e.g. the symfony/security package). Try to find something that is changed and cause your code to break.
Finally, if you don't get your script working, there are a lot of active Symfony2 users who are waiting to help you. Take a look at the community page and find your place to ask questions.