Update screenshot references and improve WordPress.org submission documentation (v1.6.26)

git checkout main
Merge tag 'v1.6.4'

Release version 1.6.4

.ai-assistant.md

@@ -0,0 +1,256 @@
+# 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.
+
+## 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. `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:
+   - `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/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/fix-plugin-does-not-exist-notices
+- Gitea: https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices
+- WordPress.org: https://wordpress.org/plugins/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
+# - fix-plugin-does-not-exist-notices.php
+# - CHANGELOG.md
+# - readme.txt
+# - README.md
+# - languages/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
+```

.ai-workflows/README.md

@@ -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.

.ai-workflows/bug-fixing.md

@@ -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

.ai-workflows/code-review.md

@@ -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.
+```

.ai-workflows/feature-development.md

@@ -0,0 +1,151 @@
+# 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
+
+### 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

.ai-workflows/release-process.md

@@ -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.

.aiconfig

@@ -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
+  }
+}

.augmentignore

@@ -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/

.boltignore

@@ -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/

.clinerc

@@ -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
+}

.codyignore

@@ -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/

.continuerc

@@ -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
+}

.cursorignore

@@ -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/

.distignore

@@ -1,3 +1,7 @@
+# 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

.drone.yml

@@ -14,14 +14,14 @@ steps:
     commands:
       - apk add --no-cache bash zip
       - VERSION=${DRONE_TAG#v}
-      - mkdir -p build/plugin-reference-cleaner
-      - cp plugin-reference-cleaner.php build/plugin-reference-cleaner/
-      - cp readme.txt build/plugin-reference-cleaner/
-      - cp LICENSE build/plugin-reference-cleaner/
-      - cp README.md build/plugin-reference-cleaner/
-      - cp CHANGELOG.md build/plugin-reference-cleaner/
+      - mkdir -p build/fix-plugin-does-not-exist-notices
+      - cp fix-plugin-does-not-exist-notices.php build/fix-plugin-does-not-exist-notices/
+      - cp readme.txt build/fix-plugin-does-not-exist-notices/
+      - cp LICENSE build/fix-plugin-does-not-exist-notices/
+      - cp README.md build/fix-plugin-does-not-exist-notices/
+      - cp CHANGELOG.md build/fix-plugin-does-not-exist-notices/
       - cd build
-      - zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
+      - zip -r ../fix-plugin-does-not-exist-notices-$VERSION.zip fix-plugin-does-not-exist-notices
       - cd ..
 
   - name: release
@@ -31,9 +31,9 @@ steps:
         from_secret: gitea_token
       base_url: https://gitea.wpallstars.com
       files:
-        - plugin-reference-cleaner-*.zip
+        - fix-plugin-does-not-exist-notices-*.zip
       title: Release ${DRONE_TAG}
       note: |
-        Plugin Reference Cleaner ${DRONE_TAG}
+        Fix 'Plugin file does not exist.' Notices ${DRONE_TAG}
 
-        See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/plugin-reference-cleaner/src/branch/main/CHANGELOG.md) for details. 
+        See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details.

.geminiignore

@@ -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/

.gitattributes

@@ -1,3 +1,6 @@
+# This file configures how Git handles line endings and file types
+# It is independent from .gitignore which controls which files are tracked
+
 # Auto detect text files and perform LF normalization
 * text=auto
 

.github/workflows/release.yml

@@ -28,6 +28,7 @@ jobs:
           cp readme.txt build/fix-plugin-does-not-exist-notices/
           cp LICENSE build/fix-plugin-does-not-exist-notices/
           cp README.md build/fix-plugin-does-not-exist-notices/
+          cp -r assets build/fix-plugin-does-not-exist-notices/
 
       - name: Create ZIP file
         run: |

.gitignore

@@ -29,6 +29,10 @@ bower_components/
 composer.lock
 package-lock.json
 
+# Composer
+vendor/
+composer.phar
+
 # Build files
 build/
 dist/
@@ -51,12 +55,98 @@ debug.log
 .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/

.loveablerc

@@ -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
+}

.rooignore

@@ -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/

.v0ignore

@@ -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/

.windsurfignore

@@ -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/

.woodpecker.yml

@@ -9,16 +9,16 @@ steps:
     commands:
       - apk add --no-cache bash zip
       - VERSION=${CI_COMMIT_TAG#v}
-      - mkdir -p build/plugin-reference-cleaner
-      - cp plugin-reference-cleaner.php build/plugin-reference-cleaner/
-      - cp readme.txt build/plugin-reference-cleaner/
-      - cp LICENSE build/plugin-reference-cleaner/
-      - cp README.md build/plugin-reference-cleaner/
-      - if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/plugin-reference-cleaner/; fi
+      - mkdir -p build/fix-plugin-does-not-exist-notices
+      - cp fix-plugin-does-not-exist-notices.php build/fix-plugin-does-not-exist-notices/
+      - cp readme.txt build/fix-plugin-does-not-exist-notices/
+      - cp LICENSE build/fix-plugin-does-not-exist-notices/
+      - cp README.md build/fix-plugin-does-not-exist-notices/
+      - if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/fix-plugin-does-not-exist-notices/; fi
       - cd build
-      - zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
+      - zip -r ../fix-plugin-does-not-exist-notices-$VERSION.zip fix-plugin-does-not-exist-notices
       - cd ..
-      - echo "Build completed - plugin-reference-cleaner-$VERSION.zip"
+      - echo "Build completed - fix-plugin-does-not-exist-notices-$VERSION.zip"
       - ls -la *.zip
 
   release:
@@ -27,9 +27,9 @@ steps:
       PLUGIN_API_KEY:
         from_secret: gitea_token
       PLUGIN_BASE_URL: https://gitea.wpallstars.com
-      PLUGIN_FILES: plugin-reference-cleaner-*.zip
+      PLUGIN_FILES: fix-plugin-does-not-exist-notices-*.zip
       PLUGIN_TITLE: "Release ${CI_COMMIT_TAG}"
-      PLUGIN_NOTE: "Plugin Reference Cleaner ${CI_COMMIT_TAG}\n\nSee [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/plugin-reference-cleaner/src/branch/main/CHANGELOG.md) for details."
+      PLUGIN_NOTE: "Fix 'Plugin file does not exist.' Notices ${CI_COMMIT_TAG}\n\nSee [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details."
 
   test:
     image: alpine:latest

CHANGELOG.md

@@ -2,6 +2,210 @@
 
 All notable changes to this project will be documented in this file.
 
+## [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

README.md

@@ -13,12 +13,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
 
 "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 Reference" link, allowing you to safely clean up invalid plugin entries with one click.
+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.
 
 ### Key Features
 
 * Adds missing plugins directly to your plugins list
-* Provides a simple "Remove Reference" action link
+* 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
@@ -30,8 +30,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 1. Detects all missing plugin references in your database
 2. Adds them to your plugins list with "(File Missing)" indicators
-3. Provides a "Remove Reference" link to safely remove them
+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
 
@@ -59,7 +61,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 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 Reference" link next to any missing plugin
+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
@@ -78,7 +80,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
 
 ### How do I know which plugin references should be removed?
 
-The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+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?
 
@@ -92,10 +94,30 @@ If you remove a reference to a plugin that you later want to reinstall, simply i
 
 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. Error message with explanation notification
-2. Missing plugin shown in the plugins list with "Remove Reference" link
+2. Missing plugin shown in the plugins list with "Remove Notice" link
 3. Auto-scroll feature that highlights the missing plugin
 
 ## Developers
@@ -110,45 +132,211 @@ Contributions are welcome! Please feel free to submit a Pull Request.
 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](https://augment.dev/) - AI-powered coding assistant
+- [Cursor](https://cursor.sh/) - AI-first code editor
+- [v0](https://v0.dev/) - AI-powered design and development tool
+- [Windsurf](https://www.windsurf.io/) - AI coding assistant
+- [Cline](https://cline.tools/) - AI terminal assistant
+- [Roo](https://roo.ai/) - AI pair programmer
+- [Gemini Code Assist](https://ai.google.dev/gemini-api) - Google's AI coding assistant
+- [Loveable](https://www.loveable.ai/) - AI development environment
+- [Bolt](https://www.bolt.dev/) - 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 Reference" action link via `plugin_action_links`
+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
 
-### 1.4.1
-- Added FAQ about keeping the plugin installed after notices are cleared
+### 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.4.0
-- Updated plugin name and text domain
-- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
+### 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.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.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.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.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.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.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.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.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)
 
@@ -158,4 +346,10 @@ This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE)
 
 ## Support
 
-For support, please visit [WP All Stars](https://www.wpallstars.com). 
+If you need help with this plugin, there are several ways to get support:
+
+* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
+* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
+* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
+
+If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.

assets/WORDPRESS_ORG_ASSETS.md

@@ -0,0 +1,91 @@
+# WordPress.org Plugin Submission Assets Guide
+
+This document explains how to prepare and upload assets for WordPress.org plugin submission.
+
+## 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.0.0/
+        [plugin files]
+    /1.0.1/
+        [plugin files]
+/trunk/          # Contains the current version of the plugin
+    [plugin files]
+```
+
+## 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"
+   ```
+
+## 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/)

assets/WORDPRESS_ORG_SUBMISSION.md

@@ -0,0 +1,76 @@
+# 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
+- ✅ PNG files created (`icon-256x256.png` and `icon-128x128.png`)
+
+### Banner
+- ✅ Both sizes available
+- ✅ Properly renamed versions created in `assets/banner-png/`
+
+### Screenshots
+- ❌ Only 1 of 3 referenced screenshots available
+- ❌ Need to create `screenshot-2.png` and `screenshot-3.png`
+- ✅ Properly renamed version of the first screenshot created in `assets/screenshots-png/`
+
+## SVN Directory Structure
+
+When submitting to WordPress.org, your SVN repository will have this structure:
+
+```
+/assets/
+    icon-256x256.png
+    banner-772x250.png
+    banner-1544x500.png
+    screenshot-1.png
+    screenshot-2.png
+    screenshot-3.png
+/tags/
+    /1.0.0/
+        [plugin files]
+    /1.0.1/
+        [plugin files]
+/trunk/
+    [current plugin files]
+```
+
+## Action Items
+
+1. Convert the SVG icon to a 256x256 PNG file
+2. Create the missing screenshots (2 and 3)
+3. Ensure all files follow the proper naming convention
+4. Upload all assets to the WordPress.org SVN repository in the `/assets` directory
+
+## 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/)

assets/banner-png/README.md

@@ -0,0 +1,11 @@
+# WordPress.org Banner Requirements
+
+For WordPress.org plugin submission, you need:
+
+1. Banner images in PNG format
+2. Two sizes:
+   - `banner-772x250.png` (for regular display)
+   - `banner-1544x500.png` (for high-resolution/retina displays)
+3. Place them in the `/assets/` directory of your WordPress.org SVN repository
+
+These files have been renamed from the original files to match WordPress.org's naming-convention and file format requirements.

assets/css/admin-styles.css

@@ -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;
+}

assets/icon-png/README.md

@@ -0,0 +1,32 @@
+# WordPress.org Icon Requirements
+
+For WordPress.org plugin submission, you need to:
+
+1. Convert the SVG icon to PNG format
+2. Create a 256x256 and 128x128 pixel version
+3. Name them `icon-256x256.png` and `icon-128x128.png`
+4. Place them in the `/assets/` directory of your WordPress.org SVN repository
+
+## How to Convert
+
+You can use tools like:
+- Inkscape (free, open-source)
+- Adobe Illustrator
+- Adobe Photoshop
+- Affinity Designer
+- Affinity Photo
+- GIMP
+- Pixelmator
+- Online converters like https://svgtopng.com/
+
+## Command Line Conversion (if you have ImageMagick installed)
+
+```bash
+# For 256x256 icon
+convert -background none -size 256x256 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon/icon-256x256.png
+
+# For 128x128 icon
+convert -background none -size 128x128 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon/icon-128x128.png
+```
+
+After creating the PNG file, it should be uploaded to the WordPress.org SVN repository in the assets directory.

assets/js/admin-scripts.js

@@ -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
+    });
+
+})();

assets/screenshots-png/README.md

@@ -0,0 +1,7 @@
+# WordPress.org Screenshot Requirements
+
+For WordPress.org plugin submission, you need:
+
+1. Screenshot in PNG format
+2. Named `screenshot-1.png`
+3. Place it in the `/assets/` directory of your WordPress.org SVN repository

build.sh

@@ -18,6 +18,10 @@ ZIP_FILE="${PLUGIN_SLUG}-${VERSION}.zip"
 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 fix-plugin-does-not-exist-notices.php $BUILD_DIR/
@@ -25,6 +29,18 @@ 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..."

composer.json

@@ -0,0 +1,21 @@
+{
+    "name": "wpallstars/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/"
+        }
+    }
+}

fix-plugin-does-not-exist-notices.php

@@ -4,14 +4,17 @@
  *
  * @package           FixPluginDoesNotExistNotices
  * @author            Marcus Quinn
- * @copyright         2023 WP All Stars
+ * @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/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: 1.4.2
- * Author: Marcus Quinn
+ * Version: 1.6.26
+ * 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
@@ -19,6 +22,11 @@
  * Domain Path: /languages
  * Requires at least: 5.0
  * Requires PHP: 7.0
+ * Update URI: https://git-updater.wpallstars.com
+ * GitHub Plugin URI: wpallstars/fix-plugin-does-not-exist-notices
+ * GitHub Branch: main
+ * Gitea Plugin URI: wpallstars/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
@@ -34,51 +42,149 @@
  * along with this plugin. If not, see https://www.gnu.org/licenses/gpl-2.0.html.
  */
 
-// Exit if accessed directly
-if (!defined('ABSPATH')) {
+// Exit if accessed directly.
+if ( ! defined( 'ABSPATH' ) ) {
     exit;
 }
 
+// Define plugin constants
+define( 'FPDEN_VERSION', '1.6.26' );
+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(
+		'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 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);
+		// 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'));
+		// 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'));
+		// 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
 	}
 
 	/**
-     * Find and add invalid plugin references to the plugins list
+	 * Enqueue scripts and styles needed for the admin area.
+	 *
+	 * @param string $hook_suffix The current admin page hook.
+	 * @return void
 	 */
-    public function add_missing_plugins_references($plugins) {
-        // Only run on the plugins page
-        if (!$this->is_plugins_page()) {
+	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', 'fix-plugin-does-not-exist-notices' ),
+					'pluginMissing' => esc_html__( 'File Missing', 'fix-plugin-does-not-exist-notices' ),
+					'removeNotice' => esc_html__( 'Remove Notice', '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
+		// 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(
+		// 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>',
-                    'Description' => 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in /wp-content/plugins/. Click "Remove Reference" to permanently remove it from your active plugins list and eliminate the error notice.',
-                    'Version' => 'N/A',
+					/* 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.', 'fix-plugin-does-not-exist-notices' ),
+						'<code>/wp-content/plugins/</code>'
+					),
+					'Version'     => __( 'N/A', 'fix-plugin-does-not-exist-notices' ),
 					'Author'      => '',
 					'PluginURI'   => '',
 					'AuthorURI'   => '',
-                    'Title' => $plugin_name . ' (Missing)',
-                    'AuthorName' => ''
+					'Title'       => $plugin_name . ' (' . __( 'Missing', 'fix-plugin-does-not-exist-notices' ) . ')',
+					'AuthorName'  => '',
 				);
 			}
 		}
@@ -87,80 +193,116 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	}
 
 	/**
-     * Add the Remove Reference action link to invalid 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()) {
+	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;
 		}
 
-        // Check if this is a missing plugin
-        if (isset($plugin_data['Name']) && strpos($plugin_data['Name'], '<span class="error">(File Missing)</span>') !== false) {
-            // Clear existing 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 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);
-            $actions['remove_reference'] = '<a href="' . esc_url($remove_url) . '" class="delete" aria-label="' . esc_attr__('Remove Reference', 'fix-plugin-does-not-exist-notices') . '">Remove Reference</a>';
+			// 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', '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', 'fix-plugin-does-not-exist-notices' ) . '</a>';
 		}
 
 		return $actions;
 	}
 
 	/**
-     * Handle the remove reference action
+	 * 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 we're removing a reference
-        if (!isset($_GET['action']) || $_GET['action'] !== 'remove_reference' || !isset($_GET['plugin'])) {
+		// Check if our specific action is being performed.
+		if ( ! isset( $_GET['action'] ) || 'remove_reference' !== $_GET['action'] || ! isset( $_GET['plugin'] ) ) {
 			return;
 		}
 
-        // Verify permissions
-        if (!current_user_can('activate_plugins')) {
-            wp_die(__('You do not have sufficient permissions to perform this action.', 'fix-plugin-does-not-exist-notices'));
+		// Verify user permissions.
+		if ( ! current_user_can( 'activate_plugins' ) ) {
+			wp_die( esc_html__( 'You do not have sufficient permissions to perform this action.', 'fix-plugin-does-not-exist-notices' ) );
 		}
 
-        // Get the plugin file
-        $plugin_file = isset($_GET['plugin']) ? $_GET['plugin'] : '';
+		// 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.', 'fix-plugin-does-not-exist-notices' ) );
+		}
 
-        // Verify nonce
-        check_admin_referer('remove_plugin_reference_' . $plugin_file);
+		// Verify nonce for security.
+		check_admin_referer( 'remove_plugin_reference_' . $plugin_file );
 
-        // Remove the plugin reference
-        $success = $this->remove_plugin_reference($plugin_file);
+		// Attempt to remove the plugin reference.
+		$success = $this->remove_plugin_reference( $plugin_file );
 
-        // Redirect back to plugins page with a message
-        $redirect = admin_url('plugins.php');
-        $redirect = add_query_arg($success ? 'reference_removed' : 'reference_removal_failed', '1', $redirect);
-        wp_redirect($redirect);
+		// 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
+	 * 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) {
+	public function remove_plugin_reference( $plugin_file ) {
 		$success = false;
 
-        // Handle multisite network admin
-        if (is_multisite() && is_network_admin()) {
-            $active_plugins = get_site_option('active_sitewide_plugins', array());
-            if (isset($active_plugins[$plugin_file])) {
-                unset($active_plugins[$plugin_file]);
-                $success = update_site_option('active_sitewide_plugins', $active_plugins);
+		// 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 );
 			}
-        // Handle single site or multisite subsite
-        else {
-            $active_plugins = get_option('active_plugins', array());
-            $key = array_search($plugin_file, $active_plugins);
-            if ($key !== false) {
-                unset($active_plugins[$key]);
-                $active_plugins = array_values($active_plugins); // Re-index array
-                $success = update_option('active_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 );
 			}
 		}
 
@@ -168,176 +310,104 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	}
 
 	/**
-     * Display admin notices
+	 * 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()) {
+		// Only run on the plugins page.
+		if ( ! $this->is_plugins_page() ) {
 			return;
 		}
 
-        // Get invalid plugins
-        $invalid_plugins = $this->get_invalid_plugins();
-        
-        // Create a highlighted notice immediately after WordPress error messages
-        if (!empty($invalid_plugins)) {
-            // Add a notice specifically targeting the WordPress error notification
-            // Use admin_head to ensure it runs early in the page load process
-            add_action('admin_head', function() use ($invalid_plugins) {
+		// Check for feedback messages from the remove action.
+		if ( isset( $_GET['reference_removed'] ) && '1' === $_GET['reference_removed'] ) {
 			?>
-                <style type="text/css">
-                    .prc-notice {
-                        border-left: 4px solid #ffba00;
-                        background-color: #fff8e5;
-                        padding: 10px 12px;
-                        margin: 5px 0 15px;
-                        font-size: 14px;
-                        position: relative;
-                    }
-                    .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>
-                <script type="text/javascript">
-                    // Function to inject our notice
-                    function injectNotice() {
-                        // Find all notification containers first
-                        var noticeContainers = document.querySelectorAll('.notice, .error, .updated');
-                        
-                        // 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')) {
-                                
-                                // Check if we already added our notice
-                                if (notice.nextElementSibling && notice.nextElementSibling.classList.contains('prc-notice')) {
-                                    return;
-                                }
-                                
-                                // Create our custom notice
-                                var ourNotice = document.createElement('div');
-                                ourNotice.className = 'prc-notice';
-                                
-                                // Add content
-                                ourNotice.innerHTML = '<h3 style="margin-top:0;color:#826200;">👉 Fix Plugin Does Not Exist Notices Can Fix This</h3>' +
-                                    '<p>To remove the above error notification, scroll down to find the plugin marked with "<strong style="color:red">(File Missing)</strong>" and click its "<strong>Remove Reference</strong>" link.</p>' +
-                                    '<p>This will permanently remove the missing plugin reference from your database.</p>' +
-                                    '<p><a href="#" id="prc-scroll-to-plugin" style="font-weight:bold;text-decoration:underline;color:#826200;">Click here to scroll to the missing plugin</a></p>';
-                                
-                                // Insert our notice right after the error
-                                notice.parentNode.insertBefore(ourNotice, notice.nextSibling);
-                                
-                                // Add scroll behavior
-                                var scrollLink = document.getElementById('prc-scroll-to-plugin');
-                                if (scrollLink) {
-                                    scrollLink.addEventListener('click', function(e) {
-                                        e.preventDefault();
-                                        var missingPlugins = document.querySelectorAll('tr.inactive:not(.plugin-update-tr)');
-                                        for (var i = 0; i < missingPlugins.length; i++) {
-                                            if (missingPlugins[i].textContent.includes('(File Missing)')) {
-                                                missingPlugins[i].style.backgroundColor = '#fff8e5';
-                                                missingPlugins[i].scrollIntoView({behavior: 'smooth', block: 'center'});
-                                                return;
-                                            }
-                                        }
-                                    });
-                                }
-                            }
-                        });
-                    }
-                    
-                    // Try to inject notices on multiple events to ensure it works
-                    document.addEventListener('DOMContentLoaded', function() {
-                        injectNotice();
-                        
-                        // 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) {
-                                    injectNotice();
-                                }
-                            });
-                        });
-                        
-                        // Start observing the body for changes
-                        observer.observe(document.body, { childList: true, subtree: true });
-                    });
-                    
-                    // Backup attempt with window.onload
-                    window.onload = function() {
-                        setTimeout(injectNotice, 500);
-                    };
-                    
-                    // Final backup in case other methods fail
-                    setTimeout(injectNotice, 1000);
-                </script>
+			<div class="notice notice-success is-dismissible">
+				<p><?php esc_html_e( 'Plugin reference removed successfully.', 'fix-plugin-does-not-exist-notices' ); ?></p>
+			</div>
 			<?php
-            });
-            
-            // Also display our standard info notice with more details
-            echo '<div class="notice notice-info is-dismissible">';
-            echo '<h3>Fix Plugin Does Not Exist Notices</h3>';
-            echo '<p><strong>Missing plugin files detected:</strong> The plugins listed below with <span style="color:red;">(File Missing)</span> tag no longer exist but are still referenced in your database.</p>';
-            echo '<p><strong>How to fix:</strong> Click the "Remove Reference" link next to each missing plugin to safely remove it from your active plugins list.</p>';
-            echo '<p>This will clean up your database and remove the error notifications.</p>';
-            echo '</div>';
 		}
 
-        // Show success message
-        if (isset($_GET['reference_removed']) && $_GET['reference_removed'] === '1') {
-            echo '<div class="notice notice-success is-dismissible"><p>Plugin reference removed successfully.</p></div>';
-        }
-        
-        // Show error message
-        if (isset($_GET['reference_removal_failed']) && $_GET['reference_removal_failed'] === '1') {
-            echo '<div class="notice notice-error is-dismissible"><p>Failed to remove plugin reference. The plugin may already have been removed.</p></div>';
+		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.', '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 we're on the plugins page
+	 * 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;
-        return is_admin() && $pagenow === 'plugins.php';
+		// 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 invalid plugin references
+	 * 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() {
-        $invalid_plugins = array();
+		// Return cached result if available
+		if ( null !== $this->invalid_plugins ) {
+			return $this->invalid_plugins;
+		}
 
-        // Get all active plugins
-        if (is_multisite() && is_network_admin()) {
-            $active_plugins = array_keys(get_site_option('active_sitewide_plugins', array()));
+		$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 {
-            $active_plugins = get_option('active_plugins', array());
+			// Single site active plugins are stored in a numerically indexed array.
+			$active_plugins = get_option( 'active_plugins', array() );
 		}
 
-        // Check if each plugin exists
-        foreach ($active_plugins as $plugin) {
-            $plugin_path = WP_PLUGIN_DIR . '/' . $plugin;
-            if (!file_exists($plugin_path)) {
-                $invalid_plugins[] = $plugin;
+		// 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 $invalid_plugins;
+		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__);
     }
 }
-
-// Initialize the plugin
-new Fix_Plugin_Does_Not_Exist_Notices();

includes/Updater.php

@@ -0,0 +1,158 @@
+<?php
+/**
+ * Plugin Updater
+ *
+ * @package FixPluginDoesNotExistNotices
+ * @noinspection PhpUndefinedFunctionInspection
+ * @noinspection PhpUndefinedClassInspection
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
+
+/**
+ * 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/fix-plugin-does-not-exist-notices'; // GitHub repository URL
+            } elseif ($this->source === 'gitea') {
+                return 'https://gitea.wpallstars.com/wpallstars/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();
+        }
+    }
+}

languages/fix-plugin-does-not-exist-notices.pot

@@ -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 1.6.26\n"
+"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/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: 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/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 ""
+
+#: fix-plugin-does-not-exist-notices.php:127
+msgid "Click here to scroll to missing plugins"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:128
+msgid "Plugin file missing"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:129
+#: fix-plugin-does-not-exist-notices.php:205
+msgid "Remove Reference"
+msgstr ""
+
+#. translators: %s: Path to wp-content/plugins
+#: 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 ""
+
+#: fix-plugin-does-not-exist-notices.php:164
+msgid "N/A"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:168
+msgid "Missing"
+msgstr ""
+
+#. translators: %s: Plugin file path
+#: fix-plugin-does-not-exist-notices.php:204
+msgid "Remove reference to missing plugin %s"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:227
+msgid "You do not have sufficient permissions to perform this action."
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:233
+msgid "Invalid plugin specified."
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:308
+msgid "Plugin reference removed successfully."
+msgstr ""
+
+#: 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 ""
+
+#: fix-plugin-does-not-exist-notices.php:331
+msgid "Fix Plugin Does Not Exist Notices"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:333
+msgid "Missing plugin files detected:"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:334
+msgid "The plugins listed below with a"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:335
+msgid "File Missing"
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:336
+msgid "tag no longer exist but are still referenced in your database."
+msgstr ""
+
+#: fix-plugin-does-not-exist-notices.php:339
+msgid "How to fix:"
+msgstr ""
+
+#: 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 ""
+
+#: fix-plugin-does-not-exist-notices.php:342
+msgid "This will clean up your database and remove the error notifications."
+msgstr ""

readme.txt

@@ -1,15 +1,15 @@
 === Fix 'Plugin file does not exist.' Notices ===
-Contributors: marcusquinn
-Donate link: https://www.wpallstars.com
-Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist
+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.4
 Requires PHP: 7.0
-Stable tag: 1.4.1
+Stable tag: 1.6.26
 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.
+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 ==
 
@@ -17,12 +17,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
 
 "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 Reference" link, allowing you to safely clean up invalid plugin entries with one click.
+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.
 
 = Key Features =
 
 * Adds missing plugins directly to your plugins list
-* Provides a simple "Remove Reference" action link
+* 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
@@ -34,8 +34,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 1. Detects all missing plugin references in your database
 2. Adds them to your plugins list with "(File Missing)" indicators
-3. Provides a "Remove Reference" link to safely remove them
+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 =
 
@@ -49,7 +51,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 1. Upload the `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 Reference" links
+4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
 
 == Frequently Asked Questions ==
 
@@ -67,7 +69,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
 
 = How do I know which plugin references should be removed? =
 
-The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+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? =
 
@@ -81,14 +83,210 @@ If you remove a reference to a plugin that you later want to reinstall, simply i
 
 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. Error message with explanation notification
-2. Missing plugin shown in the plugins list with "Remove Reference" link
-3. Auto-scroll feature that highlights the missing plugin
+1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
 
 == Changelog ==
 
+= 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
 
@@ -155,6 +353,69 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 
 == Upgrade Notice ==
 
+= 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!
 
@@ -166,4 +427,10 @@ Important stability fix - resolves timeout issues during plugin activation!
 
 == Support ==
 
-For support, please visit https://wpallstars.com 
+If you need help with this plugin, there are several ways to get support:
+
+* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
+* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
+* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
+
+If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.