Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

vincej's avatar
Level 15

@jaytee v 5.8

@connecteev I'm going for a fresh install on v 6.0 .... that's also proving to be a pain in the ass. Composer keeps saying that it wants : carbon v 1.2 ... WTF I can't win. I'm going to post a new question on this.

Jaytee's avatar
Jaytee
Best Answer
Level 39

If you're planning on staying on 5.8, remove the vendor folder and run composer install to get fresh dependencies. Could very well force the application to start behaving again

For Laravel 6, pretty sure Carbon 2 is required. Carbon 1 was deprecated. So just overwrite it in your composer.json, or port everything over to a fresh application. I prefer the latter

Sinnbeck's avatar

You could put the project on github and allow us to have a quick look. Maybe someone will spot something new

vincej's avatar
Level 15

Hallelujah!!! It is fixed!! I followed @jaytee suggestion. Deleted the vendor file and did a composer install of 5.8. And now it is behaving again !!

Thank you all for your recommendations and help - I would never have got there on my own.

Now I am going to upgrade to v 6.0 fingers crossed ! :o)

Cheers From Canada !

Jaytee's avatar

@vincej I can't believe we all didn't think of this in the first place haha.

Usually if we all have a problem after clearing cache, the first resort is to install fresh dependencies.

Glad it's working. Now just one more complicated thread left open to deal with ;)

Previous

Please or to participate in this conversation.