Version 2.3.0 - Improved development workflow documentation

git status

git push github v2.2.3
Merge branch 'main' of https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices

.ai-assistant.md

@@ -0,0 +1,113 @@
+# AI Assistant Guide for WordPress Plugin Development
+
+This guide helps AI assistants understand the project structure, workflows, and best practices for this repository.
+
+## Project Overview
+
+- **Plugin Name**: Fix 'Plugin file does not exist' Notices
+- **Repository**: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+- **Description**: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
+
+This plugin helps users clean up references to deleted plugins that cause "Plugin file does not exist" errors in the WordPress admin. It adds missing plugins to the plugins list with a "Remove Notice" link to safely remove invalid plugin entries.
+
+## AI Workflows
+
+Detailed workflow documentation is available in the `.ai-workflows/` directory:
+
+- **@.ai-workflows/bug-fixing.md**: Guidelines for identifying and fixing bugs
+- **@.ai-workflows/code-review.md**: Standards for reviewing code changes
+- **@.ai-workflows/dev-prefs-memory.md**: Persistent memory of developer preferences
+- **@.ai-workflows/feature-development.md**: Process for developing new features
+- **@.ai-workflows/folder-structure.md**: Documentation of the plugin's folder structure and naming conventions
+- **@.ai-workflows/git-workflow.md**: Detailed git workflow and branch management guidelines
+- **@.ai-workflows/incremental-development.md**: Time-efficient approach for incremental development and testing
+- **@.ai-workflows/local-env-vars.md**: Local development environment paths and URLs
+- **@.ai-workflows/release-process.md**: Steps for preparing and publishing releases
+
+## Version Management
+
+We follow [Semantic Versioning](https://semver.org/):
+- **MAJOR.MINOR.PATCH** (e.g., 2.2.2)
+  - **MAJOR**: Breaking changes
+  - **MINOR**: New features, non-breaking
+  - **PATCH**: Bug fixes, non-breaking
+
+### Time-Efficient Development Workflow
+
+For efficient development and testing:
+- Create descriptive branches (**fix/**, **feature/**, **patch/**, **refactor/**) without version numbers
+- **Don't update version numbers** during initial development and testing
+- Only create **version branches** (v2.2.3) and update version numbers when changes are confirmed working
+- Use **patch** increments for bug fixes, **minor** for features, and **major** for breaking changes
+- Mark versions as **stable** when confirmed working by the user
+- See **@.ai-workflows/incremental-development.md** for detailed guidelines
+
+When updating version numbers, see **@.ai-workflows/release-process.md** for the complete checklist.
+
+**IMPORTANT**: Always keep the changelogs in README.md, readme.txt, and CHANGELOG.md in sync to avoid confusion. All three files must be updated with the same changes for each release.
+
+## Git Workflow
+
+Detailed git workflow documentation is available in **@.ai-workflows/git-workflow.md**.
+
+### Key Principles
+- Always pull the latest main branch from origin before creating new branches (mandatory step)
+- Create one branch per issue/feature (fix/patch/feature)
+- Submit one pull/merge request per issue
+- Run CI/CD checks for each pull request
+- Create separate branches for suggested improvements outside the current issue
+
+### Branch Naming Convention
+- Feature branches: `feature/descriptive-name`
+- Bug fix branches: `fix/issue-description` or `fix/issue-number-description`
+- Patch branches: `patch/descriptive-name`
+- 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"
+
+## Remote Repositories
+
+The plugin is hosted on multiple repositories:
+- GitHub: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+- Gitea: https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+- WordPress.org: https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/
+
+Always push changes to all remotes to keep them in sync.
+
+## Git Updater Integration
+
+The plugin integrates with Git Updater to allow updates directly from GitHub or Gitea. Important notes:
+
+1. Git Updater reads version information from the readme.txt file in the main branch, not from tags or releases
+2. Always merge release changes to the main branch immediately after creating a tag
+3. The plugin includes proper headers for Git Updater in the main plugin file
+
+See **@.ai-workflows/release-process.md** for detailed Git Updater integration steps.
+
+## 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
+
+Local environment variables and paths are documented in **@.ai-workflows/local-env-vars.md**.
+
+## Developer Preferences
+
+AI assistants should maintain a record of developer preferences in **@.ai-workflows/dev-prefs-memory.md**. When you learn about a new preference through user feedback or conversation:
+
+1. Check if the preference is already documented
+2. If not, add it to the appropriate section in the dev-prefs-memory.md file
+3. Reference these preferences in future interactions
+
+This ensures consistency across coding sessions and reduces the need for developers to repeatedly explain their preferences.
+
+## Common Tasks
+
+For detailed instructions on common tasks like creating releases, adding features, fixing bugs, and testing previous versions, see **@.ai-workflows/release-process.md**.

.ai-workflows/bug-fixing.md

@@ -0,0 +1,202 @@
+# 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 latest main branch pulled from origin (this step is mandatory):
+
+```bash
+git checkout main
+git pull origin main  # Critical step - never skip this
+git checkout -b fix/bug-description
+```
+
+Use a descriptive name that clearly indicates what bug is being fixed. If there's an issue number, include it in the branch name (e.g., `fix/123-plugin-activation-error`).
+
+For more detailed git workflow guidelines, see **@.ai-workflows/git-workflow.md**.
+
+### 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 and confirming it works, determine the appropriate version increment:
+
+- **PATCH** (e.g., 1.6.0 → 1.6.1): For most bug fixes that don't change functionality
+- **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
+
+**IMPORTANT**: Don't update version numbers during initial development and testing. Only create a version branch (e.g., `v2.2.3`) and update version numbers when the fix is confirmed working.
+
+This approach is more time-efficient as it allows you to focus on fixing the bug without worrying about version updates until the fix is confirmed working.
+
+For detailed guidelines on time-efficient development and testing, see **@.ai-workflows/incremental-development.md**.
+
+## 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/dev-prefs-memory.md

@@ -0,0 +1,62 @@
+# Developer Preferences Memory
+
+This document serves as a persistent memory for developer preferences established during coding sessions. AI assistants should refer to this document to understand the developer's preferences and update it as new preferences are established.
+
+## Purpose
+
+- Maintain a consistent record of developer preferences across coding sessions
+- Ensure AI assistants can provide assistance that aligns with the developer's preferred coding style and practices
+- Reduce the need for developers to repeatedly explain their preferences
+
+## How to Use This Document
+
+- **AI Assistants**: Review this document before providing assistance. Update it when new preferences are established through user feedback.
+- **Developers**: Reference this document to see what preferences have been recorded. Feel free to edit it directly to add or modify preferences.
+
+## Recorded Preferences
+
+### File and Directory Structure
+
+- Prefer lowercase filenames for consistency across the codebase
+- Use unique folder names following best practices
+- Folder references should be easily identifiable when using @mentions in AI-assisted coding
+- Admin-specific functionality should be in the `admin/lib/` directory
+- Core plugin functionality should be in the `includes/` directory
+
+### Code Style
+
+- Follow WordPress coding standards
+- Use OOP best practices for WordPress plugins
+- Create modular, maintainable, and efficient code structure
+
+### Documentation
+
+- Prefer token-efficient documentation in `.ai-assistant.md` that references `.ai-workflows/` files
+- Document the release workflow in `.ai-assistant.md` and `.ai-workflows/release-process.md`
+- Store environment variable documentation in `.ai-workflows/local-env-vars.md`
+- Maintain consistent documentation across readme.txt, README.md, and CHANGELOG.md
+
+### Asset Organization
+
+- Store banner, icon, and screenshot images in `.wordpress-org/assets/`
+- Store WORDPRESS_ORG files within `/wordpress-org`
+- Organize files in `/assets` into relevant `/admin` folders
+
+### Version Control
+
+- Use standard Git practices for version control and code management
+- When updating plugin versions, create a GitHub tag and trigger GitHub actions
+- Follow a specific release process with proper tagging and GitHub releases
+- Ensure commits are merged to the main branch as Git Updater pulls data from the readme.txt file in the primary branch
+
+### Plugin Development
+
+- Prefer simpler solutions over complex ones for plugins
+- Use a specific formatting style for the CHANGELOG.md file, using #### for section headings
+- When updating plugin versions, remember to update language files (POT/PO)
+- Comment out redundant code during testing
+
+### Potential AI Assised IDE Issues
+
+- Check for non-standard local terminal commandline customisations that might not be understood by the AI IDE in its terminal useage and cause errors in execution or confusion in not seeing expected results, and advise on how to resolve
+- Check for non-standard or multiple python and node.js versions, including homebrew versions, that might not be understood by the AI IDE in its terminal useage and cause errors in execution or confusion in not seeing expected results, and advise on how to resolve

.ai-workflows/feature-development.md

@@ -0,0 +1,172 @@
+# 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 latest main branch pulled from origin (this step is mandatory):
+
+```bash
+git checkout main
+git pull origin main  # Critical step - never skip this
+git checkout -b feature/descriptive-name
+```
+
+Use a descriptive name that clearly indicates what the feature is about. If there's an issue number, include it in the branch name (e.g., `feature/123-update-source-selector`).
+
+For more detailed git workflow guidelines, see **@.ai-workflows/git-workflow.md**.
+
+### 2. Implement the Feature
+
+When implementing a new feature:
+
+- Follow WordPress coding standards
+- Ensure all strings are translatable
+- Add appropriate comments
+- Consider performance implications
+- Maintain backward compatibility
+- Review reference plugins in the `reference-plugins/` directory for inspiration and best practices
+
+### 3. Update Documentation
+
+Update relevant documentation to reflect the new feature:
+
+- Add a description to CHANGELOG.md under an "Unreleased" section
+- Update readme.txt if the feature affects user-facing functionality
+- Update inline documentation/comments
+- Remember that any feature addition will require a version increment in all relevant files
+
+### 4. Testing
+
+Test the feature thoroughly:
+
+- Test with the latest WordPress version
+- Test with the minimum supported WordPress version (5.0)
+- Test with PHP 7.0+ (minimum supported version)
+- Test in different environments (if possible)
+
+### 5. Commit Changes
+
+Make atomic commits with clear messages:
+
+```bash
+git add .
+git commit -m "Add feature: descriptive name"
+```
+
+### 6. Prepare for Release
+
+When the feature is ready to be released:
+
+1. Create a version branch with the appropriate version number (typically increment the minor version for features):
+
+```bash
+# Example: from 2.2.0 to 2.3.0
+git checkout -b v{MAJOR}.{MINOR+1}.0
+```
+
+2. Now update version numbers in all required files:
+
+- Main plugin file (wp-fix-plugin-does-not-exist-notices.php)
+- CHANGELOG.md (add a new version section)
+- readme.txt
+- README.md
+- languages/wp-fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
+
+3. Commit the version updates:
+
+```bash
+git add .
+git commit -m "Version {MAJOR}.{MINOR+1}.0 - [brief description]"
+```
+
+4. Tag the version as stable:
+
+```bash
+git tag -a v{MAJOR}.{MINOR+1}.0-stable -m "Stable version {MAJOR}.{MINOR+1}.0"
+```
+
+5. Follow the standard release process from this point
+
+**IMPORTANT**: Don't update version numbers during initial development and testing. Only create a version branch and update version numbers when the feature is confirmed working.
+
+For detailed guidelines on time-efficient development and testing, see **@.ai-workflows/incremental-development.md**.
+
+### 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/folder-structure.md

@@ -0,0 +1,59 @@
+# Folder Structure
+
+This document outlines the folder structure of the plugin and explains the purpose of each directory.
+
+## Root Directories
+
+- **admin/** - Contains admin-specific functionality and assets
+- **includes/** - Contains core plugin functionality and classes
+- **languages/** - Contains translation files
+- **scripts/** - Contains build and deployment scripts
+- **.ai-workflows/** - Contains documentation for AI assistants
+- **.github/** - Contains GitHub-specific files like workflows
+- **.wordpress-org/** - Contains WordPress.org assets like banners and screenshots
+
+## Admin Directory Structure
+
+- **admin/css/** - Admin-specific CSS files
+- **admin/js/** - Admin-specific JavaScript files
+- **admin/images/** - Admin-specific images
+- **admin/partials/** - Admin-specific template partials
+- **admin/settings/** - Admin settings functionality
+- **admin/tools/** - Admin tools functionality
+- **admin/lib/** - Admin-specific library files and helper functions
+  - **admin/lib/admin.php** - Admin class for handling admin-specific functionality
+  - **admin/lib/modal.php** - Modal class for handling the update source selector modal
+
+## Includes Directory
+
+The `includes/` directory contains the core plugin functionality:
+
+- **includes/core.php** - Core class for handling the main plugin functionality
+- **includes/plugin.php** - Main plugin class that initializes all components
+- **includes/updater.php** - Updater class for handling plugin updates
+
+## File Naming Conventions
+
+- All PHP files in the `includes/` directory use lowercase filenames
+- All directories use lowercase names
+- JavaScript and CSS files use kebab-case (e.g., `update-source-selector.js`)
+
+## Best Practices
+
+1. **Unique Directory Names**: Each directory should have a unique name to avoid confusion
+2. **Logical Organization**: Files should be organized logically by function
+3. **Consistent Naming**: File and directory names should follow consistent naming conventions
+4. **Clear Separation**: Admin functionality should be separate from core functionality
+5. **Minimal Dependencies**: Files should have minimal dependencies on other files
+
+## @mentions for AI Assistants
+
+When referring to files or directories in AI conversations, use the following format:
+
+- **@includes/plugin.php** - Main plugin class
+- **@includes/core.php** - Core functionality
+- **@admin/lib/admin.php** - Admin functionality
+- **@admin/lib/modal.php** - Modal functionality
+- **@includes/updater.php** - Updater functionality
+- **@admin/js/update-source-selector.js** - Update source selector JavaScript
+- **@admin/css/update-source-selector.css** - Update source selector CSS

.ai-workflows/git-workflow.md

@@ -0,0 +1,255 @@
+# Git Workflow Guide for AI Assistants
+
+This document provides guidance for AI assistants to help with git workflow management for the Fix Plugin Does Not Exist Notices plugin.
+
+## Core Git Workflow Principles
+
+### 1. Always Start from Latest Main Branch
+
+Before creating any new branch, always ensure you're working with the latest code from the main branch by pulling from the origin:
+
+```bash
+git checkout main
+git pull origin main
+```
+
+This critical step ensures that your new branch includes all the latest changes from the remote repository and reduces the chance of merge conflicts later. Never skip this step, as working from an outdated main branch can lead to integration problems.
+
+### 2. One Issue Per Branch
+
+Create a separate branch for each issue or feature you're working on:
+
+- For bug fixes: `fix/issue-description` or `fix/issue-number-description`
+- For features: `feature/descriptive-name`
+- For small improvements: `patch/descriptive-name`
+- For code restructuring: `refactor/descriptive-name`
+
+**Important**: Use descriptive names without version numbers for development branches. This allows focusing on the changes without worrying about version updates until the changes are confirmed working.
+
+Only create version branches (e.g., `v2.2.3`) when changes are ready for release, and only then update version numbers in files.
+
+This approach keeps changes focused, makes code review easier, and provides clear rollback points if needed.
+
+### 3. Pull Request for Each Issue
+
+Create a separate pull request for each issue or feature. This ensures:
+
+- Each change can be reviewed independently
+- Issues can be merged as soon as they're ready
+- Changes can be reverted individually if needed
+- CI/CD checks can run on focused changes
+
+## Detailed Workflow
+
+### Starting a New Task
+
+1. **Update Main Branch from Origin**
+   ```bash
+   git checkout main
+   git pull origin main
+   ```
+
+   This step is mandatory before creating any new branch to ensure you're working with the latest code.
+
+2. **Create a New Branch**
+   ```bash
+   git checkout -b [branch-type]/[description]
+   ```
+
+   Examples:
+   ```bash
+   git checkout -b fix/123-plugin-activation-error
+   git checkout -b feature/update-source-selector
+   git checkout -b patch/2.2.1
+   ```
+
+3. **Make Your Changes**
+   - Make focused changes related only to the specific issue
+   - Commit regularly with clear, descriptive messages
+   - Reference issue numbers in commit messages when applicable
+
+4. **Testing Approach**
+
+   For efficient development:
+   - **Local Testing (Default)**: Test without updating version numbers
+     ```bash
+     # Get current version from plugin file
+     CURRENT_VERSION=$(grep -o "Version: [0-9.]*" wp-fix-plugin-does-not-exist-notices.php | cut -d' ' -f2)
+
+     # Build and deploy with current version
+     ./build.sh $CURRENT_VERSION
+     ```
+   - **Remote Testing (When Requested)**: Push development branch to remote
+     ```bash
+     git add .
+     git commit -m "[Brief description] for remote testing"
+     git push origin [branch-name]
+     ```
+   - **Version Creation**: Only when changes are confirmed working
+     ```bash
+     # Create version branch
+     git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+
+     # Update version numbers in all required files
+     # Commit version updates
+     git add .
+     git commit -m "Version {MAJOR}.{MINOR}.{PATCH} - Brief description"
+
+     # Tag as stable
+     git tag -a v{MAJOR}.{MINOR}.{PATCH}-stable -m "Stable version {MAJOR}.{MINOR}.{PATCH}"
+     ```
+
+5. **Push Branch to Remote (When Needed)**
+   ```bash
+   git push origin [branch-name]
+   ```
+
+### Creating a Pull Request
+
+1. **Ensure Tests Pass Locally**
+   - Run any available tests to ensure your changes work as expected
+   - Fix any issues before creating a pull request
+
+2. **Create Pull Request**
+   - Create a pull request from your branch to the main branch
+   - Include a clear description of the changes
+   - Reference any related issues
+   - Assign reviewers if appropriate
+
+3. **Address Review Feedback**
+   - Make requested changes
+   - Push additional commits to the same branch
+   - Respond to comments
+
+### CI/CD Integration
+
+Each pull request should pass through CI/CD checks before being merged. This ensures that all changes are compatible with the existing codebase and meet quality standards.
+
+1. **Automated Tests**
+   - Unit tests
+   - Integration tests
+   - Code style checks
+   - Compatibility checks
+
+2. **Manual Review**
+   - Code review by team members
+   - Functional testing in test environment
+   - Verification of feature requirements
+
+3. **Approval Process**
+   - Required approvals before merging
+   - Final checks for conflicts with other pending PRs
+   - Verification that all CI/CD checks have passed
+
+4. **Compatibility with Unmerged PRs**
+   - When multiple PRs are in progress simultaneously, ensure each PR is compatible with the main branch
+   - For related changes, consider using feature flags to allow independent merging
+   - Document dependencies between PRs in the PR description
+
+### Handling Concurrent Development
+
+When working on multiple issues simultaneously:
+
+1. **Keep Branches Independent**
+   - Always create new branches from the latest main branch pulled from origin, not from other feature branches
+   - This ensures each PR can be merged independently and contains all the latest changes
+
+2. **Handle Conflicts Proactively**
+   - If main has been updated with other changes while you're working:
+     ```bash
+     git checkout main
+     git pull origin main
+     git checkout your-branch
+     git merge main
+     ```
+   - Resolve any conflicts locally before pushing
+
+3. **Coordinate on Dependent Changes**
+   - If changes depend on each other, note this in the PR description
+   - Consider using the "Depends on #PR-number" notation in PR descriptions
+
+## Release Process
+
+When preparing for a release:
+
+1. **Ensure All Required PRs are Merged**
+   - All features and fixes planned for the release should be merged to main
+
+2. **Create a Release Branch**
+   ```bash
+   git checkout main
+   git pull origin main
+   git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+   ```
+
+3. **Follow Standard Release Process**
+   - Update version numbers
+   - Update changelogs
+   - Create tag
+   - See **@.ai-workflows/release-process.md** for complete details
+
+## Contributing to External Repositories
+
+When working on issues for external repositories (pull/merge requests):
+
+### 1. Clearly Indicate Testing Status
+
+In the PR description and comments, clearly indicate the testing status:
+
+- **Not tested**: "This PR addresses [issue] but has not been tested locally or remotely. It's ready for community/maintainer testing."
+- **Locally tested**: "This PR has been tested in a local WordPress environment and [describe results]."
+- **Remotely tested**: "This PR has been tested with a remote build and [describe results]."
+
+### 2. Provide Testing Instructions
+
+Include clear instructions for maintainers on how to test the changes:
+
+- Steps to reproduce the original issue (if applicable)
+- Steps to verify the fix or feature
+- Any specific environments or configurations needed for testing
+
+### 3. Be Responsive to Feedback
+
+Monitor the PR for feedback from maintainers and be prepared to make additional changes if requested.
+
+## Best Practices
+
+### Commit Messages
+
+- 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"
+- For more complex changes, add a detailed description after the first line
+
+### Branch Management
+
+- Delete branches after they've been merged
+- Keep branch names descriptive but concise
+- Use consistent naming conventions
+
+### Code Review
+
+- Review code thoroughly before approving
+- Test changes locally when possible
+- Provide constructive feedback
+- See **@.ai-workflows/code-review.md** for detailed code review guidelines
+
+### Suggested Improvements
+
+If you identify potential improvements outside the scope of the current issue:
+
+1. **Document the Suggestion**
+   - Note the suggestion in the PR comments
+   - Create a new issue for the suggestion
+   - Be specific about the benefits and implementation details
+
+2. **Create a Separate Branch**
+   - Don't include unrelated improvements in the current PR
+   - Create a new branch from the latest main branch for the suggested improvement
+   - Submit a separate PR for the suggestion
+
+3. **Ensure Compatibility**
+   - Make sure the suggested improvement is compatible with any unmerged PRs
+   - If the improvement depends on changes in another PR, note this dependency
+   - Consider how the improvement will interact with other pending changes

.ai-workflows/incremental-development.md

@@ -0,0 +1,225 @@
+# Incremental Development and Testing Guide
+
+This document provides guidance for AI assistants to help with incremental development and testing for the Fix Plugin Does Not Exist Notices plugin.
+
+## Time-Efficient Development Principles
+
+### Branch Naming for Development
+
+1. **Initial Development Branches**
+   - Use descriptive names without version numbers:
+     - `fix/issue-description` - For bug fixes
+     - `feature/descriptive-name` - For new features
+     - `patch/descriptive-name` - For small improvements
+     - `refactor/descriptive-name` - For code restructuring
+   - **Don't update version numbers** during this phase
+   - Focus on implementing and testing the changes
+
+2. **Version Branches**
+   - Only create after changes are confirmed working:
+     - `v{MAJOR}.{MINOR}.{PATCH}` (e.g., `v2.2.3`)
+   - Only update version numbers at this point
+   - This minimizes unnecessary version updates
+
+### Version Numbering Guidelines
+
+1. **Patch Versions (X.Y.Z → X.Y.Z+1)**
+   - Use for bug fixes and small improvements
+   - Example: `v2.2.3`
+
+2. **Minor Versions (X.Y.Z → X.Y+1.0)**
+   - Use for new features or significant improvements
+   - Example: `v2.3.0`
+
+3. **Major Versions (X.Y.Z → X+1.0.0)**
+   - Only increment when numerous features and fixes are tested and confirmed stable
+   - Reserved for breaking changes or significant overhauls
+   - Example: `v3.0.0`
+
+### Marking Stable Versions
+
+When the user confirms that changes are working correctly:
+1. Create a version branch and update version numbers
+2. Tag the version branch as stable
+   ```bash
+   git tag -a v{MAJOR}.{MINOR}.{PATCH}-stable -m "Stable version {MAJOR}.{MINOR}.{PATCH}"
+   ```
+3. Document in the PR or issue that this version has been confirmed stable
+
+## Local Testing Workflow
+
+### 1. Create a Descriptive Branch for Development
+
+```bash
+# Ensure you have the latest main branch
+git checkout main
+git pull origin main
+
+# Create a descriptive branch (without version numbers)
+git checkout -b fix/plugin-activation-error
+```
+
+### 2. Make Changes Without Updating Version Numbers
+
+During the development and testing phase:
+- Implement the necessary changes
+- **Don't update version numbers** in any files yet
+- Focus on the functionality
+
+### 3. Build and Deploy Locally
+
+For local testing, use the current version number from the main plugin file:
+
+```bash
+# Get the current version from the plugin file
+CURRENT_VERSION=$(grep -o "Version: [0-9.]*" wp-fix-plugin-does-not-exist-notices.php | cut -d' ' -f2)
+
+# Build and deploy with current version
+./build.sh $CURRENT_VERSION
+```
+
+This will:
+1. Create a build directory
+2. Copy required files to the build directory
+3. Deploy the plugin to your local WordPress testing environment
+
+**Note**: For local testing iterations, you do not need to commit changes, push to remote repositories, or create tags unless specifically requested.
+
+### 4. Test and Evaluate
+
+Test the changes thoroughly in the local environment:
+- Verify that the specific issue is fixed or feature works as expected
+- Check for any regressions or new issues
+- Document the results
+
+### 5. Based on Testing Results
+
+- **If changes need further refinement**: Continue working in the same branch
+- **If changes work as expected**: Proceed to version branch creation
+
+### 6. Creating a Version Branch
+
+When changes are confirmed working and ready for release:
+
+1. Create a version branch with the appropriate version number:
+
+```bash
+# Determine the appropriate version increment (patch, minor, or major)
+# based on the nature of the changes
+git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+```
+
+2. Now update version numbers in all required files:
+
+- Main plugin file (wp-fix-plugin-does-not-exist-notices.php)
+- CHANGELOG.md (add a new version section)
+- readme.txt
+- README.md
+- languages/wp-fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
+
+3. Commit the version updates:
+
+```bash
+git add .
+git commit -m "Version {MAJOR}.{MINOR}.{PATCH} - [brief description]"
+```
+
+4. Tag the version as stable:
+
+```bash
+git tag -a v{MAJOR}.{MINOR}.{PATCH}-stable -m "Stable version {MAJOR}.{MINOR}.{PATCH}"
+```
+
+## Remote Testing Workflow
+
+When the user specifically requests remote testing:
+
+### 1. Commit Changes to Remote Repository
+
+If testing a development branch (without version updates):
+
+```bash
+git add .
+git commit -m "[brief description] for remote testing"
+git push origin [branch-name]
+```
+
+If testing a version branch (with version updates):
+
+```bash
+git add .
+git commit -m "Version {MAJOR}.{MINOR}.{PATCH} - [brief description]"
+git push origin v{MAJOR}.{MINOR}.{PATCH}
+```
+
+### 2. Create and Push Tag (For Version Branches Only)
+
+```bash
+git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Version {MAJOR}.{MINOR}.{PATCH} for remote testing"
+git push origin v{MAJOR}.{MINOR}.{PATCH}
+```
+
+This will trigger GitHub Actions to build the installable ZIP file.
+
+### 3. Verify Remote Build
+
+Check that the GitHub Actions workflow completed successfully and the ZIP file is available for download.
+
+### 4. Test and Evaluate
+
+Test the remotely built version and document the results.
+
+## Contributing to External Repositories
+
+When working on issues for external repositories (pull/merge requests):
+
+### 1. Clearly Indicate Testing Status
+
+In the PR description and comments, clearly indicate the testing status:
+
+- **Not tested**: "This PR addresses [issue] but has not been tested locally or remotely. It's ready for community/maintainer testing."
+- **Locally tested**: "This PR has been tested in a local WordPress environment and [describe results]."
+- **Remotely tested**: "This PR has been tested with a remote build and [describe results]."
+
+### 2. Provide Testing Instructions
+
+Include clear instructions for maintainers on how to test the changes:
+
+- Steps to reproduce the original issue (if applicable)
+- Steps to verify the fix or feature
+- Any specific environments or configurations needed for testing
+
+### 3. Be Responsive to Feedback
+
+Monitor the PR for feedback from maintainers and be prepared to make additional changes if requested.
+
+## Rollback Procedure
+
+If a change causes issues after release:
+
+### 1. Identify the Last Stable Version
+
+Find the last version that was marked as stable:
+
+```bash
+git tag -l "*-stable"
+```
+
+### 2. Create a New Branch from the Stable Version
+
+```bash
+git checkout v{MAJOR}.{MINOR}.{PATCH}-stable
+git checkout -b fix/rollback-based-fix
+```
+
+### 3. Make Necessary Changes
+
+Implement the fix based on the stable version. Don't update version numbers yet.
+
+### 4. Test the Changes
+
+Test thoroughly to ensure the fix resolves the issues.
+
+### 5. When Confirmed Working
+
+Create a version branch with an incremented patch version and update all version numbers as described in the "Creating a Version Branch" section.

.ai-workflows/local-env-vars.md

@@ -0,0 +1,19 @@
+# Local Development Environment Variables
+
+This file contains important paths and URLs for local development.
+
+## Repository Paths
+- Local development repository: ~/Git/wp-fix-plugin-does-not-exist-notices
+- LocalWP plugin testing site storage: ~/Local/plugin-testing/app/wp-fix-plugin-does-not-exist-notices
+- LocalWP plugin testing site configuration: ~/Local/plugin-testing/conf/
+
+## URLs
+- LocalWP plugin testing URL: http://plugin-testing.local/
+- PHP details: http://plugin-testing.local/local-phpinfo.php
+- XDebug info: http://plugin-testing.local/local-xdebuginfo.php
+- Adminer Evo: http://localhost:10010/?username=root&db=local
+- Mailpit: http://localhost:10000/
+
+## Build and Deploy Scripts
+- Build script: ~/Git/wp-fix-plugin-does-not-exist-notices/build.sh
+- Local deploy script: ~/Git/wp-fix-plugin-does-not-exist-notices/deploy-local.sh

.ai-workflows/readme.md

@@ -0,0 +1,17 @@
+# 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
+- **dev-prefs-memory.md**: Persistent memory of developer preferences
+- **feature-development.md**: Process for developing new features
+- **folder-structure.md**: Documentation of the plugin's folder structure and naming conventions
+- **git-workflow.md**: Detailed git workflow and branch management guidelines
+- **incremental-development.md**: Time-efficient approach for incremental development and testing
+- **local-env-vars.md**: Local development environment paths and URLs
+- **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/release-process.md

@@ -0,0 +1,327 @@
+# 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
+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
+   - Only increment when numerous features and fixes are tested and confirmed stable
+
+**IMPORTANT**: For time-efficient development:
+- Use descriptive branches (`fix/`, `feature/`, `patch/`, `refactor/`) without version numbers during development
+- Don't update version numbers during initial development and testing
+- Only create version branches (e.g., `v2.2.3`) and update version numbers when changes are confirmed working
+
+This approach allows focusing on the changes without worrying about version updates until they're ready for release.
+
+For detailed guidelines on time-efficient development and testing, see **@.ai-workflows/incremental-development.md**.
+
+## Release Steps
+
+### 1. Create a Version Branch
+
+When changes are confirmed working and ready for release:
+
+```bash
+# First, ensure you have the latest main branch
+git checkout main
+git pull origin main
+
+# Option 1: If you're coming from a development branch
+git checkout fix/your-fix-branch  # or feature/your-feature-branch
+
+# Option 2: Create a version branch directly from main
+git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+```
+
+Example:
+```bash
+git checkout main
+git pull origin main
+
+# If coming from a development branch
+git checkout feature/add-new-selector
+
+# Create the version branch
+git checkout -b v2.3.0
+```
+
+**IMPORTANT**: The version branch is where you'll update all version numbers. This should only be done after the changes have been tested and confirmed working.
+
+For more detailed git workflow guidelines, see **@.ai-workflows/git-workflow.md**.
+
+### 2. Update Version Numbers
+
+Update the version number in the following files:
+
+#### a. Main Plugin File (wp-fix-plugin-does-not-exist-notices.php)
+
+Update both the plugin header and the version parameter in the Plugin class initialization:
+
+```php
+/**
+ * Plugin Name: Fix 'Plugin file does not exist.' Notices
+ * Plugin URI: https://www.wpallstars.com
+ * Description: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
+ * Version: {MAJOR}.{MINOR}.{PATCH}
+ * ...
+ */
+
+// At the bottom of the file, update the version parameter:
+new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '{MAJOR}.{MINOR}.{PATCH}');
+```
+
+#### b. JavaScript Files with Version Constants
+
+Check for any JavaScript files that might contain version constants:
+
+```javascript
+// Current plugin version - this should match the version in the main plugin file
+const CURRENT_VERSION = '{MAJOR}.{MINOR}.{PATCH}';
+```
+
+**Note**: As of version 2.2.1, we've removed redundant JavaScript files like `version-fix.js` since Git Updater now correctly detects the version from the main branch.
+
+#### c. CHANGELOG.md
+
+Add a new section at the top of the CHANGELOG.md file:
+
+```markdown
+All notable changes to this project should be documented both here and in the main Readme files.
+
+#### [{MAJOR}.{MINOR}.{PATCH}] - YYYY-MM-DD
+#### Added/Changed/Fixed
+- Change 1
+- Change 2
+- Change 3
+
+#### [{PREVIOUS_VERSION}] - YYYY-MM-DD
+```
+
+Note: Use the `####` heading format for consistency with the existing CHANGELOG.md structure.
+
+#### d. README.md
+
+Update the Changelog section in the main README.md file to match the changes in readme.txt:
+
+```markdown
+## Changelog
+
+### {MAJOR}.{MINOR}.{PATCH}
+* Change 1
+* Change 2
+* Change 3
+
+### {PREVIOUS_VERSION}
+```
+
+**IMPORTANT**: Always keep the changelogs in README.md, readme.txt, and CHANGELOG.md in sync to avoid confusion.
+
+#### e. POT File (languages/wp-fix-plugin-does-not-exist-notices.pot)
+
+Update the Project-Id-Version and POT-Creation-Date (IMPORTANT - don't forget this step!):
+
+```
+"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"
+```
+
+Note: Always use the current date for POT-Creation-Date in the format YYYY-MM-DD.
+
+#### f. readme.txt
+
+Update the stable tag:
+
+```
+Stable tag: {MAJOR}.{MINOR}.{PATCH}
+```
+
+Add a new entry to the changelog section:
+
+```
+= {MAJOR}.{MINOR}.{PATCH} =
+* Change 1
+* Change 2
+* Change 3
+```
+
+### 3. Build and Test
+
+#### Local Testing (Default for Incremental Development)
+
+For incremental development and testing, only local testing is required unless specifically requested:
+
+```bash
+./build.sh {MAJOR}.{MINOR}.{PATCH}
+```
+
+This will:
+1. Create a build directory
+2. Install composer dependencies
+3. Copy required files to the build directory
+4. Create a ZIP file named `wp-fix-plugin-does-not-exist-notices-{MAJOR}.{MINOR}.{PATCH}.zip`
+5. Deploy the plugin to your local WordPress testing environment
+
+Test the plugin thoroughly in your local WordPress environment:
+- Test with the latest WordPress version
+- Verify all features work as expected
+- Check for any PHP warnings or notices
+- Test any specific changes made in this version
+
+#### Remote Testing (When Specifically Requested)
+
+When the user specifically requests remote testing, follow these additional steps after local testing:
+
+1. Commit changes to the remote repository
+2. Create and push a tag
+3. Verify that GitHub Actions builds the installable ZIP file
+4. Test the remotely built version
+
+This is necessary when testing Git Updater integration or other features that require the plugin to be installed from a remote source.
+
+### 4. Commit Changes
+
+```bash
+git add wp-fix-plugin-does-not-exist-notices.php CHANGELOG.md README.md readme.txt languages/wp-fix-plugin-does-not-exist-notices.pot
+git commit -m "Version {MAJOR}.{MINOR}.{PATCH} - Brief description of changes"
+```
+
+Note: Make sure to include README.md in your commit to keep all changelog files in sync.
+
+### 5. Create a Tag
+
+```bash
+git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Version {MAJOR}.{MINOR}.{PATCH} - Brief description of changes"
+```
+
+#### Marking a Version as Stable
+
+When the user confirms that a version is working correctly and stable:
+
+```bash
+# Create a stable tag for easy reference
+git tag -a v{MAJOR}.{MINOR}.{PATCH}-stable -m "Stable version {MAJOR}.{MINOR}.{PATCH}"
+```
+
+This provides a clear reference point for stable versions that can be used for rollbacks if needed.
+
+### 6. Push Branch and Tag to Remotes
+
+```bash
+# Push the branch
+git push github feature/branch-name
+git push gitea feature/branch-name
+
+# Push the tag
+git push github v{MAJOR}.{MINOR}.{PATCH}
+git push gitea v{MAJOR}.{MINOR}.{PATCH}
+```
+
+### 7. Verify GitHub Release
+
+Check that the GitHub release was created successfully with the ZIP file attached:
+https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/releases
+
+If the release doesn't appear or doesn't have the ZIP file attached, check the GitHub Actions page:
+https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/actions
+
+### 8. Merge to Main (CRITICAL STEP)
+
+**IMPORTANT**: This step is critical for Git Updater to detect the new version. Git Updater reads the readme.txt file from the main branch, not from tags or releases.
+
+Merge the feature branch to main immediately after pushing the tag:
+
+```bash
+git checkout main
+git merge feature/branch-name --no-ff
+git push github main
+git push gitea main
+```
+
+The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
+
+**Note**: Only use named branches like feature/*, fix/*, etc. for development. Release branches (v*) should always be merged to main immediately after tagging to ensure Git Updater can detect the new version.
+
+### 9. Verify Release
+
+- [ ] Check that the GitHub release was created successfully with the ZIP file attached
+- [ ] Verify that the plugin was deployed to WordPress.org (if applicable)
+- [ ] Test the plugin from the GitHub release ZIP to ensure it works correctly
+- [ ] Verify that Git Updater can detect and install the new version
+- [ ] Confirm that all changelog files (README.md, readme.txt, and CHANGELOG.md) are in sync
+- [ ] Verify that all CI/CD checks have passed for the release
+
+## 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
@@ -8,10 +12,14 @@
 .distignore
 build.sh
 build
+.drone.yml
+.woodpecker.yml
 
 # Documentation
 CONTRIBUTING.md
 CODE_OF_CONDUCT.md
+CHANGELOG.md
+assets/README.md
 
 # Development files
 node_modules
@@ -31,6 +39,9 @@ package-lock.json
 composer.json
 composer.lock
 
+# WordPress.org specific
+.wordpress-org
+
 # Miscellaneous
 .DS_Store
 Thumbs.db
@@ -39,4 +50,6 @@ Thumbs.db
 *.log
 *.bak
 *.tmp
-*.zip 
+*.zip
+*~
+._*

.drone.yml

@@ -14,16 +14,16 @@ 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/wp-fix-plugin-does-not-exist-notices
+      - cp wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
+      - cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
+      - cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
+      - cp README.md build/wp-fix-plugin-does-not-exist-notices/
+      - cp CHANGELOG.md build/wp-fix-plugin-does-not-exist-notices/
       - cd build
-      - zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
+      - zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
       - cd ..
-      
+
   - name: release
     image: plugins/gitea-release
     settings:
@@ -31,9 +31,9 @@ steps:
         from_secret: gitea_token
       base_url: https://gitea.wpallstars.com
       files:
-        - plugin-reference-cleaner-*.zip
+        - wp-fix-plugin-does-not-exist-notices-*.zip
       title: Release ${DRONE_TAG}
       note: |
-        Plugin Reference Cleaner ${DRONE_TAG}
-        
-        See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/plugin-reference-cleaner/src/branch/main/CHANGELOG.md) for details. 
+        Fix 'Plugin file does not exist.' Notices ${DRONE_TAG}
+
+        See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/wp-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,32 +1,101 @@
+# 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
 
-# Text files that should be normalized
-*.php text
-*.css text
-*.js text
-*.htm text
-*.html text
-*.xml text
-*.txt text
-*.ini text
-*.inc text
-*.md text
-.htaccess text
+# Text files that should be normalized with LF line endings
+*.php text eol=lf
+*.css text eol=lf
+*.js text eol=lf
+*.scss text eol=lf
+*.htm text eol=lf
+*.html text eol=lf
+*.xml text eol=lf
+*.txt text eol=lf
+*.ini text eol=lf
+*.inc text eol=lf
+*.md text eol=lf
+*.json text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
+*.po text eol=lf
+*.pot text eol=lf
+*.svg text eol=lf
+.htaccess text eol=lf
 
 # Files that should be treated as binary
 *.png binary
 *.jpg binary
+*.jpeg binary
 *.gif binary
 *.ico binary
+*.webp binary
 *.zip binary
 *.gz binary
 *.tar binary
 *.ttf binary
 *.eot binary
 *.woff binary
+*.woff2 binary
+*.pxd binary
+*.afdesign binary
+*.afphoto binary
+*.afpub binary
+
+# Exclude files from export (for WordPress.org SVN and distribution packages)
+.gitattributes export-ignore
+.gitignore export-ignore
+.github export-ignore
+.wordpress-org export-ignore
+README.md export-ignore
+CHANGELOG.md export-ignore
+composer.json export-ignore
+composer.lock export-ignore
+package.json export-ignore
+package-lock.json export-ignore
+phpcs.xml export-ignore
+.phpcs.xml export-ignore
+phpunit.xml export-ignore
+.phpunit.xml export-ignore
+.distignore export-ignore
+.editorconfig export-ignore
+.eslintrc export-ignore
+.eslintignore export-ignore
+.prettierrc export-ignore
+.prettierignore export-ignore
+.stylelintrc export-ignore
+.stylelintignore export-ignore
+.travis.yml export-ignore
+.gitlab-ci.yml export-ignore
+bitbucket-pipelines.yml export-ignore
+bin export-ignore
+tests export-ignore
+assets/icon/*.svg export-ignore
+assets/banner/*.svg export-ignore
+assets/screenshots/*.pxd export-ignore
+assets/icon/*.pxd export-ignore
+assets/banner/*.pxd export-ignore
+
+# AI assistant and workflow files
+.ai-assistant.md export-ignore
+.ai-workflows export-ignore
+.augmentignore export-ignore
+.cursorignore export-ignore
+.v0ignore export-ignore
+.clinerc export-ignore
+.continuerc export-ignore
+reference-plugins export-ignore
 
 # Set the default behavior for GitHub language detection
 *.css linguist-language=CSS
 *.js linguist-language=JavaScript
-*.php linguist-language=PHP 
+*.php linguist-language=PHP
+*.scss linguist-language=SCSS
+*.pot linguist-language=Gettext Catalog
+*.po linguist-language=Gettext Catalog
+*.mo linguist-language=Gettext Catalog
+
+# Merge driver for changelog files to prevent conflicts
+CHANGELOG.md merge=union
+readme.txt merge=union

.github/workflows/assets.yml

@@ -0,0 +1,23 @@
+name: Plugin Asset Update
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - '.wordpress-org/**'
+
+jobs:
+  assets:
+    name: Push assets to WordPress.org
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: WordPress.org plugin asset/readme update
+        uses: 10up/action-wordpress-plugin-asset-update@stable
+        env:
+          SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
+          SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
+          SLUG: wp-fix-plugin-does-not-exist-notices

.github/workflows/release.yml

@@ -20,19 +20,34 @@ jobs:
         run: echo "VERSION=${GITHUB_REF#refs/tags/v}" >> $GITHUB_OUTPUT
 
       - name: Create build directory
-        run: mkdir -p build/plugin-reference-cleaner
+        run: mkdir -p build/wp-fix-plugin-does-not-exist-notices
 
       - name: Copy plugin files
         run: |
-          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 wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
+          cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
+          cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
+          cp README.md build/wp-fix-plugin-does-not-exist-notices/
+          cp -r admin build/wp-fix-plugin-does-not-exist-notices/
+          cp -r includes build/wp-fix-plugin-does-not-exist-notices/
+
+          # Copy directories if they exist
+          if [ -d "assets" ]; then
+            cp -r assets build/wp-fix-plugin-does-not-exist-notices/
+          fi
+
+          if [ -d "languages" ]; then
+            cp -r languages build/wp-fix-plugin-does-not-exist-notices/
+          fi
+
+          if [ -d ".wordpress-org" ]; then
+            cp -r .wordpress-org build/wp-fix-plugin-does-not-exist-notices/
+          fi
 
       - name: Create ZIP file
         run: |
           cd build
-          zip -r ../plugin-reference-cleaner-${{ steps.get_version.outputs.VERSION }}.zip plugin-reference-cleaner
+          zip -r ../wp-fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip wp-fix-plugin-does-not-exist-notices
 
       - name: Create Release
         id: create_release
@@ -42,8 +57,27 @@ jobs:
           draft: false
           prerelease: false
           files: |
-            plugin-reference-cleaner-${{ steps.get_version.outputs.VERSION }}.zip
+            wp-fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip
           body: |
-            Plugin Reference Cleaner v${{ steps.get_version.outputs.VERSION }}
-            
-            See [CHANGELOG.md](https://github.com/wpallstars/plugin-reference-cleaner/blob/main/CHANGELOG.md) for details. 
+            Fix 'Plugin file does not exist.' Notices v${{ steps.get_version.outputs.VERSION }}
+
+            See [CHANGELOG.md](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/blob/main/CHANGELOG.md) for details.
+
+  # Deploy to WordPress.org
+  wordpress:
+    name: Deploy to WordPress.org
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: WordPress Plugin Deploy
+        id: deploy
+        uses: 10up/action-wordpress-plugin-deploy@stable
+        with:
+          generate-zip: true
+        env:
+          SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
+          SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
+          SLUG: wp-fix-plugin-does-not-exist-notices

.gitignore

@@ -3,6 +3,9 @@
 Thumbs.db
 ehthumbs.db
 Desktop.ini
+._*
+.Spotlight-V100
+.Trashes
 
 # Editor files
 *.swp
@@ -12,11 +15,23 @@ Desktop.ini
 .vscode/
 *.sublime-project
 *.sublime-workspace
+*.komodoproject
+.komodotools
+*.tmproj
+*.tmproject
+.project
+.settings/
 
 # Dependency directories
 node_modules/
 vendor/
 bower_components/
+composer.lock
+package-lock.json
+
+# Composer
+vendor/
+composer.phar
 
 # Build files
 build/
@@ -30,6 +45,9 @@ wp-content/backup-db/
 wp-content/cache/
 wp-content/backups/
 
+# Reference plugins
+reference-plugins/
+
 # Log files
 *.log
 error_log
@@ -38,4 +56,117 @@ debug.log
 # Misc
 .env
 .env.*
-!.env.example 
+!.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/ # Needed for GitHub Actions
+.gitlab/
+# .gitattributes # Needed for file handling
+.travis.yml
+# .drone.yml # Needed for Drone CI
+# .woodpecker.yml # Needed for Woodpecker CI
+codecov.yml
+.babelrc
+.browserslistrc
+.editorconfig
+.eslintignore
+.eslintrc
+.prettierrc
+.stylelintrc
+webpack.config.js
+gulpfile.js
+Gruntfile.js
+*.zip

.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,28 +9,28 @@ 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/wp-fix-plugin-does-not-exist-notices
+      - cp wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
+      - cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
+      - cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
+      - cp README.md build/wp-fix-plugin-does-not-exist-notices/
+      - if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/wp-fix-plugin-does-not-exist-notices/; fi
       - cd build
-      - zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
+      - zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
       - cd ..
-      - echo "Build completed - plugin-reference-cleaner-$VERSION.zip"
+      - echo "Build completed - wp-fix-plugin-does-not-exist-notices-$VERSION.zip"
       - ls -la *.zip
-      
+
   release:
     image: plugins/gitea-release
     environment:
       PLUGIN_API_KEY:
         from_secret: gitea_token
       PLUGIN_BASE_URL: https://gitea.wpallstars.com
-      PLUGIN_FILES: plugin-reference-cleaner-*.zip
+      PLUGIN_FILES: wp-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/wp-fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details."
+
   test:
     image: alpine:latest
     commands:
@@ -38,4 +38,4 @@ steps:
       - echo "Testing minimal configuration"
 
 when:
-  event: [push, tag, pull_request] 
+  event: [push, tag, pull_request]

.wordpress-org/README.md

@@ -0,0 +1,65 @@
+# WordPress.org Plugin Repository Assets
+
+This directory contains assets specific to the WordPress.org plugin repository and is used for automatic deployment via GitHub Actions.
+
+## Directory Structure
+
+```
+/.wordpress-org/
+    /assets/
+        icon-256x256.png
+        icon-128x128.png
+        banner-772x250.png
+        banner-1544x500.png
+        screenshot-1.png
+```
+
+## Asset Organization
+
+- **All Asset Files**: All files for WordPress.org are stored in this directory (`.wordpress-org/assets/`)
+  - PNG files (icon-256x256.png, banner-772x250.png, etc.)
+  - Source files (PXD, SVG)
+  - Documentation
+
+## Purpose
+
+When using GitHub Actions for WordPress.org plugin deployments (via the 10up WordPress GitHub Actions), this directory is used to automatically update plugin assets in the WordPress.org repository.
+
+## Naming Conventions
+
+Files must be named exactly as shown above to be properly recognized by the WordPress.org system during the deployment process:
+
+### Banner Images
+- `banner-772x250.png` - 772x250 pixel PNG banner (required for WordPress.org)
+- `banner-1544x500.png` - 1544x500 pixel PNG banner for high-DPI displays (optional for WordPress.org)
+
+### Icon Images
+- `icon-256x256.png` - 256x256 pixel PNG icon (required for WordPress.org)
+- `icon-128x128.png` - 128x128 pixel PNG icon (optional for WordPress.org)
+
+### Screenshots
+- `screenshot-1.png` - Main screenshot showing the plugin in action
+
+## Right-to-Left (RTL) Support
+
+For plugins that support Right-to-Left languages (like Hebrew and Arabic), you can provide RTL versions of assets by appending `-rtl` to the filename:
+
+- `banner-772x250-rtl.png`
+- `banner-1544x500-rtl.png`
+- `icon-256x256-rtl.png`
+
+Note that the `-rtl` suffix is specifically for Right-to-Left language support, not for dark mode versions of assets.
+
+## Build Process
+
+The build script (`build.sh`) is configured to:
+1. Use all asset files from the `.wordpress-org/assets/` directory
+2. Copy these files to the appropriate locations in the build directory
+
+## Additional Resources
+
+For more detailed information about WordPress.org plugin assets, please see:
+
+- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
+- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
+- [WordPress.org Plugin Submission Assets Guide](./.wordpress-org/WORDPRESS_ORG_ASSETS.md)

.wordpress-org/WORDPRESS_ORG_ASSETS.md

@@ -0,0 +1,123 @@
+# WordPress.org Plugin Submission Assets Guide
+
+This document explains how to prepare and upload assets for WordPress.org plugin submission. This is the main reference document for all asset-related information.
+
+## WordPress.org SVN Repository Structure
+
+When submitting a plugin to WordPress.org, you'll work with an SVN repository that has this structure:
+
+```
+/assets/         # Contains assets for the WordPress.org plugin page
+    icon-256x256.png
+    icon-128x128.png
+    banner-772x250.png
+    banner-1544x500.png
+    screenshot-1.png
+/tags/           # Contains tagged releases
+    /2.2.5/
+        [plugin files]
+    /2.2.4/
+        [plugin files]
+/trunk/          # Contains the current version of the plugin
+    [plugin files]
+```
+
+## Right-to-Left (RTL) Support
+
+For languages that read from right to left (like Hebrew and Arabic), you can provide RTL-specific versions of your assets by appending `-rtl` to the filename. For example:
+- `banner-772x250-rtl.png`
+- `icon-256x256-rtl.png`
+
+## 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 `.wordpress-org/assets/`
+
+### 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 `.wordpress-org/assets/`
+
+### Screenshots
+
+- **Format**: PNG
+- **Naming**: `screenshot-1.png`
+- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
+- **Status**: ✅ READY - Files are in `.wordpress-org/assets/`
+
+## 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/wp-fix-plugin-does-not-exist-notices/
+
+   # Copy plugin files to trunk
+   cp -r [your-local-plugin-files]/* wp-fix-plugin-does-not-exist-notices/trunk/
+
+   # Copy assets to assets directory
+   cp .wordpress-org/assets/icon-256x256.png wp-fix-plugin-does-not-exist-notices/assets/
+   cp .wordpress-org/assets/icon-128x128.png wp-fix-plugin-does-not-exist-notices/assets/
+   cp .wordpress-org/assets/banner-772x250.png wp-fix-plugin-does-not-exist-notices/assets/
+   cp .wordpress-org/assets/banner-1544x500.png wp-fix-plugin-does-not-exist-notices/assets/
+   cp .wordpress-org/assets/screenshot-1.png wp-fix-plugin-does-not-exist-notices/assets/
+
+   # Add new files
+   cd wp-fix-plugin-does-not-exist-notices
+   svn add --force trunk/*
+   svn add --force assets/*
+
+   # Commit changes
+   svn commit -m "Initial plugin submission"
+   ```
+
+## Image Conversion Tools
+
+For converting SVG to PNG or creating different sizes of images, you can use:
+
+- **Graphic Design Software**:
+  - Adobe Photoshop
+  - Adobe Illustrator
+  - Affinity Designer
+  - Affinity Photo
+  - GIMP (free, open-source)
+  - Inkscape (free, open-source)
+  - Pixelmator
+
+- **Online Converters**:
+  - [SVG to PNG Converter](https://svgtopng.com/)
+  - [Convertio](https://convertio.co/svg-png/)
+  - [CloudConvert](https://cloudconvert.com/svg-to-png)
+
+- **Command Line** (using ImageMagick):
+  ```bash
+  # For 256x256 icon
+  convert -background none -size 256x256 .wordpress-org/assets/icon.svg .wordpress-org/assets/icon-256x256.png
+
+  # For 128x128 icon
+  convert -background none -size 128x128 .wordpress-org/assets/icon.svg .wordpress-org/assets/icon-128x128.png
+  ```
+
+## Resources
+
+- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
+- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)

.wordpress-org/WORDPRESS_ORG_SUBMISSION.md

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

CHANGELOG.md

@@ -1,75 +1,498 @@
-# Changelog
+All notable changes to this project should be documented both here and in the main Readme files.
 
-All notable changes to this project will be documented in this file.
+#### [2.3.0] - 2025-04-15
+#### Added
+- Improved time-efficient development workflow documentation
+- New git workflow guidelines for better branch management
+- Comprehensive incremental development approach
 
-## [1.3.0] - 2023-10-05
-### Changed
+#### Improved
+- Documentation for local vs. remote testing
+- Version management process for more efficient development
+
+#### [2.2.5] - 2025-04-14
+#### Added
+- Documentation for the developer preferences memory file in .ai-workflows/
+- Improved AI assistant instructions for maintaining developer preferences
+- Updated version numbers across all files for consistency
+
+#### [2.2.4] - 2025-04-14
+#### Added
+- Developer preferences memory file for AI assistants
+- Improved AI assistant documentation with instructions for maintaining developer preferences
+- Updated WordPress.org documentation with correct plugin slug and version numbers
+
+#### [2.2.3] - 2025-04-14
+#### Changed
+- Moved admin-specific files to admin/lib directory for better organization
+- Updated namespaces to reflect the new file locations
+- Added comprehensive folder structure documentation
+- Fixed file references in the main plugin file
+
+#### [2.2.2-stable] - 2025-04-14
+#### Changed
+- Renamed includes files to lowercase for consistency with the rest of the codebase
+- Removed redundant Git Updater patches and version-fix.js as they're no longer needed
+- Improved documentation for Git Updater integration and release process
+- Fixed token-efficient documentation with references to .ai-workflows files
+- Added comprehensive release process documentation with emphasis on merging to main branch
+
+#### [2.2.1] - 2025-04-14
+#### Changed
+- Commented out version-fix.js script as it's no longer needed after refactoring
+- Fixed version consistency across all files
+
+#### [2.2.0] - 2025-04-14
+#### Added
+- Completely refactored plugin to use OOP best practices
+- New class structure with proper namespaces
+- Improved code organization and maintainability
+- Better separation of concerns with dedicated classes
+
+#### Changed
+- Changed "Choose Update Source" link to just "Update Source"
+- Fixed close button in the update source modal
+- Added links to the main page for each update source in the modal
+- Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
+
+#### [2.1.1] - 2025-04-13
+#### Added
+- New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
+- Modal dialog with detailed information about each update source option
+- Visual indicator showing the currently selected update source
+
+#### Fixed
+- Updated heading styles in CHANGELOG.md for better readability
+- Corrected dates in changelog to use 2025 instead of 2024
+
+#### Improved
+- Documentation improvements for better clarity
+- Enhanced Git Updater integration with user-selectable update sources
+
+#### [2.1.0] - 2025-04-13
+#### Changed
+- Minor version bump for Git Updater compatibility
+
+#### Improved
+- Error handling for Git Updater integration
+- Type checking in branch fix functions
+- Documentation for Git Updater installation and cache refreshing
+
+#### [2.0.13] - 2025-04-12
+#### Fixed
+- Critical error when Git Updater passes an object instead of a string to API URL filter
+- Type checking in branch fix functions to handle both string and object inputs
+
+#### Improved
+- Error handling for Git Updater integration
+- Documentation for Git Updater installation and cache refreshing
+
+#### [2.0.12] - 2025-04-11
+#### Fixed
+- Integrated Git Updater branch fix directly into main plugin
+- Removed separate "GU Branch Fix" plugin (no longer needed)
+
+#### Added
+- Documentation explaining branch fix integration
+
+#### Improved
+- Compatibility with Git Updater plugin
+- Deploy script to remove separate branch fix plugin
+
+#### [2.0.11] - 2025-04-10
+#### Added
+- Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
+- Added deploy script for local testing
+
+#### Fixed
+- Git Updater branch issues with 'main' vs 'master' branch names
+- Improved compatibility with Git Updater plugin
+
+#### [2.0.10] - 2025-04-09
+#### Fixed
+- Plugin details popup version display issue with Git Updater integration
+- Added JavaScript-based solution to ensure correct version display in plugin details
+
+#### Improved
+- Version consistency across all plugin views
+- Enhanced cache busting for plugin information API
+
+#### [2.0.9] - 2025-04-08
+#### Fixed
+- Plugin details popup now correctly shows version and author information
+- Added support for both old and new plugin slugs to fix caching issues
+
+#### Improved
+- Cache clearing mechanism to ensure plugin details are always up-to-date
+- Enhanced version display in plugin details popup
+
+#### [2.0.8] - 2025-04-07
+#### Fixed
+- Plugin details popup now correctly shows version and author information
+- Added cache-busting mechanism to ensure plugin details are always up-to-date
+
+#### Improved
+- Author and contributor information display in plugin details
+- Added WordPress 6.5 compatibility indicator
+
+#### [2.0.7] - 2025-04-06
+#### Changed
+- Additional text improvements and minor fixes
+
+#### [2.0.6] - 2025-04-05
+#### Changed
+- Text improvements and minor fixes
+
+#### [2.0.5] - 2025-04-04
+#### Fixed
+- Display correct version in plugin details popup
+
+#### [2.0.4] - 2025-04-03
+#### Fixed
+- Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
+
+#### [2.0.2] - 2025-04-02
+#### Changed
+- Consolidated WordPress.org assets into .wordpress-org directory
+- Improved organization of assets for WordPress.org submission
+- Updated .wordpress-org/README.md with comprehensive information
+
+#### [2.0.1] - 2025-04-01
+#### Added
+- Contributing section to readme.txt
+- reference-plugins directory for plugin development inspiration
+
+#### Changed
+- Updated "tested up to" version to WordPress 6.7.2
+- Improved .gitattributes with comprehensive file handling
+- Enhanced documentation organization
+
+#### [2.0.0] - 2025-03-31
+#### Added
+- Note clarifying that the plugin has no settings page
+- Clarification that functionality is limited to the admin plugins page only
+
+#### Changed
+- Major version release for WordPress.org submission
+- Finalized all assets and documentation for public release
+
+#### [1.6.28] - 2025-03-30
+#### Changed
+- Consolidated asset documentation into a single comprehensive guide
+- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
+- Updated all asset README files to point to the main documentation
+- Improved file organization and documentation structure
+
+#### [1.6.27] - 2025-03-29
+#### Changed
+- Clarified RTL support in WordPress.org asset documentation
+- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
+- Consolidated asset files and improved documentation
+
+#### [1.6.26] - 2025-03-28
+#### 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] - 2025-03-27
+#### 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] - 2025-03-26
+#### 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] - 2025-03-25
+#### 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] - 2025-03-24
+#### 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] - 2025-03-23
+#### 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] - 2025-03-22
+#### 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] - 2025-03-21
+#### 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] - 2025-03-20
+#### 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] - 2025-03-19
+#### 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] - 2025-03-18
+#### 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] - 2025-03-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] - 2025-03-16
+#### 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] - 2025-03-15
+#### Changed
+- Code cleanup and optimization
+- Improved Git Updater integration
+- Fixed author display in plugin information
+- Ensured compatibility with WordPress 6.4
+
+#### [1.6.12] - 2025-03-14
+#### Added
+- Added WPALLSTARS as a co-author
+- Updated author information and links
+- Added author websites to plugin description
+- Fixed issue with multiple author URLs
+
+#### [1.6.11] - 2025-03-13
+#### Fixed
+- Improved Git Updater integration
+- Fixed plugin header information
+- Updated author information
+
+#### [1.6.10] - 2025-03-12
+#### Fixed
+- Corrected plugin header information
+- Improved Git Updater compatibility
+- Updated documentation
+
+#### [1.6.9] - 2025-03-11
+#### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+- Improved documentation
+
+#### [1.6.8] - 2025-03-10
+#### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+#### [1.6.7] - 2025-03-09
+#### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+#### [1.6.6] - 2025-03-08
+#### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+#### [1.6.5] - 2025-03-07
+#### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+#### [1.6.4] - 2025-03-06
+#### 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] - 2025-03-05
+#### 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 'WPALLSTARS'
+- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
+#### [1.6.2] - 2025-03-04
+#### 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] - 2025-03-03
+#### Added
+- AI assistant guide and workflow documentation
+- Detailed release process documentation
+- Feature development guidelines
+- Bug fixing procedures
+- Code review standards
+
+#### [1.6.0] - 2025-03-02
+#### 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] - 2025-03-01
+#### 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] - 2025-02-28
+#### Added
+- FAQ about keeping the plugin installed after notices are cleared
+
+#### [1.4.0] - 2025-02-27
+#### Changed
+- Updated plugin name and text domain
+- Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
+
+#### [1.3.3] - 2025-02-26
+#### Added
+- "Click here to scroll" button to automatically find missing plugins
+- Visual arrow pointing from notification to error message
+- Smooth scrolling with highlighting of missing plugin rows
+
+#### Improved
+- Notification reliability using multiple injection methods
+- Earlier placement in page load cycle for better visibility
+- Enhanced error detection for all WordPress error message formats
+
+#### [1.3.2] - 2025-02-25
+#### Added
+- Prominent notification that appears directly below WordPress error messages
+- Visual styling to help users connect error message with solution
+- Direction arrows and highlighted text to improve user guidance
+
+#### [1.3.1] - 2025-02-24
+#### Added
+- Instructional notification explaining how to use the plugin
+- Step-by-step guidance for removing plugin references
+- Clear visual indicators for missing plugins
+
+#### [1.3.0] - 2025-02-23
+#### Changed
 - Complete redesign for maximum compatibility with all WordPress themes
 - Now uses the plugins list table for missing plugin references
 - Uses standard WordPress admin UI patterns and hooks
 
-### Added
+#### Added
 - Missing plugins now appear directly in the plugins list
 - "Remove Reference" action link in the plugins list
 - Success/error notices after removing references
 
-### Fixed
+#### Fixed
 - Compatibility issues with various WordPress admin themes
 - Reliability issues with notification detection
 
-## [1.2.4] - 2023-10-05
-### Fixed
+#### [1.2.4] - 2025-02-22
+#### Fixed
 - Compatibility with more WordPress admin UI variations
 - Specific targeting for admin notices in various themes
 
-### Added
+#### Added
 - Advanced DOM traversal using TreeWalker API
 - Multiple fallback approaches to ensure button appears
 - Enhanced console logging for troubleshooting
 
-## [1.2.3] - 2023-10-05
-### Fixed
+#### [1.2.3] - 2025-02-21
+#### Fixed
 - Button not appearing in some WordPress admin themes
 - Error message detection for greater theme compatibility
 
-### Improved
+#### Improved
 - DOM traversal to find notification elements in various themes
 - Added console logging for troubleshooting
 
-## [1.2.2] - 2023-10-05
-### Fixed
+#### [1.2.2] - 2025-02-20
+#### Fixed
 - Timeout issue during plugin activation
 - Potential infinite recursion in admin notices handling
 
-### Improved
+#### Improved
 - Hook management to prevent performance issues
 - Optimized by only loading on plugins page
 
-## [1.2.1] - 2025-04-07
-### Improved
+#### [1.2.1] - 2025-04-07
+#### Improved
 - Fixed typos in documentation
 - Improved text clarity
 - Added question mark to first sentence for better readability
 
-## [1.2] - 2025-04-07
-### Added
+#### [1.2] - 2025-04-07
+#### Added
 - Improved documentation with detailed explanation
 - Added SQL reference for technical users
 - Suggested potential inclusion in WordPress core
 
-## [1.1] - 2025-04-07
-### Added
+#### [1.1] - 2025-04-07
+#### Added
 - Support for multisite WordPress installations
 - Network admin page integration
 - Woodpecker CI integration for automated releases
 
-### Improved
+#### Improved
 - Error handling
 - User experience with better confirmation messages
 - Security by adding proper capability checks
 
-## [1.0] - 2025-03-15
-### Added
+#### [1.0] - 2025-03-15
+#### Added
 - Initial release
 - "Remove Reference" button for plugin deactivation error notices
-- AJAX processing for reference removal 
+- AJAX processing for reference removal

README.md

@@ -1,93 +1,556 @@
-# Plugin Reference Cleaner
-Author: Marcus Quinn
-Author URI: https://www.wpallstars.com
-Version: 1.3.0
-License: GPL-2.0+
+# Fix 'Plugin file does not exist.' Notices
+
+[![WordPress Plugin Version](https://img.shields.io/wordpress/plugin/v/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
+[![WordPress Plugin Rating](https://img.shields.io/wordpress/plugin/rating/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
+[![WordPress Plugin Downloads](https://img.shields.io/wordpress/plugin/dt/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
+[![License](https://img.shields.io/badge/license-GPL--2.0%2B-blue.svg)](https://www.gnu.org/licenses/gpl-2.0.html)
+
+Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
 
 ## Description
 
-Have you ever deleted a plugin some other way than through the /wp-admin/plugins.php page? If so, you've probably been stuck with this annoying notification that can't be cleared:
+Have you ever deleted a plugin directly from the server or database and then been stuck with annoying error notifications that can't be cleared?
 
 "The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
 
-This small WordPress utility plugin adds a "Remove Reference" button to these plugin deactivation error notices, allowing you to clean up the invalid plugin entries in the database.
+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.
 
-When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin enhances those notices with a button that allows you to safely remove the invalid reference with a single click.
+**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
 
-You can find these with `SELECT * FROM wp_options WHERE option_name = 'active_plugins';` — but the cleanup involves removing the rogue entry, and renumbering all others. This plugin can simply do that for you at the click of a button added to that WP standard notification.
+### Key Features
 
-It's probably something that should be added to WP core. If anyone from the core team wants to adopt this solution, it's GPL, so feel free.
+* Adds missing plugins directly to your plugins list
+* Provides a simple "Remove Notice" action link
+* Works with both single site and multisite WordPress installations
+* Includes helpful notifications explaining how to fix plugin errors
+* One-click auto-scroll to find missing plugins in large sites
+* Clean, user-friendly interface following WordPress design patterns
+* Integrated Git Updater branch fix (changes 'master' to 'main' for proper updates)
 
-Note: This plugin only needs to be installed and active if you have an error notification showing at /wp-admin/plugins.php, like this:
-"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
+### How It Works
 
-If you don't have this notification perpetually showing on your /wp-admin/plugins.php page, then you don't need this, but you might like to save or bookmark it for if ever you do.
+When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin:
 
-## Features
+1. Detects all missing plugin references in your database
+2. Adds them to your plugins list with "(File Missing)" indicators
+3. Provides a "Remove Notice" link to safely remove them
+4. Shows clear notifications guiding you through the cleanup process
+5. Safely removes the missing active plugin reference from your database using standard WordPress functions
+6. Leaves all remaining plugins installed and active
 
-* Adds a "Remove Reference" button to plugin error notices
-* Works for both single site and multisite WordPress installations
-* Confirms before removing any plugin references
-* Simple, lightweight solution with no settings page required
-* Secure implementation with proper permissions checking
-* Compatible with WordPress 5.0+
+### Use Cases
+
+* You've accidentally deleted a plugin via FTP
+* A plugin was removed by another admin but references remain
+* You've migrated from another site and have leftover plugin references
+* Your hosting provider removed a plugin but didn't clean the database
 
 ## Installation
 
-1. Upload the plugin-reference-cleaner.php file to your /wp-content/plugins/ directory
-2. Activate the plugin through the 'Plugins' menu in WordPress
-3. No configuration needed - the plugin works automatically
+### From WordPress.org:
+
+1. Visit Plugins > Add New in your WordPress admin
+2. Search for "Fix 'Plugin file does not exist.' Notices"
+3. Click "Install Now" and then "Activate"
+
+### Manual Installation:
+
+1. Download the plugin ZIP file
+2. Go to Plugins > Add New > Upload Plugin
+3. Upload the ZIP file
+4. Activate the plugin
 
 ## Usage
 
-1. Navigate to Plugins > Installed Plugins
-2. If any "Plugin file does not exist" error notices appear, a "Remove Reference" button will be displayed
-3. Click the button and confirm to remove the invalid plugin reference
-4. The page will refresh with the error notice removed
+1. After activation, navigate to Plugins > Installed Plugins
+2. If you have missing plugin errors, you'll see them in your plugins list with "(File Missing)" markers
+3. Click the "Remove Notice" link next to any missing plugin
+4. The reference will be removed, and the error notification will disappear
 
-## Changelog
+### Using with Git Updater
 
-### 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
+If you've installed this plugin from GitHub or Gitea, you'll need Git Updater to receive updates:
 
-### 1.2.4
-* Fixed compatibility with more WordPress admin themes
-* Added advanced DOM traversal to find error messages
-* Implemented fallback mechanisms to ensure button appears
-* Added detailed console logging for troubleshooting
+1. Install the Git Updater plugin from [git-updater.com/git-updater/](https://git-updater.com/git-updater/)
+2. Go to Settings > Git Updater > Remote Management
+3. Click the "Refresh Cache" button to ensure Git Updater recognizes the latest version
+4. Updates will now appear in your WordPress dashboard when available
 
-### 1.2.3
-* Fixed button not appearing in some WordPress admin themes
-* Improved error message detection for greater compatibility
-* Enhanced DOM traversal to find notification elements
+### Choosing Your Update Source
 
-### 1.2.2
-* Fixed timeout issue during plugin activation
-* Improved hook management to prevent potential infinite recursion
-* Optimized performance by only loading on plugins page
+This plugin allows you to choose where you want to receive updates from:
 
-### 1.2.1
-* Fixed typos in documentation
-* Improved text clarity
-* Added question mark to first sentence for better readability
+1. In the Plugins list, find "Fix 'Plugin file does not exist' Notices"
+2. Click the "Choose Update Source" link next to the plugin
+3. Select your preferred update source:
+   - **WordPress.org**: Updates from the official WordPress.org repository (has a version update delay due to the WP.org policy review and approval process, best for unmonitored auto-updates)
+   - **GitHub**: Updates directly from the GitHub repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates where the latest features and fixes are needed immediately)
+   - **Gitea**: Updates directly from the Gitea repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates and independence from big-tech)
+4. Click "Save" to apply your preference
 
-### 1.2
-* Improved documentation with detailed explanation
-* Added SQL reference for technical users
-* Suggested potential inclusion in WordPress core
+> **Note:** If no preference is set, the plugin will automatically use the source it was installed from.
 
-### 1.1
-* Improved error handling
-* Added support for multisite installations
-* Enhanced security with proper capability checks
+> **Note:** GitHub and Gitea options require the Git Updater plugin to be installed and activated.
 
-### 1.0
-* Initial release
+## Frequently Asked Questions
+
+### Is it safe to remove plugin references?
+
+Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists. It doesn't modify any other database tables or settings.
+
+### What happens after I remove a reference?
+
+The plugin entry will be removed from your active plugins list, and the corresponding error notification will no longer appear after you refresh the page.
+
+### Can I use this plugin on a multisite installation?
+
+Yes, the plugin works on both single sites and multisite installations. It properly handles network-activated plugins as well.
+
+### How do I know which plugin references should be removed?
+
+The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+
+### Will this break my site?
+
+No. Since the plugin is only removing references to plugins that no longer exist, removing these references won't affect your site's functionality. In fact, it's cleaning up remnants that might be causing issues.
+
+### What if I accidentally remove a reference I shouldn't have?
+
+If you remove a reference to a plugin that you later want to reinstall, simply install the plugin again and activate it normally.
+
+### Do I need to keep this plugin installed and active after notices are cleared?
+
+Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
+
+### How do I fix the "Plugin file does not exist" error in WordPress?
+
+This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
+
+### Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"?
+
+This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
+
+### Can this plugin fix errors after migrating a WordPress site?
+
+Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
+
+### Is it safe to remove plugin references that show "Plugin file does not exist"?
+
+Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
+
+### How is this different from manually editing the database?
+
+Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
+
+## Screenshots
+
+1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
 
 ## 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/wp-fix-plugin-does-not-exist-notices/)
+* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
+* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
+
+## Reviews
+
+This utility plugin is released under the GPLv2 license as free open source software.
+
+If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org.
+
+Your experience and feedback helps others discover the plugin, and encourages continued community-driven, open-source development and support.
+
+## Developers
+
+### Contributing
+
+Contributions are welcome! Please follow these steps to set up a development environment:
+
+1. Install [LocalWP](https://localwp.com/) and create a clean site called "Plugin Testing" using the "Preferred" setup option
+2. Run "Site shell" once from the LocalWP page on the site's settings to ensure wp-cli is enabled
+3. Run "Add Run Configurations to VS Code" to update site configuration files in: ~/Local/plugin-testing/conf/
+4. Clone this repository to your local machine, in `~/Git/` or wherever you keep your Git repositories.
+5. Use the build.sh and deploy-local.sh scripts to build and deploy the plugin for testing
+
+[AugmentCode.com](https://augmentcode.com/) is recommended as a good all-in-one AI IDE for plugin development and testing.
+
+Please feel free to submit a Pull Request with your improvements.
+
+1. Fork the repository
+2. Create your feature branch: `git checkout -b feature/amazing-feature`
+3. Commit your changes: `git commit -m 'Add some amazing feature'`
+4. Push to the branch: `git push origin feature/amazing-feature`
+5. Submit a pull request
+
+### AI-Powered Development
+
+This repository is configured to work with various AI-powered development tools. You can use any of the following AI IDEs to contribute to this project:
+
+- [Augment Code](https://www.augmentcode.com/) - AI-powered coding assistant
+- [Cursor](https://cursor.com/) - AI-first code editor
+- [v0](https://v0.dev/) - AI-powered design and development tool
+- [Windsurf](https://www.windsurf.com/) - AI coding assistant
+- [Cline](https://cline.bot/) - AI terminal assistant
+- [Roo Code](https://roocode.com/) - AI pair programmer
+- [Loveable](https://lovable.dev/) - AI development environment
+- [Bolt](https://www.bolt.new/) - AI-powered code editor
+- [Cody](https://sourcegraph.com/cody) - Sourcegraph's AI coding assistant
+- [Continue](https://continue.dev/) - Open-source AI coding assistant
+
+The repository includes configuration files for all these tools to ensure a consistent development experience.
+
+### Technical Details
+
+The plugin works by:
+1. Filtering the `all_plugins` array to add missing plugins
+2. Adding a custom "Remove Notice" action link via `plugin_action_links`
+3. Adding helpful notifications near error messages
+4. Providing a secure method to remove plugin references from the database
+
+### Git Updater Integration
+
+This plugin is designed to work seamlessly with the Git Updater plugin for updates from GitHub and Gitea. To ensure proper integration:
+
+1. **Required Headers**: The plugin includes specific headers in the main plugin file that Git Updater uses to determine update sources and branches:
+   ```php
+   * GitHub Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
+   * GitHub Branch: main
+   * Primary Branch: main
+   * Release Branch: main
+   * Release Asset: true
+   * Gitea Plugin URI: https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+   * Gitea Branch: main
+   ```
+
+2. **Tagging Releases**: When creating a new release, always tag it with the 'v' prefix (e.g., `v2.2.0`) to ensure GitHub Actions can create the proper release assets.
+
+3. **GitHub Actions**: The repository includes a GitHub Actions workflow that automatically builds the plugin and creates a release with the .zip file when a new tag is pushed.
+
+4. **Update Source Selection**: The plugin includes a feature that allows users to choose their preferred update source (WordPress.org, GitHub, or Gitea).
+
+For more information on Git Updater integration, see the [Git Updater Required Headers documentation](https://git-updater.com/knowledge-base/required-headers/).
+
+## Changelog
+
+### 2.3.0
+* Added: Improved time-efficient development workflow documentation
+* Added: New git workflow guidelines for better branch management
+* Added: Comprehensive incremental development approach
+* Improved: Documentation for local vs. remote testing
+* Improved: Version management process for more efficient development
+
+### 2.2.5
+* Added: Documentation for the developer preferences memory file in .ai-workflows/
+* Improved: AI assistant instructions for maintaining developer preferences
+* Updated: Version numbers across all files for consistency
+
+### 2.2.4
+* Added: Developer preferences memory file for AI assistants
+* Improved: AI assistant documentation with instructions for maintaining developer preferences
+* Updated: WordPress.org documentation with correct plugin slug and version numbers
+
+### 2.2.3
+* Improved: Moved admin-specific files to admin/lib directory for better organization
+* Improved: Updated namespaces to reflect the new file locations
+* Added: Comprehensive folder structure documentation
+* Fixed: File references in the main plugin file
+
+### 2.2.2-stable
+* Changed: Renamed includes files to lowercase for consistency with the rest of the codebase
+* Removed: Redundant Git Updater patches and version-fix.js as they're no longer needed
+* Improved: Documentation for Git Updater integration and release process
+* Fixed: Token-efficient documentation with references to .ai-workflows files
+* Added: Comprehensive release process documentation with emphasis on merging to main branch
+
+### 2.2.1
+* Changed: Commented out version-fix.js script as it's no longer needed after refactoring
+* Fixed: Version consistency across all files
+
+### 2.2.0
+* Added: Completely refactored plugin to use OOP best practices
+* Added: New class structure with proper namespaces
+* Added: Improved code organization and maintainability
+* Added: Better separation of concerns with dedicated classes
+* Changed: "Choose Update Source" link to just "Update Source"
+* Fixed: Close button in the update source modal
+* Added: Links to the main page for each update source in the modal
+* Changed: Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
+
+### 2.1.1
+* Added: New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
+* Added: Modal dialog with detailed information about each update source option
+* Added: Visual indicator showing the currently selected update source
+* Fixed: Updated heading styles in CHANGELOG.md for better readability
+* Fixed: Corrected dates in changelog to use 2025 instead of 2024
+* Improved: Documentation improvements for better clarity
+* Improved: Enhanced Git Updater integration with user-selectable update sources
+
+### 2.1.0
+* Minor version bump for Git Updater compatibility
+* Improved error handling for Git Updater integration
+* Enhanced type checking in branch fix functions
+* Updated documentation for Git Updater installation and cache refreshing
+
+### 2.0.13
+* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
+* Fixed: Type checking in branch fix functions to handle both string and object inputs
+* Improved: Error handling for Git Updater integration
+* Improved: Documentation for Git Updater installation and cache refreshing
+
+### 2.0.12
+* Fixed: Integrated Git Updater branch fix directly into main plugin
+* Fixed: Removed separate "GU Branch Fix" plugin (no longer needed)
+* Added: Documentation explaining branch fix integration
+* Improved: Compatibility with Git Updater plugin
+* Improved: Deploy script to remove separate branch fix plugin
+
+### 2.0.11
+* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
+* Added: Deploy script for local testing
+* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
+* Improved: Compatibility with Git Updater plugin
+
+### 2.0.10
+* Fixed: Plugin details popup version display issue with Git Updater integration
+* Added: JavaScript-based solution to ensure correct version display in plugin details
+* Improved: Version consistency across all plugin views
+* Improved: Cache busting for plugin information API
+
+### 2.0.9
+* Fixed: Plugin details popup now correctly shows version and author information
+* Added: Support for both old and new plugin slugs to fix caching issues
+* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
+* Improved: Version display in plugin details popup
+
+### 2.0.8
+* Fixed: Plugin details popup now correctly shows version and author information
+* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
+* Improved: Author and contributor information display in plugin details
+* Improved: Added WordPress 6.5 compatibility indicator
+
+### 2.0.7
+* Changed: Additional text improvements and minor fixes
+
+### 2.0.6
+* Changed: Text improvements and minor fixes
+
+### 2.0.5
+* Fixed: Display correct version in plugin details popup
+
+### 2.0.4
+* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
+
+### 2.0.2
+* Consolidated WordPress.org assets into .wordpress-org directory
+* Improved organization of assets for WordPress.org submission
+* Updated .wordpress-org/README.md with comprehensive information
+
+### 2.0.1
+* Added Contributing section to readme.txt
+* Updated "tested up to" version to WordPress 6.7.2
+* Added reference-plugins directory for plugin development inspiration
+* Improved .gitattributes with comprehensive file handling
+* Enhanced documentation organization
+
+### 2.0.0
+* Major version release for WordPress.org submission
+* Added note clarifying that the plugin has no settings page
+* Clarified that functionality is limited to the admin plugins page only
+* Finalized all assets and documentation for public release
+
+### 1.6.28
+* Consolidated asset documentation into a single comprehensive guide
+* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
+* Updated all asset README files to point to the main documentation
+* Improved file organization and documentation structure
+
+### 1.6.27
+* Clarified RTL support in WordPress.org asset documentation
+* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
+* Consolidated asset files and improved documentation
+
+### 1.6.26
+* Updated screenshot references to use a single comprehensive screenshot
+* Fixed asset directory paths in documentation
+* Improved ImageMagick conversion commands for icon generation
+* Clarified WordPress.org SVN repository structure
+
+### 1.6.25
+* Consolidated asset files into their respective directories
+* Created comprehensive WordPress.org submission guide
+* Clarified SVN repository structure and asset requirements
+* Improved organization of asset files
+
+### 1.6.24
+* Added properly named icon PNG files for WordPress.org submission
+* Created icon-256x256.png and icon-128x128.png files
+* Updated asset preparation documentation
+
+### 1.6.23
+* Prepared assets for WordPress.org plugin submission
+* Added properly named icon, banner, and screenshot files
+* Created comprehensive guide for WordPress.org asset requirements
+* Fixed file naming to comply with WordPress.org standards
+
+### 1.6.22
+* Enhanced support section with multiple support channel options
+* Added encouragement for users to leave reviews on WordPress.org
+* Improved documentation with clearer support instructions
+
+### 1.6.21
+* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
+* Updated documentation with links to supported AI IDEs
+* Enhanced SEO with additional FAQs and keywords
+* Made documentation more generic for boilerplate use
+* Updated AI configuration files with modern models and better explanations
+
+### 1.6.20
+* Added explanations about the ! prefix in ignore files
+* Moved WordPress-specific patterns to .gitignore
+* Further improved organization of ignore patterns
+* Added examples of how to include files excluded by .gitignore
+
+### 1.6.19
+* Consolidated common ignore patterns into .gitignore
+* Simplified AI IDE configuration files to only include tool-specific patterns
+* Improved organization of ignore patterns for better maintainability
+* Added more file types to .gitignore for comprehensive coverage
+
+### 1.6.18
+* Optimized AI IDE configuration files to only include patterns not in .gitignore
+* Improved efficiency of ignore files for better AI context management
+* Enhanced compatibility with various AI-powered development tools
+
+### 1.6.17
+* Added .augmentignore file with best practices
+* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
+* Added more design file formats to .gitignore
+* Added .aiconfig file for general AI IDE compatibility
+
+### 1.6.16
+* Updated CI configuration files with correct plugin slugs
+* Updated CHANGELOG.md with all recent versions
+* Fixed outdated references to plugin-reference-cleaner
+
+### 1.6.15
+* Moved AI workflow documentation to root directory for better visibility
+* Consolidated duplicate workflow files
+* Improved organization of development documentation
+
+### 1.6.14
+* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
+* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
+* Improved explanation of how the plugin works
+* Ensured consistent terminology across all documentation
+
+### 1.6.13
+* Code cleanup and optimization
+* Improved Git Updater integration
+* Fixed author display in plugin information
+* Ensured compatibility with WordPress 6.4
+
+### 1.6.12
+* Added WPALLSTARS 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 'WPALLSTARS'
+* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
+### 1.6.2
+* Updated POT file version for consistency
+* Improved JavaScript localization with proper fallbacks
+* Enhanced code quality for WordPress.org submission
+* Added Git Updater configuration with Update URI
+* Added update server URL configuration
+
+### 1.6.1
+* Added AI assistant guide and workflow documentation
+* Added detailed release process documentation
+* Added feature development guidelines
+* Added bug fixing procedures
+* Added code review standards
+
+### 1.6.0
+* Added full translation support with POT file
+* Added JavaScript localization for better multilingual support
+* Added plugin constants for improved code organization
+* Added Git Updater support for updates from GitHub and Gitea
+* Updated code to follow WordPress internationalization best practices
+* Improved asset loading with version constants
+* Added smart update detection based on installation source
+
+### 1.5.0
+* Improved compatibility with WordPress 6.4
+* Enhanced error detection for plugin references
+* Minor UI improvements for better visibility
+* Accessibility enhancements for screen readers
+
+[View full changelog](CHANGELOG.md)
+
+## License
+
+This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE) file for details.

admin/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;
+}

admin/css/update-source-selector.css

@@ -0,0 +1,99 @@
+/**
+ * Update Source Selector Styles
+ */
+#fpden-update-source-modal {
+    display: none;
+    font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;
+}
+
+#fpden-update-source-modal h2 {
+    margin-top: 0;
+    margin-bottom: 15px;
+    font-size: 1.3em;
+    font-weight: 600;
+}
+
+#fpden-update-source-modal p {
+    margin-bottom: 20px;
+}
+
+#fpden-update-source-form label {
+    display: block;
+    margin-bottom: 10px;
+    padding: 8px;
+    border-radius: 4px;
+    cursor: pointer;
+}
+
+#fpden-update-source-form label:hover {
+    background-color: #f0f0f1;
+}
+
+#fpden-update-source-form input[type="radio"] {
+    margin-right: 8px;
+}
+
+.fpden-source-description {
+    display: block;
+    margin-left: 24px;
+    font-size: 0.9em;
+    color: #666;
+    margin-top: 3px;
+}
+
+.fpden-submit-container {
+    margin-top: 20px;
+    text-align: right;
+}
+
+.fpden-submit-container button {
+    margin-left: 10px;
+}
+
+/* Remove explicit color to inherit from theme */
+.fpden-update-source-toggle {
+    /* color is now inherited from theme */
+}
+
+.fpden-update-source-toggle:hover {
+    /* hover color is now inherited from theme */
+}
+
+/* Close button styles */
+.fpden-close-modal {
+    position: absolute;
+    top: 10px;
+    right: 10px;
+    cursor: pointer;
+    font-size: 40px; /* Large size */
+    color: #666;
+    line-height: 30px;
+    text-decoration: none !important;
+}
+
+/* Source badges */
+.fpden-source-badge {
+    display: inline-block;
+    padding: 2px 6px;
+    border-radius: 3px;
+    font-size: 0.8em;
+    margin-left: 5px;
+    color: white;
+    font-weight: normal;
+}
+
+.fpden-source-badge.wordpress, .fpden-source-badge.wordpress\.org {
+    background-color: #0073aa;
+}
+
+.fpden-source-badge.github {
+    background-color: #24292e;
+}
+
+.fpden-source-badge.gitea {
+    background-color: #609926;
+}
+
+.fpden-source-badge.auto {
+    background-color: #666;
+}

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

admin/js/update-source-selector.js

@@ -0,0 +1,147 @@
+/**
+ * Update Source Selector
+ *
+ * Handles the UI for selecting which source to use for plugin updates.
+ */
+jQuery(document).ready(function($) {
+    // Open modal when toggle is clicked
+    $(document).on('click', '.fpden-update-source-toggle', function(e) {
+        e.preventDefault();
+
+        // Add overlay
+        $('body').append('<div id="fpden-modal-overlay"></div>');
+        $('#fpden-modal-overlay').css({
+            'position': 'fixed',
+            'top': 0,
+            'left': 0,
+            'width': '100%',
+            'height': '100%',
+            'background-color': 'rgba(0,0,0,0.5)',
+            'z-index': 100000
+        });
+
+        // Position and show modal
+        var modal = $('#fpden-update-source-modal');
+        modal.css({
+            'position': 'fixed',
+            'top': '50%',
+            'left': '50%',
+            'transform': 'translate(-50%, -50%)',
+            'background-color': '#fff',
+            'padding': '20px',
+            'border-radius': '5px',
+            'box-shadow': '0 0 10px rgba(0,0,0,0.5)',
+            'z-index': 100001,
+            'width': '400px',
+            'max-width': '90%'
+        }).show();
+
+        // Add close button styles
+        $('.fpden-close-modal').css({
+            'position': 'absolute',
+            'top': '10px',
+            'right': '10px',
+            'cursor': 'pointer',
+            'font-size': '20px',
+            'color': '#666'
+        });
+    });
+
+    // Close modal when clicking overlay or close button
+    $(document).on('click', '#fpden-modal-overlay', function() {
+        $('#fpden-update-source-modal').hide();
+        $('#fpden-modal-overlay').remove();
+    });
+
+    // Separate handler for close button to ensure it works
+    $(document).on('click', '.fpden-close-modal', function(e) {
+        e.preventDefault();
+        e.stopPropagation(); // Prevent event bubbling
+        $('#fpden-update-source-modal').hide();
+        $('#fpden-modal-overlay').remove();
+    });
+
+    // Direct binding to the close button for extra reliability
+    $('.fpden-close-modal').on('click', function(e) {
+        e.preventDefault();
+        e.stopPropagation(); // Prevent event bubbling
+        $('#fpden-update-source-modal').hide();
+        $('#fpden-modal-overlay').remove();
+    });
+
+    // Prevent clicks inside modal from closing it
+    $('#fpden-update-source-modal').on('click', function(e) {
+        e.stopPropagation();
+    });
+
+    // Handle form submission
+    $('#fpden-update-source-form').on('submit', function(e) {
+        e.preventDefault();
+
+        var source = $('input[name="update_source"]:checked').val();
+
+        // Show loading state
+        var submitButton = $(this).find('button[type="submit"]');
+        var originalText = submitButton.text();
+        submitButton.text('Saving...').prop('disabled', true);
+
+        // Save via AJAX
+        $.post(ajaxurl, {
+            action: 'fpden_save_update_source',
+            source: source,
+            nonce: fpdenData.updateSourceNonce
+        }, function(response) {
+            submitButton.text(originalText).prop('disabled', false);
+
+            if (response.success) {
+                // Update the badge
+                var badgeText = source.charAt(0).toUpperCase() + source.slice(1);
+                if (source === 'wordpress.org') {
+                    badgeText = 'WP.org';
+                }
+
+                // Remove all badge classes and add the new one
+                var badge = $('.fpden-update-source-toggle .fpden-source-badge');
+                badge.removeClass('auto wordpress github gitea')
+                     .addClass(source)
+                     .text(badgeText);
+
+                // Show success message
+                var message = $('<div class="fpden-success-message">Update source saved successfully!</div>');
+                message.css({
+                    'color': 'green',
+                    'margin-top': '10px',
+                    'text-align': 'center'
+                });
+
+                $('#fpden-update-source-form').append(message);
+
+                // Hide message and modal after delay
+                setTimeout(function() {
+                    message.fadeOut(function() {
+                        $(this).remove();
+                        $('#fpden-update-source-modal').hide();
+                        $('#fpden-modal-overlay').remove();
+                    });
+                }, 1500);
+            } else {
+                // Show error message
+                var message = $('<div class="fpden-error-message">Error saving update source.</div>');
+                message.css({
+                    'color': 'red',
+                    'margin-top': '10px',
+                    'text-align': 'center'
+                });
+
+                $('#fpden-update-source-form').append(message);
+
+                // Hide message after delay
+                setTimeout(function() {
+                    message.fadeOut(function() {
+                        $(this).remove();
+                    });
+                }, 3000);
+            }
+        });
+    });
+});

admin/lib/admin.php

@@ -0,0 +1,95 @@
+<?php
+/**
+ * Admin Functionality
+ *
+ * @package WPALLSTARS\FixPluginDoesNotExistNotices
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices\Admin;
+
+/**
+ * Admin Class
+ *
+ * Handles admin-specific functionality.
+ */
+class Admin {
+
+    /**
+     * Core instance
+     *
+     * @var \WPALLSTARS\FixPluginDoesNotExistNotices\Core
+     */
+    private $core;
+
+    /**
+     * Constructor
+     *
+     * @param \WPALLSTARS\FixPluginDoesNotExistNotices\Core $core Core instance.
+     */
+    public function __construct($core) {
+        $this->core = $core;
+
+        // Enqueue admin scripts and styles
+        add_action('admin_enqueue_scripts', array($this, 'enqueue_admin_assets'));
+    }
+
+    /**
+     * Enqueue scripts and styles needed for the admin area.
+     *
+     * @param string $hook_suffix The current admin page hook.
+     * @return void
+     */
+    public function enqueue_admin_assets($hook_suffix) {
+        // Only load on the plugins page
+        if ('plugins.php' !== $hook_suffix) {
+            return;
+        }
+
+        // Version fix script is no longer needed after refactoring
+        // Commented out for testing
+        /*
+        wp_enqueue_script(
+            'fpden-version-fix',
+            FPDEN_PLUGIN_URL . 'admin/js/version-fix.js',
+            array('jquery', 'thickbox'),
+            FPDEN_VERSION,
+            true // Load in footer
+        );
+        */
+
+        // Get invalid plugins to decide if other assets are needed
+        $invalid_plugins = $this->core->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 . 'admin/css/admin-styles.css',
+            array(),
+            FPDEN_VERSION
+        );
+
+        wp_enqueue_script(
+            'fpden-admin-scripts',
+            FPDEN_PLUGIN_URL . 'admin/js/admin-scripts.js',
+            array('jquery'), // Add dependencies if needed, e.g., jQuery
+            FPDEN_VERSION,
+            true // Load in footer
+        );
+
+        // Add translation strings for JavaScript
+        wp_localize_script(
+            'fpden-admin-scripts',
+            'fpdenData',
+            array(
+                'i18n' => array(
+                    'clickToScroll' => esc_html__('Click here to scroll to missing plugins', 'wp-fix-plugin-does-not-exist-notices'),
+                    'pluginMissing' => esc_html__('File Missing', 'wp-fix-plugin-does-not-exist-notices'),
+                    'removeNotice' => esc_html__('Remove Notice', 'wp-fix-plugin-does-not-exist-notices'),
+                ),
+                'version' => FPDEN_VERSION, // Add version for the plugin details fix script
+            )
+        );
+    }
+}

admin/lib/modal.php

@@ -0,0 +1,167 @@
+<?php
+/**
+ * Modal Functionality
+ *
+ * @package WPALLSTARS\FixPluginDoesNotExistNotices
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices\Admin;
+
+/**
+ * Modal Class
+ *
+ * Handles the update source selector modal.
+ */
+class Modal {
+
+    /**
+     * Constructor
+     */
+    public function __construct() {
+        // Add filter for plugin action links to add our update source selector
+        add_filter('plugin_action_links_' . plugin_basename(FPDEN_PLUGIN_DIR . 'wp-fix-plugin-does-not-exist-notices.php'), array($this, 'add_update_source_link'));
+
+        // Add AJAX handler for saving update source
+        add_action('wp_ajax_fpden_save_update_source', array($this, 'save_update_source'));
+
+        // Add the update source modal to admin footer
+        add_action('admin_footer', array($this, 'add_update_source_modal'));
+    }
+
+    /**
+     * Add the "Update Source" link to plugin action links
+     *
+     * @param array $links Array of plugin action links
+     * @return array Modified array of plugin action links
+     */
+    public function add_update_source_link($links) {
+        if (!current_user_can('manage_options')) {
+            return $links;
+        }
+
+        // Get current update source
+        $current_source = get_option('fpden_update_source', 'auto');
+
+        // Add a badge to show the current source
+        $badge_class = 'fpden-source-badge ' . $current_source;
+        $badge_text = ucfirst($current_source);
+        if ($current_source === 'auto') {
+            $badge_text = 'Auto';
+        } elseif ($current_source === 'wordpress.org') {
+            $badge_text = 'WP.org';
+        }
+
+        // Add the link with the badge
+        $update_source_link = '<a href="#" class="fpden-update-source-toggle">Update Source <span class="' . $badge_class . '">' . $badge_text . '</span></a>';
+        $links[] = $update_source_link;
+
+        return $links;
+    }
+
+    /**
+     * Add the update source modal to the admin footer
+     */
+    public function add_update_source_modal() {
+        if (!is_admin() || !current_user_can('manage_options')) {
+            return;
+        }
+
+        // Only show on plugins page
+        $screen = get_current_screen();
+        if (!$screen || $screen->id !== 'plugins') {
+            return;
+        }
+
+        // Get current source
+        $current_source = get_option('fpden_update_source', 'auto');
+
+        // Enqueue the CSS and JS
+        wp_enqueue_style(
+            'fpden-update-source-selector',
+            FPDEN_PLUGIN_URL . 'admin/css/update-source-selector.css',
+            array(),
+            FPDEN_VERSION
+        );
+
+        wp_enqueue_script(
+            'fpden-update-source-selector',
+            FPDEN_PLUGIN_URL . 'admin/js/update-source-selector.js',
+            array('jquery'),
+            FPDEN_VERSION,
+            true
+        );
+
+        // Add nonce to the existing fpdenData object or create it if it doesn't exist
+        $nonce = wp_create_nonce('fpden_update_source');
+        wp_localize_script(
+            'fpden-update-source-selector',
+            'fpdenData',
+            array(
+                'updateSourceNonce' => $nonce,
+            )
+        );
+
+        // Modal HTML
+        ?>
+        <div id="fpden-update-source-modal">
+            <a href="#" class="fpden-close-modal" aria-label="Close modal">×</a>
+            <h2>Choose Update Source</h2>
+            <p>Select where you want to receive plugin updates from:</p>
+
+            <form id="fpden-update-source-form">
+                <label>
+                    <input type="radio" name="update_source" value="wordpress.org" <?php checked($current_source, 'wordpress.org'); ?>>
+                    <a href="https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/" target="_blank" rel="noopener noreferrer">WordPress.org</a>
+                    <span class="fpden-source-description">Updates from the official WordPress.org plugin repository. Has a version update delay, to allow for the WP.org policy review and approval process. Best for unmonitored auto-updates.</span>
+                </label>
+
+                <label>
+                    <input type="radio" name="update_source" value="github" <?php checked($current_source, 'github'); ?>>
+                    <a href="https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices" target="_blank" rel="noopener noreferrer">GitHub</a>
+                    <span class="fpden-source-description">Update directly from the GitHub repo main branch for the latest stable release. Git Updater plugin must be installed & active. Best for monitored updates, where the latest features and fixes are required as soon as they are merged into the main branch.</span>
+                </label>
+
+                <label>
+                    <input type="radio" name="update_source" value="gitea" <?php checked($current_source, 'gitea'); ?>>
+                    <a href="https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices" target="_blank" rel="noopener noreferrer">Gitea</a>
+                    <span class="fpden-source-description">Update directly from the Gitea repo main branch for the latest stable release. Git Updater plugin must be installed & active. Best for monitored updates, where the latest features and fixes are required as soon as they are merged into the main branch, and independence from big-tech.</span>
+                </label>
+
+                <div class="fpden-submit-container">
+                    <button type="submit" class="button button-primary">Save</button>
+                </div>
+            </form>
+        </div>
+        <?php
+    }
+
+    /**
+     * Handle AJAX request to save update source
+     */
+    public function save_update_source() {
+        // Check nonce
+        check_ajax_referer('fpden_update_source', 'nonce');
+
+        // Check permissions
+        if (!current_user_can('manage_options')) {
+            wp_send_json_error('Permission denied');
+        }
+
+        // Get and sanitize source
+        $source = isset($_POST['source']) ? sanitize_text_field($_POST['source']) : '';
+
+        // Validate source
+        $valid_sources = ['wordpress.org', 'github', 'gitea'];
+        if (!in_array($source, $valid_sources)) {
+            $source = ''; // Empty means use auto-detection
+        }
+
+        // Save option
+        update_option('fpden_update_source', $source);
+
+        // Clear update cache
+        delete_site_transient('update_plugins');
+
+        wp_send_json_success();
+    }
+}

build.sh

@@ -10,7 +10,7 @@ if [ -z "$1" ]; then
 fi
 
 VERSION=$1
-PLUGIN_SLUG="plugin-reference-cleaner"
+PLUGIN_SLUG="wp-fix-plugin-does-not-exist-notices"
 BUILD_DIR="build/$PLUGIN_SLUG"
 ZIP_FILE="${PLUGIN_SLUG}-${VERSION}.zip"
 
@@ -18,13 +18,47 @@ 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 plugin-reference-cleaner.php $BUILD_DIR/
+cp wp-fix-plugin-does-not-exist-notices.php $BUILD_DIR/
 cp readme.txt $BUILD_DIR/
 cp LICENSE $BUILD_DIR/
 cp README.md $BUILD_DIR/
 cp CHANGELOG.md $BUILD_DIR/
+cp composer.json $BUILD_DIR/
+
+# Copy directories
+echo "Copying directories..."
+mkdir -p $BUILD_DIR/includes
+cp -r includes/* $BUILD_DIR/includes/
+mkdir -p $BUILD_DIR/languages
+cp -r languages/* $BUILD_DIR/languages/
+
+# Copy admin assets
+mkdir -p $BUILD_DIR/admin/css
+cp -r admin/css/* $BUILD_DIR/admin/css/
+mkdir -p $BUILD_DIR/admin/js
+cp -r admin/js/* $BUILD_DIR/admin/js/
+mkdir -p $BUILD_DIR/admin/lib
+cp -r admin/lib/* $BUILD_DIR/admin/lib/
+
+# Create assets directory structure
+mkdir -p $BUILD_DIR/assets
+
+# Copy PNG files from .wordpress-org/assets to the build directory
+mkdir -p $BUILD_DIR/assets/banner
+cp -r .wordpress-org/assets/banner-*.png $BUILD_DIR/assets/banner/ 2>/dev/null || :
+mkdir -p $BUILD_DIR/assets/icon
+cp -r .wordpress-org/assets/icon-*.png $BUILD_DIR/assets/icon/ 2>/dev/null || :
+mkdir -p $BUILD_DIR/assets/screenshots
+cp -r .wordpress-org/assets/screenshot-*.png $BUILD_DIR/assets/screenshots/ 2>/dev/null || :
+
+mkdir -p $BUILD_DIR/vendor
+cp -r vendor/* $BUILD_DIR/vendor/
 
 # Create ZIP file
 echo "Creating ZIP file..."
@@ -36,7 +70,11 @@ cd ..
 if [ -f "$ZIP_FILE" ]; then
   echo "✅ Build successful: $ZIP_FILE created"
   echo "File path: $(pwd)/$ZIP_FILE"
+
+  # Deploy to local WordPress installation
+  echo "\nDeploying to local WordPress installation..."
+  ./scripts/deploy-local.sh
 else
   echo "❌ Build failed: ZIP file was not created"
   exit 1
-fi 
+fi

composer.json

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

includes/Core.php

@@ -0,0 +1,619 @@
+<?php
+/**
+ * Core Functionality
+ *
+ * @package WPALLSTARS\FixPluginDoesNotExistNotices
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
+
+/**
+ * Core Class
+ *
+ * Handles the core functionality of finding and fixing invalid plugin references.
+ */
+class Core {
+
+    /**
+     * Stores a list of invalid plugins found in the active_plugins option.
+     *
+     * @var array|null
+     */
+    private $invalid_plugins = null;
+
+    /**
+     * Constructor
+     */
+    public function __construct() {
+        // Add our plugin to the plugins list
+        add_filter('all_plugins', array($this, 'add_missing_plugins_references'));
+
+        // Add our action link to the plugins list
+        add_filter('plugin_action_links', array($this, 'add_remove_reference_action'), 20, 4);
+
+        // Handle the remove reference action
+        add_action('admin_init', array($this, 'handle_remove_reference'));
+
+        // Add admin notices for operation feedback
+        add_action('admin_notices', array($this, 'admin_notices'));
+
+        // Filter the plugin API to fix version display in plugin details popup
+        add_filter('plugins_api', array($this, 'filter_plugin_details'), 10, 3);
+
+        // Prevent WordPress from caching our plugin API responses
+        add_filter('plugins_api_result', array($this, 'prevent_plugins_api_caching'), 10, 3);
+
+        // Clear plugin API transients on plugin activation and when viewing plugins page
+        add_action('admin_init', array($this, 'maybe_clear_plugin_api_cache'));
+    }
+
+    /**
+     * Get a list of invalid plugins (plugins that are active but don't exist).
+     *
+     * @return array An array of plugin file paths that don't exist.
+     */
+    public function get_invalid_plugins() {
+        // Return cached result if available
+        if (is_array($this->invalid_plugins)) {
+            return $this->invalid_plugins;
+        }
+
+        // Initialize empty array
+        $invalid_plugins = array();
+
+        // 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
+            $active_plugins = array_keys($active_plugins);
+        } else {
+            // Single site or non-network admin context
+            $active_plugins = get_option('active_plugins', array());
+        }
+
+        // Check each active plugin
+        foreach ($active_plugins as $plugin_file) {
+            $plugin_path = WP_PLUGIN_DIR . '/' . $plugin_file;
+            if (!file_exists($plugin_path)) {
+                $invalid_plugins[] = $plugin_file;
+            }
+        }
+
+        // Cache the result
+        $this->invalid_plugins = $invalid_plugins;
+
+        return $invalid_plugins;
+    }
+
+    /**
+     * Check if the current page is the plugins page.
+     *
+     * @return bool True if on the plugins page, false otherwise.
+     */
+    public function is_plugins_page() {
+        global $pagenow;
+        return is_admin() && 'plugins.php' === $pagenow;
+    }
+
+    /**
+     * Find and add invalid plugin references to the plugins list.
+     *
+     * Filters the list of plugins displayed on the plugins page to include
+     * entries for active plugins whose files are missing.
+     *
+     * @param array $plugins An array of plugin data.
+     * @return array The potentially modified array of plugin data.
+     */
+    public function add_missing_plugins_references($plugins) {
+        // Only run on the plugins page
+        if (!$this->is_plugins_page()) {
+            return $plugins;
+        }
+
+        // Get active plugins that don't exist
+        $invalid_plugins = $this->get_invalid_plugins();
+
+        // Add each invalid plugin to the plugin list
+        foreach ($invalid_plugins as $plugin_path) {
+            if (!isset($plugins[$plugin_path])) {
+                $plugin_name = basename($plugin_path);
+                $plugin_slug = dirname($plugin_path);
+                if ('.' === $plugin_slug) {
+                    $plugin_slug = basename($plugin_path, '.php');
+                }
+
+                // Create a basic plugin data array
+                $plugins[$plugin_path] = array(
+                    'Name'        => $plugin_name . ' <span class="error">(File Missing)</span>',
+                    /* translators: %s: Path to wp-content/plugins */
+                    'Description' => sprintf(
+                        __('This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices'),
+                        '<code>/wp-content/plugins/</code>'
+                    ),
+                    'Version'     => FPDEN_VERSION, // Use our plugin version instead of 'N/A'
+                    'Author'      => 'Marcus Quinn & WPALLSTARS',
+                    'PluginURI'   => 'https://www.wpallstars.com',
+                    'AuthorURI'   => 'https://www.wpallstars.com',
+                    'Title'       => $plugin_name . ' (' . __('Missing', 'wp-fix-plugin-does-not-exist-notices') . ')',
+                    'AuthorName'  => 'Marcus Quinn & WPALLSTARS',
+                );
+
+                // Add the data needed for the "View details" link
+                $plugins[$plugin_path]['slug'] = $plugin_slug;
+                $plugins[$plugin_path]['plugin'] = $plugin_path;
+                $plugins[$plugin_path]['type'] = 'plugin';
+
+                // Add Git Updater fields
+                $plugins[$plugin_path]['GitHub Plugin URI'] = 'wpallstars/wp-fix-plugin-does-not-exist-notices';
+                $plugins[$plugin_path]['GitHub Branch'] = 'main';
+                $plugins[$plugin_path]['TextDomain'] = 'wp-fix-plugin-does-not-exist-notices';
+            }
+        }
+
+        return $plugins;
+    }
+
+    /**
+     * Add the Remove Notice action link to invalid plugins.
+     *
+     * Filters the action links displayed for each plugin on the plugins page.
+     * Adds a "Remove Notice" link for plugins identified as missing.
+     *
+     * @param array  $actions     An array of plugin action links.
+     * @param string $plugin_file Path to the plugin file relative to the plugins directory.
+     * @param array  $plugin_data An array of plugin data.
+     * @param string $context     The plugin context (e.g., 'all', 'active', 'inactive').
+     * @return array The potentially modified array of plugin action links.
+     */
+    public function add_remove_reference_action($actions, $plugin_file, $plugin_data, $context) {
+        // Only run on the plugins page
+        if (!$this->is_plugins_page()) {
+            return $actions;
+        }
+
+        // Get our list of invalid plugins
+        $invalid_plugins = $this->get_invalid_plugins();
+
+        // Check if this plugin file is in our list of invalid plugins
+        if (in_array($plugin_file, $invalid_plugins, true)) {
+            // Clear existing actions like "Activate", "Deactivate", "Edit"
+            $actions = array();
+
+            // Add our custom action
+            $nonce      = wp_create_nonce('remove_plugin_reference_' . $plugin_file);
+            $remove_url = admin_url('plugins.php?action=remove_reference&plugin=' . urlencode($plugin_file) . '&_wpnonce=' . $nonce);
+            /* translators: %s: Plugin file path */
+            $aria_label                 = sprintf(__('Remove reference to missing plugin %s', 'wp-fix-plugin-does-not-exist-notices'), esc_attr($plugin_file));
+            $actions['remove_reference'] = '<a href="' . esc_url($remove_url) . '" class="delete" aria-label="' . $aria_label . '">' . esc_html__('Remove Notice', 'wp-fix-plugin-does-not-exist-notices') . '</a>';
+        }
+
+        return $actions;
+    }
+
+    /**
+     * Handle the remove reference action triggered by the link.
+     *
+     * Checks for the correct action, verifies nonce and permissions,
+     * calls the removal function, and redirects back to the plugins page.
+     *
+     * @return void
+     */
+    public function handle_remove_reference() {
+        // Check if our specific action is being performed
+        if (!isset($_GET['action']) || 'remove_reference' !== $_GET['action'] || !isset($_GET['plugin'])) {
+            return;
+        }
+
+        // Verify user permissions
+        if (!current_user_can('activate_plugins')) {
+            wp_die(esc_html__('You do not have sufficient permissions to perform this action.', 'wp-fix-plugin-does-not-exist-notices'));
+        }
+
+        // Sanitize and get the plugin file path
+        $plugin_file = isset($_GET['plugin']) ? sanitize_text_field(wp_unslash($_GET['plugin'])) : '';
+        if (empty($plugin_file)) {
+            wp_die(esc_html__('Invalid plugin specified.', 'wp-fix-plugin-does-not-exist-notices'));
+        }
+
+        // Verify nonce for security
+        check_admin_referer('remove_plugin_reference_' . $plugin_file);
+
+        // Attempt to remove the plugin reference
+        $success = $this->remove_plugin_reference($plugin_file);
+
+        // Prepare redirect URL with feedback query args
+        $redirect_url = admin_url('plugins.php');
+        $redirect_url = add_query_arg($success ? 'reference_removed' : 'reference_removal_failed', '1', $redirect_url);
+
+        // Redirect and exit
+        wp_safe_redirect($redirect_url);
+        exit;
+    }
+
+    /**
+     * Remove a plugin reference from the active plugins list in the database.
+     *
+     * Handles both single site and multisite network activated plugins.
+     *
+     * @param string $plugin_file The plugin file path to remove.
+     * @return bool True on success, false on failure or if the plugin wasn't found.
+     */
+    public function remove_plugin_reference($plugin_file) {
+        $success = false;
+
+        // Ensure plugin file path is provided
+        if (empty($plugin_file)) {
+            return false;
+        }
+
+        // Handle multisite network admin context
+        if (is_multisite() && is_network_admin()) {
+            $active_plugins = get_site_option('active_sitewide_plugins', array());
+            // Network active plugins are stored as key => timestamp
+            if (isset($active_plugins[$plugin_file])) {
+                unset($active_plugins[$plugin_file]);
+                $success = update_site_option('active_sitewide_plugins', $active_plugins);
+            }
+        } else { // Handle single site or non-network admin context
+            $active_plugins = get_option('active_plugins', array());
+            // Single site active plugins are stored as an indexed array
+            $key = array_search($plugin_file, $active_plugins, true); // Use strict comparison
+            if (false !== $key) {
+                unset($active_plugins[$key]);
+                // Re-index the array numerically
+                $active_plugins = array_values($active_plugins);
+                $success        = update_option('active_plugins', $active_plugins);
+            }
+        }
+
+        return $success;
+    }
+
+    /**
+     * Display admin notices on the plugins page.
+     *
+     * Shows feedback messages after attempting to remove a reference.
+     * The main informational notice is handled by JavaScript to position it
+     * directly below the WordPress error message.
+     *
+     * @return void
+     */
+    public function admin_notices() {
+        // Only run on the plugins page
+        if (!$this->is_plugins_page()) {
+            return;
+        }
+
+        // Check for feedback messages from the remove action
+        if (isset($_GET['reference_removed']) && '1' === $_GET['reference_removed']) {
+            ?>
+            <div class="notice notice-success is-dismissible">
+                <p><?php esc_html_e('Plugin reference removed successfully.', 'wp-fix-plugin-does-not-exist-notices'); ?></p>
+            </div>
+            <?php
+        }
+
+        if (isset($_GET['reference_removal_failed']) && '1' === $_GET['reference_removal_failed']) {
+            ?>
+            <div class="notice notice-error is-dismissible">
+                <p><?php esc_html_e('Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue.', 'wp-fix-plugin-does-not-exist-notices'); ?></p>
+            </div>
+            <?php
+        }
+    }
+
+    /**
+     * Filter plugin details API response to provide custom data for our plugin.
+     *
+     * @param object|WP_Error $result The result object or WP_Error.
+     * @param string $action The type of information being requested.
+     * @param object $args Plugin API arguments.
+     * @return object|WP_Error The result object or WP_Error.
+     */
+    public function filter_plugin_details($result, $action, $args) {
+        // Only modify plugin_information requests
+        if ('plugin_information' !== $action) {
+            return $result;
+        }
+
+        // Check if we have a slug to work with
+        if (empty($args->slug)) {
+            return $result;
+        }
+
+        // Get our list of invalid plugins
+        $invalid_plugins = $this->get_invalid_plugins();
+
+        // Check if this is our plugin or a missing plugin
+        $our_plugin = in_array($args->slug, array('wp-fix-plugin-does-not-exist-notices', 'fix-plugin-does-not-exist-notices'), true);
+        $is_missing_plugin = $this->is_missing_plugin($args->slug, $invalid_plugins);
+
+        // Only modify the result if this is our plugin or a missing plugin
+        if ($our_plugin || $is_missing_plugin) {
+            // Create a new result object
+            $new_result = new \stdClass();
+
+            // Set all the properties we need
+            $new_result->name = $our_plugin ? 'Fix \'Plugin file does not exist\' Notices' : (isset($result->name) ? $result->name : $args->slug);
+            $new_result->slug = $args->slug;
+            $new_result->version = FPDEN_VERSION;
+            $new_result->author = '<a href="https://www.wpallstars.com">Marcus Quinn & WPALLSTARS</a>';
+            $new_result->author_profile = 'https://www.wpallstars.com';
+            $new_result->requires = '5.0';
+            $new_result->tested = '6.7.2'; // Updated to match readme.txt
+            $new_result->requires_php = '7.0';
+            $new_result->last_updated = date('Y-m-d H:i:s');
+
+            // Add a cache buster timestamp
+            $new_result->cache_buster = time();
+
+            // Get full readme content for our plugin
+            $readme_file = FPDEN_PLUGIN_DIR . 'readme.txt';
+            $readme_content = '';
+            $description = '';
+            $changelog = '';
+            $faq = '';
+            $installation = '';
+            $screenshots = '';
+
+            if (file_exists($readme_file) && $our_plugin) {
+                $readme_content = file_get_contents($readme_file);
+
+                // Extract description
+                if (preg_match('/== Description ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
+                    $description = trim($matches[1]);
+                }
+
+                // Extract changelog
+                if (preg_match('/== Changelog ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
+                    $changelog = trim($matches[1]);
+                }
+
+                // Extract FAQ
+                if (preg_match('/== Frequently Asked Questions ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
+                    $faq = trim($matches[1]);
+                }
+
+                // Extract installation
+                if (preg_match('/== Installation ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
+                    $installation = trim($matches[1]);
+                }
+
+                // Extract screenshots
+                if (preg_match('/== Screenshots ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
+                    $screenshots = trim($matches[1]);
+                }
+            } else {
+                // Fallback content if readme.txt doesn't exist or for missing plugins
+                $changelog = '<h2>' . FPDEN_VERSION . '</h2><ul><li>Fixed: Plugin details popup version display issue with Git Updater integration</li><li>Added: JavaScript-based solution to ensure correct version display in plugin details</li><li>Improved: Version consistency across all plugin views</li><li>Enhanced: Cache busting for plugin information API</li></ul>';
+            }
+
+            // Set description based on whether this is our plugin or a missing plugin
+            if ($our_plugin) {
+                $description = !empty($description) ? wpautop($description) : 'Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.';
+            } else {
+                $description = sprintf(
+                    __('This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Use the "Remove Notice" link on the plugins page to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices'),
+                    '<code>/wp-content/plugins/</code>'
+                );
+            }
+
+            // Prepare sections
+            $new_result->sections = array(
+                'description' => $description,
+                'changelog' => !empty($changelog) ? wpautop($changelog) : $changelog,
+                'faq' => !empty($faq) ? wpautop($faq) : '<h3>Is it safe to remove plugin references?</h3><p>Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists.</p>',
+            );
+
+            // Add installation section if available
+            if (!empty($installation)) {
+                $new_result->sections['installation'] = wpautop($installation);
+            }
+
+            // Add screenshots section if available
+            if (!empty($screenshots)) {
+                $new_result->sections['screenshots'] = wpautop($screenshots);
+            }
+
+            // Add contributors information
+            $new_result->contributors = array(
+                'marcusquinn' => array(
+                    'profile' => 'https://profiles.wordpress.org/marcusquinn/',
+                    'avatar' => 'https://secure.gravatar.com/avatar/',
+                    'display_name' => 'Marcus Quinn'
+                ),
+                'wpallstars' => array(
+                    'profile' => 'https://profiles.wordpress.org/wpallstars/',
+                    'avatar' => 'https://secure.gravatar.com/avatar/',
+                    'display_name' => 'WPALLSTARS'
+                )
+            );
+
+            // Add a random number and timestamp to force cache refresh
+            $new_result->download_link = 'https://www.wpallstars.com/plugins/wp-fix-plugin-does-not-exist-notices.zip?v=' . FPDEN_VERSION . '&cb=' . mt_rand(1000000, 9999999) . '&t=' . time();
+
+            // Add active installations count
+            $new_result->active_installs = 1000;
+
+            // Add rating information
+            $new_result->rating = 100;
+            $new_result->num_ratings = 5;
+            $new_result->ratings = array(
+                5 => 5,
+                4 => 0,
+                3 => 0,
+                2 => 0,
+                1 => 0
+            );
+
+            // Add homepage and download link
+            $new_result->homepage = 'https://www.wpallstars.com';
+
+            // Set no caching
+            $new_result->cache_time = 0;
+
+            // Return our completely new result object
+            return $new_result;
+        }
+
+        return $result;
+    }
+
+    /**
+     * Check if a slug matches one of our missing plugins.
+     *
+     * @param string $slug The plugin slug to check.
+     * @param array $invalid_plugins List of invalid plugin paths.
+     * @return bool True if the slug matches a missing plugin.
+     */
+    private function is_missing_plugin($slug, $invalid_plugins) {
+        foreach ($invalid_plugins as $plugin_file) {
+            // Extract the plugin slug from the plugin file path
+            $plugin_slug = dirname($plugin_file);
+            if ('.' === $plugin_slug) {
+                $plugin_slug = basename($plugin_file, '.php');
+            }
+
+            if ($slug === $plugin_slug) {
+                return true;
+            }
+        }
+        return false;
+    }
+
+    /**
+     * Prevent WordPress from caching our plugin API responses.
+     *
+     * @param object|WP_Error $result The result object or WP_Error.
+     * @param string $action The type of information being requested.
+     * @param object $args Plugin API arguments.
+     * @return object|WP_Error The result object or WP_Error.
+     */
+    public function prevent_plugins_api_caching($result, $action, $args) {
+        // Only modify plugin_information requests
+        if ('plugin_information' !== $action) {
+            return $result;
+        }
+
+        // Check if we have a slug to work with
+        if (empty($args->slug)) {
+            return $result;
+        }
+
+        // Get our list of invalid plugins
+        $invalid_plugins = $this->get_invalid_plugins();
+
+        // Check if the requested plugin is one of our missing plugins
+        foreach ($invalid_plugins as $plugin_file) {
+            // Extract the plugin slug from the plugin file path
+            $plugin_slug = dirname($plugin_file);
+            if ('.' === $plugin_slug) {
+                $plugin_slug = basename($plugin_file, '.php');
+            }
+
+            // If this is one of our missing plugins, prevent caching
+            if ($args->slug === $plugin_slug) {
+                // Add a filter to prevent caching of this response
+                add_filter('plugins_api_result_' . $args->slug, '__return_false');
+
+                // Add a timestamp to force cache busting
+                if (is_object($result)) {
+                    $result->last_updated = current_time('mysql');
+                    $result->cache_time = 0;
+                }
+            }
+        }
+
+        return $result;
+    }
+
+    /**
+     * Clear plugin API cache when viewing the plugins page.
+     *
+     * @return void
+     */
+    public function maybe_clear_plugin_api_cache() {
+        // Only run on the plugins page
+        if (!$this->is_plugins_page()) {
+            return;
+        }
+
+        // Get our list of invalid plugins
+        $invalid_plugins = $this->get_invalid_plugins();
+
+        // Clear transients for each invalid plugin
+        foreach ($invalid_plugins as $plugin_file) {
+            // Extract the plugin slug from the plugin file path
+            $plugin_slug = dirname($plugin_file);
+            if ('.' === $plugin_slug) {
+                $plugin_slug = basename($plugin_file, '.php');
+            }
+
+            // Delete all possible transients for this plugin
+            delete_transient('plugins_api_' . $plugin_slug);
+            delete_site_transient('plugins_api_' . $plugin_slug);
+            delete_transient('plugin_information_' . $plugin_slug);
+            delete_site_transient('plugin_information_' . $plugin_slug);
+
+            // Clear any other transients that might be caching plugin info
+            $this->clear_all_plugin_transients();
+        }
+
+        // Also clear our own plugin's cache
+        $this->clear_own_plugin_cache();
+    }
+
+    /**
+     * Clear all plugin-related transients that might be caching information.
+     *
+     * @return void
+     */
+    private function clear_all_plugin_transients() {
+        // Clear update cache
+        delete_site_transient('update_plugins');
+        delete_site_transient('update_themes');
+        delete_site_transient('update_core');
+
+        // Clear plugins API cache
+        delete_site_transient('plugin_information');
+
+        // Clear plugin update counts
+        delete_transient('plugin_updates_count');
+        delete_site_transient('plugin_updates_count');
+
+        // Clear plugin slugs cache
+        delete_transient('plugin_slugs');
+        delete_site_transient('plugin_slugs');
+    }
+
+    /**
+     * Clear cache specifically for our own plugin.
+     *
+     * @return void
+     */
+    private function clear_own_plugin_cache() {
+        // Clear our own plugin's cache (both old and new slugs)
+        $our_slugs = array('wp-fix-plugin-does-not-exist-notices', 'fix-plugin-does-not-exist-notices');
+
+        foreach ($our_slugs as $slug) {
+            delete_transient('plugins_api_' . $slug);
+            delete_site_transient('plugins_api_' . $slug);
+            delete_transient('plugin_information_' . $slug);
+            delete_site_transient('plugin_information_' . $slug);
+        }
+
+        // Clear plugin update transients
+        delete_site_transient('update_plugins');
+        delete_site_transient('plugin_information');
+
+        // Force refresh of plugin update information if function exists
+        if (function_exists('wp_clean_plugins_cache')) {
+            wp_clean_plugins_cache(true);
+        }
+
+        // Clear object cache if function exists
+        if (function_exists('wp_cache_flush')) {
+            wp_cache_flush();
+        }
+    }
+}

includes/Plugin.php

@@ -0,0 +1,158 @@
+<?php
+/**
+ * Main Plugin Class
+ *
+ * @package WPALLSTARS\FixPluginDoesNotExistNotices
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
+
+/**
+ * Main Plugin Class
+ *
+ * Initializes all components of the plugin.
+ */
+class Plugin {
+
+    /**
+     * Plugin version
+     *
+     * @var string
+     */
+    private $version;
+
+    /**
+     * Plugin file path
+     *
+     * @var string
+     */
+    private $plugin_file;
+
+    /**
+     * Plugin directory path
+     *
+     * @var string
+     */
+    private $plugin_dir;
+
+    /**
+     * Plugin directory URL
+     *
+     * @var string
+     */
+    private $plugin_url;
+
+    /**
+     * Core functionality instance
+     *
+     * @var Core
+     */
+    private $core;
+
+    /**
+     * Admin functionality instance
+     *
+     * @var Admin\Admin
+     */
+    private $admin;
+
+    /**
+     * Updater instance
+     *
+     * @var Updater
+     */
+    private $updater;
+
+    /**
+     * Constructor
+     *
+     * @param string $plugin_file Main plugin file path.
+     * @param string $version Plugin version.
+     */
+    public function __construct($plugin_file, $version) {
+        $this->plugin_file = $plugin_file;
+        $this->version = $version;
+        $this->plugin_dir = plugin_dir_path($plugin_file);
+        $this->plugin_url = plugin_dir_url($plugin_file);
+
+        $this->define_constants();
+        $this->load_dependencies();
+        $this->init_components();
+    }
+
+    /**
+     * Define plugin constants
+     *
+     * @return void
+     */
+    private function define_constants() {
+        if (!defined('FPDEN_VERSION')) {
+            define('FPDEN_VERSION', $this->version);
+        }
+        if (!defined('FPDEN_PLUGIN_DIR')) {
+            define('FPDEN_PLUGIN_DIR', $this->plugin_dir);
+        }
+        if (!defined('FPDEN_PLUGIN_URL')) {
+            define('FPDEN_PLUGIN_URL', $this->plugin_url);
+        }
+    }
+
+    /**
+     * Load dependencies
+     *
+     * @return void
+     */
+    private function load_dependencies() {
+        // Load composer autoloader if it exists
+        $autoloader = $this->plugin_dir . 'vendor/autoload.php';
+        if (file_exists($autoloader)) {
+            require_once $autoloader;
+        }
+
+        // Load required files
+        require_once $this->plugin_dir . 'includes/core.php';
+        require_once $this->plugin_dir . 'admin/lib/admin.php';
+        require_once $this->plugin_dir . 'admin/lib/modal.php';
+    }
+
+    /**
+     * Initialize plugin components
+     *
+     * @return void
+     */
+    private function init_components() {
+        // Initialize core functionality
+        $this->core = new Core();
+
+        // Initialize admin functionality
+        $this->admin = new Admin\Admin($this->core);
+
+        // Initialize Git Updater fixes
+        $this->init_git_updater_fixes();
+
+        // Initialize the updater if the class exists
+        if (class_exists('\WPALLSTARS\FixPluginDoesNotExistNotices\Updater')) {
+            $this->updater = new Updater($this->plugin_file);
+        }
+
+        // Initialize the modal for update source selection
+        new Admin\Modal();
+    }
+
+    /**
+     * Initialize Git Updater fixes
+     *
+     * This function previously added filters to fix Git Updater's handling of 'main' vs 'master' branches.
+     * These fixes are no longer needed with proper plugin headers.
+     * See: https://git-updater.com/knowledge-base/required-headers/
+     *
+     * @return void
+     */
+    private function init_git_updater_fixes() {
+        // No fixes needed - we're using the proper plugin headers
+        // Git Updater reads version information from the readme.txt file in the main branch
+    }
+
+    // Git Updater override methods have been removed as they're no longer needed
+    // We now use the proper plugin headers for Git Updater integration
+}

includes/Updater.php

@@ -0,0 +1,200 @@
+<?php
+/**
+ * Plugin Updater
+ *
+ * @package FixPluginDoesNotExistNotices
+ * @noinspection PhpUndefinedFunctionInspection
+ * @noinspection PhpUndefinedClassInspection
+ */
+
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
+
+use function add_filter;
+
+/**
+ * Class Updater
+ *
+ * Handles plugin updates from different sources based on installation origin.
+ */
+class Updater {
+
+    /**
+     * Plugin file path
+     *
+     * @var string
+     */
+    private $plugin_file;
+
+    /**
+     * Installation source
+     *
+     * @var string
+     */
+    private $source;
+
+    /**
+     * Constructor
+     *
+     * @param string $plugin_file Main plugin file path.
+     */
+    public function __construct($plugin_file) {
+        $this->plugin_file = $plugin_file;
+        $this->source = $this->determine_installation_source();
+        $this->init();
+    }
+
+    /**
+     * Initialize the updater based on the installation source
+     *
+     * @return void
+     */
+    public function init() {
+        // Only initialize Git Updater if not installed from WordPress.org
+        if ($this->source !== 'wordpress.org') {
+            $this->init_git_updater();
+        }
+    }
+
+    /**
+     * Determine the installation source of the plugin
+     *
+     * @return string Installation source: 'github', 'gitea', or 'wordpress.org'
+     */
+    private function determine_installation_source() {
+        // Check for user preference first
+        $user_preference = \get_option('fpden_update_source', '');
+
+        // If user has set a preference, use it
+        if (!empty($user_preference)) {
+            return $user_preference;
+        }
+
+        // Otherwise, auto-detect the installation source
+        $source = 'wordpress.org'; // Default to WordPress.org if unidentifiable
+
+        // Check if the plugin was installed from GitHub
+        if ($this->is_github_installation()) {
+            $source = 'github';
+        }
+        // Check if the plugin was installed from Gitea
+        elseif ($this->is_gitea_installation()) {
+            $source = 'gitea';
+        }
+
+        return $source;
+    }
+
+    /**
+     * Check if the plugin was installed from GitHub
+     *
+     * @return bool
+     * @noinspection PhpUndefinedFunctionInspection
+     */
+    private function is_github_installation() {
+        // Check for GitHub-specific markers in the plugin directory
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
+
+        // Look for .git directory with GitHub remote
+        if (file_exists($plugin_dir . '.git')) {
+            $git_config = @file_get_contents($plugin_dir . '.git/config');
+            if ($git_config && strpos($git_config, 'github.com') !== false) {
+                return true;
+            }
+        }
+
+        // Check for GitHub-specific files that might indicate it was downloaded from GitHub
+        if (file_exists($plugin_dir . '.github')) {
+            return true;
+        }
+
+        return false;
+    }
+
+    /**
+     * Check if the plugin was installed from Gitea
+     *
+     * @return bool
+     * @noinspection PhpUndefinedFunctionInspection
+     */
+    private function is_gitea_installation() {
+        // Check for Gitea-specific markers in the plugin directory
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
+
+        // Look for .git directory with Gitea remote
+        if (file_exists($plugin_dir . '.git')) {
+            $git_config = @file_get_contents($plugin_dir . '.git/config');
+            if ($git_config && strpos($git_config, 'gitea.wpallstars.com') !== false) {
+                return true;
+            }
+        }
+
+        return false;
+    }
+
+    /**
+     * Initialize Git Updater Lite
+     *
+     * @return void
+     * @noinspection PhpUndefinedFunctionInspection
+     * @noinspection PhpUndefinedClassInspection
+     */
+    private function init_git_updater() {
+        // Check if the Git Updater Lite class exists (composer autoload)
+        if (!class_exists('\\Fragen\\Git_Updater\\Lite')) {
+            // Try to include the autoloader
+            $autoloader = dirname($this->plugin_file) . '/vendor/autoload.php';
+            if (file_exists($autoloader)) {
+                require_once $autoloader;
+            } else {
+                return; // Can't load Git Updater Lite
+            }
+        }
+
+        // Set the update server based on the installation source
+        \add_filter('gul_update_server', function() {
+            if ($this->source === 'github') {
+                return 'https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // GitHub repository URL
+            } elseif ($this->source === 'gitea') {
+                return 'https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // Gitea repository URL
+            }
+            return '';
+        });
+
+        // Add filter to trigger Git Updater cache refresh when a version update is detected
+        \add_filter('site_transient_update_plugins', function($transient) {
+            // Check if our plugin has an update
+            $plugin_basename = \plugin_basename($this->plugin_file);
+            if (isset($transient->response) && isset($transient->response[$plugin_basename])) {
+                // Check if Git Updater is active by looking for its functions
+                if (function_exists('\\Fragen\\Git_Updater\\flush_git_updater_cache') ||
+                    class_exists('\\Fragen\\Git_Updater\\API\\API')) {
+
+                    // Try to call the flush cache function if it exists
+                    if (function_exists('\\Fragen\\Git_Updater\\flush_git_updater_cache')) {
+                        \Fragen\Git_Updater\flush_git_updater_cache();
+                    } elseif (class_exists('\\Fragen\\Git_Updater\\API\\API')) {
+                        // Try to use the API class if available
+                        try {
+                            $api = new \Fragen\Git_Updater\API\API();
+                            if (method_exists($api, 'flush_cache_site_transient')) {
+                                $api->flush_cache_site_transient();
+                            }
+                        } catch (\Exception $e) {
+                            // Silently fail if API class can't be instantiated
+                        }
+                    }
+
+                    // Also delete the update plugins transient to force a refresh
+                    \delete_site_transient('update_plugins');
+                }
+            }
+
+            return $transient;
+        });
+
+        // Initialize Git Updater Lite
+        if (class_exists('\\Fragen\\Git_Updater\\Lite')) {
+            (new \Fragen\Git_Updater\Lite($this->plugin_file))->run();
+        }
+    }
+}

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

@@ -0,0 +1,59 @@
+# Copyright (C) 2024 Marcus Quinn & WP ALLSTARS
+# This file is distributed under the GPL-2.0+.
+msgid ""
+msgstr ""
+"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.3.0\n"
+"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"POT-Creation-Date: 2025-04-15T00:00:00+00:00\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"X-Generator: WP-CLI 2.9.0\n"
+"X-Domain: wp-fix-plugin-does-not-exist-notices\n"
+
+#. Plugin Name of the plugin
+msgid "Fix 'Plugin file does not exist' Notices"
+msgstr ""
+
+#. Plugin URI of the plugin
+msgid "https://www.wpallstars.com"
+msgstr ""
+
+#. Description of the plugin
+msgid "Adds missing plugins to your plugins list with a \"Remove Notice\" action link, allowing you to safely clean up invalid plugin references."
+msgstr ""
+
+#. Author of the plugin
+msgid "Marcus Quinn & WP ALLSTARS"
+msgstr ""
+
+#. Author URI of the plugin
+msgid "https://www.wpallstars.com"
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:168
+msgid "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."
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:227
+msgid "Remove Notice"
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:264
+msgid "Invalid plugin specified."
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:318
+msgid "Plugin reference removed successfully."
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:325
+msgid "Failed to remove plugin reference. Please try again."
+msgstr ""
+
+#: wp-fix-plugin-does-not-exist-notices.php:456
+msgid "This plugin is still marked as \"Active\" in your database — but its folder and files can't be found in %s. Use the \"Remove Notice\" link on the plugins page to permanently remove it from your active plugins list and eliminate the error notice."
+msgstr ""

plugin-reference-cleaner.php

@@ -1,198 +0,0 @@
-<?php
-/*
- * Plugin Name: Plugin Reference Cleaner
- * Description: Adds a "Remove Reference" button to plugin deactivation error notices, allowing users to clean up invalid plugin entries.
- * Version: 1.3.0
- * Author: Marcus Quinn
- * Author URI: https://www.wpallstars.com
- * License: GPL-2.0+
- */
-
-// Exit if accessed directly
-if (!defined('ABSPATH')) {
-    exit;
-}
-
-class Plugin_Reference_Cleaner {
-    public function __construct() {
-        // Add our plugin to the plugins list
-        add_filter('all_plugins', array($this, 'add_missing_plugins_references'));
-        
-        // Add our action link to the plugins list
-        add_filter('plugin_action_links', array($this, 'add_remove_reference_action'), 20, 4);
-        
-        // Handle the remove reference action
-        add_action('admin_init', array($this, 'handle_remove_reference'));
-        
-        // Add admin notices for operation feedback
-        add_action('admin_notices', array($this, 'admin_notices'));
-    }
-    
-    /**
-     * Find and add invalid plugin references to the plugins list
-     */
-    public function add_missing_plugins_references($plugins) {
-        // Only run on the plugins page
-        if (!$this->is_plugins_page()) {
-            return $plugins;
-        }
-
-        // Get active plugins that don't exist
-        $invalid_plugins = $this->get_invalid_plugins();
-        
-        // Add each invalid plugin to the plugin list
-        foreach ($invalid_plugins as $plugin_path) {
-            if (!isset($plugins[$plugin_path])) {
-                $plugin_name = basename($plugin_path);
-                $plugins[$plugin_path] = array(
-                    'Name' => $plugin_name . ' <span class="error">(File Missing)</span>',
-                    'Description' => 'This plugin file does not exist. You can safely remove this reference.',
-                    'Version' => 'N/A',
-                    'Author' => '',
-                    'PluginURI' => '',
-                    'AuthorURI' => '',
-                    'Title' => $plugin_name . ' (Missing)',
-                    'AuthorName' => ''
-                );
-            }
-        }
-        
-        return $plugins;
-    }
-    
-    /**
-     * Add the Remove Reference action link to invalid plugins
-     */
-    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
-            $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', 'plugin-reference-cleaner') . '">Remove Reference</a>';
-        }
-        
-        return $actions;
-    }
-    
-    /**
-     * Handle the remove reference action
-     */
-    public function handle_remove_reference() {
-        // Check if we're removing a reference
-        if (!isset($_GET['action']) || $_GET['action'] !== 'remove_reference' || !isset($_GET['plugin'])) {
-            return;
-        }
-        
-        // Verify permissions
-        if (!current_user_can('activate_plugins')) {
-            wp_die(__('You do not have sufficient permissions to perform this action.', 'plugin-reference-cleaner'));
-        }
-        
-        // Get the plugin file
-        $plugin_file = isset($_GET['plugin']) ? $_GET['plugin'] : '';
-        
-        // Verify nonce
-        check_admin_referer('remove_plugin_reference_' . $plugin_file);
-        
-        // 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);
-        exit;
-    }
-    
-    /**
-     * Remove a plugin reference from the active plugins
-     */
-    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);
-            }
-        } 
-        // 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);
-            }
-        }
-        
-        return $success;
-    }
-    
-    /**
-     * Display admin notices
-     */
-    public function admin_notices() {
-        // Only run on the plugins page
-        if (!$this->is_plugins_page()) {
-            return;
-        }
-        
-        // 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>';
-        }
-    }
-    
-    /**
-     * Check if we're on the plugins page
-     */
-    private function is_plugins_page() {
-        global $pagenow;
-        return is_admin() && $pagenow === 'plugins.php';
-    }
-    
-    /**
-     * Get a list of invalid plugin references
-     */
-    private function get_invalid_plugins() {
-        $invalid_plugins = array();
-        
-        // Get all active plugins
-        if (is_multisite() && is_network_admin()) {
-            $active_plugins = array_keys(get_site_option('active_sitewide_plugins', array()));
-        } else {
-            $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;
-            }
-        }
-        
-        return $invalid_plugins;
-    }
-}
-
-// Initialize the plugin
-new Plugin_Reference_Cleaner();

readme.txt

@@ -1,52 +1,521 @@
-=== Plugin Reference Cleaner ===
-Author: Marcus Quinn
-Author URI: https://www.wpallstars.com
-Version: 1.3.0
+=== Fix 'Plugin file does not exist.' Notices ===
+Contributors: surferking, wpallstars
+Donate link: https://www.wpallstars.com/
+Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist, wordpress error, plugin error, deactivated plugin, remove plugin reference, fix plugin error, plugin does not exist, plugin file does not exist error
+Requires at least: 5.0
+Tested up to: 6.7.2
+Requires PHP: 7.0
+Stable tag: 2.3.0
 License: GPL-2.0+
+License URI: https://www.gnu.org/licenses/gpl-2.0.html
+
+Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WPALLSTARS (wpallstars.com).
 
 == Description ==
 
-Have you ever deleted a plugin some other way than through the /wp-admin/plugins.php page? If so, you've probably been stuck with this annoying notification that can't be cleared:
+Have you ever deleted a plugin directly from the server or database and then been stuck with annoying error notifications that can't be cleared?
 
 "The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
 
-This small WordPress utility plugin adds a "Remove Reference" button to these plugin deactivation error notices, allowing you to clean up the invalid plugin entries in the database.
+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.
 
-When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin enhances those notices with a button that allows you to safely remove the invalid reference with a single click.
+**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
 
-You can find these with `SELECT * FROM wp_options WHERE option_name = 'active_plugins';` — but the cleanup involves removing the rogue entry, and renumbering all others. This plugin can simply do that for you at the click of a button added to that WP standard notification.
+= Key Features =
 
-It's probably something that should be added to WP core. If anyone from the core team wants to adopt this solution, it's GPL, so feel free.
+* Adds missing plugins directly to your plugins list
+* Provides a simple "Remove Notice" action link
+* Works with both single site and multisite WordPress installations
+* Includes helpful notifications explaining how to fix plugin errors
+* One-click auto-scroll to find missing plugins in large sites
+* Clean, user-friendly interface following WordPress design patterns
+* Integrated Git Updater branch fix (changes 'master' to 'main' for proper updates)
 
-Note: This plugin only needs to be installed and active if you have an error notification showing at /wp-admin/plugins.php, like this:
-"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
+= How It Works =
 
-If you don't have this notification perpetually showing on your /wp-admin/plugins.php page, then you don't need this, but you might like to save or bookmark it for if ever you do.
+When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin:
 
-== Features ==
+1. Detects all missing plugin references in your database
+2. Adds them to your plugins list with "(File Missing)" indicators
+3. Provides a "Remove Notice" link to safely remove them
+4. Shows clear notifications guiding you through the cleanup process
+5. Safely removes the missing active plugin reference from your database using standard WordPress functions
+6. Leaves all remaining plugins installed and active
 
-* Adds a "Remove Reference" button to plugin error notices
-* Works for both single site and multisite WordPress installations
-* Confirms before removing any plugin references
-* Simple, lightweight solution with no settings page required
-* Secure implementation with proper permissions checking
-* Compatible with WordPress 5.0+
+= Use Cases =
+
+* You've accidentally deleted a plugin via FTP
+* A plugin was removed by another admin but references remain
+* You've migrated from another site and have leftover plugin references
+* Your hosting provider removed a plugin but didn't clean the database
+
+= Support & Feedback =
+
+If you need help with this plugin, there are several ways to get support:
+
+* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
+* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
+* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
+
+= Reviews =
+
+This utility plugin is released under the GPLv2 license as free open source software.
+
+If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org.
+
+Your experience and feedback helps others discover the plugin, and encourages continued community-driven, open-source development and support.
+
+= Contributing =
+
+Contributions are welcome! Please feel free to submit a Pull Request.
+
+1. Fork the repository on [GitHub](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/) or [Gitea](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/)
+2. Create your feature branch: `git checkout -b feature/amazing-feature`
+3. Commit your changes: `git commit -m 'Add some amazing feature'`
+4. Push to the branch: `git push origin feature/amazing-feature`
+5. Submit a pull request
+
+The plugin is designed to be a best-practice example for WordPress plugin development and can be used as a boilerplate for your own plugins.
 
 == Installation ==
 
-1. Upload the plugin-reference-cleaner.php file to your /wp-content/plugins/ directory
+1. Upload the `wp-fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
 2. Activate the plugin through the 'Plugins' menu in WordPress
 3. No configuration needed - the plugin works automatically
+4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
 
-== Usage ==
+= Using with Git Updater =
 
-1. Navigate to Plugins > Installed Plugins
-2. If any "Plugin file does not exist" error notices appear, a "Remove Reference" button will be displayed
-3. Click the button and confirm to remove the invalid plugin reference
-4. The page will refresh with the error notice removed
+If you've installed this plugin from GitHub or Gitea, you'll need Git Updater to receive updates:
+
+1. Install the Git Updater plugin from [https://git-updater.com/git-updater/](https://git-updater.com/git-updater/)
+2. Go to Settings > Git Updater > Remote Management
+3. Click the "Refresh Cache" button to ensure Git Updater recognizes the latest version
+4. Updates will now appear in your WordPress dashboard when available
+
+= Choosing Your Update Source =
+
+This plugin allows you to choose where you want to receive updates from:
+
+1. In the Plugins list, find "Fix 'Plugin file does not exist' Notices"
+2. Click the "Update Source" link next to the plugin
+3. Select your preferred update source:
+   * **WordPress.org**: Updates from the official WordPress.org repository (has a version update delay due to the WP.org policy review and approval process, best for unmonitored auto-updates)
+   * **GitHub**: Updates directly from the GitHub repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates where the latest features and fixes are needed immediately)
+   * **Gitea**: Updates directly from the Gitea repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates and independence from big-tech)
+4. Click "Save" to apply your preference
+
+If no preference is set, the plugin will automatically use the source it was installed from.
+
+**Note:** GitHub and Gitea options require the Git Updater plugin to be installed and activated.
+
+== Contributing ==
+
+Contributions are welcome! Please follow these steps to set up a development environment:
+
+1. Install [LocalWP](https://localwp.com/) and create a clean site called "Plugin Testing" using the "Preferred" setup option
+2. Run "Site shell" once from the LocalWP page on the site's settings to ensure wp-cli is enabled
+3. Run "Add Run Configurations to VS Code" to update site configuration files in: ~/Local/plugin-testing/conf/
+4. Clone this repository to your local machine
+5. Use the build.sh and deploy-local.sh scripts to build and deploy the plugin for testing
+
+[AugmentCode.com](https://augmentcode.com/) is recommended as a good all-in-one AI IDE for plugin development and testing.
+
+Please feel free to submit a Pull Request with your improvements.
+
+== Frequently Asked Questions ==
+
+= Is it safe to remove plugin references? =
+
+Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists. It doesn't modify any other database tables or settings.
+
+= What happens after I remove a reference? =
+
+The plugin entry will be removed from your active plugins list, and the corresponding error notification will no longer appear after you refresh the page.
+
+= Can I use this plugin on a multisite installation? =
+
+Yes, the plugin works on both single sites and multisite installations. It properly handles network-activated plugins as well.
+
+= How do I know which plugin references should be removed? =
+
+The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+
+= Will this break my site? =
+
+No. Since the plugin is only removing references to plugins that no longer exist, removing these references won't affect your site's functionality. In fact, it's cleaning up remnants that might be causing issues.
+
+= What if I accidentally remove a reference I shouldn't have? =
+
+If you remove a reference to a plugin that you later want to reinstall, simply install the plugin again and activate it normally.
+
+= Do I need to keep this plugin installed and active after notices are cleared? =
+
+Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
+
+= How do I fix the "Plugin file does not exist" error in WordPress? =
+
+This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
+
+= Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"? =
+
+This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
+
+= Can this plugin fix errors after migrating a WordPress site? =
+
+Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
+
+= Is it safe to remove plugin references that show "Plugin file does not exist"? =
+
+Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
+
+= How is this different from manually editing the database? =
+
+Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
+
+== Screenshots ==
+
+1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
 
 == Changelog ==
 
+= 2.3.0 =
+* Added: Improved time-efficient development workflow documentation
+* Added: New git workflow guidelines for better branch management
+* Added: Comprehensive incremental development approach
+* Improved: Documentation for local vs. remote testing
+* Improved: Version management process for more efficient development
+
+= 2.2.5 =
+* Added: Documentation for the developer preferences memory file in .ai-workflows/
+* Improved: AI assistant instructions for maintaining developer preferences
+* Updated: Version numbers across all files for consistency
+
+= 2.2.4 =
+* Added: Developer preferences memory file for AI assistants
+* Improved: AI assistant documentation with instructions for maintaining developer preferences
+* Updated: WordPress.org documentation with correct plugin slug and version numbers
+
+= 2.2.3 =
+* Improved: Moved admin-specific files to admin/lib directory for better organization
+* Improved: Updated namespaces to reflect the new file locations
+* Added: Comprehensive folder structure documentation
+* Fixed: File references in the main plugin file
+
+= 2.2.2-stable =
+* Changed: Renamed includes files to lowercase for consistency with the rest of the codebase
+* Removed: Redundant Git Updater patches and version-fix.js as they're no longer needed
+* Improved: Documentation for Git Updater integration and release process
+* Fixed: Token-efficient documentation with references to .ai-workflows files
+* Added: Comprehensive release process documentation with emphasis on merging to main branch
+
+= 2.2.1 =
+* Changed: Commented out version-fix.js script as it's no longer needed after refactoring
+* Fixed: Version consistency across all files
+
+= 2.2.0 =
+* Added: Completely refactored plugin to use OOP best practices
+* Added: New class structure with proper namespaces
+* Added: Improved code organization and maintainability
+* Added: Better separation of concerns with dedicated classes
+* Changed: "Choose Update Source" link to just "Update Source"
+* Fixed: Close button in the update source modal
+* Added: Links to the main page for each update source in the modal
+* Changed: Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
+
+= 2.1.1 =
+* Added: New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
+* Added: Modal dialog with detailed information about each update source option
+* Added: Visual indicator showing the currently selected update source
+* Fixed: Updated heading styles in CHANGELOG.md for better readability
+* Fixed: Corrected dates in changelog to use 2025 instead of 2024
+* Improved: Documentation improvements for better clarity
+* Improved: Enhanced Git Updater integration with user-selectable update sources
+
+= 2.1.0 =
+* Minor version bump for Git Updater compatibility
+* Improved error handling for Git Updater integration
+* Enhanced type checking in branch fix functions
+* Updated documentation for Git Updater installation and cache refreshing
+
+= 2.0.13 =
+* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
+* Improved: Type checking in branch fix functions to handle both string and object inputs
+* Enhanced: Error handling for Git Updater integration
+* Removed: Redundant GU Branch Fix plugin (fully integrated into main plugin)
+
+= 2.0.12 =
+* Fixed: Integrated Git Updater branch fix directly into main plugin
+* Removed: Separate "GU Branch Fix" plugin (no longer needed)
+* Updated: Deploy script to remove separate branch fix plugin
+* Added: Documentation explaining branch fix integration
+* Improved: Compatibility with Git Updater plugin
+
+= 2.0.11 =
+* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
+* Added: Deploy script for local testing
+* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
+* Improved: Compatibility with Git Updater plugin
+
+= 2.0.10 =
+* Fixed: Plugin details popup version display issue with Git Updater integration
+* Added: JavaScript-based solution to ensure correct version display in plugin details
+* Improved: Version consistency across all plugin views
+* Enhanced: Cache busting for plugin information API
+
+= 2.0.9 =
+* Fixed: Plugin details popup now correctly shows version and author information
+* Added: Support for both old and new plugin slugs to fix caching issues
+* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
+* Enhanced: Version display in plugin details popup
+
+= 2.0.8 =
+* Fixed: Plugin details popup now correctly shows version and author information
+* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
+* Improved: Author and contributor information display in plugin details
+
+= 2.0.7 =
+* Additional text improvements and minor fixes
+
+= 2.0.6 =
+* Text improvements and minor fixes
+
+= 2.0.5 =
+* Fixed: Display correct version in plugin details popup
+
+= 2.0.4 =
+* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
+
+= 2.0.2 =
+* Consolidated WordPress.org assets into .wordpress-org directory
+* Improved organization of assets for WordPress.org submission
+* Updated .wordpress-org/README.md with comprehensive information
+
+= 2.0.1 =
+* Added Contributing section to readme.txt
+* Updated "tested up to" version to WordPress 6.7.2
+* Added reference-plugins directory for plugin development inspiration
+* Improved .gitattributes with comprehensive file handling
+* Enhanced documentation organization
+
+= 2.0.0 =
+* Major version release for WordPress.org submission
+* Added note clarifying that the plugin has no settings page
+* Clarified that functionality is limited to the admin plugins page only
+* Finalized all assets and documentation for public release
+
+= 1.6.28 =
+* Consolidated asset documentation into a single comprehensive guide
+* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
+* Updated all asset README files to point to the main documentation
+* Improved file organization and documentation structure
+
+= 1.6.27 =
+* Clarified RTL support in WordPress.org asset documentation
+* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
+* Consolidated asset files and improved documentation
+
+= 1.6.26 =
+* Updated screenshot references to use a single comprehensive screenshot
+* Fixed asset directory paths in documentation
+* Improved ImageMagick conversion commands for icon generation
+* Clarified WordPress.org SVN repository structure
+
+= 1.6.25 =
+* Consolidated asset files into their respective directories
+* Created comprehensive WordPress.org submission guide
+* Clarified SVN repository structure and asset requirements
+* Improved organization of asset files
+
+= 1.6.24 =
+* Added properly named icon PNG files for WordPress.org submission
+* Created icon-256x256.png and icon-128x128.png files
+* Updated asset preparation documentation
+
+= 1.6.23 =
+* Prepared assets for WordPress.org plugin submission
+* Added properly named icon, banner, and screenshot files
+* Created comprehensive guide for WordPress.org asset requirements
+* Fixed file naming to comply with WordPress.org standards
+
+= 1.6.22 =
+* Enhanced support section with multiple support channel options
+* Added encouragement for users to leave reviews on WordPress.org
+* Improved documentation with clearer support instructions
+
+= 1.6.21 =
+* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
+* Updated documentation with links to supported AI IDEs
+* Enhanced SEO with additional FAQs and keywords
+* Made documentation more generic for boilerplate use
+* Updated AI configuration files with modern models and better explanations
+
+= 1.6.20 =
+* Added explanations about the ! prefix in ignore files
+* Moved WordPress-specific patterns to .gitignore
+* Further improved organization of ignore patterns
+* Added examples of how to include files excluded by .gitignore
+
+= 1.6.19 =
+* Consolidated common ignore patterns into .gitignore
+* Simplified AI IDE configuration files to only include tool-specific patterns
+* Improved organization of ignore patterns for better maintainability
+* Added more file types to .gitignore for comprehensive coverage
+
+= 1.6.18 =
+* Optimized AI IDE configuration files to only include patterns not in .gitignore
+* Improved efficiency of ignore files for better AI context management
+* Enhanced compatibility with various AI-powered development tools
+
+= 1.6.17 =
+* Added .augmentignore file with best practices
+* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
+* Added more design file formats to .gitignore
+* Added .aiconfig file for general AI IDE compatibility
+
+= 1.6.16 =
+* Updated CI configuration files with correct plugin slugs
+* Updated CHANGELOG.md with all recent versions
+* Fixed outdated references to plugin-reference-cleaner
+
+= 1.6.15 =
+* Moved AI workflow documentation to root directory for better visibility
+* Consolidated duplicate workflow files
+* Improved organization of development documentation
+
+= 1.6.14 =
+* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
+* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
+* Improved explanation of how the plugin works
+* Ensured consistent terminology across all documentation
+
+= 1.6.13 =
+* Code cleanup and optimization
+* Improved Git Updater integration
+* Fixed author display in plugin information
+* Ensured compatibility with WordPress 6.4
+
+= 1.6.12 =
+* Added WP ALLSTARS as a co-author
+* Updated author information and links
+* Added author websites to plugin description
+* Fixed issue with multiple author URLs
+
+= 1.6.11 =
+* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
+* Simplified plugin functionality to focus on core features only
+* Improved compatibility with various WordPress configurations
+* Ensured plugin works correctly when other plugins are deleted
+
+= 1.6.10 =
+* Fixed critical error that could occur when a plugin folder is deleted
+* Improved error handling with try/catch blocks
+* Added more specific checks for the plugins page
+* Enhanced compatibility with various WordPress configurations
+* Made the code more defensive to prevent potential issues
+
+= 1.6.9 =
+* Fixed issue with notices not appearing below WordPress error messages
+* Improved JavaScript detection of WordPress error notices
+* Prevented WordPress from automatically clearing error notices on page refresh
+* Added multiple timing attempts to ensure notices appear correctly
+* Enhanced error notice targeting for better compatibility
+
+= 1.6.8 =
+* Fixed notice positioning to appear directly below WordPress error messages
+* Improved notice width to match WordPress error messages
+* Updated explanatory text for better clarity
+* Fixed issue with notices not appearing in some cases
+* Improved JavaScript detection of WordPress error messages
+
+= 1.6.7 =
+* Fixed duplicate notices issue by removing PHP-generated notice
+* Simplified notice system to only show one notice below WordPress error
+* Ensured consistent terminology with "Remove Notice" text
+* Optimized plugin detection with caching to improve performance
+* Fixed JavaScript to correctly handle multiple error messages
+
+= 1.6.6 =
+* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
+* Fixed issue with automatic removal of plugin references without user action
+* Fixed notice positioning to ensure it appears below error messages
+* Restored pointer triangle to indicate relationship with error message
+* Improved detection of missing plugins in the plugin list
+* Enhanced scroll functionality to work with all plugin types
+
+= 1.6.5 =
+* Fixed duplicate notices issue - now only one notice appears below error messages
+* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
+* Updated explanatory text to be more clear about the removal process
+* Changed "Remove Reference" link text to "Remove Notice" for better clarity
+* Made "(File Missing)" text bold and red for better visibility
+* Fixed scroll functionality to work with all plugin rows
+* Improved JavaScript to prevent multiple notices from appearing
+
+= 1.6.4 =
+* Updated version management to ensure consistent patch version increments
+* Improved documentation for version update process
+* Enhanced AI workflow files with detailed version increment instructions
+
+= 1.6.3 =
+* Fixed Git Updater repository URLs to use full repository paths
+* Corrected Update URI configuration for proper update detection
+* Improved version management following semantic versioning
+* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
+= 1.6.2 =
+* Updated POT file version for consistency
+* Improved JavaScript localization with proper fallbacks
+* Enhanced code quality for WordPress.org submission
+* Added Git Updater configuration with Update URI
+* Added update server URL configuration
+
+= 1.6.1 =
+* Added AI assistant guide and workflow documentation
+* Added detailed release process documentation
+* Added feature development guidelines
+* Added bug fixing procedures
+* Added code review standards
+
+= 1.6.0 =
+* Added full translation support with POT file
+* Added JavaScript localization for better multilingual support
+* Added plugin constants for improved code organization
+* Added Git Updater support for updates from GitHub and Gitea
+* Updated code to follow WordPress internationalization best practices
+* Improved asset loading with version constants
+* Added smart update detection based on installation source
+
+= 1.5.0 =
+* Improved compatibility with WordPress 6.4
+* Enhanced error detection for plugin references
+* Minor UI improvements for better visibility
+* Accessibility enhancements for screen readers
+
+= 1.4.1 =
+* Added FAQ about keeping the plugin installed after notices are cleared
+
+= 1.4.0 =
+* Updated plugin name and text domain
+* Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
+
+= 1.3.3 =
+* Improved notification placement next to WordPress error messages
+* Added "Click here to scroll" button that automatically locates missing plugins
+* Enhanced reliability with multiple injection methods
+* Added visual arrow pointing from notification to error message
+
+= 1.3.2 =
+* Added prominent notification directly below WordPress error messages
+* Improved user guidance with visual cues to connect error and solution
+* Added eye-catching styling to help users understand how to fix errors
+
+= 1.3.1 =
+* Added instructional notification explaining how to use the plugin
+* Improved user guidance with step-by-step instructions
+* Enhanced visual identification of missing plugins
+
 = 1.3.0 =
 * Complete redesign for maximum compatibility with all WordPress themes
 * Now adds missing plugins directly to the plugins list table
@@ -88,6 +557,97 @@ If you don't have this notification perpetually showing on your /wp-admin/plugin
 = 1.0 =
 * Initial release
 
-== Support ==
+== Upgrade Notice ==
 
-For support, please visit https://wpallstars.com 
+= 2.1.1 =
+Added new "Choose Update Source" feature allowing you to select where to receive plugin updates from (WordPress.org, GitHub, or Gitea).
+
+= 2.1.0 =
+Minor version bump with improved Git Updater compatibility and error handling.
+
+= 2.0.2 =
+Improved organization of assets for WordPress.org submission.
+
+= 2.0.1 =
+Improved documentation with Contributing section and updated WordPress compatibility to 6.7.2.
+
+= 2.0.0 =
+Major version release for WordPress.org submission with improved documentation and clarification about plugin functionality.
+
+= 1.6.28 =
+Improved asset documentation and clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode.
+
+= 1.6.27 =
+Clarified RTL support in WordPress.org asset documentation and improved asset organization.
+
+= 1.6.26 =
+Updated screenshot references and improved WordPress.org submission documentation.
+
+= 1.6.25 =
+Improved organization of asset files and created comprehensive WordPress.org submission guide.
+
+= 1.6.24 =
+Added properly named icon PNG files for WordPress.org submission.
+
+= 1.6.23 =
+Prepared assets for WordPress.org plugin submission with properly named icon, banner, and screenshot files.
+
+= 1.6.22 =
+Improved support documentation with multiple support channel options and encouragement for users to leave reviews.
+
+= 1.6.21 =
+Added support for more AI-powered development tools and enhanced documentation with links to supported AI IDEs.
+
+= 1.6.20 =
+Added explanations about using the ! prefix in ignore files to include files excluded by .gitignore.
+
+= 1.6.19 =
+Improved organization of ignore patterns with consolidated .gitignore and simplified AI IDE configuration files.
+
+= 1.6.18 =
+Optimized AI IDE configuration files for better efficiency and compatibility.
+
+= 1.6.17 =
+Added configuration files for AI-powered IDEs and improved compatibility with development tools.
+
+= 1.6.16 =
+Updated CI configuration files and fixed outdated references to the previous plugin name.
+
+= 1.6.15 =
+Improved organization of development documentation with consolidated AI workflow files.
+
+= 1.6.14 =
+Improved documentation with consistent terminology and better explanation of how the plugin works.
+
+= 1.6.13 =
+Code cleanup, improved Git Updater integration, and ensured compatibility with WordPress 6.4.
+
+= 1.6.12 =
+Added WP ALLSTARS as a co-author and updated author information.
+
+= 1.6.11 =
+URGENT CRITICAL FIX: Completely removes code that was causing fatal errors. If you're experiencing the "critical error" message, this update will resolve it.
+
+= 1.6.3 =
+Fixed Git Updater repository URLs and updated organization naming for consistent branding across all platforms!
+
+= 1.6.2 =
+Improved JavaScript localization, enhanced code quality, and added Git Updater configuration for seamless updates!
+
+= 1.6.1 =
+Added comprehensive AI assistant guide and workflow documentation for improved development processes!
+
+= 1.6.0 =
+Added full translation support and Git Updater compatibility for direct updates from GitHub and Gitea!
+
+= 1.5.0 =
+Improved compatibility with WordPress 6.4 and accessibility enhancements for screen readers!
+
+= 1.3.3 =
+Major usability improvement with auto-scroll feature to help find missing plugins in your list!
+
+= 1.3.0 =
+Completely redesigned for better compatibility with all WordPress themes - now works with any WordPress installation!
+
+= 1.2.2 =
+Important stability fix - resolves timeout issues during plugin activation!

scripts/deploy-local.sh

@@ -0,0 +1,46 @@
+#!/bin/bash
+
+# Exit on error
+set -e
+
+# Define paths
+PLUGIN_SLUG="wp-fix-plugin-does-not-exist-notices"
+SOURCE_DIR="/Users/marcusquinn/Git/wp-fix-plugin-does-not-exist-notices/build/$PLUGIN_SLUG"
+DEST_DIR="/Users/marcusquinn/Local/plugin-testing/app/public/wp-content/plugins/$PLUGIN_SLUG"
+WP_CLI="/Users/marcusquinn/Local/plugin-testing/app/bin/wp"
+
+# Check if build directory exists
+if [ ! -d "$SOURCE_DIR" ]; then
+  echo "Build directory not found. Running build script first..."
+  cd /Users/marcusquinn/Git/wp-fix-plugin-does-not-exist-notices
+  ./build.sh "$(grep -m 1 "Version:" wp-fix-plugin-does-not-exist-notices.php | awk -F': ' '{print $2}' | tr -d '[:space:]')"
+  # Exit if build failed
+  if [ ! -d "$SOURCE_DIR" ]; then
+    echo "❌ Build failed: Build directory was not created"
+    exit 1
+  fi
+fi
+
+# Check if destination directory exists, create if not
+if [ ! -d "$DEST_DIR" ]; then
+  echo "Creating destination directory..."
+  mkdir -p "$DEST_DIR"
+fi
+
+# Rsync the plugin files to the local WordPress installation
+echo "Deploying to local WordPress installation..."
+rsync -av --delete "$SOURCE_DIR/" "$DEST_DIR/"
+
+# Clear WordPress transients to ensure fresh plugin data
+echo "Clearing WordPress transients..."
+if [ -f "$WP_CLI" ]; then
+  cd /Users/marcusquinn/Local/plugin-testing/app/public
+  "$WP_CLI" transient delete --all
+  "$WP_CLI" cache flush
+  echo "✅ WordPress transients cleared"
+else
+  echo "⚠️ WP-CLI not found, skipping transient clearing"
+fi
+
+echo "✅ Local deployment successful!"
+echo "Plugin deployed to: $DEST_DIR"

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

@@ -0,0 +1,39 @@
+<?php
+/**
+ * Plugin Name: Fix 'Plugin file does not exist' Notices
+ * Plugin URI: https://www.wpallstars.com
+ * Description: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
+ * Version: 2.3.0
+ * Author: Marcus Quinn & The WPALLSTARS Team
+ * Author URI: https://www.wpallstars.com
+ * License: GPL-2.0+
+ * License URI: http://www.gnu.org/licenses/gpl-2.0.txt
+ * Text Domain: wp-fix-plugin-does-not-exist-notices
+ * Domain Path: /languages
+ * GitHub Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
+ * GitHub Branch: main
+ * Primary Branch: main
+ * Release Branch: main
+ * Release Asset: true
+ * Requires at least: 5.0
+ * Requires PHP: 7.0
+ * Update URI: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+ *
+ * Gitea Plugin URI: https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices
+ * Gitea Branch: main
+ * Gitea Languages: languages
+ *
+ * @package WPALLSTARS\FixPluginDoesNotExistNotices
+ */
+
+// If this file is called directly, abort.
+if (!defined('WPINC')) {
+    die;
+}
+
+// Load the main plugin class
+require_once plugin_dir_path(__FILE__) . 'includes/plugin.php';
+
+// Initialize the plugin
+// This is a test change for our new workflow
+new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '2.3.0');