Optimize AI IDE configuration files for better efficiency (v1.6.18)

git checkout main
Merge tag 'v1.6.4'

Release version 1.6.4

.ai-assistant.md

@@ -20,7 +20,7 @@ We follow [Semantic Versioning](https://semver.org/):
 
 ### When to Increment Version Numbers
 
-- **PATCH** (1.6.0 → 1.6.1): 
+- **PATCH** (1.6.0 → 1.6.1):
   - Bug fixes
   - Small text changes
   - Minor improvements that don't add new features
@@ -41,7 +41,10 @@ When updating the version number, always update these files:
 1. `fix-plugin-does-not-exist-notices.php` (Plugin header)
 2. `CHANGELOG.md` (Add new version section)
 3. `readme.txt` (Stable tag and Changelog section)
-4. Update `FPDEN_VERSION` constant in the main plugin file
+4. `README.md` (Update Changelog section to match readme.txt)
+5. Update `FPDEN_VERSION` constant in the main plugin file
+
+**IMPORTANT**: Always ensure README.md is kept in sync with readme.txt for consistency across platforms.
 
 ## Git Workflow
 
@@ -58,23 +61,48 @@ When updating the version number, always update these files:
 - Keep the first line under 50 characters
 - Reference issues when relevant: "Fix #123: Resolve plugin detection issue"
 
+### Pre-Release Checklist
+
+Before creating a new release, verify the following:
+
+- [ ] Determine the correct version increment (MAJOR, MINOR, or PATCH) based on the changes
+- [ ] Ensure all changes are documented in CHANGELOG.md
+- [ ] Verify all code changes are tested and working correctly
+- [ ] Check that all files are properly formatted and follow WordPress coding standards
+- [ ] Ensure Git Updater configuration is correct (if applicable)
+
 ### Release Process
 
 1. Create a new branch for the version: `git checkout -b v{MAJOR}.{MINOR}.{PATCH}`
-2. Update version numbers in all required files
+2. Update version numbers in ALL required files:
+   - `fix-plugin-does-not-exist-notices.php` (Plugin header)
+   - `FPDEN_VERSION` constant in the main plugin file
+   - `readme.txt` (Stable tag)
+   - `README.md` (Ensure changelog is updated)
+   - `languages/fix-plugin-does-not-exist-notices.pot` (Project-Id-Version)
+   - Any other files that reference the version number
 3. Update CHANGELOG.md with all changes
-4. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
+4. Update readme.txt changelog section
-5. Push branch to all remotes:
+5. Update README.md changelog section to match readme.txt
+6. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
+7. Test changes locally on the version branch
+8. When satisfied with testing, merge to main:
    ```
-   git push github HEAD:v{MAJOR}.{MINOR}.{PATCH}
+   git checkout main
-   git push gitea HEAD:v{MAJOR}.{MINOR}.{PATCH}
+   git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
    ```
-6. Create and push a tag to trigger the GitHub Actions workflow:
+9. Push main to all remotes:
    ```
-   git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
+   git push github main
-   git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
+   git push gitea main
-   git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
    ```
+10. Create and push a tag to trigger the GitHub Actions workflow:
+    ```
+    git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
+    git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
+    git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
+    ```
+11. Verify the GitHub Actions workflow completes successfully
 
 ## Build Process
 
@@ -120,23 +148,33 @@ Before releasing:
 
 ```
 # 1. Create a new branch
+git checkout main
 git checkout -b v1.7.0
 
-# 2. Update version numbers in files
+# 2. Update version numbers in ALL required files
 # - fix-plugin-does-not-exist-notices.php
 # - CHANGELOG.md
 # - readme.txt
+# - README.md
+# - languages/fix-plugin-does-not-exist-notices.pot
 # - FPDEN_VERSION constant
 
 # 3. Commit changes
 git add .
 git commit -m "Prepare release v1.7.0"
 
-# 4. Push to remotes
+# 4. Test changes locally on the version branch
-git push github HEAD:v1.7.0
+# (Run tests, verify functionality)
-git push gitea HEAD:v1.7.0
 
-# 5. Create and push tag
+# 5. Merge to main when ready
+git checkout main
+git merge v1.7.0 --no-ff
+
+# 6. Push main to remotes
+git push github main
+git push gitea main
+
+# 7. Create and push tag
 git tag -a v1.7.0 -m "Release version 1.7.0"
 git push github refs/tags/v1.7.0
 git push gitea refs/tags/v1.7.0
@@ -145,29 +183,53 @@ git push gitea refs/tags/v1.7.0
 ### Adding a New Feature
 
 ```
-# 1. Create feature branch
+# 1. Create feature branch from main
+git checkout main
 git checkout -b feature/new-feature-name
 
 # 2. Make changes and commit
 git add .
 git commit -m "Add new feature"
 
-# 3. Push to remotes
+# 3. Test locally
-git push github HEAD:feature/new-feature-name
+# (Run tests, verify functionality)
-git push gitea HEAD:feature/new-feature-name
+
+# 4. When ready for release, merge to a version branch
+git checkout -b v1.7.0
+git merge feature/new-feature-name --no-ff
+
+# 5. Continue with the release process
+# (Update version numbers, etc.)
 ```
 
 ### Fixing a Bug
 
 ```
-# 1. Create bugfix branch
+# 1. Create bugfix branch from main
+git checkout main
 git checkout -b fix/bug-description
 
 # 2. Make changes and commit
 git add .
 git commit -m "Fix #123: Fix bug description"
 
-# 3. Push to remotes
+# 3. Test locally
-git push github HEAD:fix/bug-description
+# (Run tests, verify functionality)
-git push gitea HEAD:fix/bug-description
+
+# 4. When ready for release, merge to a version branch
+git checkout -b v1.6.5
+git merge fix/bug-description --no-ff
+
+# 5. Continue with the release process
+# (Update version numbers, etc.)
+```
+
+### Testing a Previous Version
+
+```
+# Checkout a specific tag for testing
+git checkout v1.6.3
+
+# Or create a test branch from a specific tag
+git checkout v1.6.3 -b test/some-feature
 ```

.ai-workflows/README.md

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

.ai-workflows/bug-fixing.md

@@ -64,27 +64,60 @@ git commit -m "Fix #123: Brief description of the bug fix"
 
 If there's an issue number, reference it in the commit message.
 
-### 7. Push to Remote
+### 7. Prepare for Release
 
-Push the bug fix branch to the remote repositories:
+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
 ```
 
-### 8. Create Pull Request (Optional)
+### 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 main branch.
+If the repository uses pull requests for code review, create a pull request from the bug fix branch to the version branch.
 
 ## Determining Version Increment
 
 After fixing a bug, determine the appropriate version increment:
 
 - **PATCH** (e.g., 1.6.0 → 1.6.1): For most bug fixes that don't change functionality
+  - **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
 - **MINOR** (e.g., 1.6.0 → 1.7.0): For bug fixes that introduce new features or significant changes
 - **MAJOR** (e.g., 1.6.0 → 2.0.0): For bug fixes that introduce breaking changes
 
+## Testing Previous Versions
+
+To test a previous version of the plugin:
+
+```bash
+# Checkout a specific tag for testing
+git checkout v{MAJOR}.{MINOR}.{PATCH}
+
+# Or create a test branch from a specific tag
+git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
+```
+
 ## Hotfix Process
 
 For critical bugs that need immediate fixing in a released version:
@@ -96,7 +129,7 @@ git checkout v{MAJOR}.{MINOR}.{PATCH}
 git checkout -b hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
 ```
 
-### 2. Fix the Bug
+### 2. Fix the Issues
 
 Apply the minimal fix necessary to address the critical issue.
 
@@ -108,6 +141,8 @@ Increment the PATCH version and update all version numbers:
 - FPDEN_VERSION constant
 - CHANGELOG.md
 - readme.txt
+- README.md
+- languages/fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
 
 ### 4. Commit and Push
 

.ai-workflows/feature-development.md

@@ -33,6 +33,7 @@ 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
 
@@ -52,18 +53,38 @@ git add .
 git commit -m "Add feature: descriptive name"
 ```
 
-### 6. Push to Remote
+### 6. Prepare for Release
 
-Push the feature branch to the remote repositories:
+When the feature is ready to be released:
+
+1. Create a version branch for the release:
+
+```bash
+git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+```
+
+2. Merge your feature branch into the version branch:
+
+```bash
+git merge feature/descriptive-name --no-ff
+```
+
+3. Update version numbers and changelog entries
+
+4. Follow the standard release process from this point
+
+### 7. Push to Remote (Optional for Collaboration)
+
+If you need to collaborate with others on the feature before it's ready for release:
 
 ```bash
 git push github HEAD:feature/descriptive-name
 git push gitea HEAD:feature/descriptive-name
 ```
 
-### 7. Create Pull Request (Optional)
+### 8. Create Pull Request (Optional)
 
-If the repository uses pull requests for code review, create a pull request from the feature branch to the main branch.
+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
 

.ai-workflows/release-process.md

@@ -15,6 +15,7 @@ This document provides step-by-step instructions for AI assistants to help with
 Based on the changes made, determine the appropriate version increment:
 
 1. **PATCH** (e.g., 1.6.0 → 1.6.1): For bug fixes and minor improvements
+   - **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
 2. **MINOR** (e.g., 1.6.0 → 1.7.0): For new features and significant improvements
 3. **MAJOR** (e.g., 1.6.0 → 2.0.0): For breaking changes
 
@@ -72,7 +73,16 @@ Add a new section at the top of the CHANGELOG.md file:
 - Bug fix 2
 ```
 
-#### c. readme.txt
+#### c. POT File (languages/fix-plugin-does-not-exist-notices.pot)
+
+Update the Project-Id-Version and POT-Creation-Date:
+
+```
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices {MAJOR}.{MINOR}.{PATCH}\n"
+"POT-Creation-Date: YYYY-MM-DDT00:00:00+00:00\n"
+```
+
+#### d. readme.txt
 
 Update the stable tag:
 
@@ -102,18 +112,38 @@ Brief description of the most important changes in this release
 ### 3. Commit Changes
 
 ```bash
-git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt
+git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt README.md languages/fix-plugin-does-not-exist-notices.pot
 git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"
 ```
 
-### 4. Push Branch to Remotes
+### 4. Test Changes Locally
+
+Test the changes thoroughly on the version branch to ensure everything works as expected:
+
+- Test with the latest WordPress version
+- Test with PHP 7.0+ (minimum supported version)
+- Verify all features work as expected
+- Check for any PHP warnings or notices
+
+### 5. Merge to Main
+
+When satisfied with testing, merge the version branch to main:
 
 ```bash
-git push github HEAD:v{MAJOR}.{MINOR}.{PATCH}
+git checkout main
-git push gitea HEAD:v{MAJOR}.{MINOR}.{PATCH}
+git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
 ```
 
-### 5. Create and Push Tag
+The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
+
+### 6. Push Main to Remotes
+
+```bash
+git push github main
+git push gitea main
+```
+
+### 7. Create and Push Tag
 
 ```bash
 git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
@@ -121,17 +151,29 @@ git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
 git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
 ```
 
-### 6. Monitor GitHub Actions
+### 8. Monitor GitHub Actions
 
 Open the GitHub Actions page to monitor the build and deployment process:
 https://github.com/wpallstars/fix-plugin-does-not-exist-notices/actions
 
-### 7. Verify Release
+### 9. Verify Release
 
 - [ ] Check that the GitHub release was created successfully
 - [ ] Verify that the plugin was deployed to WordPress.org
 - [ ] Test the plugin from WordPress.org to ensure it works correctly
 
+## Testing Previous Versions
+
+To test a previous version of the plugin:
+
+```bash
+# Checkout a specific tag for testing
+git checkout v{MAJOR}.{MINOR}.{PATCH}
+
+# Or create a test branch from a specific tag
+git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
+```
+
 ## Rollback Procedure (If Needed)
 
 If issues are discovered after release:
@@ -151,16 +193,27 @@ Make the necessary changes to fix the issues.
 
 Increment the PATCH version and update all version numbers as described above.
 
-### 4. Commit and Push
+### 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}"
-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
+### 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}"
@@ -168,6 +221,6 @@ git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
 git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
 ```
 
-### 6. Monitor and Verify
+### 8. Monitor and Verify
 
-Follow steps 6 and 7 from the release process to monitor and verify the hotfix release.
+Follow steps 8 and 9 from the release process to monitor and verify the hotfix release.

.aiconfig

@@ -0,0 +1,26 @@
+{
+  "name": "fix-plugin-does-not-exist-notices",
+  "description": "WordPress plugin to fix 'Plugin file does not exist' notices",
+  "schema_version": "1.0.0",
+  "ignore_patterns": [
+    "*.code-workspace",
+    ".history/",
+    ".ionide/",
+    ".ai-prompts/",
+    ".completions/",
+    ".chat-history/",
+    "*.docx",
+    "*.xlsx",
+    "*.pptx"
+  ],
+  "models": {
+    "default": "gpt-4",
+    "code_generation": "gpt-4",
+    "code_explanation": "gpt-4",
+    "documentation": "gpt-4"
+  },
+  "settings": {
+    "temperature": 0.2,
+    "max_tokens": 4000
+  }
+}

.augmentignore

@@ -0,0 +1,26 @@
+# Augment ignore file
+# Additional patterns beyond .gitignore that should be ignored by Augment's context engine
+
+# IDE and editor files not in .gitignore
+*.code-workspace
+.history/
+.ionide/
+
+# Temporary files that might not be in .gitignore
+.temp-*
+
+# WordPress specific files that might not be in .gitignore
+wp-content/advanced-cache.php
+wp-content/object-cache.php
+wp-content/db.php
+wp-content/debug.log
+
+# Large files that might be missed by .gitignore
+*.docx
+*.xlsx
+*.pptx
+
+# AI-specific files
+.ai-prompts/
+.completions/
+.chat-history/

.clinerc

@@ -0,0 +1,13 @@
+{
+  "ignore": [
+    ".cline/",
+    ".cline-cache/",
+    "*.code-workspace",
+    ".history/",
+    ".ai-prompts/",
+    ".completions/",
+    ".chat-history/"
+  ],
+  "model": "gpt-4",
+  "temperature": 0.2
+}

.cursorignore

@@ -0,0 +1,15 @@
+# Cursor ignore file
+# Additional patterns beyond .gitignore for Cursor's AI context
+
+# Cursor-specific files
+.cursor/
+.cursor-cache/
+
+# IDE and editor files not in .gitignore
+*.code-workspace
+.history/
+
+# AI-specific files
+.ai-prompts/
+.completions/
+.chat-history/

.drone.yml

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

.gitignore

@@ -55,6 +55,32 @@ debug.log
 .env.*
 !.env.example
 
+# Design files
+*.pxd
+*.afdesign
+*.afphoto
+*.afpub
+*.psd
+*.ai
+*.sketch
+*.fig
+*.xd
+*.indd
+*.aep
+*.prproj
+*.psb
+*.xcf
+*.cdr
+*.eps
+*.svg.bak
+*.blend
+*.blend1
+*.blend2
+*.c4d
+*.max
+*.3ds
+*.fbx
+
 # WordPress testing
 .phpunit.result.cache
 .phpcs.cache

.v0ignore

@@ -0,0 +1,15 @@
+# v0 ignore file
+# Additional patterns beyond .gitignore for v0's context
+
+# v0-specific files
+.v0/
+.v0-cache/
+
+# IDE and editor files not in .gitignore
+*.code-workspace
+.history/
+
+# AI-specific files
+.ai-prompts/
+.completions/
+.chat-history/

.windsurfignore

@@ -0,0 +1,15 @@
+# Windsurf ignore file
+# Additional patterns beyond .gitignore for Windsurf's context
+
+# Windsurf-specific files
+.windsurf/
+.windsurf-cache/
+
+# IDE and editor files not in .gitignore
+*.code-workspace
+.history/
+
+# AI-specific files
+.ai-prompts/
+.completions/
+.chat-history/

.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
+      - mkdir -p build/fix-plugin-does-not-exist-notices
-      - cp plugin-reference-cleaner.php build/plugin-reference-cleaner/
+      - cp fix-plugin-does-not-exist-notices.php build/fix-plugin-does-not-exist-notices/
-      - cp readme.txt build/plugin-reference-cleaner/
+      - cp readme.txt build/fix-plugin-does-not-exist-notices/
-      - cp LICENSE build/plugin-reference-cleaner/
+      - cp LICENSE build/fix-plugin-does-not-exist-notices/
-      - cp README.md build/plugin-reference-cleaner/
+      - cp README.md build/fix-plugin-does-not-exist-notices/
-      - if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/plugin-reference-cleaner/; fi
+      - if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/fix-plugin-does-not-exist-notices/; fi
       - cd build
-      - zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
+      - zip -r ../fix-plugin-does-not-exist-notices-$VERSION.zip fix-plugin-does-not-exist-notices
       - cd ..
-      - echo "Build completed - plugin-reference-cleaner-$VERSION.zip"
+      - echo "Build completed - fix-plugin-does-not-exist-notices-$VERSION.zip"
       - ls -la *.zip
-      
+
   release:
     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: fix-plugin-does-not-exist-notices-*.zip
       PLUGIN_TITLE: "Release ${CI_COMMIT_TAG}"
-      PLUGIN_NOTE: "Plugin Reference Cleaner ${CI_COMMIT_TAG}\n\nSee [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/plugin-reference-cleaner/src/branch/main/CHANGELOG.md) for details."
+      PLUGIN_NOTE: "Fix 'Plugin file does not exist.' Notices ${CI_COMMIT_TAG}\n\nSee [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details."
-  
+
   test:
     image: alpine:latest
     commands:
@@ -38,4 +38,4 @@ steps:
       - echo "Testing minimal configuration"
 
 when:
-  event: [push, tag, pull_request] 
+  event: [push, tag, pull_request]

CHANGELOG.md

@@ -2,13 +2,115 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.6.18] - 2024-05-17
+### Changed
+- Optimized AI IDE configuration files to only include patterns not in .gitignore
+- Improved efficiency of ignore files for better AI context management
+- Enhanced compatibility with various AI-powered development tools
+
+## [1.6.17] - 2024-05-17
+### Added
+- .augmentignore file with best practices
+- Configuration files for Cursor, Windsurf, v0, and Cline IDEs
+- More design file formats to .gitignore
+- .aiconfig file for general AI IDE compatibility
+
+## [1.6.16] - 2024-05-17
+### Fixed
+- Updated CI configuration files with correct plugin slugs
+- Updated CHANGELOG.md with all recent versions
+- Fixed outdated references to plugin-reference-cleaner
+
+## [1.6.15] - 2024-05-17
+### Changed
+- Moved AI workflow documentation to root directory for better visibility
+- Consolidated duplicate workflow files
+- Improved organization of development documentation
+- Updated CI configuration files with correct plugin slugs
+
+## [1.6.14] - 2024-05-17
+### Changed
+- Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
+- Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
+- Improved explanation of how the plugin works
+- Ensured consistent terminology across all documentation
+
+## [1.6.13] - 2024-05-17
+### Changed
+- Code cleanup and optimization
+- Improved Git Updater integration
+- Fixed author display in plugin information
+- Ensured compatibility with WordPress 6.4
+
+## [1.6.12] - 2024-05-17
+### Added
+- Added WP ALLSTARS as a co-author
+- Updated author information and links
+- Added author websites to plugin description
+- Fixed issue with multiple author URLs
+
+## [1.6.11] - 2024-05-17
+### Fixed
+- Improved Git Updater integration
+- Fixed plugin header information
+- Updated author information
+
+## [1.6.10] - 2024-05-17
+### Fixed
+- Corrected plugin header information
+- Improved Git Updater compatibility
+- Updated documentation
+
+## [1.6.9] - 2024-05-17
+### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+- Improved documentation
+
+## [1.6.8] - 2024-05-17
+### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+## [1.6.7] - 2024-05-17
+### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+## [1.6.6] - 2024-05-17
+### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+## [1.6.5] - 2024-05-16
+### Fixed
+- Fixed Git Updater integration
+- Updated plugin header information
+
+## [1.6.4] - 2024-05-16
+### Improved
+- Version management to ensure consistent patch version increments
+- Documentation for version update process
+- AI workflow files with detailed version increment instructions
+
+## [1.6.3] - 2024-05-15
+### Fixed
+- Git Updater repository URLs to use full repository paths
+- Update URI configuration for proper update detection
+- Version management following semantic versioning
+
+### Changed
+- Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
 ## [1.6.2] - 2024-05-15
 ### Changed
 - Updated POT file version for consistency
 - Improved JavaScript localization with proper fallbacks
 - Enhanced code quality for WordPress.org submission
-- Fixed Git Updater configuration with correct Update URI
+### Added
-- Improved update server URL configuration
+- Git Updater configuration with Update URI
+- Update server URL configuration
 
 ## [1.6.1] - 2024-05-15
 ### Added

README.md

@@ -13,12 +13,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
 
 "The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
 
-This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Reference" link, allowing you to safely clean up invalid plugin entries with one click.
+This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
 
 ### Key Features
 
 * Adds missing plugins directly to your plugins list
-* Provides a simple "Remove Reference" action link
+* Provides a simple "Remove Notice" action link
 * Works with both single site and multisite WordPress installations
 * Includes helpful notifications explaining how to fix plugin errors
 * One-click auto-scroll to find missing plugins in large sites
@@ -30,8 +30,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 1. Detects all missing plugin references in your database
 2. Adds them to your plugins list with "(File Missing)" indicators
-3. Provides a "Remove Reference" link to safely remove them
+3. Provides a "Remove Notice" link to safely remove them
 4. Shows clear notifications guiding you through the cleanup process
+5. Safely removes the missing active plugin reference from your database using standard WordPress functions
+6. Leaves all remaining plugins installed and active
 
 ### Use Cases
 
@@ -59,7 +61,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 1. After activation, navigate to Plugins > Installed Plugins
 2. If you have missing plugin errors, you'll see them in your plugins list with "(File Missing)" markers
-3. Click the "Remove Reference" link next to any missing plugin
+3. Click the "Remove Notice" link next to any missing plugin
 4. The reference will be removed, and the error notification will disappear
 
 ## Frequently Asked Questions
@@ -78,7 +80,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
 
 ### How do I know which plugin references should be removed?
 
-The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
 
 ### Will this break my site?
 
@@ -95,7 +97,7 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 ## Screenshots
 
 1. Error message with explanation notification
-2. Missing plugin shown in the plugins list with "Remove Reference" link
+2. Missing plugin shown in the plugins list with "Remove Notice" link
 3. Auto-scroll feature that highlights the missing plugin
 
 ## Developers
@@ -114,41 +116,142 @@ Contributions are welcome! Please feel free to submit a Pull Request.
 
 The plugin works by:
 1. Filtering the `all_plugins` array to add missing plugins
-2. Adding a custom "Remove Reference" action link via `plugin_action_links`
+2. Adding a custom "Remove Notice" action link via `plugin_action_links`
 3. Adding helpful notifications near error messages
 4. Providing a secure method to remove plugin references from the database
 
 ## Changelog
 
-### 1.4.1
+### 1.6.18
-- Added FAQ about keeping the plugin installed after notices are cleared
+* 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.4.0
+### 1.6.17
-- Updated plugin name and text domain
+* Added .augmentignore file with best practices
-- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
+* 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.3.3
+### 1.6.16
-* Improved notification placement next to WordPress error messages
+* Updated CI configuration files with correct plugin slugs
-* Added "Click here to scroll" button that automatically locates missing plugins
+* Updated CHANGELOG.md with all recent versions
-* Enhanced reliability with multiple injection methods
+* Fixed outdated references to plugin-reference-cleaner
-* Added visual arrow pointing from notification to error message
 
-### 1.3.2
+### 1.6.15
-* Added prominent notification directly below WordPress error messages
+* Moved AI workflow documentation to root directory for better visibility
-* Improved user guidance with visual cues to connect error and solution
+* Consolidated duplicate workflow files
-* Added eye-catching styling to help users understand how to fix errors
+* Improved organization of development documentation
 
-### 1.3.1
+### 1.6.14
-* Added instructional notification explaining how to use the plugin
+* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
-* Improved user guidance with step-by-step instructions
+* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
-* Enhanced visual identification of missing plugins
+* Improved explanation of how the plugin works
+* Ensured consistent terminology across all documentation
 
-### 1.3.0
+### 1.6.13
-* Complete redesign for maximum compatibility with all WordPress themes
+* Code cleanup and optimization
-* Now adds missing plugins directly to the plugins list table
+* Improved Git Updater integration
-* Uses standard WordPress admin UI patterns instead of DOM manipulation
+* Fixed author display in plugin information
-* Added "Remove Reference" action link in the plugins list
+* Ensured compatibility with WordPress 6.4
-* Significantly improved reliability across all WordPress configurations
+
+### 1.6.12
+* Added WP ALLSTARS as a co-author
+* Updated author information and links
+* Added author websites to plugin description
+* Fixed issue with multiple author URLs
+
+### 1.6.11
+* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
+* Simplified plugin functionality to focus on core features only
+* Improved compatibility with various WordPress configurations
+* Ensured plugin works correctly when other plugins are deleted
+
+### 1.6.10
+* Fixed critical error that could occur when a plugin folder is deleted
+* Improved error handling with try/catch blocks
+* Added more specific checks for the plugins page
+* Enhanced compatibility with various WordPress configurations
+* Made the code more defensive to prevent potential issues
+
+### 1.6.9
+* Fixed issue with notices not appearing below WordPress error messages
+* Improved JavaScript detection of WordPress error notices
+* Prevented WordPress from automatically clearing error notices on page refresh
+* Added multiple timing attempts to ensure notices appear correctly
+* Enhanced error notice targeting for better compatibility
+
+### 1.6.8
+* Fixed notice positioning to appear directly below WordPress error messages
+* Improved notice width to match WordPress error messages
+* Updated explanatory text for better clarity
+* Fixed issue with notices not appearing in some cases
+* Improved JavaScript detection of WordPress error messages
+
+### 1.6.7
+* Fixed duplicate notices issue by removing PHP-generated notice
+* Simplified notice system to only show one notice below WordPress error
+* Ensured consistent terminology with "Remove Notice" text
+* Optimized plugin detection with caching to improve performance
+* Fixed JavaScript to correctly handle multiple error messages
+
+### 1.6.6
+* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
+* Fixed issue with automatic removal of plugin references without user action
+* Fixed notice positioning to ensure it appears below error messages
+* Restored pointer triangle to indicate relationship with error message
+* Improved detection of missing plugins in the plugin list
+* Enhanced scroll functionality to work with all plugin types
+
+### 1.6.5
+* Fixed duplicate notices issue - now only one notice appears below error messages
+* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
+* Updated explanatory text to be more clear about the removal process
+* Changed "Remove Reference" link text to "Remove Notice" for better clarity
+* Made "(File Missing)" text bold and red for better visibility
+* Fixed scroll functionality to work with all plugin rows
+* Improved JavaScript to prevent multiple notices from appearing
+
+### 1.6.4
+* Updated version management to ensure consistent patch version increments
+* Improved documentation for version update process
+* Enhanced AI workflow files with detailed version increment instructions
+
+### 1.6.3
+* Fixed Git Updater repository URLs to use full repository paths
+* Corrected Update URI configuration for proper update detection
+* Improved version management following semantic versioning
+* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
+### 1.6.2
+* Updated POT file version for consistency
+* Improved JavaScript localization with proper fallbacks
+* Enhanced code quality for WordPress.org submission
+* Added Git Updater configuration with Update URI
+* Added update server URL configuration
+
+### 1.6.1
+* Added AI assistant guide and workflow documentation
+* Added detailed release process documentation
+* Added feature development guidelines
+* Added bug fixing procedures
+* Added code review standards
+
+### 1.6.0
+* Added full translation support with POT file
+* Added JavaScript localization for better multilingual support
+* Added plugin constants for improved code organization
+* Added Git Updater support for updates from GitHub and Gitea
+* Updated code to follow WordPress internationalization best practices
+* Improved asset loading with version constants
+* Added smart update detection based on installation source
+
+### 1.5.0
+* Improved compatibility with WordPress 6.4
+* Enhanced error detection for plugin references
+* Minor UI improvements for better visibility
+* Accessibility enhancements for screen readers
 
 [View full changelog](CHANGELOG.md)
 
@@ -158,4 +261,4 @@ This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE)
 
 ## Support
 
-For support, please visit [WP All Stars](https://www.wpallstars.com). 
+For support, please visit [WP ALLSTARS](https://www.wpallstars.com).

assets/css/admin-styles.css

@@ -5,6 +5,9 @@
     margin: 5px 0 15px;
     font-size: 14px;
     position: relative;
+    width: 100%;
+    box-sizing: border-box;
+    max-width: none;
 }
 .prc-notice h3 {
     margin-top: 0;
@@ -23,6 +26,13 @@
 }
 
 /* Style for highlighting the missing plugin row */
-tr.inactive.prc-highlight-missing {
+tr.inactive.prc-highlight-missing,
+tr.active.prc-highlight-missing {
     background-color: #fff8e5 !important; /* Use !important to override default styles */
 }
+
+/* Make File Missing text bold and red */
+span.error {
+    font-weight: bold !important;
+    color: #dc3232 !important;
+}

assets/js/admin-scripts.js

@@ -1,66 +1,104 @@
 (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');
+        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') ||
+            if ((notice.textContent.includes('Plugin file does not exist') ||
-                notice.textContent.includes('has been deactivated due to an error')) {
+                notice.textContent.includes('has been deactivated due to an error')) &&
-
+                (notice.classList.contains('error') || notice.classList.contains('notice-error'))) {
-                // Check if we already added our notice
+                // We'll use the last matching notice as our target
-                if (notice.nextElementSibling && notice.nextElementSibling.classList.contains('prc-notice')) {
+                targetNotice = notice;
-                    return;
+                console.log('Found WordPress error notice:', notice.textContent);
-                }
-
-                // 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 : 'Plugin file missing';
-                var removeReferenceText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.removeReference ?
-                    fpdenData.i18n.removeReference : 'Remove Reference';
-                var clickToScrollText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.clickToScroll ?
-                    fpdenData.i18n.clickToScroll : 'Click here to scroll to missing plugins';
-
-                ourNotice.innerHTML = '<h3 style="margin-top:0;color:#826200;">👉 Fix Plugin Does Not Exist Notices Can Fix This</h3>' +
-                    '<p>To remove the above error notification, scroll down to find the plugin marked with "<strong style="color:red">(' + pluginMissingText + ')</strong>" and click its "<strong>' + removeReferenceText + '</strong>" link.</p>' +
-                    '<p>This will permanently remove the missing plugin reference from your database.</p>' +
-                    '<p><a href="#" id="prc-scroll-to-plugin" style="font-weight:bold;text-decoration:underline;color:#826200;">' + clickToScrollText + '</a></p>';
-
-                // Insert our notice right after the error
-                notice.parentNode.insertBefore(ourNotice, notice.nextSibling);
-
-                // Add scroll behavior
-                var scrollLink = document.getElementById('prc-scroll-to-plugin');
-                if (scrollLink) {
-                    scrollLink.addEventListener('click', function(e) {
-                        e.preventDefault();
-                        var missingPlugins = document.querySelectorAll('tr.inactive:not(.plugin-update-tr)');
-                        for (var i = 0; i < missingPlugins.length; i++) {
-                            if (missingPlugins[i].textContent.includes('(File Missing)')) {
-                                // Add a class for highlighting instead of direct style manipulation
-                                missingPlugins[i].classList.add('prc-highlight-missing');
-                                missingPlugins[i].scrollIntoView({ behavior: 'smooth', block: 'center' });
-                                // Optional: Remove highlight after a delay
-                                setTimeout(function() {
-                                    missingPlugins[i].classList.remove('prc-highlight-missing');
-                                }, 3000); // Remove highlight after 3 seconds
-                                return;
-                            }
-                        }
-                    });
-                }
             }
         });
+
+        // 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() {
-        injectNotice();
+        // 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) {
@@ -68,8 +106,8 @@
                 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') || node.querySelector('.notice, .error, .updated'))) {
+                        if (node.nodeType === 1 && (node.matches('.notice, .error, .updated, div.error') || node.querySelector('.notice, .error, .updated, div.error'))) {
-                            injectNotice();
+                            setTimeout(injectNotice, 50); // Small delay to ensure the DOM is updated
                         }
                     });
                 }
@@ -85,4 +123,9 @@
         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
+    });
+
 })();

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

@@ -4,15 +4,17 @@
  *
  * @package           FixPluginDoesNotExistNotices
  * @author            Marcus Quinn
- * @copyright         2023 WP All Stars
+ * @copyright         2023 WP ALLSTARS
  * @license           GPL-2.0+
+ * @noinspection      PhpUndefinedFunctionInspection
+ * @noinspection      PhpUndefinedConstantInspection
  *
  * @wordpress-plugin
  * Plugin Name: Fix 'Plugin file does not exist.' Notices
  * Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
- * Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
+ * 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. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
- * Version: 1.6.2
+ * Version: 1.6.18
- * Author: Marcus Quinn
+ * Author: Marcus Quinn & WP ALLSTARS
  * Author URI: https://www.wpallstars.com
  * License: GPL-2.0+
  * License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -46,7 +48,7 @@ if ( ! defined( 'ABSPATH' ) ) {
 }
 
 // Define plugin constants
-define( 'FPDEN_VERSION', '1.6.2' );
+define( 'FPDEN_VERSION', '1.6.18' );
 define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
 define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
 define( 'FPDEN_PLUGIN_FILE', __FILE__ );
@@ -71,6 +73,13 @@ add_action( 'plugins_loaded', 'fpden_load_textdomain' );
  */
 class Fix_Plugin_Does_Not_Exist_Notices {
 
+	/**
+	 * Cached list of invalid plugins.
+	 *
+	 * @var array
+	 */
+	private $invalid_plugins = null;
+
 	/**
 	 * Constructor. Hooks into WordPress actions and filters.
 	 */
@@ -89,6 +98,9 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 
 		// Enqueue admin scripts and styles.
 		add_action( 'admin_enqueue_scripts', array( $this, 'enqueue_admin_assets' ) );
+
+		// We're no longer trying to prevent WordPress from auto-deactivating plugins
+		// as it was causing critical errors in some environments
 	}
 
 	/**
@@ -131,8 +143,8 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 			array(
 				'i18n' => array(
 					'clickToScroll' => esc_html__( 'Click here to scroll to missing plugins', 'fix-plugin-does-not-exist-notices' ),
-					'pluginMissing' => esc_html__( 'Plugin file missing', 'fix-plugin-does-not-exist-notices' ),
+					'pluginMissing' => esc_html__( 'File Missing', 'fix-plugin-does-not-exist-notices' ),
-					'removeReference' => esc_html__( 'Remove Reference', 'fix-plugin-does-not-exist-notices' ),
+					'removeNotice' => esc_html__( 'Remove Notice', 'fix-plugin-does-not-exist-notices' ),
 				),
 			)
 		);
@@ -164,7 +176,7 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 					'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 Reference" to permanently remove it from your active plugins list and eliminate the error notice.', 'fix-plugin-does-not-exist-notices' ),
+						__( 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'fix-plugin-does-not-exist-notices' ),
 						'<code>/wp-content/plugins/</code>'
 					),
 					'Version'     => __( 'N/A', 'fix-plugin-does-not-exist-notices' ),
@@ -181,16 +193,17 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	}
 
 	/**
-	 * Add the Remove Reference action link to invalid plugins.
+	 * Add the Remove Notice action link to invalid plugins.
 	 *
 	 * Filters the action links displayed for each plugin on the plugins page.
-	 * Adds a "Remove Reference" link for plugins identified as missing.
+	 * Adds a "Remove Notice" link for plugins identified as missing.
 	 *
 	 * @param array  $actions     An array of plugin action links.
 	 * @param string $plugin_file Path to the plugin file relative to the plugins directory.
 	 * @param array  $plugin_data An array of plugin data.
 	 * @param string $context     The plugin context (e.g., 'all', 'active', 'inactive').
 	 * @return array The potentially modified array of plugin action links.
+	 * @noinspection PhpUnusedParameterInspection
 	 */
 	public function add_remove_reference_action( $actions, $plugin_file, $plugin_data, $context ) {
 		// Only run on the plugins page.
@@ -198,8 +211,11 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 			return $actions;
 		}
 
-		// Check if this is a missing plugin identified by our previous filter.
+		// Get our list of invalid plugins
-		if ( isset( $plugin_data['Name'] ) && strpos( $plugin_data['Name'], '<span class="error">(File Missing)</span>' ) !== false ) {
+		$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();
 
@@ -208,7 +224,7 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 			$remove_url = admin_url( 'plugins.php?action=remove_reference&plugin=' . urlencode( $plugin_file ) . '&_wpnonce=' . $nonce );
 			/* translators: %s: Plugin file path */
 			$aria_label                 = sprintf( __( 'Remove reference to missing plugin %s', 'fix-plugin-does-not-exist-notices' ), esc_attr( $plugin_file ) );
-			$actions['remove_reference'] = '<a href="' . esc_url( $remove_url ) . '" class="delete" aria-label="' . $aria_label . '">' . esc_html__( 'Remove Reference', 'fix-plugin-does-not-exist-notices' ) . '</a>';
+			$actions['remove_reference'] = '<a href="' . esc_url( $remove_url ) . '" class="delete" aria-label="' . $aria_label . '">' . esc_html__( 'Remove Notice', 'fix-plugin-does-not-exist-notices' ) . '</a>';
 		}
 
 		return $actions;
@@ -296,8 +312,9 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	/**
 	 * Display admin notices on the plugins page.
 	 *
-	 * Shows informational notices about missing plugins and feedback
+	 * Shows feedback messages after attempting to remove a reference.
-	 * 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
 	 */
@@ -323,34 +340,8 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 			</div>
 			<?php
 		}
-
+		// The main informational notice is now handled entirely by JavaScript
-		// Get invalid plugins to display the main informational notice.
+		// to position it directly below the WordPress error message.
-		// Note: We don't need to call get_invalid_plugins() again if enqueue_admin_assets already did,
-		// but calling it here ensures the notice shows even if assets weren't enqueued (e.g., JS disabled).
-		// Consider caching the result in a class property if performance is critical.
-		$invalid_plugins = $this->get_invalid_plugins();
-
-		// Display the main informational notice if there are missing plugins.
-		if ( ! empty( $invalid_plugins ) ) {
-			?>
-			<div class="notice notice-info is-dismissible">
-				<h3><?php esc_html_e( 'Fix Plugin Does Not Exist Notices', 'fix-plugin-does-not-exist-notices' ); ?></h3>
-				<p>
-					<strong><?php esc_html_e( 'Missing plugin files detected:', 'fix-plugin-does-not-exist-notices' ); ?></strong>
-					<?php esc_html_e( 'The plugins listed below with a', 'fix-plugin-does-not-exist-notices' ); ?>
-					<span style="color:red;">(<?php esc_html_e( 'File Missing', 'fix-plugin-does-not-exist-notices' ); ?>)</span>
-					<?php esc_html_e( 'tag no longer exist but are still referenced in your database.', 'fix-plugin-does-not-exist-notices' ); ?>
-				</p>
-				<p>
-					<strong><?php esc_html_e( 'How to fix:', 'fix-plugin-does-not-exist-notices' ); ?></strong>
-					<?php esc_html_e( 'Click the "Remove Reference" link next to each missing plugin to safely remove it from your active plugins list.', 'fix-plugin-does-not-exist-notices' ); ?>
-				</p>
-				<p><?php esc_html_e( 'This will clean up your database and remove the error notifications.', 'fix-plugin-does-not-exist-notices' ); ?></p>
-			</div>
-			<?php
-			// The JavaScript enqueued by enqueue_admin_assets() will handle adding the contextual notice
-			// near the actual WordPress error message.
-		}
 	}
 
 	/**
@@ -369,11 +360,17 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	 * Get a list of active plugin file paths that do not exist on the filesystem.
 	 *
 	 * Checks both single site and network active plugins based on the context.
+	 * Uses caching to avoid repeated filesystem checks.
 	 *
 	 * @return array An array of plugin file paths (relative to WP_PLUGIN_DIR) that are missing.
 	 */
 	private function get_invalid_plugins() {
-		$invalid_plugins = array();
+		// Return cached result if available
+		if ( null !== $this->invalid_plugins ) {
+			return $this->invalid_plugins;
+		}
+
+		$this->invalid_plugins = array();
 		$active_plugins  = array();
 
 		// Determine which option to check based on context (Network Admin or single site).
@@ -391,12 +388,14 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 			$plugin_path = WP_PLUGIN_DIR . '/' . $plugin_file;
 			// Use validate_file to prevent directory traversal issues, although less likely here.
 			if ( validate_file( $plugin_file ) === 0 && ! file_exists( $plugin_path ) ) {
-				$invalid_plugins[] = $plugin_file;
+				$this->invalid_plugins[] = $plugin_file;
 			}
 		}
 
-		return $invalid_plugins;
+		return $this->invalid_plugins;
 	}
+
+// We've removed the prevent_auto_deactivation method as it was causing critical errors
 } // End class Fix_Plugin_Does_Not_Exist_Notices
 
 // Initialize the plugin class.
@@ -408,7 +407,7 @@ if (file_exists($autoloader)) {
     require_once $autoloader;
 
     // Initialize the updater if the class exists
-    if (class_exists('\WPAllStars\FixPluginDoesNotExistNotices\Updater')) {
+    if (class_exists('\WPALLSTARS\FixPluginDoesNotExistNotices\Updater')) {
-        new \WPAllStars\FixPluginDoesNotExistNotices\Updater(__FILE__);
+        new \WPALLSTARS\FixPluginDoesNotExistNotices\Updater(__FILE__);
     }
 }

includes/Updater.php

@@ -3,9 +3,11 @@
  * Plugin Updater
  *
  * @package FixPluginDoesNotExistNotices
+ * @noinspection PhpUndefinedFunctionInspection
+ * @noinspection PhpUndefinedClassInspection
  */
 
-namespace WPAllStars\FixPluginDoesNotExistNotices;
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
 
 /**
  * Class Updater
@@ -76,10 +78,11 @@ class Updater {
      * 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);
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
 
         // Look for .git directory with GitHub remote
         if (file_exists($plugin_dir . '.git')) {
@@ -101,10 +104,11 @@ class Updater {
      * 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);
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
 
         // Look for .git directory with Gitea remote
         if (file_exists($plugin_dir . '.git')) {
@@ -121,6 +125,8 @@ class Updater {
      * 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)
@@ -135,9 +141,11 @@ class Updater {
         }
 
         // Set the update server based on the installation source
-        add_filter('gul_update_server', function() {
+        \add_filter('gul_update_server', function() {
-            if ($this->source === 'github' || $this->source === 'gitea') {
+            if ($this->source === 'github') {
-                return 'https://git-updater.wpallstars.com'; // Update server for both GitHub and Gitea
+                return 'https://github.com/wpallstars/fix-plugin-does-not-exist-notices'; // GitHub repository URL
+            } elseif ($this->source === 'gitea') {
+                return 'https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices'; // Gitea repository URL
             }
             return '';
         });

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

@@ -2,14 +2,14 @@
 # This file is distributed under the GPL-2.0+.
 msgid ""
 msgstr ""
-"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.2\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.18\n"
 "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"POT-Creation-Date: 2024-05-15T12:00:00+00:00\n"
+"POT-Creation-Date: 2024-05-16T12:00:00+00:00\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "X-Generator: WP-CLI 2.8.1\n"
 "X-Domain: fix-plugin-does-not-exist-notices\n"

readme.txt

@@ -1,15 +1,15 @@
 === Fix 'Plugin file does not exist.' Notices ===
-Contributors: marcusquinn
+Contributors: marcusquinn, wpallstars
-Donate link: https://www.wpallstars.com
+Donate link: https://www.marcusquinn.com
 Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist
 Requires at least: 5.0
 Tested up to: 6.4
 Requires PHP: 7.0
-Stable tag: 1.6.2
+Stable tag: 1.6.18
 License: GPL-2.0+
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
-Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
+Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
 
 == Description ==
 
@@ -17,12 +17,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
 
 "The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
 
-This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Reference" link, allowing you to safely clean up invalid plugin entries with one click.
+This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
 
 = Key Features =
 
 * Adds missing plugins directly to your plugins list
-* Provides a simple "Remove Reference" action link
+* Provides a simple "Remove Notice" action link
 * Works with both single site and multisite WordPress installations
 * Includes helpful notifications explaining how to fix plugin errors
 * One-click auto-scroll to find missing plugins in large sites
@@ -34,8 +34,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 
 1. Detects all missing plugin references in your database
 2. Adds them to your plugins list with "(File Missing)" indicators
-3. Provides a "Remove Reference" link to safely remove them
+3. Provides a "Remove Notice" link to safely remove them
 4. Shows clear notifications guiding you through the cleanup process
+5. Safely removes the missing active plugin reference from your database using standard WordPress functions
+6. Leaves all remaining plugins installed and active
 
 = Use Cases =
 
@@ -49,7 +51,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
 1. Upload the `fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
 2. Activate the plugin through the 'Plugins' menu in WordPress
 3. No configuration needed - the plugin works automatically
-4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Reference" links
+4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
 
 == Frequently Asked Questions ==
 
@@ -67,7 +69,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
 
 = How do I know which plugin references should be removed? =
 
-The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
+The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
 
 = Will this break my site? =
 
@@ -84,17 +86,119 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 == Screenshots ==
 
 1. Error message with explanation notification
-2. Missing plugin shown in the plugins list with "Remove Reference" link
+2. Missing plugin shown in the plugins list with "Remove Notice" link
 3. Auto-scroll feature that highlights the missing plugin
 
 == Changelog ==
 
+= 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
-* Fixed Git Updater configuration with correct Update URI
+* Added Git Updater configuration with Update URI
-* Improved update server URL configuration
+* Added update server URL configuration
 
 = 1.6.1 =
 * Added AI assistant guide and workflow documentation
@@ -184,8 +288,35 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 
 == Upgrade Notice ==
 
+= 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 fixed Git Updater configuration for seamless updates!
+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!