-
Notifications
You must be signed in to change notification settings - Fork 83
Check Direct File Access #1133
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
base: trunk
Are you sure you want to change the base?
Check Direct File Access #1133
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
| * @param string $plugin_path The plugin path. | ||
| * @return bool True if the file is uninstall.php, false otherwise. | ||
| */ | ||
| private function is_uninstall_file( $file, $plugin_path ) { |
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.
Logic for checking uninstall file seems to complex. In "Plugin_Uninstall_Check.php" it is pretty simple. What do you think?
| * | ||
| * Every check must have at least one category. | ||
| * | ||
| * @since n.e.x.t |
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.
| * @since n.e.x.t | |
| * @since 1.8.0 |
This check is based on the code that @frantorres created for the Internal Scanner.
There are many cases based on past experience.
Fixes #603