Fixes

Author: PDowney

.github/CODE_OF_CONDUCT.md

@@ -45,7 +45,7 @@ an individual is officially representing the community in public spaces.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the project maintainers responsible for enforcement at
-peter@visistruct.com.
+<security@enginescript.com>.
 
 Project maintainers will review and investigate all complaints, and will
 respond in a way that they deem appropriate to the circumstances.

.github/ISSUE_TEMPLATE/compatibility-test-failure.md

@@ -21,7 +21,7 @@ The automated compatibility test for PHP {{ env.PHP_VERSION }} has failed.
 
 This issue has been automatically created because the EngineScript Site Optimizer plugin failed to load properly with PHP {{ env.PHP_VERSION }}. This could indicate compatibility issues that need to be addressed.
 
-#### Recommended Actions:
+#### Recommended Actions
 
 1. Review the workflow logs for specific error messages
 2. Check for PHP {{ env.PHP_VERSION }} specific syntax or function compatibility issues

.github/ISSUE_TEMPLATE/phpcs-failure.md

@@ -11,6 +11,7 @@ assignees: []
 The PHPCS (PHP CodeSniffer) check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
@@ -19,12 +20,14 @@ The PHPCS (PHP CodeSniffer) check has failed for the repository.
 The code does not meet WordPress coding standards as defined by PHPCS.
 
 **What needs to be done:**
+
 1. Review the PHPCS output in the failed workflow run
 2. Fix coding standard violations in the code
 3. Ensure all PHP files follow WordPress coding standards
 4. Test locally with: `composer run phpcs`
 
 **Resources:**
+
 - [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
 - [PHP CodeSniffer Documentation](https://github.com/squizlabs/PHP_CodeSniffer)
 

.github/ISSUE_TEMPLATE/phpmd-failure.md

@@ -11,6 +11,7 @@ assignees: []
 The PHPMD (PHP Mess Detector) check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
@@ -19,6 +20,7 @@ The PHPMD (PHP Mess Detector) check has failed for the repository.
 The code has quality issues detected by PHPMD analysis.
 
 **What needs to be done:**
+
 1. Review the PHPMD output in the failed workflow run
 2. Address code quality issues such as:
    - Complex methods that should be simplified
@@ -29,6 +31,7 @@ The code has quality issues detected by PHPMD analysis.
 3. Test locally with: `composer run phpmd`
 
 **Resources:**
+
 - [PHPMD Documentation](https://phpmd.org/)
 - [PHPMD Rules](https://phpmd.org/rules/index.html)
 

.github/ISSUE_TEMPLATE/phpstan-failure.md

@@ -13,9 +13,11 @@ assignees: []
 **Date:** {{ date | date('YYYY-MM-DD') }}
 
 ### Description
+
 The PHPStan for WordPress static analysis check has failed during the automated testing process.
 
 ### What happened?
+
 PHPStan for WordPress detected potential code issues during static analysis. This could indicate:
 
 - Type safety issues specific to WordPress APIs
@@ -24,13 +26,15 @@ PHPStan for WordPress detected potential code issues during static analysis. Thi
 - Incorrect usage of WordPress functions or hooks
 
 ### Next Steps
+
 1. Review the workflow logs at the link above
 2. Check the specific PHPStan error messages
 3. Fix any identified code issues
 4. Ensure WordPress-specific type annotations are correct
 5. Re-run the workflow to verify fixes
 
 ### Additional Information
+
 - This check uses WordPress-specific PHPStan rules
 - The analysis helps catch WordPress-related coding issues early
 - Consider updating code to follow WordPress best practices

.github/ISSUE_TEMPLATE/plugin-check-failure.md

@@ -19,14 +19,16 @@ The WordPress Plugin Check action has identified issues with the EngineScript Si
 
 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:
 
-#### Categories:
+#### Categories
+
 - **Accessibility**: Checks for accessibility compliance issues
 - **General**: General WordPress coding standards and best practices
 - **Performance**: Tests that identify performance bottlenecks
 - **Plugin Repo**: Requirements for WordPress.org plugin repository
 - **Security**: Security-focused checks to identify vulnerabilities
 
-#### Specific Checks:
+#### Specific Checks
+
 - **i18n_usage**: Proper internationalization usage
 - **code_obfuscation**: Detecting potentially obfuscated code
 - **direct_db_queries**: Identifying direct database queries that bypass WordPress APIs
@@ -44,7 +46,7 @@ This issue has been automatically created because the WordPress Plugin Check fou
 - **plugin_updater**: Checking plugin update mechanisms
 - **trademarks**: Checking for potential trademark violations
 
-#### Recommended Actions:
+#### Recommended Actions
 
 1. Review the workflow logs for specific error messages and warnings
 2. Address each identified issue in the plugin code

.github/ISSUE_TEMPLATE/psalm-failure.md

@@ -11,6 +11,7 @@ assignees: []
 The Psalm static analysis check has failed for the repository.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
@@ -19,6 +20,7 @@ The Psalm static analysis check has failed for the repository.
 Psalm has detected potential issues in the code through static analysis.
 
 **What needs to be done:**
+
 1. Review the Psalm output in the failed workflow run
 2. Address static analysis issues such as:
    - Type errors
@@ -29,6 +31,7 @@ Psalm has detected potential issues in the code through static analysis.
 3. Test locally with: `composer run psalm`
 
 **Resources:**
+
 - [Psalm Documentation](https://psalm.dev/)
 - [Psalm Error Levels](https://psalm.dev/docs/running_psalm/error_levels/)
 

.github/ISSUE_TEMPLATE/security-failure.md

@@ -11,6 +11,7 @@ assignees: []
 A security vulnerability has been detected in the project dependencies.
 
 **Failure Details:**
+
 - **PHP Version:** {{ env.PHP_VERSION }}
 - **Workflow Run:** [View Details]({{ env.WORKFLOW_URL }})
 - **Run ID:** {{ env.RUN_ID }}
@@ -19,6 +20,7 @@ A security vulnerability has been detected in the project dependencies.
 The security checker has identified known vulnerabilities in one or more of the project's dependencies.
 
 **What needs to be done:**
+
 1. Review the security check output in the failed workflow run
 2. Identify which dependencies have vulnerabilities
 3. Update vulnerable dependencies to secure versions
@@ -31,6 +33,7 @@ The security checker has identified known vulnerabilities in one or more of the
 **Priority:** This is a security issue and should be addressed immediately.
 
 **Resources:**
+
 - [Symfony Security Checker](https://github.com/FriendsOfPHP/security-advisories)
 - [WordPress Security Best Practices](https://developer.wordpress.org/plugins/security/)
 

.github/ISSUE_TEMPLATE/vip-phpcs-failure.md

@@ -19,18 +19,21 @@ The WordPress VIP coding standards check failed during the automated workflow. T
 The WordPress VIP Go coding standards check covers the following areas:
 
 **Enterprise Platform Requirements:**
+
 - File system operation restrictions (VIP platform limitations)
 - Performance and caching best practices for high-traffic sites
 - Security vulnerabilities specific to enterprise WordPress environments
 - User experience guidelines for enterprise-level WordPress
 
 **Performance and Caching:**
+
 - Uncached function usage patterns
 - Database query optimization
 - Remote data fetching best practices
 - Resource-heavy operation detection
 
 **VIP-Specific Security:**
+
 - File operation security in restricted environments
 - Admin bar removal restrictions for VIP support users
 - Cookie and caching constraint validations
@@ -39,6 +42,7 @@ The WordPress VIP Go coding standards check covers the following areas:
 ### Important Notes
 
 **VIP Standards Context:**
+
 - Many VIP standards are specific to the WordPress VIP hosting platform
 - Not all VIP recommendations may apply to standard WordPress installations
 - Some restrictions are platform-specific (e.g., file system limitations)

.github/ISSUE_TEMPLATE/wp-dependencies-failure.md

@@ -13,9 +13,11 @@ assignees: []
 **Date:** {{ date | date('YYYY-MM-DD') }}
 
 ### Description
+
 The WordPress dependencies monitoring check has failed during the automated testing process.
 
 ### What happened?
+
 The WordPress dependencies monitoring action detected issues with dependencies. This could indicate:
 
 - Outdated WordPress core dependencies
@@ -25,12 +27,14 @@ The WordPress dependencies monitoring action detected issues with dependencies.
 - Plugin dependency conflicts
 
 ### Potential Issues
+
 - **WordPress Core Updates:** WordPress core may have been updated with breaking changes
 - **Plugin Dependencies:** Dependencies used by the plugin may be outdated or incompatible
 - **API Changes:** WordPress APIs used by the plugin may have changed
 - **Deprecated Functions:** The plugin may be using deprecated WordPress functions
 
 ### Next Steps
+
 1. Review the workflow logs at the link above
 2. Check for specific dependency warnings or errors
 3. Update WordPress core compatibility if needed
@@ -40,6 +44,7 @@ The WordPress dependencies monitoring action detected issues with dependencies.
 7. Re-run the workflow to verify fixes
 
 ### Additional Information
+
 - This monitoring helps ensure WordPress ecosystem compatibility
 - Regular dependency monitoring prevents future compatibility issues
 - Consider updating minimum WordPress version requirements if needed