|
| 1 | +--- |
| 2 | +title: WordPress Plugin Check Failure |
| 3 | +labels: bug, plugin-check, automated |
| 4 | +assignees: |
| 5 | +--- |
| 6 | + |
| 7 | +## WordPress Plugin Check Failure |
| 8 | + |
| 9 | +The WordPress Plugin Check action has identified issues with the Simple WP Optimizer plugin. |
| 10 | + |
| 11 | +### Details |
| 12 | + |
| 13 | +- **Test Date:** {{ date | date('YYYY-MM-DD HH:mm:ss') }} |
| 14 | +- **Workflow Run:** [View detailed logs]({{ env.WORKFLOW_URL }}) |
| 15 | + |
| 16 | +### Next Steps |
| 17 | + |
| 18 | +This issue has been automatically created because the WordPress Plugin Check found issues with the plugin that should be addressed. The check performed the following specific tests: |
| 19 | + |
| 20 | +#### Categories: |
| 21 | +- **Accessibility**: Checks for accessibility compliance issues |
| 22 | +- **General**: General WordPress coding standards and best practices |
| 23 | +- **Performance**: Tests that identify performance bottlenecks |
| 24 | +- **Plugin Repo**: Requirements for WordPress.org plugin repository |
| 25 | +- **Security**: Security-focused checks to identify vulnerabilities |
| 26 | + |
| 27 | +#### Specific Checks: |
| 28 | +- **i18n_usage**: Proper internationalization usage |
| 29 | +- **code_obfuscation**: Detecting potentially obfuscated code |
| 30 | +- **direct_db_queries**: Identifying direct database queries that bypass WordPress APIs |
| 31 | +- **enqueued_scripts_in_footer**: Ensuring scripts are properly enqueued in the footer |
| 32 | +- **enqueued_scripts_size**: Checking for excessively large script files |
| 33 | +- **enqueued_styles_scope**: Ensuring styles are properly scoped |
| 34 | +- **file_type**: Checking for proper file types and formats |
| 35 | +- **late_escaping**: Ensuring output is properly escaped |
| 36 | +- **localhost**: Checking for references to localhost or development environments |
| 37 | +- **no_unfiltered_uploads**: Ensuring uploads are properly filtered |
| 38 | +- **performant_wp_query_params**: Checking for inefficient WP_Query parameters |
| 39 | +- **plugin_header_text_domain**: Verifying correct text domain in plugin header |
| 40 | +- **plugin_readme**: Checking the plugin readme file format |
| 41 | +- **plugin_review_phpcs**: PHP CodeSniffer checks for WordPress standards |
| 42 | +- **plugin_updater**: Checking plugin update mechanisms |
| 43 | +- **trademarks**: Checking for potential trademark violations |
| 44 | + |
| 45 | +#### Recommended Actions: |
| 46 | + |
| 47 | +1. Review the workflow logs for specific error messages and warnings |
| 48 | +2. Address each identified issue in the plugin code |
| 49 | +3. Test locally using the [WordPress Plugin Check tool](https://github.com/WordPress/plugin-check) to verify fixes |
| 50 | +4. Submit a pull request with the necessary changes |
| 51 | + |
| 52 | +Once all issues are fixed, please close this issue and reference it in the changelog. |
| 53 | + |
| 54 | +### About WordPress Plugin Check |
| 55 | + |
| 56 | +The WordPress Plugin Check tool helps plugin authors create plugins that follow WordPress best practices. It checks for issues related to security, performance, and compatibility to ensure plugins work well in the WordPress ecosystem. |
| 57 | + |
| 58 | +--- |
0 commit comments