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

Fix PHP8.1 throw 'Deprecated' #2248

Closed
wants to merge 2 commits into from
Closed

Fix PHP8.1 throw 'Deprecated' #2248

wants to merge 2 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Jan 30, 2022

In PHP8.1,Implicit incompatible float to int conversion is deprecated.
Because of it, wordpress will throw a PHP Deprecated in page footer.

Trac ticket: https://core.trac.wordpress.org/ticket/54996

In PHP8.1,Implicit incompatible float to int conversion is deprecated.
Because of it, wordpress will throw a PHP Deprecated in page footer.
@github-actions
Copy link

Hi @devhaozi! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in this blog post.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

}
public function get( $num ) {
if ( isset( $this->cache[ (int) $num ] ) ) {
return $this->cache[ $num ];
Copy link
Contributor

@costdev costdev Jan 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this one also be cast to (int)?

If so, can we add $num = (int) $num at the start of the get() method instead of repeating the (int) cast?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can. Good idea!

Copy link
Member

@jrfnl jrfnl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've also left a comment in the Trac ticket: adding the (int) cast is hiding the actual problem, not fixing it.

The origin of the notice should be traced back and the problem should be solved at the source, not here. I.e. it should be solved at the function call which is passing a float instead of an int.

@ghost ghost closed this by deleting the head repository Oct 11, 2022
This pull request was closed.
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.

3 participants