Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
What is the easiest and fastest way to upgrade code from Laravel 5.3 to Laravel 7.3 or 8 ? Is there a tool which can do that for me ? How long does it take to do that?
Please help .
Regards
The easiest way is to follow the documentation by laravel, best way is to upgrade to the next version, for example in your situation upgrade to 5.4, when everything is working, and all composer packages are upgraded to the right version, then move on to 5.5 etc...
heres a place to start : https://laravel.com/docs/5.4/upgrade#upgrade-5.4.0
and you can just change version in top right corner to get upgrade for the next version.
keep in mind you gonna have to keep upgrading manually packages versions in your composer.json to the proper versions, so just analyze the error codes you gonna be getting.
if theres a tool to help with that, then I dont know about it, hopefully next person does.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to upgrade PHP version of my project. It is PHP5.6 and I want to upgrade it to PHP8.1. I tried to search for such information but couldn't find it, thus, I want to ask. Is it better to upgrade directly from PHP5.6 to PHP8.1, or step by step (PHP5.6 -> PHP7.0, PHP7.0 -> PHP7.1, PHP7.1->PHP7.2 and etc until I reach PHP8.1)?
Upgrading step by step can help you to see what is deprecated by following the logs files and then review the code.
I have recently been made aware of this tool which ostensibly makes this process much easier. Note that I have not used it myself and as such can't speak to how well it works. It looks to be a FOSS project though which is good.
Website: https://getrector.org/
Github: https://github.com/rectorphp/rector
Updating manually as per the guides provided by vee will likely give you better understanding of the benefit each upgrade offers as well as maintaining full control over your project.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I have a legacy application which uses
Symfony 1_4
PHP 5.3
MySQL 5.6
Client is asking for an upgrade of all the tech stack to the latest.
Symfony 5
PHP 8
MySQL 8
How can I do this upgrade with minimum effort ?
A solution required without re-writing the whole application.
Upgraded application's security should be major feature
Upgrading from such an old version to the latest version is most likely never going to work.
I suggest rebuilding the application in Symfony 5 manually, it will probably save you a lot time and effort.
You can try to reuse as much business logic as you can.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
In silex's web page, it says that the stable version of siles is 1.3 but silex-skeleton uses version 2 of silex, is this recommended?
Silex 2.0 is not stable yet, in fact is a dev-master. The bigger problem is that a dev-master can change at any time. Unlike a stable version, it may be that one day you will do composer update and your application will stop working for some reason.
It is always preferable stable versions, but you can also developed you application in sync with the branch master of silex.
For your sake and the sake of your team don't do it.
I have made the mistake of putting one of my big projects back in time of Symfony2.0-alpha (or was it beta, not sure). The documentation was scarce, it was unstable for some use-cases - I wen't thought hell and back.
Projects are marked unstable for a reason - they should not be used in production until the devs make sable release.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have an app currently running on a PHP 5.2 server that I need to migrate to a PHP 5.5 (or 5.6) server. What are the things to look at, what issues might I encounter?
Thanks in advance
This is well documented.
http://php.net/manual/en/migration53.php
http://php.net/manual/en/migration54.php
http://php.net/manual/en/migration55.php
http://php.net/manual/en/migration56.php
Go through each of these one by one. This may be a good time to refactor your application.
Basically, you have to migrate your code from 5.2 to 5.3, then to 5.4, then to 5.5, and then to 5.6. For each Migration, the PHP documentation has listed what you may encounter:
5.2 -> 5.3 : http://php.net/manual/de/migration53.php
5.3 -> 5.4 : http://php.net/manual/de/migration54.php
5.4 -> 5.5 : http://php.net/manual/de/migration55.php
5.5 -> 5.6 : http://php.net/manual/de/migration56.php
Look for Backward incompatible changes and deprecated features. Hope I could help.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
PHP 5.3 has been released some time ago and the developers tried to keep the number of backwards compatibility breaks low. What issues did you find while testing/migrating your code with PHP 5.3?
I don't know about you, but I found all of these things I had to fix. :P
Migrating from PHP 5.2.x to PHP 5.3.x
Using CakePHP 1.2 it causes a lot of deprecated notices in debug mode.
Upgrading to latest CakePHP version fix it.
Beside the deprecated notices, I did not find any major issue.