Skip to content

Commit

Permalink
32bit integer workaround (#1014)
Browse files Browse the repository at this point in the history
This is a temporary workaround to hide the 32bit integer warnings that
appear when using various time related function, such as strtotime() and
mktime().

## What problem is it solving?
Hiding the warning messages from being displayed on the page.

## How is the problem addressed?
Adding an error handler to ignore warning if it matches the message "fit
in a PHP integer"

## Testing Instructions
add ?year=123 to any playground URL (e.g. /?year=123). Normally it would
display `Warning: mktime(): Epoch doesn't fit in a PHP integer in
/wordpress/wp-includes/class-wp-date-query.php on line 3`
  • Loading branch information
stoph authored Feb 8, 2024
1 parent c265d61 commit ef5ca8c
Showing 1 changed file with 14 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -1,5 +1,19 @@
<?php

/**
* This is a temporary workaround to hide the 32bit integer warnings that
* appear when using various time related function, such as strtotime and mktime.
* Examples of the warnings that are displayed:
* Warning: mktime(): Epoch doesn't fit in a PHP integer in <file>
* Warning: strtotime(): Epoch doesn't fit in a PHP integer in <file>
*/
set_error_handler(function($severity, $message, $file, $line) {
if (strpos($message, "fit in a PHP integer") !== false) {
return;
}
return false;
});

/**
* Add a notice to wp-login.php offering the username and password.
*/
Expand Down

0 comments on commit ef5ca8c

Please sign in to comment.