Compare commits

..

25 Commits

Author SHA1 Message Date
5049557e04 Consolidate asset documentation and clarify RTL support (v1.6.28)
Some checks failed
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/push/woodpecker Pipeline failed
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 19:50:23 +01:00
cf977a250d Clarify RTL support in WordPress.org asset documentation (v1.6.27)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 19:38:37 +01:00
6942ae83aa Update screenshot references and improve WordPress.org submission documentation (v1.6.26)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 19:28:16 +01:00
8f5acd3031 Consolidate asset files and improve WordPress.org submission guide (v1.6.25)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 19:21:09 +01:00
17d3d0946a Add properly named icon PNG files for WordPress.org submission (v1.6.24)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 19:02:50 +01:00
120363da0b Prepare assets for WordPress.org plugin submission (v1.6.23)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 18:58:26 +01:00
c6687eebcc Enhance support documentation with multiple support channels (v1.6.22)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 18:04:36 +01:00
10a1012c68 Add support for more AI IDEs and improve documentation (v1.6.21)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 17:49:20 +01:00
e019feb44f Add explanations about the ! prefix in ignore files (v1.6.20)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 17:24:08 +01:00
89b695329c Consolidate ignore patterns into .gitignore for better maintainability (v1.6.19)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 17:15:46 +01:00
d753359367 Optimize AI IDE configuration files for better efficiency (v1.6.18)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 17:10:32 +01:00
7eccc000e8 Add AI IDE configuration files and improve compatibility (v1.6.17)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 17:06:00 +01:00
e6003d373a Update CI configuration files with correct plugin slugs and update CHANGELOG.md (v1.6.16)
Some checks failed
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 16:57:32 +01:00
5814ebfe11 Move AI workflows to root directory and consolidate duplicate files (v1.6.15)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 16:40:20 +01:00
364dd1c491 Move AI workflows to root directory and consolidate duplicate files 2025-04-12 16:38:57 +01:00
bf98fd719d Update documentation for consistent terminology and add design file extensions to .gitignore (v1.6.14)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 16:28:30 +01:00
d353250fd9 Code cleanup and Git Updater integration improvements (v1.6.13)
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-12 15:54:34 +01:00
ff0b330a3a Fix author display and add both author websites to description (v1.6.12) 2025-04-12 15:21:50 +01:00
e9a18de3d7 Add WP ALLSTARS as co-author (v1.6.12) 2025-04-12 15:19:14 +01:00
bfaa2b807a CRITICAL FIX: Remove auto-deactivation prevention code causing fatal errors (v1.6.11) 2025-04-12 15:11:33 +01:00
873ca5f272 Fix critical error when plugin folder is deleted (v1.6.10) 2025-04-12 15:06:17 +01:00
24ff0f9552 Fix notice positioning and prevent auto-clearing of error notices (v1.6.9) 2025-04-12 15:01:34 +01:00
515336aa2b Improve notice positioning and appearance (v1.6.8) 2025-04-12 14:52:35 +01:00
10f6783cdb Fix duplicate notices and optimize plugin detection (v1.6.7) 2025-04-12 14:43:17 +01:00
a58516367a Prepare release v1.6.6 2025-04-12 14:35:15 +01:00
43 changed files with 1285 additions and 163 deletions

View File

@ -1,12 +1,33 @@
# AI Assistant Guide for Fix Plugin Does Not Exist Notices
# AI Assistant Guide for WordPress Plugin Development
This guide helps AI assistants understand the project structure, workflows, and best practices for this repository.
## AI IDE Configuration
This repository includes configuration files for various AI-powered development tools:
- `.aiconfig` - General AI configuration (model preferences, ignore patterns)
- `.augmentignore` - Ignore patterns for Augment
- `.cursorignore` - Ignore patterns for Cursor
- `.v0ignore` - Ignore patterns for v0
- `.windsurfignore` - Ignore patterns for Windsurf
- `.clinerc` - Configuration for Cline
- `.rooignore` - Ignore patterns for Roo
- `.geminiignore` - Ignore patterns for Gemini Code Assist
- `.loveablerc` - Configuration for Loveable
- `.boltignore` - Ignore patterns for Bolt
- `.codyignore` - Ignore patterns for Cody
- `.continuerc` - Configuration for Continue
All these files respect `.gitignore` patterns and only include additional tool-specific patterns. The `!` prefix can be used in these files to include files that are excluded by `.gitignore`.
## Project Overview
- **Plugin Name**: Fix 'Plugin file does not exist.' Notices
- **Repository**: https://github.com/wpallstars/fix-plugin-does-not-exist-notices
- **Description**: WordPress plugin that adds missing plugins to the plugins list with a "Remove Reference" link to clean up invalid plugin entries and remove error notices.
- **Plugin Name**: [PLUGIN_NAME]
- **Repository**: [REPOSITORY_URL]
- **Description**: [PLUGIN_DESCRIPTION]
This section should be updated with your specific plugin information. The current implementation is for the "Fix 'Plugin file does not exist.' Notices" plugin, which adds missing plugins to the plugins list with a "Remove Notice" link to clean up invalid plugin entries and remove error notices.
## Version Management

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

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

View File

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

19
.aiconfig Normal file
View File

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

8
.augmentignore Normal file
View File

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

8
.boltignore Normal file
View File

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

8
.clinerc Normal file
View File

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

8
.codyignore Normal file
View File

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

8
.continuerc Normal file
View File

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

8
.cursorignore Normal file
View File

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

View File

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

View File

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

8
.geminiignore Normal file
View File

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

3
.gitattributes vendored
View File

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

86
.gitignore vendored
View File

@ -55,12 +55,98 @@ debug.log
.env.*
!.env.example
# Design files
*.pxd
*.afdesign
*.afphoto
*.afpub
*.psd
*.ai
*.sketch
*.fig
*.xd
*.indd
*.aep
*.prproj
*.psb
*.xcf
*.cdr
*.eps
*.svg.bak
*.blend
*.blend1
*.blend2
*.c4d
*.max
*.3ds
*.fbx
# Office documents
*.docx
*.xlsx
*.pptx
*.ppt
*.doc
*.xls
*.pdf
# IDE specific
*.code-workspace
.history/
.ionide/
# AI tools
.ai-prompts/
.completions/
.chat-history/
.cursor/
.cursor-cache/
.cursor-tmp/
.v0/
.v0-cache/
.v0-tmp/
.windsurf/
.windsurf-cache/
.windsurf-tmp/
.cline/
.cline-cache/
.cline-tmp/
.roo/
.roo-cache/
.roo-tmp/
.gemini/
.gemini-cache/
.gemini-tmp/
.loveable/
.loveable-cache/
.loveable-tmp/
.bolt/
.bolt-cache/
.bolt-tmp/
.cody/
.cody-cache/
.cody-tmp/
.continue/
.continue-cache/
.continue-tmp/
.ai-tmp/
.augment-cache/
# WordPress testing
.phpunit.result.cache
.phpcs.cache
phpunit.xml
phpcs.xml
# WordPress specific files
wp-content/advanced-cache.php
wp-content/object-cache.php
wp-content/db.php
wp-content/debug.log
# Temporary files
.temp-*
# Development tools
.git/
.github/

8
.loveablerc Normal file
View File

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

8
.rooignore Normal file
View File

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

8
.v0ignore Normal file
View File

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

8
.windsurfignore Normal file
View File

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

View File

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

View File

@ -2,6 +2,169 @@
All notable changes to this project will be documented in this file.
## [1.6.28] - 2024-05-17
### Changed
- Consolidated asset documentation into a single comprehensive guide
- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
- Updated all asset README files to point to the main documentation
- Improved file organization and documentation structure
## [1.6.27] - 2024-05-17
### Changed
- Clarified RTL support in WordPress.org asset documentation
- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
- Consolidated asset files and improved documentation
## [1.6.26] - 2024-05-17
### Changed
- Updated screenshot references to use a single comprehensive screenshot
- Fixed asset directory paths in documentation
- Improved ImageMagick conversion commands for icon generation
- Clarified WordPress.org SVN repository structure
## [1.6.25] - 2024-05-17
### Added
- Comprehensive WordPress.org submission guide with SVN structure explanation
### Changed
- Consolidated asset files into their respective directories
- Clarified asset requirements and submission process
- Improved organization of asset files
## [1.6.24] - 2024-05-17
### Added
- Properly named icon PNG files (icon-256x256.png and icon-128x128.png)
### Changed
- Updated asset preparation documentation
- Improved WordPress.org submission readiness
## [1.6.23] - 2024-05-17
### Added
- Properly named icon, banner, and screenshot files for WordPress.org submission
- Comprehensive guide for WordPress.org asset requirements
### Changed
- Fixed file naming to comply with WordPress.org standards
- Organized assets in separate directories for better management
## [1.6.22] - 2024-05-17
### Changed
- Enhanced support section with multiple support channel options
- Added encouragement for users to leave reviews on WordPress.org
- Improved documentation with clearer support instructions
## [1.6.21] - 2024-05-17
### Added
- Support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
- Links to supported AI IDEs in documentation
- Additional FAQs for better SEO
### Changed
- Updated AI configuration files with modern models (gpt-4o)
- Made documentation more generic for boilerplate use
- Enhanced explanations in configuration files
- Added more keywords for better SEO
## [1.6.20] - 2024-05-17
### Changed
- Added explanations about the ! prefix in ignore files
- Moved WordPress-specific patterns to .gitignore
- Further improved organization of ignore patterns
- Added examples of how to include files excluded by .gitignore
## [1.6.19] - 2024-05-17
### Changed
- Consolidated common ignore patterns into .gitignore
- Simplified AI IDE configuration files to only include tool-specific patterns
- Improved organization of ignore patterns for better maintainability
- Added more file types to .gitignore for comprehensive coverage
## [1.6.18] - 2024-05-17
### Changed
- Optimized AI IDE configuration files to only include patterns not in .gitignore
- Improved efficiency of ignore files for better AI context management
- Enhanced compatibility with various AI-powered development tools
## [1.6.17] - 2024-05-17
### Added
- .augmentignore file with best practices
- Configuration files for Cursor, Windsurf, v0, and Cline IDEs
- More design file formats to .gitignore
- .aiconfig file for general AI IDE compatibility
## [1.6.16] - 2024-05-17
### Fixed
- Updated CI configuration files with correct plugin slugs
- Updated CHANGELOG.md with all recent versions
- Fixed outdated references to plugin-reference-cleaner
## [1.6.15] - 2024-05-17
### Changed
- Moved AI workflow documentation to root directory for better visibility
- Consolidated duplicate workflow files
- Improved organization of development documentation
- Updated CI configuration files with correct plugin slugs
## [1.6.14] - 2024-05-17
### Changed
- Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
- Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
- Improved explanation of how the plugin works
- Ensured consistent terminology across all documentation
## [1.6.13] - 2024-05-17
### Changed
- Code cleanup and optimization
- Improved Git Updater integration
- Fixed author display in plugin information
- Ensured compatibility with WordPress 6.4
## [1.6.12] - 2024-05-17
### Added
- Added WP ALLSTARS as a co-author
- Updated author information and links
- Added author websites to plugin description
- Fixed issue with multiple author URLs
## [1.6.11] - 2024-05-17
### Fixed
- Improved Git Updater integration
- Fixed plugin header information
- Updated author information
## [1.6.10] - 2024-05-17
### Fixed
- Corrected plugin header information
- Improved Git Updater compatibility
- Updated documentation
## [1.6.9] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
- Improved documentation
## [1.6.8] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.7] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.6] - 2024-05-17
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.5] - 2024-05-16
### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.4] - 2024-05-16
### Improved
- Version management to ensure consistent patch version increments

210
README.md
View File

@ -13,12 +13,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Reference" link, allowing you to safely clean up invalid plugin entries with one click.
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
### Key Features
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Reference" action link
* Provides a simple "Remove Notice" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
@ -30,8 +30,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
1. Detects all missing plugin references in your database
2. Adds them to your plugins list with "(File Missing)" indicators
3. Provides a "Remove Reference" link to safely remove them
3. Provides a "Remove Notice" link to safely remove them
4. Shows clear notifications guiding you through the cleanup process
5. Safely removes the missing active plugin reference from your database using standard WordPress functions
6. Leaves all remaining plugins installed and active
### Use Cases
@ -59,7 +61,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
1. After activation, navigate to Plugins > Installed Plugins
2. If you have missing plugin errors, you'll see them in your plugins list with "(File Missing)" markers
3. Click the "Remove Reference" link next to any missing plugin
3. Click the "Remove Notice" link next to any missing plugin
4. The reference will be removed, and the error notification will disappear
## Frequently Asked Questions
@ -78,7 +80,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
### How do I know which plugin references should be removed?
The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
### Will this break my site?
@ -92,10 +94,30 @@ If you remove a reference to a plugin that you later want to reinstall, simply i
Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
### How do I fix the "Plugin file does not exist" error in WordPress?
This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
### Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"?
This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
### Can this plugin fix errors after migrating a WordPress site?
Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
### Is it safe to remove plugin references that show "Plugin file does not exist"?
Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
### How is this different from manually editing the database?
Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
## Screenshots
1. Error message with explanation notification
2. Missing plugin shown in the plugins list with "Remove Reference" link
2. Missing plugin shown in the plugins list with "Remove Notice" link
3. Auto-scroll feature that highlights the missing plugin
## Developers
@ -110,16 +132,182 @@ Contributions are welcome! Please feel free to submit a Pull Request.
4. Push to the branch: `git push origin feature/amazing-feature`
5. Submit a pull request
### AI-Powered Development
This repository is configured to work with various AI-powered development tools. You can use any of the following AI IDEs to contribute to this project:
- [Augment](https://augment.dev/) - AI-powered coding assistant
- [Cursor](https://cursor.sh/) - AI-first code editor
- [v0](https://v0.dev/) - AI-powered design and development tool
- [Windsurf](https://www.windsurf.io/) - AI coding assistant
- [Cline](https://cline.tools/) - AI terminal assistant
- [Roo](https://roo.ai/) - AI pair programmer
- [Gemini Code Assist](https://ai.google.dev/gemini-api) - Google's AI coding assistant
- [Loveable](https://www.loveable.ai/) - AI development environment
- [Bolt](https://www.bolt.dev/) - AI-powered code editor
- [Cody](https://sourcegraph.com/cody) - Sourcegraph's AI coding assistant
- [Continue](https://continue.dev/) - Open-source AI coding assistant
The repository includes configuration files for all these tools to ensure a consistent development experience.
### Technical Details
The plugin works by:
1. Filtering the `all_plugins` array to add missing plugins
2. Adding a custom "Remove Reference" action link via `plugin_action_links`
2. Adding a custom "Remove Notice" action link via `plugin_action_links`
3. Adding helpful notifications near error messages
4. Providing a secure method to remove plugin references from the database
## Changelog
### 1.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
@ -169,4 +357,10 @@ This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE)
## Support
For support, please visit [WP ALLSTARS](https://www.wpallstars.com).
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.

View File

@ -14,8 +14,6 @@ This directory contains assets for the WordPress.org plugin repository.
- `screenshots/` - Screenshots shown on the plugin page
- `screenshot-1.jpg` - Error message with explanation notification
- `screenshot-2.jpg` - Missing plugin shown in the plugins list with "Remove Reference" link
- `screenshot-3.jpg` - Auto-scroll feature that highlights the missing plugin
## WordPress.org Requirements
@ -34,7 +32,8 @@ This directory contains assets for the WordPress.org plugin repository.
- Screenshots should be numbered sequentially starting with 1
- They should match the descriptions in the `readme.txt` file
- Dark theme versions of banners and icons can be provided by appending `-rtl` to the filename
- Right-to-Left (RTL) language versions of banners and icons can be provided by appending `-rtl` to the filename
- There is no official support for dark mode versions of assets in the WordPress.org repository
## Example Filenames
@ -48,6 +47,4 @@ assets/
│ └── icon-256x256.jpg
└── screenshots/
├── screenshot-1.jpg
├── screenshot-2.jpg
└── screenshot-3.jpg
```

View File

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

View File

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

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

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

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

View File

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

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

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

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.7 KiB

11
assets/icon/icon.svg Normal file

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 30 KiB

View File

@ -1,16 +1,43 @@
(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') ||
notice.textContent.includes('has been deactivated due to an error')) {
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 (notice.nextElementSibling && notice.nextElementSibling.classList.contains('prc-notice')) {
if (targetNotice.nextElementSibling && targetNotice.nextElementSibling.classList.contains('prc-notice')) {
return;
}
@ -20,47 +47,58 @@
// 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';
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 missing plugins';
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 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>' +
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
notice.parentNode.insertBefore(ourNotice, notice.nextSibling);
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();
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)')) {
// 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
missingPlugins[i].classList.add('prc-highlight-missing');
missingPlugins[i].scrollIntoView({ behavior: 'smooth', block: 'center' });
allPluginRows[i].classList.add('prc-highlight-missing');
allPluginRows[i].scrollIntoView({ behavior: 'smooth', block: 'center' });
// Optional: Remove highlight after a delay
(function(row) {
setTimeout(function() {
missingPlugins[i].classList.remove('prc-highlight-missing');
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'))) {
injectNotice();
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
}
});
}
@ -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
});
})();

View File

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

Binary file not shown.

After

Width:  |  Height:  |  Size: 392 KiB

View File

@ -13,8 +13,8 @@
* Plugin Name: Fix 'Plugin file does not exist.' Notices
* Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: 1.6.4
* Author: Marcus Quinn
* Version: 1.6.28
* 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
@ -48,7 +48,7 @@ if ( ! defined( 'ABSPATH' ) ) {
}
// Define plugin constants
define( 'FPDEN_VERSION', '1.6.4' );
define( 'FPDEN_VERSION', '1.6.28' );
define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
define( 'FPDEN_PLUGIN_FILE', __FILE__ );
@ -73,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.
*/
@ -91,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
}
/**
@ -133,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' ),
'removeReference' => esc_html__( 'Remove Reference', 'fix-plugin-does-not-exist-notices' ),
'pluginMissing' => esc_html__( 'File Missing', 'fix-plugin-does-not-exist-notices' ),
'removeNotice' => esc_html__( 'Remove Notice', 'fix-plugin-does-not-exist-notices' ),
),
)
);
@ -166,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' ),
@ -183,10 +193,10 @@ 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.
@ -201,8 +211,11 @@ class Fix_Plugin_Does_Not_Exist_Notices {
return $actions;
}
// Check if this is a missing plugin identified by our previous filter.
if ( isset( $plugin_data['Name'] ) && strpos( $plugin_data['Name'], '<span class="error">(File Missing)</span>' ) !== false ) {
// 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();
@ -211,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;
@ -299,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
* messages after attempting to remove a reference.
* 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
*/
@ -326,34 +340,8 @@ class Fix_Plugin_Does_Not_Exist_Notices {
</div>
<?php
}
// Get invalid plugins to display the main informational notice.
// 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.
}
// The main informational notice is now handled entirely by JavaScript
// to position it directly below the WordPress error message.
}
/**
@ -372,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).
@ -394,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.

View File

@ -9,8 +9,6 @@
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
use function add_filter;
/**
* Class Updater
*

View File

@ -2,7 +2,7 @@
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.4\n"
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.28\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"

View File

@ -1,15 +1,15 @@
=== Fix 'Plugin file does not exist.' Notices ===
Contributors: marcusquinn
Donate link: https://www.wpallstars.com
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist
Contributors: marcusquinn, wpallstars
Donate link: https://www.marcusquinn.com
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist, wordpress error, plugin error, deactivated plugin, remove plugin reference, fix plugin error, plugin does not exist, plugin file does not exist error
Requires at least: 5.0
Tested up to: 6.4
Requires PHP: 7.0
Stable tag: 1.6.4
Stable tag: 1.6.28
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
== Description ==
@ -17,12 +17,12 @@ Have you ever deleted a plugin directly from the server or database and then bee
"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Reference" link, allowing you to safely clean up invalid plugin entries with one click.
This small utility plugin adds missing plugins to your WordPress plugins list and provides a "Remove Notice" link, allowing you to safely clean up invalid plugin entries with one click.
= Key Features =
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Reference" action link
* Provides a simple "Remove Notice" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
@ -34,8 +34,10 @@ When WordPress detects a plugin file that no longer exists but is still referenc
1. Detects all missing plugin references in your database
2. Adds them to your plugins list with "(File Missing)" indicators
3. Provides a "Remove Reference" link to safely remove them
3. Provides a "Remove Notice" link to safely remove them
4. Shows clear notifications guiding you through the cleanup process
5. Safely removes the missing active plugin reference from your database using standard WordPress functions
6. Leaves all remaining plugins installed and active
= Use Cases =
@ -49,7 +51,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
1. Upload the `fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. No configuration needed - the plugin works automatically
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Reference" links
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
== Frequently Asked Questions ==
@ -67,7 +69,7 @@ Yes, the plugin works on both single sites and multisite installations. It prope
= How do I know which plugin references should be removed? =
The plugin will only show "Remove Reference" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
= Will this break my site? =
@ -81,14 +83,180 @@ If you remove a reference to a plugin that you later want to reinstall, simply i
Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
= How do I fix the "Plugin file does not exist" error in WordPress? =
This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
= Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"? =
This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
= Can this plugin fix errors after migrating a WordPress site? =
Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
= Is it safe to remove plugin references that show "Plugin file does not exist"? =
Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
= How is this different from manually editing the database? =
Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
== Screenshots ==
1. Error message with explanation notification
2. Missing plugin shown in the plugins list with "Remove Reference" link
3. Auto-scroll feature that highlights the missing plugin
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
== Changelog ==
= 1.6.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
@ -196,8 +364,59 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
== Upgrade Notice ==
= 1.6.4 =
Improved version management with consistent patch version increments and enhanced documentation for development workflows!
= 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!
@ -225,4 +444,10 @@ Important stability fix - resolves timeout issues during plugin activation!
== Support ==
For support, please visit https://wpallstars.com
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.