I've been upgrading from 10 to 11 Laravel so was glad to have found your video just. Thanks for posting this, an excellent walk through As a Laravel newbie as of V10, may I ask, if you have a composer.json file that has packages other than the ones the Laravel upgrade notes to refer to, would you tend to upgrade these also ? I guess its a relative question, as it would depend on your use case and how up to date you need to be - in node apps I'm familiar with I know you can upgrade to latest on all packages, not just the core of the app. thanks again for the video - very timely !
It totally depends on the available packages in the composer.json file. However it is needed to upgrade the core packages while upgrading the Laravel version.
I've started adding automated feature tests to my apps that are Laravel, which follows on from other frameworks I've worked on in the past and I plan to run these after each upgrade of Laravel or other packages - to help gain confidence there are not breaking changes
@@GauravMehta1190 In Laravel 11, the Collective HTML package, which was previously used to manage forms and HTML, is not included by default. This package was separated from the Laravel core a while back and isn't maintained as part of the Laravel framework. If you're upgrading to Laravel 11 and encountering the "Collective HTML service provider not found" issue, you'll need to manually include the package in your project. Therefore you can install it using the composer itself. composer require laravelcollective/html
This is not working. Getting multiple errors in command prompt. Getting below errors. Problem 1 - laravelcollective/html[v5.0.0, ..., v5.0.4] require illuminate/http ~5.0 -> found illuminate/http[v5.0.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html v5.0.5 requires illuminate/http ~5.1 -> found illuminate/http[v5.1.1, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.1.0, ..., v5.1.11] require illuminate/http 5.1.* -> found illuminate/http[v5.1.1, ..., v5.1.41] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.2, ..., v5.2.6] require illuminate/http 5.2.* -> found illuminate/http[v5.2.0, ..., v5.2.45] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.3.0, ..., v5.3.2] require illuminate/http 5.3.* -> found illuminate/http[v5.3.0, v5.3.4, v5.3.16, v5.3.23] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.4, ..., v5.4.9] require illuminate/http 5.4.* -> found illuminate/http[v5.4.0, ..., v5.4.36] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.5, ..., v5.5.4] require illuminate/http 5.5.* -> found illuminate/http[v5.5.0, ..., v5.5.44] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.5.2, ..., v5.6.10] require illuminate/http 5.6.* -> found illuminate/http[v5.6.0, ..., v5.6.39] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.7, ..., v5.7.1] require illuminate/http 5.7.* -> found illuminate/http[v5.7.0, ..., v5.7.28] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v5.8.0, ..., v5.8.1] require illuminate/http 5.8.* -> found illuminate/http[v5.8.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v6.0, ..., v6.0.2] require illuminate/http 6.0.* -> found illuminate/http[v6.0.0, ..., v6.0.4] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html v6.0.3 requires illuminate/http ^6.0 -> found illuminate/http[v6.0.0, ..., v6.20.44] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v6.1.0, ..., v6.1.2] require illuminate/http ^6.0|^7.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v6.2.0, ..., v6.2.1] require illuminate/http ^6.0|^7.0|^8.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html v6.3.0 requires illuminate/http ^6.0|^7.0|^8.0|^9.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require. - laravelcollective/html[v6.4.0, ..., v6.4.1] require illuminate/http ^6.0|^7.0|^8.0|^9.0|^10.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.20] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires laravelcollective/html * -> satisfiable by laravelcollective/html[v5.0.0, ..., v5.8.1, v6.0, ..., v6.4.1]. You can also try re-running composer require with an explicit version constraint, e.g. "composer require laravelcollective/html:*" to figure out if any version is installable, or "composer require laravelcollective/html:^2.1" if you know which you need. Installation failed, reverting ./composer.json and ./composer.lock to their original content.
I've been upgrading from 10 to 11 Laravel so was glad to have found your video just. Thanks for posting this, an excellent walk through
As a Laravel newbie as of V10, may I ask, if you have a composer.json file that has packages other than the ones the Laravel upgrade notes to refer to, would you tend to upgrade these also ?
I guess its a relative question, as it would depend on your use case and how up to date you need to be - in node apps I'm familiar with I know you can upgrade to latest on all packages, not just the core of the app.
thanks again for the video - very timely !
It totally depends on the available packages in the composer.json file. However it is needed to upgrade the core packages while upgrading the Laravel version.
I've started adding automated feature tests to my apps that are Laravel, which follows on from other frameworks I've worked on in the past and I plan to run these after each upgrade of Laravel or other packages - to help gain confidence there are not breaking changes
@@JonBrookes Glad to hear.
Class "Collective\Html\HtmlServiceProvider" not found. Getting this error. Please help me.
@@GauravMehta1190 In Laravel 11, the Collective HTML package, which was previously used to manage forms and HTML, is not included by default. This package was separated from the Laravel core a while back and isn't maintained as part of the Laravel framework. If you're upgrading to Laravel 11 and encountering the "Collective HTML service provider not found" issue, you'll need to manually include the package in your project.
Therefore you can install it using the composer itself.
composer require laravelcollective/html
This is not working. Getting multiple errors in command prompt. Getting below errors.
Problem 1
- laravelcollective/html[v5.0.0, ..., v5.0.4] require illuminate/http ~5.0 -> found illuminate/http[v5.0.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html v5.0.5 requires illuminate/http ~5.1 -> found illuminate/http[v5.1.1, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.1.0, ..., v5.1.11] require illuminate/http 5.1.* -> found illuminate/http[v5.1.1, ..., v5.1.41] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.2, ..., v5.2.6] require illuminate/http 5.2.* -> found illuminate/http[v5.2.0, ..., v5.2.45] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.3.0, ..., v5.3.2] require illuminate/http 5.3.* -> found illuminate/http[v5.3.0, v5.3.4, v5.3.16, v5.3.23] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.4, ..., v5.4.9] require illuminate/http 5.4.* -> found illuminate/http[v5.4.0, ..., v5.4.36] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.5, ..., v5.5.4] require illuminate/http 5.5.* -> found illuminate/http[v5.5.0, ..., v5.5.44] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.5.2, ..., v5.6.10] require illuminate/http 5.6.* -> found illuminate/http[v5.6.0, ..., v5.6.39] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.7, ..., v5.7.1] require illuminate/http 5.7.* -> found illuminate/http[v5.7.0, ..., v5.7.28] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v5.8.0, ..., v5.8.1] require illuminate/http 5.8.* -> found illuminate/http[v5.8.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v6.0, ..., v6.0.2] require illuminate/http 6.0.* -> found illuminate/http[v6.0.0, ..., v6.0.4] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html v6.0.3 requires illuminate/http ^6.0 -> found illuminate/http[v6.0.0, ..., v6.20.44] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v6.1.0, ..., v6.1.2] require illuminate/http ^6.0|^7.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v6.2.0, ..., v6.2.1] require illuminate/http ^6.0|^7.0|^8.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html v6.3.0 requires illuminate/http ^6.0|^7.0|^8.0|^9.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16] but these were not loaded, likely because it conflicts with another require.
- laravelcollective/html[v6.4.0, ..., v6.4.1] require illuminate/http ^6.0|^7.0|^8.0|^9.0|^10.0 -> found illuminate/http[v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.16, v10.0.0, ..., v10.48.20] but these were not loaded, likely because it conflicts with another require.
- Root composer.json requires laravelcollective/html * -> satisfiable by laravelcollective/html[v5.0.0, ..., v5.8.1, v6.0, ..., v6.4.1].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require laravelcollective/html:*" to figure out if any version is installable, or "composer require laravelcollective/html:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
The added version is not satisfied with the required one.
you didn't make the sanctum change as shown in the laravel site
How to check database name in existing files
You can checkout the .env file.