wpallstars/wp-fix-plugin-does-not-exist-notices
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Initial commit after renaming from fix-plugin-does-not-exist-notices to wp-fix-plugin-does-not-exist-notices

Browse Source
This commit is contained in:
Marcus Quinn
2025-04-12 22:53:28 +01:00
commit f315c943e5
49 changed files with 4200 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

267
.ai-assistant.md Normal file
View File

@ -0,0 +1,267 @@
# AI Assistant Guide for WordPress Plugin Development
This guide helps AI assistants understand the project structure, workflows, and best practices for this repository.
## AI IDE Configuration
This repository includes configuration files for various AI-powered development tools:
- `.aiconfig` - General AI configuration (model preferences, ignore patterns)
- `.augmentignore` - Ignore patterns for Augment
- `.cursorignore` - Ignore patterns for Cursor
- `.v0ignore` - Ignore patterns for v0
- `.windsurfignore` - Ignore patterns for Windsurf
- `.clinerc` - Configuration for Cline
- `.rooignore` - Ignore patterns for Roo
- `.geminiignore` - Ignore patterns for Gemini Code Assist
- `.loveablerc` - Configuration for Loveable
- `.boltignore` - Ignore patterns for Bolt
- `.codyignore` - Ignore patterns for Cody
- `.continuerc` - Configuration for Continue
All these files respect `.gitignore` patterns and only include additional tool-specific patterns. The `!` prefix can be used in these files to include files that are excluded by `.gitignore`.
## Project Overview
- **Plugin Name**: [PLUGIN_NAME]
- **Repository**: [REPOSITORY_URL]
- **Description**: [PLUGIN_DESCRIPTION]
This section should be updated with your specific plugin information. The current implementation is for the "Fix 'Plugin file does not exist.' Notices" plugin, which adds missing plugins to the plugins list with a "Remove Notice" link to clean up invalid plugin entries and remove error notices.
## Reference Plugins
The `reference-plugins/` directory contains plugins that can be used for reference or inspiration. When developing new features or improving existing ones, you should:
1. Examine these reference plugins for best practices in code structure, organization, and implementation
2. Look for patterns in how they handle similar functionality
3. Consider their approach to user interface design and user experience
4. Study their documentation style and thoroughness
These plugins are not part of the codebase and are ignored by Git, but they provide valuable examples of WordPress plugin development standards and techniques.
## Version Management
### Version Numbering Convention
We follow [Semantic Versioning](https://semver.org/):
- **MAJOR.MINOR.PATCH** (e.g., 1.6.0)
- **MAJOR**: Breaking changes
- **MINOR**: New features, non-breaking
- **PATCH**: Bug fixes, non-breaking
### When to Increment Version Numbers
- **PATCH** (1.6.0 → 1.6.1):
- Bug fixes
- Small text changes
- Minor improvements that don't add new features
- **MINOR** (1.6.0 → 1.7.0):
- New features
- Significant improvements to existing functionality
- Deprecation of features (but not removal)
- **MAJOR** (1.6.0 → 2.0.0):
- Breaking changes
- Removal of features
- Major architectural changes
### Version Update Checklist
When updating the version number, always update these files:
1. `wp-fix-plugin-does-not-exist-notices.php` (Plugin header)
2. `CHANGELOG.md` (Add new version section)
3. `readme.txt` (Stable tag and Changelog section)
4. `README.md` (Update Changelog section to match readme.txt)
5. Update `FPDEN_VERSION` constant in the main plugin file
**IMPORTANT**: Always ensure README.md is kept in sync with readme.txt for consistency across platforms.
## Git Workflow
### Branch Naming Convention
- Feature branches: `feature/descriptive-name`
- Bug fix branches: `fix/issue-description`
- Release branches: `v{MAJOR}.{MINOR}.{PATCH}`
### Commit Message Guidelines
- Use present tense ("Add feature" not "Added feature")
- Start with a verb
- Keep the first line under 50 characters
- Reference issues when relevant: "Fix #123: Resolve plugin detection issue"
### Pre-Release Checklist
Before creating a new release, verify the following:
- [ ] Determine the correct version increment (MAJOR, MINOR, or PATCH) based on the changes
- [ ] Ensure all changes are documented in CHANGELOG.md
- [ ] Verify all code changes are tested and working correctly
- [ ] Check that all files are properly formatted and follow WordPress coding standards
- [ ] Ensure Git Updater configuration is correct (if applicable)
### Release Process
1. Create a new branch for the version: `git checkout -b v{MAJOR}.{MINOR}.{PATCH}`
2. Update version numbers in ALL required files:
- `wp-fix-plugin-does-not-exist-notices.php` (Plugin header)
- `FPDEN_VERSION` constant in the main plugin file
- `readme.txt` (Stable tag)
- `README.md` (Ensure changelog is updated)
- `languages/wp-fix-plugin-does-not-exist-notices.pot` (Project-Id-Version)
- Any other files that reference the version number
3. Update CHANGELOG.md with all changes
4. Update readme.txt changelog section
5. Update README.md changelog section to match readme.txt
6. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
7. Test changes locally on the version branch
8. When satisfied with testing, merge to main:
```
git checkout main
git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
```
9. Push main to all remotes:
```
git push github main
git push gitea main
```
10. Create and push a tag to trigger the GitHub Actions workflow:
```
git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
```
11. Verify the GitHub Actions workflow completes successfully
## Build Process
The build process is handled by `build.sh`:
1. Updates version numbers
2. Installs composer dependencies
3. Copies files to build directory
4. Creates ZIP file
To manually build the plugin:
```
./build.sh {MAJOR}.{MINOR}.{PATCH}
```
## Remote Repositories
The plugin is hosted on multiple repositories:
- GitHub: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
- Gitea: https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices
- WordPress.org: https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/
Always push changes to all remotes to keep them in sync.
## GitHub Actions
The repository uses GitHub Actions for automated builds and deployments:
- Triggered by tags matching the pattern `v*`
- Builds the plugin
- Creates a GitHub release
- Deploys to WordPress.org
## Testing Guidelines
Before releasing:
1. Test with the latest WordPress version
2. Test with PHP 7.0+ (minimum supported version)
3. Verify all features work as expected
4. Check for any PHP warnings or notices
## Common Tasks for AI Assistants
### Creating a New Release
```
# 1. Create a new branch
git checkout main
git checkout -b v1.7.0
# 2. Update version numbers in ALL required files
# - wp-fix-plugin-does-not-exist-notices.php
# - CHANGELOG.md
# - readme.txt
# - README.md
# - languages/wp-fix-plugin-does-not-exist-notices.pot
# - FPDEN_VERSION constant
# 3. Commit changes
git add .
git commit -m "Prepare release v1.7.0"
# 4. Test changes locally on the version branch
# (Run tests, verify functionality)
# 5. Merge to main when ready
git checkout main
git merge v1.7.0 --no-ff
# 6. Push main to remotes
git push github main
git push gitea main
# 7. Create and push tag
git tag -a v1.7.0 -m "Release version 1.7.0"
git push github refs/tags/v1.7.0
git push gitea refs/tags/v1.7.0
```
### Adding a New Feature
```
# 1. Create feature branch from main
git checkout main
git checkout -b feature/new-feature-name
# 2. Make changes and commit
git add .
git commit -m "Add new feature"
# 3. Test locally
# (Run tests, verify functionality)
# 4. When ready for release, merge to a version branch
git checkout -b v1.7.0
git merge feature/new-feature-name --no-ff
# 5. Continue with the release process
# (Update version numbers, etc.)
```
### Fixing a Bug
```
# 1. Create bugfix branch from main
git checkout main
git checkout -b fix/bug-description
# 2. Make changes and commit
git add .
git commit -m "Fix #123: Fix bug description"
# 3. Test locally
# (Run tests, verify functionality)
# 4. When ready for release, merge to a version branch
git checkout -b v1.6.5
git merge fix/bug-description --no-ff
# 5. Continue with the release process
# (Update version numbers, etc.)
```
### Testing a Previous Version
```
# Checkout a specific tag for testing
git checkout v1.6.3
# Or create a test branch from a specific tag
git checkout v1.6.3 -b test/some-feature
```

12
.ai-workflows/README.md Normal file
View File

@ -0,0 +1,12 @@
# AI Workflows
This directory contains workflow documentation for AI assistants working with this repository.
## Contents
- **bug-fixing.md**: Guidelines for identifying and fixing bugs in the codebase
- **code-review.md**: Standards and procedures for reviewing code changes
- **feature-development.md**: Process for developing new features
- **release-process.md**: Steps for preparing and publishing new releases
These documents help ensure consistent quality and approach when using AI tools to assist with development tasks.

195
.ai-workflows/bug-fixing.md Normal file
View File

@ -0,0 +1,195 @@
# Bug Fixing Guide for AI Assistants
This document provides guidance for AI assistants to help with bug fixing for the Fix Plugin Does Not Exist Notices plugin.
## Bug Fixing Workflow
### 1. Create a Bug Fix Branch
Always start by creating a bug fix branch from the main branch:
```bash
git checkout main
git pull github main
git checkout -b fix/bug-description
```
Use a descriptive name that clearly indicates what bug is being fixed.
### 2. Understand the Bug
Before fixing a bug, make sure you understand:
- What is the expected behavior?
- What is the actual behavior?
- What are the steps to reproduce the bug?
- What is the impact of the bug?
- What is the root cause of the bug?
### 3. Fix the Bug
When fixing a bug:
- Make minimal changes necessary to fix the bug
- Avoid introducing new features while fixing bugs
- Maintain backward compatibility
- Add appropriate comments explaining the fix
- Consider adding tests to prevent regression
### 4. Update Documentation
Update relevant documentation to reflect the bug fix:
- Add a description to CHANGELOG.md under an "Unreleased" section
- Update readme.txt if the bug fix affects user-facing functionality
### 5. Testing
Test the bug fix thoroughly:
- Verify that the bug is fixed
- Ensure no regression in related functionality
- Test with the latest WordPress version
- Test with the minimum supported WordPress version (5.0)
- Test with PHP 7.0+ (minimum supported version)
### 6. Commit Changes
Make atomic commits with clear messages:
```bash
git add .
git commit -m "Fix #123: Brief description of the bug fix"
```
If there's an issue number, reference it in the commit message.
### 7. Prepare for Release
When the bug fix is ready to be released:
1. Create a version branch for the release:
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
2. Merge your bug fix branch into the version branch:
```bash
git merge fix/bug-description --no-ff
```
3. Update version numbers and changelog entries
4. Follow the standard release process from this point
### 8. Push to Remote (Optional for Collaboration)
If you need to collaborate with others on the bug fix before it's ready for release:
```bash
git push github HEAD:fix/bug-description
git push gitea HEAD:fix/bug-description
```
### 9. Create Pull Request (Optional)
If the repository uses pull requests for code review, create a pull request from the bug fix branch to the version branch.
## Determining Version Increment
After fixing a bug, determine the appropriate version increment:
- **PATCH** (e.g., 1.6.0 → 1.6.1): For most bug fixes that don't change functionality
- **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
- **MINOR** (e.g., 1.6.0 → 1.7.0): For bug fixes that introduce new features or significant changes
- **MAJOR** (e.g., 1.6.0 → 2.0.0): For bug fixes that introduce breaking changes
## Testing Previous Versions
To test a previous version of the plugin:
```bash
# Checkout a specific tag for testing
git checkout v{MAJOR}.{MINOR}.{PATCH}
# Or create a test branch from a specific tag
git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
```
## Hotfix Process
For critical bugs that need immediate fixing in a released version:
### 1. Create a Hotfix Branch
```bash
git checkout v{MAJOR}.{MINOR}.{PATCH}
git checkout -b hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 2. Fix the Issues
Apply the minimal fix necessary to address the critical issue.
### 3. Update Version Numbers
Increment the PATCH version and update all version numbers:
- Main plugin file (fix-plugin-does-not-exist-notices.php)
- FPDEN_VERSION constant
- CHANGELOG.md
- readme.txt
- README.md
- languages/fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
### 4. Commit and Push
```bash
git add .
git commit -m "Hotfix: Brief description of the critical bug fix"
git push github HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 5. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH+1} -m "Hotfix release version {MAJOR}.{MINOR}.{PATCH+1}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
```
## Common Bug Types and Fixing Strategies
### WordPress Compatibility Issues
- Test with the specific WordPress version where the issue occurs
- Check for deprecated functions or hooks
- Review WordPress changelog for relevant changes
### PHP Compatibility Issues
- Test with the specific PHP version where the issue occurs
- Check for deprecated PHP functions or features
- Use appropriate polyfills if necessary
### JavaScript Issues
- Test in different browsers
- Check for browser console errors
- Consider browser-specific workarounds if necessary
### CSS Issues
- Test in different browsers and screen sizes
- Use browser developer tools to inspect elements
- Consider browser-specific workarounds if necessary
### Database Issues
- Use proper database prefixing
- Sanitize database inputs
- Use prepared statements for queries
- Consider database version differences

163
.ai-workflows/code-review.md Normal file
View File

@ -0,0 +1,163 @@
# Code Review Guide for AI Assistants
This document provides guidance for AI assistants to help with code review for the Fix Plugin Does Not Exist Notices plugin.
## Code Review Checklist
When reviewing code, check for the following:
### Functionality
- [ ] Does the code work as expected?
- [ ] Does it handle edge cases appropriately?
- [ ] Are there any logical errors?
- [ ] Is error handling implemented properly?
### Code Quality
- [ ] Does the code follow WordPress coding standards?
- [ ] Is the code well-organized and easy to understand?
- [ ] Are there any code smells (duplicate code, overly complex functions, etc.)?
- [ ] Are functions and variables named appropriately?
- [ ] Are there appropriate comments and documentation?
### Security
- [ ] Is user input properly validated and sanitized?
- [ ] Is output properly escaped?
- [ ] Are capability checks used for user actions?
- [ ] Are nonces used for form submissions?
- [ ] Are there any potential SQL injection vulnerabilities?
- [ ] Are there any potential XSS vulnerabilities?
### Performance
- [ ] Are there any performance bottlenecks?
- [ ] Are database queries optimized?
- [ ] Is caching used appropriately?
- [ ] Are assets (CSS, JS) properly enqueued?
### Compatibility
- [ ] Is the code compatible with the minimum supported WordPress version (5.0)?
- [ ] Is the code compatible with the minimum supported PHP version (7.0)?
- [ ] Are there any browser compatibility issues?
- [ ] Are there any conflicts with other plugins?
### Internationalization
- [ ] Are all user-facing strings translatable?
- [ ] Is the correct text domain used?
- [ ] Are translation functions used correctly?
### Accessibility
- [ ] Does the code follow accessibility best practices?
- [ ] Are ARIA attributes used appropriately?
- [ ] Is keyboard navigation supported?
- [ ] Is screen reader support implemented?
## Code Review Process
### 1. Understand the Context
Before reviewing code, understand:
- What problem is the code trying to solve?
- What are the requirements?
- What are the constraints?
### 2. Review the Code
Review the code with the checklist above in mind.
### 3. Provide Feedback
When providing feedback:
- Be specific and clear
- Explain why a change is needed
- Provide examples or suggestions when possible
- Prioritize feedback (critical issues vs. minor improvements)
- Be constructive and respectful
### 4. Follow Up
After the code has been updated:
- Review the changes
- Verify that issues have been addressed
- Provide additional feedback if necessary
## Common Issues to Look For
### PHP Issues
- Undefined variables or functions
- Incorrect function parameters
- Missing return statements
- Improper error handling
- Inefficient loops or conditionals
- Hardcoded values that should be configurable
### WordPress-Specific Issues
- Incorrect hook usage
- Missing or incorrect nonces
- Missing capability checks
- Direct database queries instead of using WordPress functions
- Improper enqueuing of scripts and styles
- Not using WordPress functions for common tasks
### JavaScript Issues
- Undefined variables or functions
- Event listener memory leaks
- jQuery conflicts
- Browser compatibility issues
- Missing error handling
### CSS Issues
- Browser compatibility issues
- Specificity issues
- Unused styles
- Overriding WordPress admin styles inappropriately
## Example Feedback
### Good Feedback Example
```
In function `handle_remove_reference()`:
1. The nonce check is missing, which could lead to CSRF vulnerabilities.
Consider adding:
```php
if (!isset($_GET['_wpnonce']) || !wp_verify_nonce($_GET['_wpnonce'], 'fpden_remove_reference')) {
wp_die(__('Security check failed.', 'fix-plugin-does-not-exist-notices'));
}
```
2. The user capability check should be more specific. Instead of:
```php
if (!current_user_can('manage_options')) {
```
Consider using:
```php
if (!current_user_can('activate_plugins')) {
```
This is more appropriate for the action being performed.
3. The success message should be translatable:
```php
// Change this:
add_settings_error('fpden', 'fpden_removed', 'Plugin reference removed successfully.', 'updated');
// To this:
add_settings_error('fpden', 'fpden_removed', __('Plugin reference removed successfully.', 'fix-plugin-does-not-exist-notices'), 'updated');
```
```
### Poor Feedback Example
```
This code has security issues and doesn't follow best practices. Fix it.
```

152
.ai-workflows/feature-development.md Normal file
View File

@ -0,0 +1,152 @@
# Feature Development Guide for AI Assistants
This document provides guidance for AI assistants to help with feature development for the Fix Plugin Does Not Exist Notices plugin.
## Feature Development Workflow
### 1. Create a Feature Branch
Always start by creating a feature branch from the main branch:
```bash
git checkout main
git pull github main
git checkout -b feature/descriptive-name
```
Use a descriptive name that clearly indicates what the feature is about.
### 2. Implement the Feature
When implementing a new feature:
- Follow WordPress coding standards
- Ensure all strings are translatable
- Add appropriate comments
- Consider performance implications
- Maintain backward compatibility
- Review reference plugins in the `reference-plugins/` directory for inspiration and best practices
### 3. Update Documentation
Update relevant documentation to reflect the new feature:
- Add a description to CHANGELOG.md under an "Unreleased" section
- Update readme.txt if the feature affects user-facing functionality
- Update inline documentation/comments
- Remember that any feature addition will require a version increment in all relevant files
### 4. Testing
Test the feature thoroughly:
- Test with the latest WordPress version
- Test with the minimum supported WordPress version (5.0)
- Test with PHP 7.0+ (minimum supported version)
- Test in different environments (if possible)
### 5. Commit Changes
Make atomic commits with clear messages:
```bash
git add .
git commit -m "Add feature: descriptive name"
```
### 6. Prepare for Release
When the feature is ready to be released:
1. Create a version branch for the release:
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
2. Merge your feature branch into the version branch:
```bash
git merge feature/descriptive-name --no-ff
```
3. Update version numbers and changelog entries
4. Follow the standard release process from this point
### 7. Push to Remote (Optional for Collaboration)
If you need to collaborate with others on the feature before it's ready for release:
```bash
git push github HEAD:feature/descriptive-name
git push gitea HEAD:feature/descriptive-name
```
### 8. Create Pull Request (Optional)
If the repository uses pull requests for code review, create a pull request from the feature branch to the version branch.
## Code Standards and Best Practices
### PHP Coding Standards
- Follow [WordPress PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
- Use tabs for indentation, not spaces
- Use proper naming conventions:
- Class names: `Class_Name`
- Function names: `function_name`
- Variable names: `$variable_name`
### JavaScript Coding Standards
- Follow [WordPress JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
- Use tabs for indentation, not spaces
- Use proper naming conventions:
- Function names: `functionName`
- Variable names: `variableName`
### Internationalization (i18n)
- Wrap all user-facing strings in appropriate translation functions:
- `__()` for simple strings
- `_e()` for echoed strings
- `esc_html__()` for escaped strings
- `esc_html_e()` for escaped and echoed strings
- Always use the plugin's text domain: `fix-plugin-does-not-exist-notices`
### Security Best Practices
- Validate and sanitize all input
- Escape all output
- Use nonces for form submissions
- Use capability checks for user actions
## Feature Types and Implementation Guidelines
### Admin Interface Features
When adding features to the admin interface:
- Use WordPress admin UI components for consistency
- Follow WordPress admin UI patterns
- Ensure accessibility compliance
- Add appropriate help text
### Plugin Functionality Features
When adding core functionality:
- Ensure compatibility with WordPress hooks system
- Consider performance impact
- Maintain backward compatibility
- Add appropriate error handling
### Integration Features
When adding integration with other plugins or services:
- Make integrations optional when possible
- Check if the integrated plugin/service is available before using it
- Provide fallback functionality when the integration is not available
- Document the integration requirements

226
.ai-workflows/release-process.md Normal file
View File

@ -0,0 +1,226 @@
# Release Process for AI Assistants
This document provides step-by-step instructions for AI assistants to help with the release process for the Fix Plugin Does Not Exist Notices plugin.
## Pre-Release Checklist
- [ ] All features for this release are complete
- [ ] All bug fixes for this release are complete
- [ ] CHANGELOG.md is up to date
- [ ] readme.txt is up to date
- [ ] All tests pass
## Determining the New Version Number
Based on the changes made, determine the appropriate version increment:
1. **PATCH** (e.g., 1.6.0 → 1.6.1): For bug fixes and minor improvements
- **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
2. **MINOR** (e.g., 1.6.0 → 1.7.0): For new features and significant improvements
3. **MAJOR** (e.g., 1.6.0 → 2.0.0): For breaking changes
## Release Steps
### 1. Create a New Branch
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
Example:
```bash
git checkout -b v1.7.0
```
### 2. Update Version Numbers
Update the version number in the following files:
#### a. Main Plugin File (fix-plugin-does-not-exist-notices.php)
```php
/**
* Plugin Name: Fix 'Plugin file does not exist.' Notices
* Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: {MAJOR}.{MINOR}.{PATCH}
* ...
*/
```
Also update the FPDEN_VERSION constant:
```php
define( 'FPDEN_VERSION', '{MAJOR}.{MINOR}.{PATCH}' );
```
#### b. CHANGELOG.md
Add a new section at the top of the CHANGELOG.md file:
```markdown
## [{MAJOR}.{MINOR}.{PATCH}] - YYYY-MM-DD
### Added
- New feature 1
- New feature 2
### Changed
- Change 1
- Change 2
### Fixed
- Bug fix 1
- Bug fix 2
```
#### c. POT File (languages/fix-plugin-does-not-exist-notices.pot)
Update the Project-Id-Version and POT-Creation-Date:
```
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices {MAJOR}.{MINOR}.{PATCH}\n"
"POT-Creation-Date: YYYY-MM-DDT00:00:00+00:00\n"
```
#### d. readme.txt
Update the stable tag:
```
Stable tag: {MAJOR}.{MINOR}.{PATCH}
```
Add a new entry to the changelog section:
```
= {MAJOR}.{MINOR}.{PATCH} =
* New feature 1
* New feature 2
* Change 1
* Change 2
* Fixed bug 1
* Fixed bug 2
```
Update the upgrade notice section:
```
= {MAJOR}.{MINOR}.{PATCH} =
Brief description of the most important changes in this release
```
### 3. Commit Changes
```bash
git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt README.md languages/fix-plugin-does-not-exist-notices.pot
git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"
```
### 4. Test Changes Locally
Test the changes thoroughly on the version branch to ensure everything works as expected:
- Test with the latest WordPress version
- Test with PHP 7.0+ (minimum supported version)
- Verify all features work as expected
- Check for any PHP warnings or notices
### 5. Merge to Main
When satisfied with testing, merge the version branch to main:
```bash
git checkout main
git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
```
The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
### 6. Push Main to Remotes
```bash
git push github main
git push gitea main
```
### 7. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
```
### 8. Monitor GitHub Actions
Open the GitHub Actions page to monitor the build and deployment process:
https://github.com/wpallstars/fix-plugin-does-not-exist-notices/actions
### 9. Verify Release
- [ ] Check that the GitHub release was created successfully
- [ ] Verify that the plugin was deployed to WordPress.org
- [ ] Test the plugin from WordPress.org to ensure it works correctly
## Testing Previous Versions
To test a previous version of the plugin:
```bash
# Checkout a specific tag for testing
git checkout v{MAJOR}.{MINOR}.{PATCH}
# Or create a test branch from a specific tag
git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
```
## Rollback Procedure (If Needed)
If issues are discovered after release:
### 1. Create a Hotfix Branch
```bash
git checkout v{MAJOR}.{MINOR}.{PATCH}
git checkout -b hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 2. Fix the Issues
Make the necessary changes to fix the issues.
### 3. Update Version Numbers
Increment the PATCH version and update all version numbers as described above.
### 4. Test the Hotfix
Test the hotfix thoroughly to ensure it resolves the issue without introducing new problems.
### 5. Commit Changes
```bash
git add .
git commit -m "Fix issues in v{MAJOR}.{MINOR}.{PATCH}"
```
### 6. Merge to Main
```bash
git checkout main
git merge hotfix/v{MAJOR}.{MINOR}.{PATCH+1} --no-ff
git push github main
git push gitea main
```
### 7. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH+1} -m "Hotfix release version {MAJOR}.{MINOR}.{PATCH+1}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 8. Monitor and Verify
Follow steps 8 and 9 from the release process to monitor and verify the hotfix release.

19
.aiconfig Normal file
View File

@ -0,0 +1,19 @@
{
"name": "fix-plugin-does-not-exist-notices",
"description": "WordPress plugin to fix 'Plugin file does not exist' notices",
"schema_version": "1.0.0",
"_comment": "This configuration file is used by AI tools that support the .aiconfig format. It defines model preferences and ignore patterns for AI context. You can use the ! prefix to include files that are excluded by .gitignore. Example: !important-file.log",
"ignore_patterns": [
".ai-tmp/"
],
"models": {
"default": "gpt-4o",
"code_generation": "gpt-4o",
"code_explanation": "gpt-4o",
"documentation": "gpt-4o"
},
"settings": {
"temperature": 0.2,
"max_tokens": 4000
}
}

8
.augmentignore Normal file
View File

@ -0,0 +1,8 @@
# Augment ignore file
# Additional patterns beyond .gitignore that should be ignored by Augment's context engine
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Augment specific
.augment-cache/

8
.boltignore Normal file
View File

@ -0,0 +1,8 @@
# Bolt.net ignore file
# Additional patterns beyond .gitignore for Bolt.net's AI context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Bolt-specific temporary files
.bolt-tmp/

8
.clinerc Normal file
View File

@ -0,0 +1,8 @@
{
"_comment": "This configuration file is used by Cline AI IDE. It defines model preferences and ignore patterns for AI context. You can use the ! prefix to include files that are excluded by .gitignore. Example: !important-file.log",
"ignore": [
".cline-tmp/"
],
"model": "gpt-4o",
"temperature": 0.2
}

8
.codyignore Normal file
View File

@ -0,0 +1,8 @@
# Cody ignore file
# Additional patterns beyond .gitignore for Cody's AI context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Cody-specific temporary files
.cody-tmp/

8
.continuerc Normal file
View File

@ -0,0 +1,8 @@
{
"_comment": "This configuration file is used by Continue AI IDE. It defines model preferences and ignore patterns for AI context. You can use the ! prefix to include files that are excluded by .gitignore. Example: !important-file.log",
"ignore": [
".continue-tmp/"
],
"model": "gpt-4o",
"temperature": 0.2
}

8
.cursorignore Normal file
View File

@ -0,0 +1,8 @@
# Cursor ignore file
# Additional patterns beyond .gitignore for Cursor's AI context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Cursor-specific temporary files
.cursor-tmp/

55
.distignore Normal file
View File

@ -0,0 +1,55 @@
# This file is used by WordPress.org plugin deployment scripts
# It determines which files/directories should be excluded from the plugin zip
# Note: Many patterns are already in .gitignore - this file focuses on deployment-specific exclusions
# Git
.git
.github
.gitignore
.gitattributes
# Build tools
.distignore
build.sh
build
.drone.yml
.woodpecker.yml
# Documentation
CONTRIBUTING.md
CODE_OF_CONDUCT.md
CHANGELOG.md
assets/README.md
# Development files
node_modules
.editorconfig
.eslintrc
.eslintignore
.stylelintrc
phpcs.xml
phpunit.xml
tests
.travis.yml
.gitlab-ci.yml
Gruntfile.js
gulpfile.js
package.json
package-lock.json
composer.json
composer.lock
# WordPress.org specific
.wordpress-org
# Miscellaneous
.DS_Store
Thumbs.db
.idea
.vscode
*.log
*.bak
*.tmp
*.zip
*~
._*

8
.geminiignore Normal file
View File

@ -0,0 +1,8 @@
# Gemini Code Assist ignore file
# Additional patterns beyond .gitignore for Gemini Code Assist's AI context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Gemini-specific temporary files
.gemini-tmp/

172
.gitignore vendored Normal file
View File

@ -0,0 +1,172 @@
# Operating System files
.DS_Store
Thumbs.db
ehthumbs.db
Desktop.ini
._*
.Spotlight-V100
.Trashes
# Editor files
*.swp
*.swo
*~
.idea/
.vscode/
*.sublime-project
*.sublime-workspace
*.komodoproject
.komodotools
*.tmproj
*.tmproject
.project
.settings/
# Dependency directories
node_modules/
vendor/
bower_components/
composer.lock
package-lock.json
# Composer
vendor/
composer.phar
# Build files
build/
dist/
# WordPress specific
wp-config.php
wp-content/uploads/
wp-content/upgrade/
wp-content/backup-db/
wp-content/cache/
wp-content/backups/
# Reference plugins
reference-plugins/
# Log files
*.log
error_log
debug.log
# Misc
.env
.env.*
!.env.example
# Design files
*.pxd
*.afdesign
*.afphoto
*.afpub
*.psd
*.ai
*.sketch
*.fig
*.xd
*.indd
*.aep
*.prproj
*.psb
*.xcf
*.cdr
*.eps
*.svg.bak
*.blend
*.blend1
*.blend2
*.c4d
*.max
*.3ds
*.fbx
# Office documents
*.docx
*.xlsx
*.pptx
*.ppt
*.doc
*.xls
*.pdf
# IDE specific
*.code-workspace
.history/
.ionide/
# AI tools
.ai-prompts/
.completions/
.chat-history/
.cursor/
.cursor-cache/
.cursor-tmp/
.v0/
.v0-cache/
.v0-tmp/
.windsurf/
.windsurf-cache/
.windsurf-tmp/
.cline/
.cline-cache/
.cline-tmp/
.roo/
.roo-cache/
.roo-tmp/
.gemini/
.gemini-cache/
.gemini-tmp/
.loveable/
.loveable-cache/
.loveable-tmp/
.bolt/
.bolt-cache/
.bolt-tmp/
.cody/
.cody-cache/
.cody-tmp/
.continue/
.continue-cache/
.continue-tmp/
.ai-tmp/
.augment-cache/
# WordPress testing
.phpunit.result.cache
.phpcs.cache
phpunit.xml
phpcs.xml
# WordPress specific files
wp-content/advanced-cache.php
wp-content/object-cache.php
wp-content/db.php
wp-content/debug.log
# Temporary files
.temp-*
# Development tools
.git/
.github/
.gitlab/
.gitattributes
.travis.yml
.drone.yml
.woodpecker.yml
codecov.yml
.babelrc
.browserslistrc
.editorconfig
.eslintignore
.eslintrc
.prettierrc
.stylelintrc
webpack.config.js
gulpfile.js
Gruntfile.js
*.zip

8
.loveablerc Normal file
View File

@ -0,0 +1,8 @@
{
"_comment": "This configuration file is used by Loveable AI IDE. It defines model preferences and ignore patterns for AI context. You can use the ! prefix to include files that are excluded by .gitignore. Example: !important-file.log",
"ignore": [
".loveable-tmp/"
],
"model": "gpt-4o",
"temperature": 0.2
}

8
.rooignore Normal file
View File

@ -0,0 +1,8 @@
# Roo Code ignore file
# Additional patterns beyond .gitignore for Roo Code's AI context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Roo-specific temporary files
.roo-tmp/

8
.v0ignore Normal file
View File

@ -0,0 +1,8 @@
# v0 ignore file
# Additional patterns beyond .gitignore for v0's context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# v0-specific temporary files
.v0-tmp/

8
.windsurfignore Normal file
View File

@ -0,0 +1,8 @@
# Windsurf ignore file
# Additional patterns beyond .gitignore for Windsurf's context
# You can use the ! prefix to include files that are excluded by .gitignore
# Example: !important-file.log (This would include important-file.log even if *.log is in .gitignore)
# Windsurf-specific temporary files
.windsurf-tmp/

39
.wordpress-org/README.md Normal file
View File

@ -0,0 +1,39 @@
# WordPress.org Plugin Repository Assets
This directory contains assets specific to the WordPress.org plugin repository and is used for automatic deployment via GitHub Actions.
## Directory Structure
```
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
```
## Purpose
When using GitHub Actions for WordPress.org plugin deployments (via the 10up WordPress GitHub Actions), this directory is used to automatically update plugin assets in the WordPress.org repository.
## Naming Conventions
Files must be named exactly as shown above to be properly recognized by the WordPress.org system during the deployment process.
## Right-to-Left (RTL) Support
For plugins that support Right-to-Left languages (like Hebrew and Arabic), you can provide RTL versions of assets by appending `-rtl` to the filename:
- `banner-772x250-rtl.png`
- `banner-1544x500-rtl.png`
- `icon-256x256-rtl.png`
Note that the `-rtl` suffix is specifically for Right-to-Left language support, not for dark mode versions of assets.
## Additional Resources
For more detailed information about WordPress.org plugin assets, please see:
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)

BIN
.wordpress-org/assets/banner-1544x500.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
.wordpress-org/assets/banner-772x250.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
.wordpress-org/assets/icon-128x128.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

BIN
.wordpress-org/assets/icon-256x256.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BIN
.wordpress-org/assets/screenshot-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 392 KiB

349
CHANGELOG.md Normal file
View File

@ -0,0 +1,349 @@
# Changelog
All notable changes to this project will be documented in this file.
## [2.0.2] - 2024-05-17
### Changed
- Consolidated WordPress.org assets into .wordpress-org directory
- Improved organization of assets for WordPress.org submission
- Updated .wordpress-org/README.md with comprehensive information
## [2.0.1] - 2024-05-17
### Added
- Contributing section to readme.txt
- reference-plugins directory for plugin development inspiration
### Changed
- Updated "tested up to" version to WordPress 6.7.2
- Improved .gitattributes with comprehensive file handling
- Enhanced documentation organization
## [2.0.0] - 2024-05-17
### Added
- Note clarifying that the plugin has no settings page
- Clarification that functionality is limited to the admin plugins page only
### Changed
- Major version release for WordPress.org submission
- Finalized all assets and documentation for public release
## [1.6.28] - 2024-05-17
### Changed
- Consolidated asset documentation into a single comprehensive guide
- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
- Updated all asset README files to point to the main documentation
- Improved file organization and documentation structure
## [1.6.27] - 2024-05-17
### Changed
- Clarified RTL support in WordPress.org asset documentation
- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
- Consolidated asset files and improved documentation
## [1.6.26] - 2024-05-17
### Changed
- Updated screenshot references to use a single comprehensive screenshot
- Fixed asset directory paths in documentation
- Improved ImageMagick conversion commands for icon generation
- Clarified WordPress.org SVN repository structure
## [1.6.25] - 2024-05-17
### Added
- Comprehensive WordPress.org submission guide with SVN structure explanation
### Changed
- Consolidated asset files into their respective directories
- Clarified asset requirements and submission process
- Improved organization of asset files
## [1.6.24] - 2024-05-17
### Added
- Properly named icon PNG files (icon-256x256.png and icon-128x128.png)
### Changed
- Updated asset preparation documentation
- Improved WordPress.org submission readiness
## [1.6.23] - 2024-05-17
### Added
- Properly named icon, banner, and screenshot files for WordPress.org submission
- Comprehensive guide for WordPress.org asset requirements
### Changed
- Fixed file naming to comply with WordPress.org standards
- Organized assets in separate directories for better management
## [1.6.22] - 2024-05-17
### Changed
- Enhanced support section with multiple support channel options
- Added encouragement for users to leave reviews on WordPress.org
- Improved documentation with clearer support instructions
## [1.6.21] - 2024-05-17
### Added
- Support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
- Links to supported AI IDEs in documentation
- Additional FAQs for better SEO
### Changed
- Updated AI configuration files with modern models (gpt-4o)
- Made documentation more generic for boilerplate use
- Enhanced explanations in configuration files
- Added more keywords for better SEO
## [1.6.20] - 2024-05-17
### Changed
- Added explanations about the ! prefix in ignore files
- Moved WordPress-specific patterns to .gitignore
- Further improved organization of ignore patterns
- Added examples of how to include files excluded by .gitignore
## [1.6.19] - 2024-05-17
### Changed
- Consolidated common ignore patterns into .gitignore
- Simplified AI IDE configuration files to only include tool-specific patterns
- Improved organization of ignore patterns for better maintainability
- Added more file types to .gitignore for comprehensive coverage
## [1.6.18] - 2024-05-17
### Changed
- Optimized AI IDE configuration files to only include patterns not in .gitignore
- Improved efficiency of ignore files for better AI context management
- Enhanced compatibility with various AI-powered development tools
## [1.6.17] - 2024-05-17
### Added
- .augmentignore file with best practices
- Configuration files for Cursor, Windsurf, v0, and Cline IDEs
- More design file formats to .gitignore
- .aiconfig file for general AI IDE compatibility
## [1.6.16] - 2024-05-17
### Fixed
- Updated CI configuration files with correct plugin slugs
- Updated CHANGELOG.md with all recent versions
- Fixed outdated references to plugin-reference-cleaner
## [1.6.15] - 2024-05-17
### Changed
- Moved AI workflow documentation to root directory for better visibility
- Consolidated duplicate workflow files
- Improved organization of development documentation
- Updated CI configuration files with correct plugin slugs
## [1.6.14] - 2024-05-17
### Changed
- Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
- Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
- Improved explanation of how the plugin works
- Ensured consistent terminology across all documentation
## [1.6.13] - 2024-05-17
### Changed
- Code cleanup and optimization
- Improved Git Updater integration
- Fixed author display in plugin information
- Ensured compatibility with WordPress 6.4
## [1.6.12] - 2024-05-17
### Added
- Added WP ALLSTARS as a co-author
- Updated author information and links
- Added author websites to plugin description
- Fixed issue with multiple author URLs
## [1.6.11] - 2024-05-17
### Fixed
- Improved Git Updater integration
- Fixed plugin header information
- Updated author information
## [1.6.10] - 2024-05-17
### Fixed
- Corrected plugin header information
- Improved Git Updater compatibility
- Updated documentation
## [1.6.9] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
- Improved documentation
## [1.6.8] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.7] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.6] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.5] - 2024-05-16
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.4] - 2024-05-16
### Improved
- Version management to ensure consistent patch version increments
- Documentation for version update process
- AI workflow files with detailed version increment instructions
## [1.6.3] - 2024-05-15
### Fixed
- Git Updater repository URLs to use full repository paths
- Update URI configuration for proper update detection
- Version management following semantic versioning
### Changed
- Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
## [1.6.2] - 2024-05-15
### Changed
- Updated POT file version for consistency
- Improved JavaScript localization with proper fallbacks
- Enhanced code quality for WordPress.org submission
### Added
- Git Updater configuration with Update URI
- Update server URL configuration
## [1.6.1] - 2024-05-15
### Added
- AI assistant guide and workflow documentation
- Detailed release process documentation
- Feature development guidelines
- Bug fixing procedures
- Code review standards
## [1.6.0] - 2024-05-15
### Added
- Full translation support with POT file
- JavaScript localization for better multilingual support
- Plugin constants for improved code organization
- Git Updater support for updates from GitHub and Gitea
### Changed
- Updated code to follow WordPress internationalization best practices
- Improved asset loading with version constants
- Smart update detection based on installation source
## [1.5.0] - 2024-05-15
### Added
- Improved compatibility with WordPress 6.4
- Enhanced error detection for plugin references
### Fixed
- Minor UI improvements for better visibility
- Accessibility enhancements for screen readers
## [1.4.1] - 2023-11-30
### Added
- FAQ about keeping the plugin installed after notices are cleared
## [1.4.0] - 2023-11-30
### Changed
- Updated plugin name and text domain
- Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
## [1.3.3] - 2023-10-05
### Added
- "Click here to scroll" button to automatically find missing plugins
- Visual arrow pointing from notification to error message
- Smooth scrolling with highlighting of missing plugin rows
### Improved
- Notification reliability using multiple injection methods
- Earlier placement in page load cycle for better visibility
- Enhanced error detection for all WordPress error message formats
## [1.3.2] - 2023-10-05
### Added
- Prominent notification that appears directly below WordPress error messages
- Visual styling to help users connect error message with solution
- Direction arrows and highlighted text to improve user guidance
## [1.3.1] - 2023-10-05
### Added
- Instructional notification explaining how to use the plugin
- Step-by-step guidance for removing plugin references
- Clear visual indicators for missing plugins
## [1.3.0] - 2023-10-05
### Changed
- Complete redesign for maximum compatibility with all WordPress themes
- Now uses the plugins list table for missing plugin references
- Uses standard WordPress admin UI patterns and hooks
### Added
- Missing plugins now appear directly in the plugins list
- "Remove Reference" action link in the plugins list
- Success/error notices after removing references
### Fixed
- Compatibility issues with various WordPress admin themes
- Reliability issues with notification detection
## [1.2.4] - 2023-10-05
### Fixed
- Compatibility with more WordPress admin UI variations
- Specific targeting for admin notices in various themes
### Added
- Advanced DOM traversal using TreeWalker API
- Multiple fallback approaches to ensure button appears
- Enhanced console logging for troubleshooting
## [1.2.3] - 2023-10-05
### Fixed
- Button not appearing in some WordPress admin themes
- Error message detection for greater theme compatibility
### Improved
- DOM traversal to find notification elements in various themes
- Added console logging for troubleshooting
## [1.2.2] - 2023-10-05
### Fixed
- Timeout issue during plugin activation
- Potential infinite recursion in admin notices handling
### Improved
- Hook management to prevent performance issues
- Optimized by only loading on plugins page
## [1.2.1] - 2025-04-07
### Improved
- Fixed typos in documentation
- Improved text clarity
- Added question mark to first sentence for better readability
## [1.2] - 2025-04-07
### Added
- Improved documentation with detailed explanation
- Added SQL reference for technical users
- Suggested potential inclusion in WordPress core
## [1.1] - 2025-04-07
### Added
- Support for multisite WordPress installations
- Network admin page integration
- Woodpecker CI integration for automated releases
### Improved
- Error handling
- User experience with better confirmation messages
- Security by adding proper capability checks
## [1.0] - 2025-03-15
### Added
- Initial release
- "Remove Reference" button for plugin deactivation error notices
- AJAX processing for reference removal

338
LICENSE Normal file
View File

@ -0,0 +1,338 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
<https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Moe Ghoul>, 1 April 1989
Moe Ghoul, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

383
README.md Normal file
View File

@ -0,0 +1,383 @@
# Fix 'Plugin file does not exist.' Notices
[![WordPress Plugin Version](https://img.shields.io/wordpress/plugin/v/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Rating](https://img.shields.io/wordpress/plugin/rating/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Downloads](https://img.shields.io/wordpress/plugin/dt/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![License](https://img.shields.io/badge/license-GPL--2.0%2B-blue.svg)](https://www.gnu.org/licenses/gpl-2.0.html)
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
## Description
Have you ever deleted a plugin directly from the server or database and then been stuck with annoying error notifications that can't be cleared?
"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
### Key Features
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Notice" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
* Clean, user-friendly interface following WordPress design patterns
### How It Works
When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin:
1. Detects all missing plugin references in your database
2. Adds them to your plugins list with "(File Missing)" indicators
3. Provides a "Remove Notice" link to safely remove them
4. Shows clear notifications guiding you through the cleanup process
5. Safely removes the missing active plugin reference from your database using standard WordPress functions
6. Leaves all remaining plugins installed and active
### Use Cases
* You've accidentally deleted a plugin via FTP
* A plugin was removed by another admin but references remain
* You've migrated from another site and have leftover plugin references
* Your hosting provider removed a plugin but didn't clean the database
## Installation
### From WordPress.org:
1. Visit Plugins > Add New in your WordPress admin
2. Search for "Fix 'Plugin file does not exist.' Notices"
3. Click "Install Now" and then "Activate"
### Manual Installation:
1. Download the plugin ZIP file
2. Go to Plugins > Add New > Upload Plugin
3. Upload the ZIP file
4. Activate the plugin
## Usage
1. After activation, navigate to Plugins > Installed Plugins
2. If you have missing plugin errors, you'll see them in your plugins list with "(File Missing)" markers
3. Click the "Remove Notice" link next to any missing plugin
4. The reference will be removed, and the error notification will disappear
## Frequently Asked Questions
### Is it safe to remove plugin references?
Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists. It doesn't modify any other database tables or settings.
### What happens after I remove a reference?
The plugin entry will be removed from your active plugins list, and the corresponding error notification will no longer appear after you refresh the page.
### Can I use this plugin on a multisite installation?
Yes, the plugin works on both single sites and multisite installations. It properly handles network-activated plugins as well.
### How do I know which plugin references should be removed?
The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
### Will this break my site?
No. Since the plugin is only removing references to plugins that no longer exist, removing these references won't affect your site's functionality. In fact, it's cleaning up remnants that might be causing issues.
### What if I accidentally remove a reference I shouldn't have?
If you remove a reference to a plugin that you later want to reinstall, simply install the plugin again and activate it normally.
### Do I need to keep this plugin installed and active after notices are cleared?
Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
### How do I fix the "Plugin file does not exist" error in WordPress?
This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
### Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"?
This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
### Can this plugin fix errors after migrating a WordPress site?
Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
### Is it safe to remove plugin references that show "Plugin file does not exist"?
Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
### How is this different from manually editing the database?
Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
## Screenshots
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
## Developers
### Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository
2. Create your feature branch: `git checkout -b feature/amazing-feature`
3. Commit your changes: `git commit -m 'Add some amazing feature'`
4. Push to the branch: `git push origin feature/amazing-feature`
5. Submit a pull request
### AI-Powered Development
This repository is configured to work with various AI-powered development tools. You can use any of the following AI IDEs to contribute to this project:
- [Augment Code](https://www.augmentcode.com/) - AI-powered coding assistant
- [Cursor](https://cursor.com/) - AI-first code editor
- [v0](https://v0.dev/) - AI-powered design and development tool
- [Windsurf](https://www.windsurf.com/) - AI coding assistant
- [Cline](https://cline.bot/) - AI terminal assistant
- [Roo Code](https://roocode.com/) - AI pair programmer
- [Loveable](https://lovable.dev/) - AI development environment
- [Bolt](https://www.bolt.new/) - AI-powered code editor
- [Cody](https://sourcegraph.com/cody) - Sourcegraph's AI coding assistant
- [Continue](https://continue.dev/) - Open-source AI coding assistant
The repository includes configuration files for all these tools to ensure a consistent development experience.
### Technical Details
The plugin works by:
1. Filtering the `all_plugins` array to add missing plugins
2. Adding a custom "Remove Notice" action link via `plugin_action_links`
3. Adding helpful notifications near error messages
4. Providing a secure method to remove plugin references from the database
## Changelog
### 2.0.2
* Consolidated WordPress.org assets into .wordpress-org directory
* Improved organization of assets for WordPress.org submission
* Updated .wordpress-org/README.md with comprehensive information
### 2.0.1
* Added Contributing section to readme.txt
* Updated "tested up to" version to WordPress 6.7.2
* Added reference-plugins directory for plugin development inspiration
* Improved .gitattributes with comprehensive file handling
* Enhanced documentation organization
### 2.0.0
* Major version release for WordPress.org submission
* Added note clarifying that the plugin has no settings page
* Clarified that functionality is limited to the admin plugins page only
* Finalized all assets and documentation for public release
### 1.6.28
* Consolidated asset documentation into a single comprehensive guide
* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
* Updated all asset README files to point to the main documentation
* Improved file organization and documentation structure
### 1.6.27
* Clarified RTL support in WordPress.org asset documentation
* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
* Consolidated asset files and improved documentation
### 1.6.26
* Updated screenshot references to use a single comprehensive screenshot
* Fixed asset directory paths in documentation
* Improved ImageMagick conversion commands for icon generation
* Clarified WordPress.org SVN repository structure
### 1.6.25
* Consolidated asset files into their respective directories
* Created comprehensive WordPress.org submission guide
* Clarified SVN repository structure and asset requirements
* Improved organization of asset files
### 1.6.24
* Added properly named icon PNG files for WordPress.org submission
* Created icon-256x256.png and icon-128x128.png files
* Updated asset preparation documentation
### 1.6.23
* Prepared assets for WordPress.org plugin submission
* Added properly named icon, banner, and screenshot files
* Created comprehensive guide for WordPress.org asset requirements
* Fixed file naming to comply with WordPress.org standards
### 1.6.22
* Enhanced support section with multiple support channel options
* Added encouragement for users to leave reviews on WordPress.org
* Improved documentation with clearer support instructions
### 1.6.21
* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
* Updated documentation with links to supported AI IDEs
* Enhanced SEO with additional FAQs and keywords
* Made documentation more generic for boilerplate use
* Updated AI configuration files with modern models and better explanations
### 1.6.20
* Added explanations about the ! prefix in ignore files
* Moved WordPress-specific patterns to .gitignore
* Further improved organization of ignore patterns
* Added examples of how to include files excluded by .gitignore
### 1.6.19
* Consolidated common ignore patterns into .gitignore
* Simplified AI IDE configuration files to only include tool-specific patterns
* Improved organization of ignore patterns for better maintainability
* Added more file types to .gitignore for comprehensive coverage
### 1.6.18
* Optimized AI IDE configuration files to only include patterns not in .gitignore
* Improved efficiency of ignore files for better AI context management
* Enhanced compatibility with various AI-powered development tools
### 1.6.17
* Added .augmentignore file with best practices
* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
* Added more design file formats to .gitignore
* Added .aiconfig file for general AI IDE compatibility
### 1.6.16
* Updated CI configuration files with correct plugin slugs
* Updated CHANGELOG.md with all recent versions
* Fixed outdated references to plugin-reference-cleaner
### 1.6.15
* Moved AI workflow documentation to root directory for better visibility
* Consolidated duplicate workflow files
* Improved organization of development documentation
### 1.6.14
* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
* Improved explanation of how the plugin works
* Ensured consistent terminology across all documentation
### 1.6.13
* Code cleanup and optimization
* Improved Git Updater integration
* Fixed author display in plugin information
* Ensured compatibility with WordPress 6.4
### 1.6.12
* Added WP ALLSTARS as a co-author
* Updated author information and links
* Added author websites to plugin description
* Fixed issue with multiple author URLs
### 1.6.11
* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
* Simplified plugin functionality to focus on core features only
* Improved compatibility with various WordPress configurations
* Ensured plugin works correctly when other plugins are deleted
### 1.6.10
* Fixed critical error that could occur when a plugin folder is deleted
* Improved error handling with try/catch blocks
* Added more specific checks for the plugins page
* Enhanced compatibility with various WordPress configurations
* Made the code more defensive to prevent potential issues
### 1.6.9
* Fixed issue with notices not appearing below WordPress error messages
* Improved JavaScript detection of WordPress error notices
* Prevented WordPress from automatically clearing error notices on page refresh
* Added multiple timing attempts to ensure notices appear correctly
* Enhanced error notice targeting for better compatibility
### 1.6.8
* Fixed notice positioning to appear directly below WordPress error messages
* Improved notice width to match WordPress error messages
* Updated explanatory text for better clarity
* Fixed issue with notices not appearing in some cases
* Improved JavaScript detection of WordPress error messages
### 1.6.7
* Fixed duplicate notices issue by removing PHP-generated notice
* Simplified notice system to only show one notice below WordPress error
* Ensured consistent terminology with "Remove Notice" text
* Optimized plugin detection with caching to improve performance
* Fixed JavaScript to correctly handle multiple error messages
### 1.6.6
* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
* Fixed issue with automatic removal of plugin references without user action
* Fixed notice positioning to ensure it appears below error messages
* Restored pointer triangle to indicate relationship with error message
* Improved detection of missing plugins in the plugin list
* Enhanced scroll functionality to work with all plugin types
### 1.6.5
* Fixed duplicate notices issue - now only one notice appears below error messages
* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
* Updated explanatory text to be more clear about the removal process
* Changed "Remove Reference" link text to "Remove Notice" for better clarity
* Made "(File Missing)" text bold and red for better visibility
* Fixed scroll functionality to work with all plugin rows
* Improved JavaScript to prevent multiple notices from appearing
### 1.6.4
* Updated version management to ensure consistent patch version increments
* Improved documentation for version update process
* Enhanced AI workflow files with detailed version increment instructions
### 1.6.3
* Fixed Git Updater repository URLs to use full repository paths
* Corrected Update URI configuration for proper update detection
* Improved version management following semantic versioning
* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
### 1.6.2
* Updated POT file version for consistency
* Improved JavaScript localization with proper fallbacks
* Enhanced code quality for WordPress.org submission
* Added Git Updater configuration with Update URI
* Added update server URL configuration
### 1.6.1
* Added AI assistant guide and workflow documentation
* Added detailed release process documentation
* Added feature development guidelines
* Added bug fixing procedures
* Added code review standards
### 1.6.0
* Added full translation support with POT file
* Added JavaScript localization for better multilingual support
* Added plugin constants for improved code organization
* Added Git Updater support for updates from GitHub and Gitea
* Updated code to follow WordPress internationalization best practices
* Improved asset loading with version constants
* Added smart update detection based on installation source
### 1.5.0
* Improved compatibility with WordPress 6.4
* Enhanced error detection for plugin references
* Minor UI improvements for better visibility
* Accessibility enhancements for screen readers
[View full changelog](CHANGELOG.md)
## License
This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE) file for details.
## Support
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.

50
assets/README.md Normal file
View File

@ -0,0 +1,50 @@
# Plugin Assets for WordPress.org
This directory contains assets for the WordPress.org plugin repository.
## Directory Structure
- `banner/` - Banner images for the plugin page header
- `banner-772x250.jpg` - Standard banner (772x250px)
- `banner-1544x500.jpg` - Retina banner (1544x500px)
- `icon/` - Plugin icon images
- `icon-128x128.jpg` - Standard icon (128x128px)
- `icon-256x256.jpg` - Retina icon (256x256px)
- `screenshots/` - Screenshots shown on the plugin page
- `screenshot-1.jpg` - Error message with explanation notification
## WordPress.org Requirements
### Required Image Dimensions
- **Banner**: 772x250px with 2x retina version at 1544x500px
- **Icon**: 128x128px with 2x retina version at 256x256px
- **Screenshots**: No specific size requirements, but they should be clear and readable
### Image Formats
- All images should be in JPG or PNG format
- Images should be optimized for web (compressed without losing quality)
### Additional Notes
- Screenshots should be numbered sequentially starting with 1
- They should match the descriptions in the `readme.txt` file
- Right-to-Left (RTL) language versions of banners and icons can be provided by appending `-rtl` to the filename
- There is no official support for dark mode versions of assets in the WordPress.org repository
## Example Filenames
```
assets/
├── banner/
│ ├── banner-772x250.jpg
│ └── banner-1544x500.jpg
├── icon/
│ ├── icon-128x128.jpg
│ └── icon-256x256.jpg
└── screenshots/
├── screenshot-1.jpg
```

126
assets/WORDPRESS_ORG_ASSETS.md Normal file
View File

@ -0,0 +1,126 @@
# WordPress.org Plugin Submission Assets Guide
This document explains how to prepare and upload assets for WordPress.org plugin submission. This is the main reference document for all asset-related information.
## WordPress.org SVN Repository Structure
When submitting a plugin to WordPress.org, you'll work with an SVN repository that has this structure:
```
/assets/ # Contains assets for the WordPress.org plugin page
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
/tags/ # Contains tagged releases
/1.6.27/
[plugin files]
/1.6.26/
[plugin files]
/trunk/ # Contains the current version of the plugin
[plugin files]
```
## Right-to-Left (RTL) Support
For languages that read from right to left (like Hebrew and Arabic), you can provide RTL-specific versions of your assets by appending `-rtl` to the filename. For example:
- `banner-772x250-rtl.png`
- `icon-256x256-rtl.png`
Note: `-rtl` is specifically for Right-to-Left language support, not for dark theme versions.
## Asset Requirements
### Icon
- **Format**: PNG
- **Sizes**:
- Required: 256x256 pixels (`icon-256x256.png`)
- Optional: 128x128 pixels (`icon-128x128.png`)
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `assets/icon/`
### Banner
- **Format**: PNG
- **Sizes**:
- Required: 772x250 pixels (`banner-772x250.png`)
- Optional: 1544x500 pixels (`banner-1544x500.png`) for high-DPI displays
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `assets/banner/`
### Screenshots
- **Format**: PNG
- **Naming**: `screenshot-1.png`
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY
- `screenshot-1.png` is available in `assets/screenshots/`
## Submission Process
1. **Prepare Plugin Files**:
- Ensure all plugin files are ready in your local repository
- Make sure version numbers are consistent across all files
2. **Prepare Assets**:
- Ensure all assets follow the naming conventions above
- Verify that screenshots match the descriptions in readme.txt
3. **Upload to WordPress.org**:
- When you receive SVN access, use these commands:
```bash
# Check out the repository
svn checkout https://plugins.svn.wordpress.org/fix-plugin-does-not-exist-notices/
# Copy plugin files to trunk
cp -r [your-local-plugin-files]/* fix-plugin-does-not-exist-notices/trunk/
# Copy assets to assets directory
cp assets/icon/icon-256x256.png fix-plugin-does-not-exist-notices/assets/
cp assets/icon/icon-128x128.png fix-plugin-does-not-exist-notices/assets/
cp assets/banner/banner-772x250.png fix-plugin-does-not-exist-notices/assets/
cp assets/banner/banner-1544x500.png fix-plugin-does-not-exist-notices/assets/
cp assets/screenshots/screenshot-1.png fix-plugin-does-not-exist-notices/assets/
# Add new files
cd fix-plugin-does-not-exist-notices
svn add --force trunk/*
svn add --force assets/*
# Commit changes
svn commit -m "Initial plugin submission"
```
## Image Conversion Tools
For converting SVG to PNG or creating different sizes of images, you can use:
- **Graphic Design Software**:
- Adobe Photoshop
- Adobe Illustrator
- Affinity Designer
- Affinity Photo
- GIMP (free, open-source)
- Inkscape (free, open-source)
- Pixelmator
- **Online Converters**:
- [SVG to PNG Converter](https://svgtopng.com/)
- [Convertio](https://convertio.co/svg-png/)
- [CloudConvert](https://cloudconvert.com/svg-to-png)
- **Command Line** (using ImageMagick):
```bash
# For 256x256 icon
convert -background none -size 256x256 assets/icon/icon.svg assets/icon/icon-256x256.png
# For 128x128 icon
convert -background none -size 128x128 assets/icon/icon.svg assets/icon/icon-128x128.png
```
## Resources
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)

81
assets/WORDPRESS_ORG_SUBMISSION.md Normal file
View File

@ -0,0 +1,81 @@
# WordPress.org Plugin Submission Assets Guide
This document outlines the requirements for assets when submitting a plugin to the WordPress.org plugin repository.
## Asset Requirements
### Icon
- **Format**: PNG
- **Size**: 256x256 pixels
- **Filename**: `icon-256x256.png`
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Optional**: You can also include `icon-128x128.png` for backward compatibility
### Banner
- **Format**: PNG
- **Sizes**:
- Regular: 772x250 pixels (`banner-772x250.png`)
- High-DPI: 1544x500 pixels (`banner-1544x500.png`)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
### Screenshots
- **Format**: PNG
- **Naming**: Sequential numbers (`screenshot-1.png`, `screenshot-2.png`, etc.)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Important**: The number and order must match the descriptions in the `readme.txt` file
## Current Status
### Icon
- ✅ SVG source available in `assets/icon/icon.svg`
- ✅ PNG files created in `assets/icon/icon-256x256.png` and `assets/icon/icon-128x128.png`
### Banner
- ✅ Both sizes available in `assets/banner/`
- ✅ Properly named files: `banner-772x250.png` and `banner-1544x500.png`
### Screenshots
- ✅ One screenshot available in `assets/screenshots/screenshot-1.png`
- ✅ Screenshot description in readme.txt updated to reference only one screenshot
## SVN Directory Structure
When submitting to WordPress.org, your SVN repository will have this structure:
```
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
/tags/
/1.6.27/
[plugin files]
/1.6.26/
[plugin files]
/trunk/
[current plugin files]
```
## Action Items
1. Ensure all files follow the proper naming convention
2. Upload all assets to the WordPress.org SVN repository in the `/assets` directory using these commands:
```bash
# Copy assets to WordPress.org SVN assets directory
cp assets/icon/icon-256x256.png /path/to/wordpress-svn/assets/
cp assets/icon/icon-128x128.png /path/to/wordpress-svn/assets/
cp assets/banner/banner-772x250.png /path/to/wordpress-svn/assets/
cp assets/banner/banner-1544x500.png /path/to/wordpress-svn/assets/
cp assets/screenshots/screenshot-1.png /path/to/wordpress-svn/assets/
```
## Resources
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)

15
assets/banner/README.md Normal file
View File

@ -0,0 +1,15 @@
# WordPress.org Banner Files
This directory contains banner files for the WordPress.org plugin repository.
## Files in this Directory
- `banner-772x250.png` - 772x250 pixel PNG banner (required for WordPress.org)
- `banner-1544x500.png` - 1544x500 pixel PNG banner for high-DPI displays (optional for WordPress.org)
- `banner-1544x500.pxd` - Source file for editing in Pixelmator
## WordPress.org Submission
For detailed information about WordPress.org banner requirements and submission process, please see the main asset documentation:
[WordPress.org Plugin Submission Assets Guide](../WORDPRESS_ORG_ASSETS.md)

BIN
assets/banner/banner-1544x500.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
assets/banner/banner-772x250.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

38
assets/css/admin-styles.css Normal file
View File

@ -0,0 +1,38 @@
.prc-notice {
border-left: 4px solid #ffba00;
background-color: #fff8e5;
padding: 10px 12px;
margin: 5px 0 15px;
font-size: 14px;
position: relative;
width: 100%;
box-sizing: border-box;
max-width: none;
}
.prc-notice h3 {
margin-top: 0;
color: #826200;
}
.prc-notice::before {
content: "";
position: absolute;
top: -10px;
left: 20px;
width: 0;
height: 0;
border-left: 10px solid transparent;
border-right: 10px solid transparent;
border-bottom: 10px solid #fff8e5;
}
/* Style for highlighting the missing plugin row */
tr.inactive.prc-highlight-missing,
tr.active.prc-highlight-missing {
background-color: #fff8e5 !important; /* Use !important to override default styles */
}
/* Make File Missing text bold and red */
span.error {
font-weight: bold !important;
color: #dc3232 !important;
}

16
assets/icon/README.md Normal file
View File

@ -0,0 +1,16 @@
# WordPress.org Icon Files
This directory contains icon files for the WordPress.org plugin repository.
## Files in this Directory
- `icon.svg` - Source SVG icon
- `icon-256x256.png` - 256x256 pixel PNG icon (required for WordPress.org)
- `icon-128x128.png` - 128x128 pixel PNG icon (optional for WordPress.org)
- `icon-1024x1024.pxd` - Source file for editing in Pixelmator
## WordPress.org Submission
For detailed information about WordPress.org icon requirements and submission process, please see the main asset documentation:
[WordPress.org Plugin Submission Assets Guide](../WORDPRESS_ORG_ASSETS.md)

BIN
assets/icon/icon-128x128.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

BIN
assets/icon/icon-256x256.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

11
assets/icon/icon.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 30 KiB

131
assets/js/admin-scripts.js Normal file
View File

@ -0,0 +1,131 @@
(function() {
// Track if we've already added our notice
var noticeAdded = false;
// Function to inject our notice
function injectNotice() {
// If we've already added a notice, don't add another one
if (noticeAdded) {
return;
}
// Find all notification containers first
var noticeContainers = document.querySelectorAll('.notice, .error, .updated, div.error');
var targetNotice = null;
// Find all error notifications about missing plugins
noticeContainers.forEach(function(notice) {
if ((notice.textContent.includes('Plugin file does not exist') ||
notice.textContent.includes('has been deactivated due to an error')) &&
(notice.classList.contains('error') || notice.classList.contains('notice-error'))) {
// We'll use the last matching notice as our target
targetNotice = notice;
console.log('Found WordPress error notice:', notice.textContent);
}
});
// If we didn't find a specific error notice, look for the general WordPress error at the top
if (!targetNotice) {
// Try to find the WordPress error message at the top of the page
var wpError = document.querySelector('.error:not(.below-h2), div.error:not(.below-h2), .notice-error:not(.below-h2)');
if (wpError) {
targetNotice = wpError;
console.log('Found general WordPress error notice');
}
}
// If we found a target notice, add our custom notice after it
if (targetNotice) {
// Check if we already added our notice
if (targetNotice.nextElementSibling && targetNotice.nextElementSibling.classList.contains('prc-notice')) {
return;
}
// Create our custom notice
var ourNotice = document.createElement('div');
ourNotice.className = 'prc-notice';
// Add content using localized strings passed via wp_localize_script
var pluginMissingText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.pluginMissing ?
fpdenData.i18n.pluginMissing : 'File Missing';
var removeNoticeText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.removeNotice ?
fpdenData.i18n.removeNotice : 'Remove Notice';
var clickToScrollText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.clickToScroll ?
fpdenData.i18n.clickToScroll : 'Click here to scroll to and highlight missing plugins';
ourNotice.innerHTML = '<h3 style="margin-top:0;color:#826200;">Fix Plugin Does Not Exist Notices 👆</h3>' +
'<p>To remove these notices, scroll down to each plugin\'s row showing: plugin-name.php "<strong style="color:red">(' + pluginMissingText + ')</strong>". Then, click the "<strong>' + removeNoticeText + '</strong>" link for that plugin.</p>' +
'<p>This safely removes the missing active plugin reference from your database, using the standard WordPress function to update your active plugin options table, to leave the remaining plugins installed and active.</p>' +
'<p><a href="#" id="prc-scroll-to-plugin" style="font-weight:bold;text-decoration:underline;color:#826200;">' + clickToScrollText + '</a></p>';
// Insert our notice right after the error
targetNotice.parentNode.insertBefore(ourNotice, targetNotice.nextSibling);
// Make sure our notice has the same width as the WordPress error notice
ourNotice.style.width = targetNotice.offsetWidth + 'px';
ourNotice.style.maxWidth = '100%';
ourNotice.style.boxSizing = 'border-box';
// Mark that we've added our notice
noticeAdded = true;
// Add scroll behavior
var scrollLink = document.getElementById('prc-scroll-to-plugin');
if (scrollLink) {
scrollLink.addEventListener('click', function(e) {
e.preventDefault();
// Look for all plugin rows, not just inactive ones
var allPluginRows = document.querySelectorAll('tr.active, tr.inactive');
for (var i = 0; i < allPluginRows.length; i++) {
if (allPluginRows[i].textContent.includes('(File Missing)')) {
// Add a class for highlighting instead of direct style manipulation
allPluginRows[i].classList.add('prc-highlight-missing');
allPluginRows[i].scrollIntoView({ behavior: 'smooth', block: 'center' });
// Optional: Remove highlight after a delay
(function(row) {
setTimeout(function() {
row.classList.remove('prc-highlight-missing');
}, 3000); // Remove highlight after 3 seconds
})(allPluginRows[i]);
return;
}
}
});
}
}
}
// Try to inject notices on multiple events to ensure it works
document.addEventListener('DOMContentLoaded', function() {
// Delay the initial injection to ensure WordPress has fully loaded its notices
setTimeout(injectNotice, 100);
// Also set up a MutationObserver to watch for dynamically added notices
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(mutation) {
if (mutation.addedNodes && mutation.addedNodes.length > 0) {
// Check if added nodes are notices or contain notices
mutation.addedNodes.forEach(function(node) {
if (node.nodeType === 1 && (node.matches('.notice, .error, .updated, div.error') || node.querySelector('.notice, .error, .updated, div.error'))) {
setTimeout(injectNotice, 50); // Small delay to ensure the DOM is updated
}
});
}
});
});
// Start observing the body for changes in children
observer.observe(document.body, { childList: true, subtree: true });
});
// Backup attempt with window.onload (less reliable than DOMContentLoaded but good fallback)
window.addEventListener('load', function() {
setTimeout(injectNotice, 500); // Delay slightly to ensure dynamic content is loaded
});
// Additional attempt after a longer delay to catch late-loading notices
window.addEventListener('load', function() {
setTimeout(injectNotice, 1000); // Longer delay as final attempt
});
})();

14
assets/screenshots/README.md Normal file
View File

@ -0,0 +1,14 @@
# WordPress.org Screenshot Files
This directory contains screenshot files for the WordPress.org plugin repository.
## Files in this Directory
- `screenshot-1.png` - Main screenshot showing the plugin in action
- `screenshot-1.pxd` - Source file for editing in Pixelmator
## WordPress.org Submission
For detailed information about WordPress.org screenshot requirements and submission process, please see the main asset documentation:
[WordPress.org Plugin Submission Assets Guide](../WORDPRESS_ORG_ASSETS.md)

BIN
assets/screenshots/screenshot-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 392 KiB

58
build.sh Executable file
View File

@ -0,0 +1,58 @@
#!/bin/bash
# Exit on error
set -e
# Check if version is provided
if [ -z "$1" ]; then
echo "Error: Please provide a version number. Example: ./build.sh 1.2"
exit 1
fi
VERSION=$1
PLUGIN_SLUG="wp-fix-plugin-does-not-exist-notices"
BUILD_DIR="build/$PLUGIN_SLUG"
ZIP_FILE="${PLUGIN_SLUG}-${VERSION}.zip"
# Create build directory
echo "Creating build directory..."
mkdir -p $BUILD_DIR
# Install composer dependencies
echo "Installing composer dependencies..."
composer install --no-dev --optimize-autoloader
# Copy required files
echo "Copying plugin files..."
cp wp-fix-plugin-does-not-exist-notices.php $BUILD_DIR/
cp readme.txt $BUILD_DIR/
cp LICENSE $BUILD_DIR/
cp README.md $BUILD_DIR/
cp CHANGELOG.md $BUILD_DIR/
cp composer.json $BUILD_DIR/
# Copy directories
echo "Copying directories..."
mkdir -p $BUILD_DIR/includes
cp -r includes/* $BUILD_DIR/includes/
mkdir -p $BUILD_DIR/languages
cp -r languages/* $BUILD_DIR/languages/
mkdir -p $BUILD_DIR/assets
cp -r assets/* $BUILD_DIR/assets/
mkdir -p $BUILD_DIR/vendor
cp -r vendor/* $BUILD_DIR/vendor/
# Create ZIP file
echo "Creating ZIP file..."
cd build
zip -r ../$ZIP_FILE $PLUGIN_SLUG
cd ..
# Verify the ZIP file was created
if [ -f "$ZIP_FILE" ]; then
echo "✅ Build successful: $ZIP_FILE created"
echo "File path: $(pwd)/$ZIP_FILE"
else
echo "❌ Build failed: ZIP file was not created"
exit 1
fi

21
composer.json Normal file
View File

@ -0,0 +1,21 @@
{
"name": "wpallstars/wp-fix-plugin-does-not-exist-notices",
"description": "Adds missing plugins to the plugins list with a 'Remove Reference' link so you can permanently clean up invalid plugin entries and remove error notices.",
"type": "wordpress-plugin",
"license": "GPL-2.0-or-later",
"authors": [
{
"name": "Marcus Quinn",
"email": "6428977+marcusquinn@users.noreply.github.com"
}
],
"require": {
"php": ">=7.0",
"afragen/git-updater-lite": "^1"
},
"autoload": {
"psr-4": {
"WPAllStars\\FixPluginDoesNotExistNotices\\": "includes/"
}
}
}

160
includes/Updater.php Normal file
View File

@ -0,0 +1,160 @@
<?php
/**
* Plugin Updater
*
* @package FixPluginDoesNotExistNotices
* @noinspection PhpUndefinedFunctionInspection
* @noinspection PhpUndefinedClassInspection
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
use function add_filter;
/**
* Class Updater
*
* Handles plugin updates from different sources based on installation origin.
*/
class Updater {
/**
* Plugin file path
*
* @var string
*/
private $plugin_file;
/**
* Installation source
*
* @var string
*/
private $source;
/**
* Constructor
*
* @param string $plugin_file Main plugin file path.
*/
public function __construct($plugin_file) {
$this->plugin_file = $plugin_file;
$this->source = $this->determine_installation_source();
$this->init();
}
/**
* Initialize the updater based on the installation source
*
* @return void
*/
public function init() {
// Only initialize Git Updater if not installed from WordPress.org
if ($this->source !== 'wordpress.org') {
$this->init_git_updater();
}
}
/**
* Determine the installation source of the plugin
*
* @return string Installation source: 'github', 'gitea', or 'wordpress.org'
*/
private function determine_installation_source() {
// Default to WordPress.org
$source = 'wordpress.org';
// Check if the plugin was installed from GitHub
if ($this->is_github_installation()) {
$source = 'github';
}
// Check if the plugin was installed from Gitea
elseif ($this->is_gitea_installation()) {
$source = 'gitea';
}
return $source;
}
/**
* Check if the plugin was installed from GitHub
*
* @return bool
* @noinspection PhpUndefinedFunctionInspection
*/
private function is_github_installation() {
// Check for GitHub-specific markers in the plugin directory
$plugin_dir = \plugin_dir_path($this->plugin_file);
// Look for .git directory with GitHub remote
if (file_exists($plugin_dir . '.git')) {
$git_config = @file_get_contents($plugin_dir . '.git/config');
if ($git_config && strpos($git_config, 'github.com') !== false) {
return true;
}
}
// Check for GitHub-specific files that might indicate it was downloaded from GitHub
if (file_exists($plugin_dir . '.github')) {
return true;
}
return false;
}
/**
* Check if the plugin was installed from Gitea
*
* @return bool
* @noinspection PhpUndefinedFunctionInspection
*/
private function is_gitea_installation() {
// Check for Gitea-specific markers in the plugin directory
$plugin_dir = \plugin_dir_path($this->plugin_file);
// Look for .git directory with Gitea remote
if (file_exists($plugin_dir . '.git')) {
$git_config = @file_get_contents($plugin_dir . '.git/config');
if ($git_config && strpos($git_config, 'gitea.wpallstars.com') !== false) {
return true;
}
}
return false;
}
/**
* Initialize Git Updater Lite
*
* @return void
* @noinspection PhpUndefinedFunctionInspection
* @noinspection PhpUndefinedClassInspection
*/
private function init_git_updater() {
// Check if the Git Updater Lite class exists (composer autoload)
if (!class_exists('\\Fragen\\Git_Updater\\Lite')) {
// Try to include the autoloader
$autoloader = dirname($this->plugin_file) . '/vendor/autoload.php';
if (file_exists($autoloader)) {
require_once $autoloader;
} else {
return; // Can't load Git Updater Lite
}
}
// Set the update server based on the installation source
\add_filter('gul_update_server', function() {
if ($this->source === 'github') {
return 'https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // GitHub repository URL
} elseif ($this->source === 'gitea') {
return 'https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // Gitea repository URL
}
return '';
});
// Initialize Git Updater Lite
if (class_exists('\\Fragen\\Git_Updater\\Lite')) {
(new \Fragen\Git_Updater\Lite($this->plugin_file))->run();
}
}
}

114
languages/wp-fix-plugin-does-not-exist-notices.pot Normal file
View File

@ -0,0 +1,114 @@
# Copyright (C) 2024 Marcus Quinn
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 2.0.2\n"
"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"POT-Creation-Date: 2024-05-16T12:00:00+00:00\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"X-Generator: WP-CLI 2.8.1\n"
"X-Domain: wp-fix-plugin-does-not-exist-notices\n"
#. Plugin Name of the plugin
msgid "Fix 'Plugin file does not exist.' Notices"
msgstr ""
#. Plugin URI of the plugin
msgid "https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/"
msgstr ""
#. Description of the plugin
msgid "Adds missing plugins to the plugins list with a \"Remove Reference\" link so you can permanently clean up invalid plugin entries and remove error notices."
msgstr ""
#. Author of the plugin
msgid "Marcus Quinn"
msgstr ""
#. Author URI of the plugin
msgid "https://www.wpallstars.com"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:127
msgid "Click here to scroll to missing plugins"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:128
msgid "Plugin file missing"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:129
#: wp-fix-plugin-does-not-exist-notices.php:205
msgid "Remove Reference"
msgstr ""
#. translators: %s: Path to wp-content/plugins
#: wp-fix-plugin-does-not-exist-notices.php:161
msgid "This plugin is still marked as \"Active\" in your database — but its folder and files can't be found in %s. Click \"Remove Reference\" to permanently remove it from your active plugins list and eliminate the error notice."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:164
msgid "N/A"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:168
msgid "Missing"
msgstr ""
#. translators: %s: Plugin file path
#: wp-fix-plugin-does-not-exist-notices.php:204
msgid "Remove reference to missing plugin %s"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:227
msgid "You do not have sufficient permissions to perform this action."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:233
msgid "Invalid plugin specified."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:308
msgid "Plugin reference removed successfully."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:316
msgid "Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:331
msgid "Fix Plugin Does Not Exist Notices"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:333
msgid "Missing plugin files detected:"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:334
msgid "The plugins listed below with a"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:335
msgid "File Missing"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:336
msgid "tag no longer exist but are still referenced in your database."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:339
msgid "How to fix:"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:340
msgid "Click the \"Remove Reference\" link next to each missing plugin to safely remove it from your active plugins list."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:342
msgid "This will clean up your database and remove the error notifications."
msgstr ""

494
readme.txt Normal file
View File

@ -0,0 +1,494 @@
=== Fix 'Plugin file does not exist.' Notices ===
Contributors: marcusquinn, wpallstars
Donate link: https://www.marcusquinn.com
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist, wordpress error, plugin error, deactivated plugin, remove plugin reference, fix plugin error, plugin does not exist, plugin file does not exist error
Requires at least: 5.0
Tested up to: 6.7.2
Requires PHP: 7.0
Stable tag: 2.0.2
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
== Description ==
Have you ever deleted a plugin directly from the server or database and then been stuck with annoying error notifications that can't be cleared?
"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
= Key Features =
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Notice" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
* Clean, user-friendly interface following WordPress design patterns
= How It Works =
When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin:
1. Detects all missing plugin references in your database
2. Adds them to your plugins list with "(File Missing)" indicators
3. Provides a "Remove Notice" link to safely remove them
4. Shows clear notifications guiding you through the cleanup process
5. Safely removes the missing active plugin reference from your database using standard WordPress functions
6. Leaves all remaining plugins installed and active
= Use Cases =
* You've accidentally deleted a plugin via FTP
* A plugin was removed by another admin but references remain
* You've migrated from another site and have leftover plugin references
* Your hosting provider removed a plugin but didn't clean the database
== Installation ==
1. Upload the `wp-fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. No configuration needed - the plugin works automatically
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
== Frequently Asked Questions ==
= Is it safe to remove plugin references? =
Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists. It doesn't modify any other database tables or settings.
= What happens after I remove a reference? =
The plugin entry will be removed from your active plugins list, and the corresponding error notification will no longer appear after you refresh the page.
= Can I use this plugin on a multisite installation? =
Yes, the plugin works on both single sites and multisite installations. It properly handles network-activated plugins as well.
= How do I know which plugin references should be removed? =
The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
= Will this break my site? =
No. Since the plugin is only removing references to plugins that no longer exist, removing these references won't affect your site's functionality. In fact, it's cleaning up remnants that might be causing issues.
= What if I accidentally remove a reference I shouldn't have? =
If you remove a reference to a plugin that you later want to reinstall, simply install the plugin again and activate it normally.
= Do I need to keep this plugin installed and active after notices are cleared? =
Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
= How do I fix the "Plugin file does not exist" error in WordPress? =
This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
= Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"? =
This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
= Can this plugin fix errors after migrating a WordPress site? =
Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
= Is it safe to remove plugin references that show "Plugin file does not exist"? =
Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
= How is this different from manually editing the database? =
Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
== Screenshots ==
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
== Changelog ==
= 2.0.2 =
* Consolidated WordPress.org assets into .wordpress-org directory
* Improved organization of assets for WordPress.org submission
* Updated .wordpress-org/README.md with comprehensive information
= 2.0.1 =
* Added Contributing section to readme.txt
* Updated "tested up to" version to WordPress 6.7.2
* Added reference-plugins directory for plugin development inspiration
* Improved .gitattributes with comprehensive file handling
* Enhanced documentation organization
= 2.0.0 =
* Major version release for WordPress.org submission
* Added note clarifying that the plugin has no settings page
* Clarified that functionality is limited to the admin plugins page only
* Finalized all assets and documentation for public release
= 1.6.28 =
* Consolidated asset documentation into a single comprehensive guide
* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
* Updated all asset README files to point to the main documentation
* Improved file organization and documentation structure
= 1.6.27 =
* Clarified RTL support in WordPress.org asset documentation
* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
* Consolidated asset files and improved documentation
= 1.6.26 =
* Updated screenshot references to use a single comprehensive screenshot
* Fixed asset directory paths in documentation
* Improved ImageMagick conversion commands for icon generation
* Clarified WordPress.org SVN repository structure
= 1.6.25 =
* Consolidated asset files into their respective directories
* Created comprehensive WordPress.org submission guide
* Clarified SVN repository structure and asset requirements
* Improved organization of asset files
= 1.6.24 =
* Added properly named icon PNG files for WordPress.org submission
* Created icon-256x256.png and icon-128x128.png files
* Updated asset preparation documentation
= 1.6.23 =
* Prepared assets for WordPress.org plugin submission
* Added properly named icon, banner, and screenshot files
* Created comprehensive guide for WordPress.org asset requirements
* Fixed file naming to comply with WordPress.org standards
= 1.6.22 =
* Enhanced support section with multiple support channel options
* Added encouragement for users to leave reviews on WordPress.org
* Improved documentation with clearer support instructions
= 1.6.21 =
* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
* Updated documentation with links to supported AI IDEs
* Enhanced SEO with additional FAQs and keywords
* Made documentation more generic for boilerplate use
* Updated AI configuration files with modern models and better explanations
= 1.6.20 =
* Added explanations about the ! prefix in ignore files
* Moved WordPress-specific patterns to .gitignore
* Further improved organization of ignore patterns
* Added examples of how to include files excluded by .gitignore
= 1.6.19 =
* Consolidated common ignore patterns into .gitignore
* Simplified AI IDE configuration files to only include tool-specific patterns
* Improved organization of ignore patterns for better maintainability
* Added more file types to .gitignore for comprehensive coverage
= 1.6.18 =
* Optimized AI IDE configuration files to only include patterns not in .gitignore
* Improved efficiency of ignore files for better AI context management
* Enhanced compatibility with various AI-powered development tools
= 1.6.17 =
* Added .augmentignore file with best practices
* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
* Added more design file formats to .gitignore
* Added .aiconfig file for general AI IDE compatibility
= 1.6.16 =
* Updated CI configuration files with correct plugin slugs
* Updated CHANGELOG.md with all recent versions
* Fixed outdated references to plugin-reference-cleaner
= 1.6.15 =
* Moved AI workflow documentation to root directory for better visibility
* Consolidated duplicate workflow files
* Improved organization of development documentation
= 1.6.14 =
* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
* Improved explanation of how the plugin works
* Ensured consistent terminology across all documentation
= 1.6.13 =
* Code cleanup and optimization
* Improved Git Updater integration
* Fixed author display in plugin information
* Ensured compatibility with WordPress 6.4
= 1.6.12 =
* Added WP ALLSTARS as a co-author
* Updated author information and links
* Added author websites to plugin description
* Fixed issue with multiple author URLs
= 1.6.11 =
* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
* Simplified plugin functionality to focus on core features only
* Improved compatibility with various WordPress configurations
* Ensured plugin works correctly when other plugins are deleted
= 1.6.10 =
* Fixed critical error that could occur when a plugin folder is deleted
* Improved error handling with try/catch blocks
* Added more specific checks for the plugins page
* Enhanced compatibility with various WordPress configurations
* Made the code more defensive to prevent potential issues
= 1.6.9 =
* Fixed issue with notices not appearing below WordPress error messages
* Improved JavaScript detection of WordPress error notices
* Prevented WordPress from automatically clearing error notices on page refresh
* Added multiple timing attempts to ensure notices appear correctly
* Enhanced error notice targeting for better compatibility
= 1.6.8 =
* Fixed notice positioning to appear directly below WordPress error messages
* Improved notice width to match WordPress error messages
* Updated explanatory text for better clarity
* Fixed issue with notices not appearing in some cases
* Improved JavaScript detection of WordPress error messages
= 1.6.7 =
* Fixed duplicate notices issue by removing PHP-generated notice
* Simplified notice system to only show one notice below WordPress error
* Ensured consistent terminology with "Remove Notice" text
* Optimized plugin detection with caching to improve performance
* Fixed JavaScript to correctly handle multiple error messages
= 1.6.6 =
* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
* Fixed issue with automatic removal of plugin references without user action
* Fixed notice positioning to ensure it appears below error messages
* Restored pointer triangle to indicate relationship with error message
* Improved detection of missing plugins in the plugin list
* Enhanced scroll functionality to work with all plugin types
= 1.6.5 =
* Fixed duplicate notices issue - now only one notice appears below error messages
* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
* Updated explanatory text to be more clear about the removal process
* Changed "Remove Reference" link text to "Remove Notice" for better clarity
* Made "(File Missing)" text bold and red for better visibility
* Fixed scroll functionality to work with all plugin rows
* Improved JavaScript to prevent multiple notices from appearing
= 1.6.4 =
* Updated version management to ensure consistent patch version increments
* Improved documentation for version update process
* Enhanced AI workflow files with detailed version increment instructions
= 1.6.3 =
* Fixed Git Updater repository URLs to use full repository paths
* Corrected Update URI configuration for proper update detection
* Improved version management following semantic versioning
* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
= 1.6.2 =
* Updated POT file version for consistency
* Improved JavaScript localization with proper fallbacks
* Enhanced code quality for WordPress.org submission
* Added Git Updater configuration with Update URI
* Added update server URL configuration
= 1.6.1 =
* Added AI assistant guide and workflow documentation
* Added detailed release process documentation
* Added feature development guidelines
* Added bug fixing procedures
* Added code review standards
= 1.6.0 =
* Added full translation support with POT file
* Added JavaScript localization for better multilingual support
* Added plugin constants for improved code organization
* Added Git Updater support for updates from GitHub and Gitea
* Updated code to follow WordPress internationalization best practices
* Improved asset loading with version constants
* Added smart update detection based on installation source
= 1.5.0 =
* Improved compatibility with WordPress 6.4
* Enhanced error detection for plugin references
* Minor UI improvements for better visibility
* Accessibility enhancements for screen readers
= 1.4.1 =
* Added FAQ about keeping the plugin installed after notices are cleared
= 1.4.0 =
* Updated plugin name and text domain
* Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
= 1.3.3 =
* Improved notification placement next to WordPress error messages
* Added "Click here to scroll" button that automatically locates missing plugins
* Enhanced reliability with multiple injection methods
* Added visual arrow pointing from notification to error message
= 1.3.2 =
* Added prominent notification directly below WordPress error messages
* Improved user guidance with visual cues to connect error and solution
* Added eye-catching styling to help users understand how to fix errors
= 1.3.1 =
* Added instructional notification explaining how to use the plugin
* Improved user guidance with step-by-step instructions
* Enhanced visual identification of missing plugins
= 1.3.0 =
* Complete redesign for maximum compatibility with all WordPress themes
* Now adds missing plugins directly to the plugins list table
* Uses standard WordPress admin UI patterns instead of DOM manipulation
* Added "Remove Reference" action link in the plugins list
* Significantly improved reliability across all WordPress configurations
= 1.2.4 =
* Fixed compatibility with more WordPress admin themes
* Added advanced DOM traversal to find error messages
* Implemented fallback mechanisms to ensure button appears
* Added detailed console logging for troubleshooting
= 1.2.3 =
* Fixed button not appearing in some WordPress admin themes
* Improved error message detection for greater compatibility
* Enhanced DOM traversal to find notification elements
= 1.2.2 =
* Fixed timeout issue during plugin activation
* Improved hook management to prevent potential infinite recursion
* Optimized performance by only loading on plugins page
= 1.2.1 =
* Fixed typos in documentation
* Improved text clarity
* Added question mark to first sentence for better readability
= 1.2 =
* Improved documentation with detailed explanation
* Added SQL reference for technical users
* Suggested potential inclusion in WordPress core
= 1.1 =
* Improved error handling
* Added support for multisite installations
* Enhanced security with proper capability checks
= 1.0 =
* Initial release
== Upgrade Notice ==
= 2.0.2 =
Improved organization of assets for WordPress.org submission.
= 2.0.1 =
Improved documentation with Contributing section and updated WordPress compatibility to 6.7.2.
= 2.0.0 =
Major version release for WordPress.org submission with improved documentation and clarification about plugin functionality.
= 1.6.28 =
Improved asset documentation and clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode.
= 1.6.27 =
Clarified RTL support in WordPress.org asset documentation and improved asset organization.
= 1.6.26 =
Updated screenshot references and improved WordPress.org submission documentation.
= 1.6.25 =
Improved organization of asset files and created comprehensive WordPress.org submission guide.
= 1.6.24 =
Added properly named icon PNG files for WordPress.org submission.
= 1.6.23 =
Prepared assets for WordPress.org plugin submission with properly named icon, banner, and screenshot files.
= 1.6.22 =
Improved support documentation with multiple support channel options and encouragement for users to leave reviews.
= 1.6.21 =
Added support for more AI-powered development tools and enhanced documentation with links to supported AI IDEs.
= 1.6.20 =
Added explanations about using the ! prefix in ignore files to include files excluded by .gitignore.
= 1.6.19 =
Improved organization of ignore patterns with consolidated .gitignore and simplified AI IDE configuration files.
= 1.6.18 =
Optimized AI IDE configuration files for better efficiency and compatibility.
= 1.6.17 =
Added configuration files for AI-powered IDEs and improved compatibility with development tools.
= 1.6.16 =
Updated CI configuration files and fixed outdated references to the previous plugin name.
= 1.6.15 =
Improved organization of development documentation with consolidated AI workflow files.
= 1.6.14 =
Improved documentation with consistent terminology and better explanation of how the plugin works.
= 1.6.13 =
Code cleanup, improved Git Updater integration, and ensured compatibility with WordPress 6.4.
= 1.6.12 =
Added WP ALLSTARS as a co-author and updated author information.
= 1.6.11 =
URGENT CRITICAL FIX: Completely removes code that was causing fatal errors. If you're experiencing the "critical error" message, this update will resolve it.
= 1.6.3 =
Fixed Git Updater repository URLs and updated organization naming for consistent branding across all platforms!
= 1.6.2 =
Improved JavaScript localization, enhanced code quality, and added Git Updater configuration for seamless updates!
= 1.6.1 =
Added comprehensive AI assistant guide and workflow documentation for improved development processes!
= 1.6.0 =
Added full translation support and Git Updater compatibility for direct updates from GitHub and Gitea!
= 1.5.0 =
Improved compatibility with WordPress 6.4 and accessibility enhancements for screen readers!
= 1.3.3 =
Major usability improvement with auto-scroll feature to help find missing plugins in your list!
= 1.3.0 =
Completely redesigned for better compatibility with all WordPress themes - now works with any WordPress installation!
= 1.2.2 =
Important stability fix - resolves timeout issues during plugin activation!
== Contributing ==
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository on [GitHub](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/) or [Gitea](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/)
2. Create your feature branch: `git checkout -b feature/amazing-feature`
3. Commit your changes: `git commit -m 'Add some amazing feature'`
4. Push to the branch: `git push origin feature/amazing-feature`
5. Submit a pull request
The plugin is designed to be a best-practice example for WordPress plugin development and can be used as a boilerplate for your own plugins.
== Support ==
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.

413
wp-fix-plugin-does-not-exist-notices.php Normal file
View File

@ -0,0 +1,413 @@
<?php
/**
* Fix 'Plugin file does not exist.' Notices
*
* @package FixPluginDoesNotExistNotices
* @author Marcus Quinn
* @copyright 2023 WP ALLSTARS
* @license GPL-2.0+
* @noinspection PhpUndefinedFunctionInspection
* @noinspection PhpUndefinedConstantInspection
*
* @wordpress-plugin
* Plugin Name: Fix 'Plugin file does not exist.' Notices
* Plugin URI: https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: 2.0.2
* Author: Marcus Quinn & WP ALLSTARS
* Author URI: https://www.wpallstars.com
* License: GPL-2.0+
* License URI: https://www.gnu.org/licenses/gpl-2.0.html
* Text Domain: wp-fix-plugin-does-not-exist-notices
* Domain Path: /languages
* Requires at least: 5.0
* Requires PHP: 7.0
* Update URI: https://git-updater.wpallstars.com
* GitHub Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
* GitHub Branch: main
* Gitea Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
* Gitea Branch: main
*
* This plugin is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation, either version 2 of the License, or
* any later version.
*
* This plugin is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this plugin. If not, see https://www.gnu.org/licenses/gpl-2.0.html.
*/
// Exit if accessed directly.
if ( ! defined( 'ABSPATH' ) ) {
exit;
}
// Define plugin constants
define( 'FPDEN_VERSION', '2.0.2' );
define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
define( 'FPDEN_PLUGIN_FILE', __FILE__ );
define( 'FPDEN_PLUGIN_BASENAME', plugin_basename( __FILE__ ) );
/**
* Load plugin text domain.
*
* @return void
*/
function fpden_load_textdomain() {
load_plugin_textdomain(
'wp-fix-plugin-does-not-exist-notices',
false,
dirname( plugin_basename( __FILE__ ) ) . '/languages/'
);
}
add_action( 'plugins_loaded', 'fpden_load_textdomain' );
/**
* Main class for the plugin.
*/
class Fix_Plugin_Does_Not_Exist_Notices {
/**
* Cached list of invalid plugins.
*
* @var array
*/
private $invalid_plugins = null;
/**
* Constructor. Hooks into WordPress actions and filters.
*/
public function __construct() {
// Add our plugin to the plugins list.
add_filter( 'all_plugins', array( $this, 'add_missing_plugins_references' ) );
// Add our action link to the plugins list.
add_filter( 'plugin_action_links', array( $this, 'add_remove_reference_action' ), 20, 4 );
// Handle the remove reference action.
add_action( 'admin_init', array( $this, 'handle_remove_reference' ) );
// Add admin notices for operation feedback.
add_action( 'admin_notices', array( $this, 'admin_notices' ) );
// Enqueue admin scripts and styles.
add_action( 'admin_enqueue_scripts', array( $this, 'enqueue_admin_assets' ) );
// We're no longer trying to prevent WordPress from auto-deactivating plugins
// as it was causing critical errors in some environments
}
/**
* Enqueue scripts and styles needed for the admin area.
*
* @param string $hook_suffix The current admin page hook.
* @return void
*/
public function enqueue_admin_assets( $hook_suffix ) {
// Only load on the plugins page.
if ( 'plugins.php' !== $hook_suffix ) {
return;
}
// Get invalid plugins to decide if assets are needed.
$invalid_plugins = $this->get_invalid_plugins();
if ( empty( $invalid_plugins ) ) {
return; // No missing plugins, no need for the special notice JS/CSS.
}
wp_enqueue_style(
'fpden-admin-styles',
FPDEN_PLUGIN_URL . 'assets/css/admin-styles.css',
array(),
FPDEN_VERSION
);
wp_enqueue_script(
'fpden-admin-scripts',
FPDEN_PLUGIN_URL . 'assets/js/admin-scripts.js',
array( 'jquery' ), // Add dependencies if needed, e.g., jQuery.
FPDEN_VERSION,
true // Load in footer.
);
// Add translation strings for JavaScript
wp_localize_script(
'fpden-admin-scripts',
'fpdenData',
array(
'i18n' => array(
'clickToScroll' => esc_html__( 'Click here to scroll to missing plugins', 'wp-fix-plugin-does-not-exist-notices' ),
'pluginMissing' => esc_html__( 'File Missing', 'wp-fix-plugin-does-not-exist-notices' ),
'removeNotice' => esc_html__( 'Remove Notice', 'wp-fix-plugin-does-not-exist-notices' ),
),
)
);
}
/**
* Find and add invalid plugin references to the plugins list.
*
* Filters the list of plugins displayed on the plugins page to include
* entries for active plugins whose files are missing.
*
* @param array $plugins An array of plugin data.
* @return array The potentially modified array of plugin data.
*/
public function add_missing_plugins_references( $plugins ) {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return $plugins;
}
// Get active plugins that don't exist.
$invalid_plugins = $this->get_invalid_plugins();
// Add each invalid plugin to the plugin list.
foreach ( $invalid_plugins as $plugin_path ) {
if ( ! isset( $plugins[ $plugin_path ] ) ) {
$plugin_name = basename( $plugin_path );
$plugins[ $plugin_path ] = array(
'Name' => $plugin_name . ' <span class="error">(File Missing)</span>',
/* translators: %s: Path to wp-content/plugins */
'Description' => sprintf(
__( 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices' ),
'<code>/wp-content/plugins/</code>'
),
'Version' => __( 'N/A', 'wp-fix-plugin-does-not-exist-notices' ),
'Author' => '',
'PluginURI' => '',
'AuthorURI' => '',
'Title' => $plugin_name . ' (' . __( 'Missing', 'wp-fix-plugin-does-not-exist-notices' ) . ')',
'AuthorName' => '',
);
}
}
return $plugins;
}
/**
* Add the Remove Notice action link to invalid plugins.
*
* Filters the action links displayed for each plugin on the plugins page.
* Adds a "Remove Notice" link for plugins identified as missing.
*
* @param array $actions An array of plugin action links.
* @param string $plugin_file Path to the plugin file relative to the plugins directory.
* @param array $plugin_data An array of plugin data.
* @param string $context The plugin context (e.g., 'all', 'active', 'inactive').
* @return array The potentially modified array of plugin action links.
* @noinspection PhpUnusedParameterInspection
*/
public function add_remove_reference_action( $actions, $plugin_file, $plugin_data, $context ) {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return $actions;
}
// Get our list of invalid plugins
$invalid_plugins = $this->get_invalid_plugins();
// Check if this plugin file is in our list of invalid plugins
if ( in_array( $plugin_file, $invalid_plugins, true ) ) {
// Clear existing actions like "Activate", "Deactivate", "Edit".
$actions = array();
// Add our custom action.
$nonce = wp_create_nonce( 'remove_plugin_reference_' . $plugin_file );
$remove_url = admin_url( 'plugins.php?action=remove_reference&plugin=' . urlencode( $plugin_file ) . '&_wpnonce=' . $nonce );
/* translators: %s: Plugin file path */
$aria_label = sprintf( __( 'Remove reference to missing plugin %s', 'wp-fix-plugin-does-not-exist-notices' ), esc_attr( $plugin_file ) );
$actions['remove_reference'] = '<a href="' . esc_url( $remove_url ) . '" class="delete" aria-label="' . $aria_label . '">' . esc_html__( 'Remove Notice', 'wp-fix-plugin-does-not-exist-notices' ) . '</a>';
}
return $actions;
}
/**
* Handle the remove reference action triggered by the link.
*
* Checks for the correct action, verifies nonce and permissions,
* calls the removal function, and redirects back to the plugins page.
*
* @return void
*/
public function handle_remove_reference() {
// Check if our specific action is being performed.
if ( ! isset( $_GET['action'] ) || 'remove_reference' !== $_GET['action'] || ! isset( $_GET['plugin'] ) ) {
return;
}
// Verify user permissions.
if ( ! current_user_can( 'activate_plugins' ) ) {
wp_die( esc_html__( 'You do not have sufficient permissions to perform this action.', 'wp-fix-plugin-does-not-exist-notices' ) );
}
// Sanitize and get the plugin file path.
$plugin_file = isset( $_GET['plugin'] ) ? sanitize_text_field( wp_unslash( $_GET['plugin'] ) ) : '';
if ( empty( $plugin_file ) ) {
wp_die( esc_html__( 'Invalid plugin specified.', 'wp-fix-plugin-does-not-exist-notices' ) );
}
// Verify nonce for security.
check_admin_referer( 'remove_plugin_reference_' . $plugin_file );
// Attempt to remove the plugin reference.
$success = $this->remove_plugin_reference( $plugin_file );
// Prepare redirect URL with feedback query args.
$redirect_url = admin_url( 'plugins.php' );
$redirect_url = add_query_arg( $success ? 'reference_removed' : 'reference_removal_failed', '1', $redirect_url );
// Redirect and exit.
wp_safe_redirect( $redirect_url );
exit;
}
/**
* Remove a plugin reference from the active plugins list in the database.
*
* Handles both single site and multisite network activated plugins.
*
* @param string $plugin_file The plugin file path to remove.
* @return bool True on success, false on failure or if the plugin wasn't found.
*/
public function remove_plugin_reference( $plugin_file ) {
$success = false;
// Ensure plugin file path is provided.
if ( empty( $plugin_file ) ) {
return false;
}
// Handle multisite network admin context.
if ( is_multisite() && is_network_admin() ) {
$active_plugins = get_site_option( 'active_sitewide_plugins', array() );
// Network active plugins are stored as key => timestamp.
if ( isset( $active_plugins[ $plugin_file ] ) ) {
unset( $active_plugins[ $plugin_file ] );
$success = update_site_option( 'active_sitewide_plugins', $active_plugins );
}
} else { // Handle single site or non-network admin context.
$active_plugins = get_option( 'active_plugins', array() );
// Single site active plugins are stored as an indexed array.
$key = array_search( $plugin_file, $active_plugins, true ); // Use strict comparison.
if ( false !== $key ) {
unset( $active_plugins[ $key ] );
// Re-index the array numerically.
$active_plugins = array_values( $active_plugins );
$success = update_option( 'active_plugins', $active_plugins );
}
}
return $success;
}
/**
* Display admin notices on the plugins page.
*
* Shows feedback messages after attempting to remove a reference.
* The main informational notice is handled by JavaScript to position it
* directly below the WordPress error message.
*
* @return void
*/
public function admin_notices() {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return;
}
// Check for feedback messages from the remove action.
if ( isset( $_GET['reference_removed'] ) && '1' === $_GET['reference_removed'] ) {
?>
<div class="notice notice-success is-dismissible">
<p><?php esc_html_e( 'Plugin reference removed successfully.', 'wp-fix-plugin-does-not-exist-notices' ); ?></p>
</div>
<?php
}
if ( isset( $_GET['reference_removal_failed'] ) && '1' === $_GET['reference_removal_failed'] ) {
?>
<div class="notice notice-error is-dismissible">
<p><?php esc_html_e( 'Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue.', 'wp-fix-plugin-does-not-exist-notices' ); ?></p>
</div>
<?php
}
// The main informational notice is now handled entirely by JavaScript
// to position it directly below the WordPress error message.
}
/**
* Check if the current admin page is the plugins page.
*
* @global string $pagenow WordPress global variable for the current admin page filename.
* @return bool True if the current page is plugins.php, false otherwise.
*/
private function is_plugins_page() {
global $pagenow;
// Check if it's an admin page and the filename is plugins.php.
return is_admin() && isset( $pagenow ) && 'plugins.php' === $pagenow;
}
/**
* Get a list of active plugin file paths that do not exist on the filesystem.
*
* Checks both single site and network active plugins based on the context.
* Uses caching to avoid repeated filesystem checks.
*
* @return array An array of plugin file paths (relative to WP_PLUGIN_DIR) that are missing.
*/
private function get_invalid_plugins() {
// Return cached result if available
if ( null !== $this->invalid_plugins ) {
return $this->invalid_plugins;
}
$this->invalid_plugins = array();
$active_plugins = array();
// Determine which option to check based on context (Network Admin or single site).
if ( is_multisite() && is_network_admin() ) {
// Network active plugins are stored as keys in an associative array.
$active_plugins = array_keys( get_site_option( 'active_sitewide_plugins', array() ) );
} else {
// Single site active plugins are stored in a numerically indexed array.
$active_plugins = get_option( 'active_plugins', array() );
}
// Check if the file exists for each active plugin.
foreach ( $active_plugins as $plugin_file ) {
// Construct the full path to the main plugin file.
$plugin_path = WP_PLUGIN_DIR . '/' . $plugin_file;
// Use validate_file to prevent directory traversal issues, although less likely here.
if ( validate_file( $plugin_file ) === 0 && ! file_exists( $plugin_path ) ) {
$this->invalid_plugins[] = $plugin_file;
}
}
return $this->invalid_plugins;
}
// We've removed the prevent_auto_deactivation method as it was causing critical errors
} // End class Fix_Plugin_Does_Not_Exist_Notices
// Initialize the plugin class.
new Fix_Plugin_Does_Not_Exist_Notices();
// Initialize the updater if composer autoload exists
$autoloader = __DIR__ . '/vendor/autoload.php';
if (file_exists($autoloader)) {
require_once $autoloader;
// Initialize the updater if the class exists
if (class_exists('\WPALLSTARS\FixPluginDoesNotExistNotices\Updater')) {
new \WPALLSTARS\FixPluginDoesNotExistNotices\Updater(__FILE__);
}
}