-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 Fatal Errors: don't assume set_ini() exists #7352
base: trunk
Are you sure you want to change the base?
Conversation
Hi @maltfield! 👋 Thank you for your contribution to WordPress! 💖 It looks like this is your first pull request to 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 the Core Handbook. 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 following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @maltfield. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. Core Committers: Use this line as a base for the props when committing in SVN:
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we should make any changes to this file directly, as it's a 3rd-party library... 🤔
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
Co-authored-by: Ari Stathopoulos <[email protected]>
this commit fixes bug #62693, which prevents users from uploading media to wordpress because wordpress throws a fatal error when calling 'chmod' on servers with php.ini security-hardened following best practices, which disables dangerous functions, such as exec(), chmod(), etc. * https://core.trac.wordpress.org/ticket/62693 this change doesn't make the assumption that the chmod() function is available for use; it checks it first with function_exists()
this commit fixes bug #62693, which prevents users from uploading media to wordpress because wordpress throws a fatal error when calling 'chmod' on servers with php.ini security-hardened following best practices, which disables dangerous functions, such as exec(), chmod(), etc. * https://core.trac.wordpress.org/ticket/62693 this change doesn't make the assumption that the chmod() function is available for use; it checks it first with function_exists()
I couldn't figure out how to tell GitHub to make a different PR for this and the new bug: So both of these bug fixes are combined into one PR. |
Trac ticket:
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.