i have a project that is almost done base on Sylius-alpha and now i want to migrate to Sylius-BETA , should i just run composer update or install sylius-beta and rework on sylius-beta again from the first ? what should i do plz ?
I think alpha->beta has some BCs so you will need check everything you did, here upgrade from beta1 to beta2 https://github.com/Sylius/Sylius/blob/master/UPGRADE.md
Related
Is it even worth it upgrading a laravel 5.4 project to laravel 7 which includes many packages ?
Do I have to upgrade it manually version after version or is there any tool that might help with the migration ?
Thank you for all the answers.
By upgrading one version at time, it will be easier to fix and change whats needs to be changed.
Here is how I did:
https://laravel.com/docs/5.5/upgrade
Follow the guide
Change the code
Test your code
https://laravel.com/docs/5.6/upgrade
Follow the guide
Change the code
Test your code
And so on.
Depends on the size of your project. Go to the github pages of your third party packages to check if they have updated as well. You can always change the package.
It will be a pain in the ass, but it's possible.
(Don't forget the php version.)
Good luck!
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.
I am using Laravel 5.1 and I would like to know how to upgrade to the latest version of Laravel which is 5.4.
Can we directly upgrade to Laravel 5.4 From 5.1 ?
The best way to upgrade is to follow the steps for each version. So upgrade to 5.2 then 5.3 then finally 5.4. The upgrade guides look lengthy but it most cases it wont take to much time because the guide covers all potential changes but they won't all apply to your application.
Alternatively you could install a fresh version of 5.4 then copy your application code into the new Laravel. Since the upgrade for each version is relatively straight forward and this method would lose your git history I wouldn't recommend it.
Another paid method would be to use Laravel Shift which will automate the upgrade process for you.
Edit: As #Scott mentioned you should make sure your server meets the server requirements for your target Laravel version. Specifically make sure you have PHP >= 5.6.4 installed
Well, you first you need to update your composer.json file. Around line 9, you should be requiring in the framework itself. Change that to use version 5.4.*. After that, run a composer update and then, yes, you do need to go through your files manually to address any incompatibilities.
after you replace provider folder to the new version.
https://github.com/laravel-shift/laravel-5.4/tree/master/app/Providers.
i have some error with my application symfony. one error is Unsupported declare 'strict_types'. Please help me to resolve that.
My php version is 7.0.12
My symphony version is 2.7.16
My Ocramius/proxy-manager version is 2.0.3
this is the link to my server : http://www.kossa.cm
I actually encounter the exact same issue and the only ugly fix I could find to just pass through (without fixing it) is to remove that vendor/ocramius/proxy-manager folder and do not run a composer update (that would install the proxy-manager back).
As I said, it is not a proper fix, I'm trying to solve it now.
If you found any kind of information about it, please share it with us ;)
--Edit-- Are you using wamp ?
to solve your problem, downgrade your php version to 5.6, because ocramius is not compatible for the momment with php 7.0 and above!
I'm a laravel newb, so this might be a question most of you find stupid, but I haven't found a straight answer to this one even after several hours search. I do know how to use GIT, but I thought there might be a Laravel way to do it like many things seems to be done with artisan commands. If the update is only possible through GIT commands so have you found that you can do it without messing up the app folder where you have made your changes?
I have a quit new version of beta, only about one month old, but have worked on it already quit much.
Thanks for helping out one Laravel newb.
If you have composer install globally run:
composer update
Otherwise (locally), run:
php composer.phar update
Checkout official documentation