Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

32bit integer workaround #1014

Merged
merged 1 commit into from
Feb 8, 2024
Merged

32bit integer workaround #1014

merged 1 commit into from
Feb 8, 2024

Conversation

stoph
Copy link
Contributor

@stoph stoph commented Feb 8, 2024

What is this PR doing?

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

This is a temporary workaround to hide the 32bit integer warnings that appear when using various time related function, such as strtotime and mktime.
@stoph stoph changed the title 32bit integer workaround (#1013) 32bit integer workaround Feb 8, 2024
@adamziel
Copy link
Collaborator

adamziel commented Feb 8, 2024

Lovely, thank you @stoph!

@adamziel adamziel merged commit ef5ca8c into WordPress:trunk Feb 8, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants