sc0ttkclark/papertrail

Papertrail Logging API for WordPress

Hello, it’s nice to meet you. My name is Scott. And I like pizza.

papertrail's Issues

Dies in php 8

When upgrading my server from 7.4 to PHP 8.0, I encountered this (slightly edited)
Fatal error: Uncaught ArgumentCountError: Too few arguments to function WP_Papertrail_API::error_handler(), 4 passed and exactly 5 expected in /nas/content/live/ccc/WP_Papertrail_API.php:194

I replaced, in WP_Papertrails_API.php,
this
public static function error_handler( $id, $message, $file, $line, $context )
with
public static function error_handler( $id, $message, $file, $line ) {

Seems to work, but I'm not confident enough in this solution to post a Pull Request.
See also: //https://stackoverflow.com/questions/65201307/too-few-arguments-to-function-exception-error-handler-php8

Logging all PHP errors

Thanks for putting this together!

More a question than anything else, just to check whether I'm barking up the wrong tree, if I wanted to send all PHP errors to Papertrail (and can't use the usual remote_syslog option because it's shared hosting), I would imagine I could use set_error_handler() and send errors through to WP_Papertrail_API::log()... right?

Would you suggest doing this any differently?

Reuse the socket instance

At a higher load, calling socket_create( AF_INET, SOCK_DGRAM, SOL_UDP ) for each log message will become expensive.

It would perform better to only create one socket (in a constructor, for instance) and reuse it for all log calls.