laravelshoppingcart icon indicating copy to clipboard operation
laravelshoppingcart copied to clipboard

When will laravel11 be supported?

Open demonyun opened this issue 3 months ago • 11 comments

When will laravel11 be supported? Thanks.

demonyun avatar Mar 15 '24 07:03 demonyun

While waiting original author to update the version to support Laravel 11, in the mean time:

  1. You can fork this repo and change the line illuminate/support, illuminate/validation, illuminate/translation to ^11.0 in the composer.json (not your project composer.json).
  2. Then use VCS type to load the laravelshoppingcart (in your project composer.json), and then composer install.

E,g,

"require": {
        "xxx/laravelshoppingcart": "dev-master",
    },
"repositories": {
    "repo-name": {
        "type": "vcs",
        "url": "[email protected]:xxx/laravelshoppingcart.git"
    }
}

Replace xxx with your own github username.

Tested on my own project, laravelshoppingcart in Laravel 11 is worked.

sjkhew avatar Apr 29 '24 10:04 sjkhew

+1 request for laravel 11

tanero avatar May 03 '24 06:05 tanero

Just fork it an create a PR with the required changes if you need that, that is how open source works :)

ronaldvaneede avatar May 03 '24 07:05 ronaldvaneede

@ronaldvaneede

Just fork it an create a PR with the required changes if you need that, that is how open source works :)

I'm sure I know very well how open source works, but if the main administrator of the repo doesn't take it into consideration, there's not much left to do.

Did you check the pull requests ?

There is already https://github.com/darryldecode/laravelshoppingcart/pull/379 and https://github.com/darryldecode/laravelshoppingcart/pull/375

tanero avatar May 03 '24 07:05 tanero

I have this error when I try to install in Laravel 11, is this fixed with first response of this thread? thanks for advance

`Your requirements could not be resolved to an installable set of packages.

Problem 1 - darryldecode/cart 4.0.0 requires illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.* -> found illuminate/support[v5.0.0, ..., v5.6.39] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart[4.0.1, ..., 4.0.2] require illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7. -> found illuminate/support[v5.0.0, ..., v5.7.28] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart[4.0.3, ..., 4.0.4] require illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.* -> found illuminate/support[v5.0.0, ..., v5.8.36] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart 4.0.5 requires illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|6.0. -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.0.4] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart 4.0.6 requires illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|6.0.|6.1.* -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.1.0] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart[4.0.7, ..., 4.1.1] require illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|^6.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.44] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart 4.1.2 requires illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|^6.0|^7.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, v6.0.0, ..., v6.20.44, v7.0.0, ..., v7.30.6] but these were not loaded, likely because it conflicts with another require. - darryldecode/cart[4.2.0, ..., 4.2.1] require illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|^6.0|^7.0|^8.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, 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. - darryldecode/cart 4.2.2 requires illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.|^6.0|^7.0|^8.0|^9.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, 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. - darryldecode/cart[4.2.3, ..., 4.2.4] require illuminate/support 5.0.|5.1.|5.2.|5.3.|5.4.|5.5.|5.6.|5.7.|5.8.*|^6.0|^7.0|^8.0|^9.0|^10.0 -> found illuminate/support[v5.0.0, ..., v5.8.36, 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.10] but these were not loaded, likely because it conflicts with another require. - Root composer.json requires darryldecode/cart ~4.0 -> satisfiable by darryldecode/cart[4.0.0, ..., 4.2.4].

Installation failed, reverting ./composer.json and ./composer.lock to their original content.`

plescanos avatar May 09 '24 12:05 plescanos

plescanos

Yes, you can use solution provided by sjkhew

maxxdev avatar May 10 '24 07:05 maxxdev

Thanks a lot, but not work. When I make composer install console returns this:

Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run composer update or composer update <package name>.

  • Required package "plescanos/laravelshoppingcart" is not present in the lock file. This usually happens when composer files are incorrectly merged or the composer.json file is manually edited. Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r

And when I use composer update (as first error says) it return the following error:

Your requirements could not be resolved to an installable set of packages.

Problem 1 - Root composer.json requires plescanos/laravelshoppingcart, it could not be found in any version, there may be a typo in the package name.

Potential causes:

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

So please if someone can help me , i'll say thanks forever

plescanos avatar May 11 '24 04:05 plescanos

Thanks a lot, but not work. When I make composer install console returns this:

Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run composer update or composer update <package name>.

  • Required package "plescanos/laravelshoppingcart" is not present in the lock file. This usually happens when composer files are incorrectly merged or the composer.json file is manually edited. Read more about correctly resolving merge conflicts https://getcomposer.org/doc/articles/resolving-merge-conflicts.md and prefer using the "require" command over editing the composer.json file directly https://getcomposer.org/doc/03-cli.md#require-r

And when I use composer update (as first error says) it return the following error:

Your requirements could not be resolved to an installable set of packages.

Problem 1 - Root composer.json requires plescanos/laravelshoppingcart, it could not be found in any version, there may be a typo in the package name.

Potential causes:

  • A typo in the package name
  • The package is not available in a stable-enough version according to your minimum-stability setting see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
  • It's a private package and you forgot to add a custom repository to find it

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

So please if someone can help me , i'll say thanks forever

package name must be same or change your package name in your repos composer.json.

Example: xxxx = your github username

"require": {
        "darryldecode/cart": "dev-master"
 },
 "repositories": [
        {
            "type": "vcs",
            "url": "[email protected]:xxxx/laravelshoppingcart.git"
        }
    ]

Reason: In this respect, composer prioritizes private repos when updating; even if the package names are the same, it takes it into consideration first when it is found in your repo.

@plescanos

tanero avatar May 11 '24 04:05 tanero

@tanero Thanks !! is solved. So in my case final solution was:

  1. Change my composer.json

"require": { "darryldecode/cart": "dev-master" }, "repositories": [ { "type": "vcs", "url": "[email protected]:xxxx/laravelshoppingcart.git" } ]

  1. Do not use "composer install", I use "composer update" and it works fine.

Thanks again!

plescanos avatar May 11 '24 11:05 plescanos

@darryldecode

Misagh90 avatar May 18 '24 18:05 Misagh90