Replies: 4 comments 3 replies
-
@pitylee I've suddenly got the same issue. No idea how to solve it After looking into this for a while it was pretty clear to me that this library (ignition) does not have any coding bugs. Yet for some reason composer's autoload could never find this unless I included it directly. I tried blowing away composer.lock and the vendor file to no avail. The only thing that worked was a composer self-upgrade (from 2.2.2 to 2.2.3) then blowing away composer.lock and the vendor file but I see nothing in the change log about this in composer.. Anyways after I did that I wasn't able to replicate it. My suggestion to others experiencing this is to do the following:
|
Beta Was this translation helpful? Give feedback.
-
We were getting this error in our local development environments using Laravel 8 and checking this package's readme I found:
Removing this plugin via |
Beta Was this translation helpful? Give feedback.
-
Discussed in #443
Originally posted by pitylee December 20, 2021
Hello,
Anyobody met this?
I have the basic configuration which comes with Laravel, and the logging config is the default one.
By simply using the Laravel Log::info() the following will happen every time:
Beta Was this translation helpful? Give feedback.
All reactions