I usually wait for 2-3 months (just because I am the only one in a core team in our project) to update, also upgrades that include PHP version changes are not the easiest ones in our case, because of the oci8 and mssql packages that require phar recompiling.
I have upgraded 1 of my projects to Laravel 11 since it is still in the development phase. Luckily all the packages that I use have already update to support L11 so the upgrade process was very smooth. Oh, did the upgrade manually.
@@amitdev1485 Yes. Spatie Permissions 6.4.0 supports L11. Spatie packages that I am using with L11: - Image - Simple Excel - Permissions - Multi tenancy
Bingo... I too share the same opinion... This is applicable to any new technology... Give it some time... So that all the common bugs / issues are resolved / addressed at least...
I already did the upgrade and it was mostly seamless in my case. It probably helped that I almost don't use external laravel packages and coded what I needed myself so I didn't have to wait for any support for laravel 11.
You need to update to new framework versions. But you also need to remember that not all packages or code can start working with the new version. And even if it can, does it work correctly? Therefore, there is no clear path for you. As in everything. But if possible, do it. Updating to several versions at once a year, two, ten years later can be a real pain in the ass. Programmer dad writes code all night. He sleeps on the table in the morning. The son comes, wakes it up and says that the sun has already risen. Dad asks, "Does she do that every morning?". Son: "Yes". Dad: "Okay. Then just don't touch anything.".
Hi, the new feature on Laravel 11 is Laravel Reverb which is instead of Broadcast. is that correct? so could you make the tutorial about how to work by Laravel Reverb as a WebSocket service?
Great advice!!!. Do you think it's possible upgrade a Laravel 10 project to Laravel 11 in terms of directory structure? I mean, for example, putting all code of the RouteServiceProvider in the new structure... Or, literally, will I have always the old structure even if I upgrade to 11 version?
I have a client that has a very complex system that was build using laravel 7, is it possible to upgrade it to 11 or just leave it? It depends on php 7.
You should then upgrade version by version: to 8, to 9, to 10, and then to 11, along the way upgrading PHP version. So, for complex system this is a very complex process, may easily take months.
Good day sir how to fix this error? Problem 1 - filament/filament v3.2.39 requires filament/support v3.2.39 -> satisfiable by filament/support[v3.2.39]. - filament/filament v3.2.40 requires filament/support v3.2.40 -> satisfiable by filament/support[v3.2.40]. - filament/filament v3.2.41 requires filament/support v3.2.41 -> satisfiable by filament/support[v3.2.41]. - filament/filament v3.2.42 requires filament/support v3.2.42 -> satisfiable by filament/support[v3.2.42]. - filament/filament v3.2.43 requires filament/support v3.2.43 -> satisfiable by filament/support[v3.2.43]. - filament/filament v3.2.44 requires filament/support v3.2.44 -> satisfiable by filament/support[v3.2.44]. - filament/filament v3.2.45 requires filament/support v3.2.45 -> satisfiable by filament/support[v3.2.45]. - filament/filament v3.2.46 requires filament/support v3.2.46 -> satisfiable by filament/support[v3.2.46]. - filament/filament v3.2.47 requires filament/support v3.2.47 -> satisfiable by filament/support[v3.2.47]. - filament/filament v3.2.48 requires filament/support v3.2.48 -> satisfiable by filament/support[v3.2.48]. - filament/filament v3.2.49 requires filament/support v3.2.49 -> satisfiable by filament/support[v3.2.49]. - filament/filament[v3.2.36, ..., v3.2.38] require illuminate/console ^10.45 -> satisfiable by illuminate/console[v10.45.0, ..., v10.48.3]. - filament/filament[v3.2.0, ..., v3.2.35] require illuminate/console ^10.0 -> satisfiable by illuminate/console[v10.0.0, ..., v10.48.3]. - filament/filament v3.2.50 requires filament/support v3.2.50 -> satisfiable by filament/support[v3.2.50]. - filament/support[v3.2.39, ..., v3.2.50] require ext-intl * -> it is missing from your system. Install or enable PHP's intl extension. - illuminate/console[v10.0.0, ..., v10.48.3] require nunomaduro/termwind ^1.13 -> found nunomaduro/termwind[v1.13.0, ..., v1.15.1] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires filament/filament ^3.2 -> satisfiable by filament/filament[v3.2.0, ..., v3.2.50]. To enable extensions, verify that they are enabled in your .ini files: - C:\xampp\php\php.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-intl` to temporarily ignore these required extensions. Installation failed, reverting ./composer.json and ./composer.lock to their original content.
The main error is this: "equire ext-intl * -> it is missing from your system. Install or enable PHP's intl extension" Google how to enable this PHP extension on your web-server.
I usually wait for 2-3 months (just because I am the only one in a core team in our project) to update, also upgrades that include PHP version changes are not the easiest ones in our case, because of the oci8 and mssql packages that require phar recompiling.
Just what i was thinking about now - upgrade or not upgrade, that is the question. Perfect timing.
You talk like the Hamlet
Same dilemma here
I have upgraded 1 of my projects to Laravel 11 since it is still in the development phase. Luckily all the packages that I use have already update to support L11 so the upgrade process was very smooth.
Oh, did the upgrade manually.
did spatie laravel permissions supported it?
@@amitdev1485 Yes. Spatie packages that I used:
Image
Simple Excel
Multi Tenancy
Permissions
and they all support L11.
no. not yet
@@amitdev1485 Yes. Spatie Permissions 6.4.0 supports L11.
Spatie packages that I am using with L11:
- Image
- Simple Excel
- Permissions
- Multi tenancy
@@amitdev1485 Yes. It is supported. You will need to update it to 6.4.0.
I always keep my projects 1 version before the most recent one, now that 11 is out, I will update to 10.
Bingo... I too share the same opinion... This is applicable to any new technology... Give it some time... So that all the common bugs / issues are resolved / addressed at least...
I already did the upgrade and it was mostly seamless in my case. It probably helped that I almost don't use external laravel packages and coded what I needed myself so I didn't have to wait for any support for laravel 11.
thanks for the advice
this , few months later is absolute right 👍
Thanks for your opinion It is really attractive
Thanks for your opinion!
Thanks. That seems like like sound advice!
Agree 100%
You need to update to new framework versions. But you also need to remember that not all packages or code can start working with the new version. And even if it can, does it work correctly? Therefore, there is no clear path for you. As in everything.
But if possible, do it. Updating to several versions at once a year, two, ten years later can be a real pain in the ass.
Programmer dad writes code all night. He sleeps on the table in the morning. The son comes, wakes it up and says that the sun has already risen.
Dad asks, "Does she do that every morning?".
Son: "Yes".
Dad: "Okay. Then just don't touch anything.".
Hi, the new feature on Laravel 11 is Laravel Reverb which is instead of Broadcast. is that correct?
so could you make the tutorial about how to work by Laravel Reverb as a WebSocket service?
Yes, it's not a new feature but a separate totally new tool.
Yes I'm planning to review it in a week or two, when I try it myself on a real project.
Great advice!!!. Do you think it's possible upgrade a Laravel 10 project to Laravel 11 in terms of directory structure?
I mean, for example, putting all code of the RouteServiceProvider in the new structure...
Or, literally, will I have always the old structure even if I upgrade to 11 version?
It's tricky. I think the best comment on this is from the creator of Laravel Shift: twitter.com/laravelshift/status/1768289031308071034
I always build a blank project of the new version, then copy code over. Will be doing the same here.
thanks man. how to work with csrf and cors.php in laravel 11, so work with SPA and serverSide Authentications.?
I usually wait 2 to 3 months, and all modules must be compatible with laravel 11. I use composer why-not laravel/framework 11.0 to check it
I tried updating but spatie packages didn't accept it and stopped updating it
Exactly, personally for me green light is spatie packages support 😂
nice
Is Devin AI going to take software Developer jobs? Should we be worried as Software Developers?
No. And no.
I have a client that has a very complex system that was build using laravel 7, is it possible to upgrade it to 11 or just leave it? It depends on php 7.
You should then upgrade version by version: to 8, to 9, to 10, and then to 11, along the way upgrading PHP version.
So, for complex system this is a very complex process, may easily take months.
This is the easiest laravel upgrade ever don't need to change a thing in my code
First day upgrade 😂😂😂, well the app is still in development Soo it doesn't matter
just want to say that dont upgrade it yet. it has a lot of fckin buga although the it has patches and fix but still it is still not matured
Good day sir how to fix this error?
Problem 1
- filament/filament v3.2.39 requires filament/support v3.2.39 -> satisfiable by filament/support[v3.2.39].
- filament/filament v3.2.40 requires filament/support v3.2.40 -> satisfiable by filament/support[v3.2.40].
- filament/filament v3.2.41 requires filament/support v3.2.41 -> satisfiable by filament/support[v3.2.41].
- filament/filament v3.2.42 requires filament/support v3.2.42 -> satisfiable by filament/support[v3.2.42].
- filament/filament v3.2.43 requires filament/support v3.2.43 -> satisfiable by filament/support[v3.2.43].
- filament/filament v3.2.44 requires filament/support v3.2.44 -> satisfiable by filament/support[v3.2.44].
- filament/filament v3.2.45 requires filament/support v3.2.45 -> satisfiable by filament/support[v3.2.45].
- filament/filament v3.2.46 requires filament/support v3.2.46 -> satisfiable by filament/support[v3.2.46].
- filament/filament v3.2.47 requires filament/support v3.2.47 -> satisfiable by filament/support[v3.2.47].
- filament/filament v3.2.48 requires filament/support v3.2.48 -> satisfiable by filament/support[v3.2.48].
- filament/filament v3.2.49 requires filament/support v3.2.49 -> satisfiable by filament/support[v3.2.49].
- filament/filament[v3.2.36, ..., v3.2.38] require illuminate/console ^10.45 -> satisfiable by illuminate/console[v10.45.0, ..., v10.48.3].
- filament/filament[v3.2.0, ..., v3.2.35] require illuminate/console ^10.0 -> satisfiable by illuminate/console[v10.0.0, ..., v10.48.3].
- filament/filament v3.2.50 requires filament/support v3.2.50 -> satisfiable by filament/support[v3.2.50].
- filament/support[v3.2.39, ..., v3.2.50] require ext-intl * -> it is missing from your system. Install or enable PHP's intl extension.
- illuminate/console[v10.0.0, ..., v10.48.3] require nunomaduro/termwind ^1.13 -> found nunomaduro/termwind[v1.13.0, ..., v1.15.1] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires filament/filament ^3.2 -> satisfiable by filament/filament[v3.2.0, ..., v3.2.50].
To enable extensions, verify that they are enabled in your .ini files:
- C:\xampp\php\php.ini
You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode.
Alternatively, you can run Composer with `--ignore-platform-req=ext-intl` to temporarily ignore these required extensions.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
The main error is this: "equire ext-intl * -> it is missing from your system. Install or enable PHP's intl extension"
Google how to enable this PHP extension on your web-server.