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.
Related
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!
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.
I have started project in Laravel 5.2 based on Laravel Framework 5 Bootstrap 3 Starter Site. I have successful upgraded to latest 5.2 laravel version.
Right now I want to use Propel 2 instead of Eloquent.
Is there much work with replacing it? How about Auth model? Any traps or dead ends?
I appreciate any suggestions.
We have our site running on Laravel 4.2 and have been thinking about upgrading to 5.0 for a long time now.
We also have a subdomain that we started building and decided to use Laravel 5.1 so that we could get used to it before the migration. We have the sub domain setup and installed and it is running.
However, our login does not persist between the two domains. We have the domain set in session settings on both systems. The cookie gets set but I am assuming Laravel 4.2 and 5.1 have different auth systems therefore the cookie from 4.2 does not work in 5.1 and vice versa. We have also tried database sessions and file sessions without much luck.
Is there a way to convert a Laravel 4 session into a Laravel 5 session so that users can go from our 4.2 main site to our 5.1 sub domain easily?
Is it possible to make both types of cookie one for the 4.2 and one for the 5.1 at the same time so that users would have and use both domains?
Or are we looking at this all wrong and should try something totally different to get what we want?
Or are we looking at this all wrong and should try something totally different to get what we want?
Do you really need to run 4.2 & 5.1?
Personally I've done a few upgrades from 4.2 to 5.1 (and even 4.2 to 5.3 recently). Your best bet is just dedicate 3-4 hours (or even 1-2 days depending on the size of your app) and follow the upgrade guide: https://laravel.com/docs/5.1/upgrade#upgrade-5.0
If you follow each step systematically - it is a fairly easy upgrade path.
Then put the 5.1 application in a sub-domain and have some users "test" the new version, before you push it into production.
There is also the Laravel Shift paid option as well: https://laravelshift.com/
Watchout, Laravel 5.1 use a new Hash system, watch the line
'cipher' => 'AES-256-CBC',
in config/app.php and compare with the old app.php
I am simply trying to install a laravel bundle via the Artisan CLI using the latest Laravel 4 beta from github.
But when I try something like:
php artisan bundle:install bob
I'm confronted with
[InvalidArgumentException]
There are no commands defined in the "bundle" namespace.
I've had a look around online and can't seem to find a solution to this or even anyone else having similar problems for that matter.
Has anyone else experienced this error or any ideas on a solution?
If you're using Laravel 4 (which based on the tags for this question, you are) then bundles are no longer used.
Out with bundles, in with composer
Instead, Laravel 4 makes use of composer packages. It's kind of similar but at the same time very different in how it works. Here isn't the right place to explain all of composer, so check out the links below to find out more:
Getting started with Laravel 4
How to setup Laravel 4
Composer primer
Laravel 4 Generator
Now, since you were asking about bob, the closest equivalent for the bob bundle would probably be Jeffrey Ways generator package, which you can learn more about here: Laravel-4-Generators