Closed filipz-proglove closed 9 months ago
In fact when combined with this issue :
https://github.com/barryvdh/laravel-debugbar/issues/1261
The debug bar becomes quite populated with useless warnings.
I looked at a patch for a similar Drupal-related issue and suspect that it may be simply a matter or replacing the trait name with static. I will let @jeremykenedy look at that and test the functionality.
Hi @jeremykenedy ,
Can we update this?
I checked changing public static function activity($description = null, $details = null)
to public function activity($description = null, $details = null)
inside ActivityLogger
And using it like this
//ActivityLogger::activity($description);
$this->activity($description);
Does remove the warning logs. But don't know the drawback of making this function non-static. This would be nice if we could get rid of these warnings,
Rolling into issue #166
Hello there. I am facing some warnings with this package, that I wanted to bring to attention. This wasn't the case until I updated PHP. It seems that calling some static trait methods is deprecated. As can be seen below :
PHP version :
OS :
Also affects other package by the same author -
LaravelBlocker
jeremykenedy\LaravelBlocker\App\Traits\IpAddressDetails::checkIP is deprecated, it should only be called on a class using the trait in /vendor/jeremykenedy/laravel-blocker/src/App/Traits/LaravelCheckBlockedTrait.php on line 22