herregroen

Results 12 issues of herregroen

The `Ruckusing_Util_Logger` is not PSR compatible ( see https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md ). It's `log` method should accept a log level as the first argument and the message as the second argument. Because...

:warning: First the revert done in https://github.com/Yoast/wordpress-seo/pull/18784 needs to be undone :warning: This PR also moves the `getMemoizedFindCustomFields` to a separate file to be reused. So after undoing the above...

## Is your feature request related to a problem? `WP_Error` is the WordPress equivalent of an exception. It's completely expected and accepted that when you call a function that throws...

Component: Extras
Type: Enhancement
Focus: WP interoperability

**Is your feature request related to a problem? Please describe.** Currently only the PDO extension is supported. This means that queries made with the [mysqli](https://www.php.net/manual/en/book.mysqli.php) extension are not being measured....

enhancement
agent-php
PHP specific technology
8.4-candidate

## Context * Fixes ESLint errors showing up in every PR. ## Summary This PR can be summarized in the following changelog entry: * Fixes ESLint errors in the CI...

changelog: non-user-facing

## Explanation Currently there's a lot of complexity around linking the monorepo in Travis to ensure Travis is using the intended versions of our packages when testing. The root cause...

In PHP the [session functions](https://www.php.net/manual/en/ref.session.php) by default store session date in files. On many WordPress hosts creating files in this manner can lead to errors, either due to the amount...

Type: enhancement
Status: wait for upstream/WordPressCS

In our integrations directory we have all our classes that hook into WordPress filters and actions. As any exceptions thrown here in public functions wouldn't be able to be caught...

Type: enhancement
Status: wait for upstream/WordPressCS

With the 14.0 release we ran into unfortunate issues where we were not catching all our own exceptions, thus leading to fatals. Because of this we'd like to explore options...

Status: blocked
Status: needs investigation

For the parent trac issue please see: https://meta.trac.wordpress.org/ticket/3063. In order to add the Gutenberg JSDoc into the code reference we'd want to be able to differentiate between JS and PHP...