Laravel 5.8 not suported

[ddjikic]

installation fails on laravel 5.8.16

To Reproduce Steps to reproduce the behavior:

1. install fresh laravel
2. run "composer require grafite/cms"

Expected behavior to install

Desktop (please complete the following information):

• OS: Linux

Problem 1 - Conclusion: don't install grafite/cms v3.2.2 - Conclusion: don't install grafite/cms v3.2.1 - Conclusion: remove laravel/framework v5.8.16 - Installation request for grafite/cms ^3.2 -> satisfiable by grafite/cms[v3.2.0, v3.2.1, v3.2.2]. - Conclusion: don't install laravel/framework v5.8.16 - grafite/cms v3.2.0 requires illuminate/support 5.7.* -> satisfiable by illuminate/support[5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9].

[phpSal]

Same issue with laravel 5.8.24.

I even downgraded illuminate/support to 5.7.17

Still same error as laravel same version.

Platform: windows and wamp

[jmazier-j2d]

Same issue on Laravel 5.8 with Grafite 3.2.2

EDIT (made it work with laravel 5.8) : End up forking the project (+ dep. such as crypto, builder or formMaker had to be forked and slightly modified). Is someone still maitaining this project ? Is it worth submiting a PR for CMS update to laravel 5.8 ? Not so many changes, from I've tested so far, it has to do with customs directives being declared within Provider's register() method and not boot() (as it is required with laravel 5.8 now).

[sdebarun]

I am facing the same issue. procedure to replicate same as the process as @ddjikic. My laravel version is 5.8.30.does that mean we cannot use this package with lates laravel releases??

[CarlonchoMaster]

I am also interested in continuing this project !!

[IlyasMakari]

Is there a temporary fix in the meantime? Is it possible to trick composer into thinking it's Laravel 5.7?

[jmazier-j2d]

Is there a temporary fix in the meantime? Is it possible to trick composer into thinking it's Laravel 5.7?

The only fix I found so far was to fork the project and to make the modification described above in my previous comment. If you need help, I can provide the modifications I've made but I had no time to test in details. Most of it is working so far tho ..