Compare commits

..

36 Commits

Author SHA1 Message Date
marcus 22d13ef8aa Add Git Updater support with smart source detection
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 00:03:10 +01:00
marcus 322cada133 Add translation support and internationalization improvements
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-11 23:49:22 +01:00
marcus df344d76ae Update changelog for version 1.5.0
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-11 23:44:42 +01:00
marcus 4014716da9 Fix: Include assets directory in release workflow 2025-04-11 22:55:39 +01:00
marcus 613c4f43b6 Refactor: Enqueue assets, add docblocks, bump version to 1.5.0 2025-04-11 22:48:47 +01:00
marcus b883a222c0 Version 1.4.2: Improved plugin descriptions for better clarity
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-11 00:19:13 +01:00
marcus 8562c311c5 Align README.md FAQ with readme.txt for consistency
ci/woodpecker/push/woodpecker Pipeline is pending
2025-04-10 01:36:03 +01:00
marcus 78a911640f Version 1.4.1: Add FAQ about keeping plugin installed
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-10 01:24:17 +01:00
marcus c45621d896 Version 1.4.0: Rename plugin and update text domain
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-10 01:13:49 +01:00
marcus 7ae1da3775 Rename plugin to 'Fix Plugin file does not exist. Notices' for better SEO 2025-04-10 01:03:23 +01:00
marcus 113c4d54da Prepare for WordPress.org plugin repository submission
ci/woodpecker/push/woodpecker Pipeline is pending
2025-04-10 00:54:56 +01:00
marcus bcc9f984f6 Improved notification reliability with auto-scroll feature (v1.3.3)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-10 00:31:17 +01:00
marcus db662096e4 Add prominent notification next to WordPress error messages (v1.3.2)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-10 00:26:32 +01:00
marcus d6b89887fc Add instructional notification for users (v1.3.1)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-10 00:15:16 +01:00
marcus cd593f68d3 Complete redesign to use WordPress plugins list directly (v1.3.0)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-10 00:06:07 +01:00
marcus 7ac72fd3c0 Fix compatibility with more WordPress admin themes (v1.2.4)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-10 00:01:20 +01:00
marcus 0a394fa671 Fix button not appearing in some WP admin themes (v1.2.3)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-09 23:56:47 +01:00
marcus f200ff6f96 Fix timeout issue during plugin activation (v1.2.2)
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-09 23:46:06 +01:00
marcus fb4a54ab57 Version 1.2.1: Fix typos and improve text clarity
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-07 14:35:48 +01:00
marcus 67d13c9354 Bump version to 1.2 with improved documentation
ci/woodpecker/push/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline failed
2025-04-07 14:29:53 +01:00
marcus 6aa330c387 Sync readme.txt with README.md and improve documentation 2025-04-07 14:29:16 +01:00
marcus 18772160cf Update README.md with detailed explanation and SQL reference
ci/woodpecker/push/woodpecker Pipeline is pending
2025-04-07 13:47:23 +01:00
marcus 361a361a50 Fix duplicate steps section in Woodpecker CI configuration
ci/woodpecker/push/woodpecker Pipeline is pending
2025-04-07 06:19:06 +01:00
marcus d74b0835bf Fix Woodpecker CI configuration to avoid duplicate steps and use multiple events 2025-04-07 06:18:17 +01:00
marcus f85f6f0d3c Use minimal Woodpecker CI configuration for testing
ci/woodpecker/push/woodpecker Pipeline is pending
ci/woodpecker/tag/woodpecker Pipeline is pending
ci/woodpecker/manual/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 06:16:04 +01:00
marcus 63a2ec3ff9 Add clone debugging to Woodpecker CI configuration
ci/woodpecker/tag/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 06:11:28 +01:00
marcus f8cabf71b6 Update Woodpecker CI configuration to use environment variables instead of secrets
ci/woodpecker/tag/woodpecker Pipeline is pending
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 05:52:02 +01:00
marcus bbdc06b4c1 Fix command formatting in Woodpecker CI configuration
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 05:51:18 +01:00
marcus 3bf5e3d4ab Fix Woodpecker CI configuration format
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 05:50:19 +01:00
marcus c27dbe9343 Improve Woodpecker CI configuration and add CHANGELOG
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 05:47:54 +01:00
marcus aa416c1950 Add Woodpecker CI configuration for Gitea 2025-04-07 05:44:24 +01:00
marcus feff61ca3f Add release automation for GitHub and Gitea
Build Release / Build and Create Release (push) Has been cancelled
2025-04-07 05:43:29 +01:00
marcus d1d8c0bad1 Add WordPress compatibility info 2025-04-07 05:36:27 +01:00
Marcus Quinn 031c759a84 Update README with security feature highlight 2025-04-07 05:32:40 +01:00
Marcus Quinn 14b1434c65 Improved plugin security and compatibility 2025-04-07 05:17:37 +01:00
Marcus Quinn 57e63ff55e Initial commit with standard Git files 2025-04-07 04:59:49 +01:00
57 changed files with 850 additions and 4714 deletions
-293
View File
@@ -1,293 +0,0 @@
# 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/wp-fix-plugin-does-not-exist-notices
- **Description**: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
This plugin helps users clean up references to deleted plugins that cause "Plugin file does not exist" errors in the WordPress admin. It adds missing plugins to the plugins list with a "Remove Notice" link to safely remove invalid plugin entries.
## Reference Plugins
The `reference-plugins/` directory contains plugins that can be used for reference or inspiration. When developing new features or improving existing ones, you should:
1. Examine these reference plugins for best practices in code structure, organization, and implementation
2. Look for patterns in how they handle similar functionality
3. Consider their approach to user interface design and user experience
4. Study their documentation style and thoroughness
These plugins are not part of the codebase and are ignored by Git, but they provide valuable examples of WordPress plugin development standards and techniques.
## Version Management
### Version Numbering Convention
We follow [Semantic Versioning](https://semver.org/):
- **MAJOR.MINOR.PATCH** (e.g., 1.6.0)
- **MAJOR**: Breaking changes
- **MINOR**: New features, non-breaking
- **PATCH**: Bug fixes, non-breaking
### When to Increment Version Numbers
- **PATCH** (1.6.0 → 1.6.1):
- Bug fixes
- Small text changes
- Minor improvements that don't add new features
- **MINOR** (1.6.0 → 1.7.0):
- New features
- Significant improvements to existing functionality
- Deprecation of features (but not removal)
- **MAJOR** (1.6.0 → 2.0.0):
- Breaking changes
- Removal of features
- Major architectural changes
### Version Update Checklist
When updating the version number, always update these files:
1. `wp-fix-plugin-does-not-exist-notices.php` (Plugin header)
2. `CHANGELOG.md` (Add new version section)
3. `readme.txt` (Stable tag and Changelog section)
4. `README.md` (Update Changelog section to match readme.txt)
5. Update `FPDEN_VERSION` constant in the main plugin file
6. Update `languages/wp-fix-plugin-does-not-exist-notices.pot` (Project-Id-Version and POT-Creation-Date)
**IMPORTANT**: Always ensure README.md is kept in sync with readme.txt for consistency across platforms.
## Git Workflow
### Branch Naming Convention
- Feature branches: `feature/descriptive-name`
- Bug fix branches: `fix/issue-description`
- Release branches: `v{MAJOR}.{MINOR}.{PATCH}`
### Commit Message Guidelines
- Use present tense ("Add feature" not "Added feature")
- Start with a verb
- Keep the first line under 50 characters
- Reference issues when relevant: "Fix #123: Resolve plugin detection issue"
### Pre-Release Checklist
Before creating a new release, verify the following:
- [ ] Determine the correct version increment (MAJOR, MINOR, or PATCH) based on the changes
- [ ] Ensure all changes are documented in CHANGELOG.md
- [ ] Verify all code changes are tested and working correctly
- [ ] Check that all files are properly formatted and follow WordPress coding standards
- [ ] Ensure Git Updater configuration is correct (if applicable)
### Release Process
1. Create a new branch for the version: `git checkout -b v{MAJOR}.{MINOR}.{PATCH}`
2. Update version numbers in ALL required files:
- `wp-fix-plugin-does-not-exist-notices.php` (Plugin header)
- `FPDEN_VERSION` constant in the main plugin file
- `readme.txt` (Stable tag)
- `README.md` (Ensure changelog is updated)
- `languages/wp-fix-plugin-does-not-exist-notices.pot` (Project-Id-Version)
- Any other files that reference the version number
3. Update CHANGELOG.md with all changes
4. Update readme.txt changelog section
5. Update README.md changelog section to match readme.txt
6. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
7. Test changes locally on the version branch
8. When satisfied with testing, merge to main:
```
git checkout main
git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
```
9. Push main to all remotes:
```
git push github main
git push gitea main
```
10. Create and push a tag to trigger the GitHub Actions workflow:
```
git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
```
11. Verify the GitHub Actions workflow completes successfully
## Build Process
The build process is handled by `build.sh`:
1. Updates version numbers
2. Installs composer dependencies
3. Copies files to build directory
4. Creates ZIP file
To manually build the plugin:
```
./build.sh {MAJOR}.{MINOR}.{PATCH}
```
## Remote Repositories
The plugin is hosted on multiple repositories:
- GitHub: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
- Gitea: https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices
- WordPress.org: https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/
Always push changes to all remotes to keep them in sync.
## GitHub Actions
The repository uses GitHub Actions for automated builds and deployments:
- Triggered by tags matching the pattern `v*`
- Builds the plugin
- Creates a GitHub release
- Deploys to WordPress.org
## Testing Guidelines
Before releasing:
1. Test with the latest WordPress version
2. Test with PHP 7.0+ (minimum supported version)
3. Verify all features work as expected
4. Check for any PHP warnings or notices
### Local Testing Environment
Local environment variables and paths are documented in `.ai-workflows/local-env-vars.md`. This includes:
- Repository paths
- Local WordPress testing environment paths
- URLs for testing and development tools
- Build and deploy script locations
Refer to this file for the most up-to-date information about the local development environment.
### Using WP-CLI with LocalWP
WP-CLI can be used with LocalWP for various tasks:
```bash
# Navigate to the WordPress directory
cd ~/Local/plugin-testing/app/public
# Run WP-CLI commands
~/Local/plugin-testing/app/bin/wp plugin list
~/Local/plugin-testing/app/bin/wp transient delete --all
~/Local/plugin-testing/app/bin/wp cache flush
```
## Common Tasks for AI Assistants
### Creating a New Release
```
# 1. Create a new branch
git checkout main
git checkout -b v1.7.0
# 2. Update version numbers in ALL required files
# - wp-fix-plugin-does-not-exist-notices.php
# - CHANGELOG.md
# - readme.txt
# - README.md
# - languages/wp-fix-plugin-does-not-exist-notices.pot
# - FPDEN_VERSION constant
# 3. Commit changes
git add .
git commit -m "Prepare release v1.7.0"
# 4. Test changes locally on the version branch
# (Run tests, verify functionality)
# 5. Merge to main when ready
git checkout main
git merge v1.7.0 --no-ff
# 6. Push main to remotes
git push github main
git push gitea main
# 7. Create and push tag
git tag -a v1.7.0 -m "Release version 1.7.0"
git push github refs/tags/v1.7.0
git push gitea refs/tags/v1.7.0
```
### Adding a New Feature
```
# 1. Create feature branch from main
git checkout main
git checkout -b feature/new-feature-name
# 2. Make changes and commit
git add .
git commit -m "Add new feature"
# 3. Test locally
# (Run tests, verify functionality)
# 4. When ready for release, merge to a version branch
git checkout -b v1.7.0
git merge feature/new-feature-name --no-ff
# 5. Continue with the release process
# (Update version numbers, etc.)
```
### Fixing a Bug
```
# 1. Create bugfix branch from main
git checkout main
git checkout -b fix/bug-description
# 2. Make changes and commit
git add .
git commit -m "Fix #123: Fix bug description"
# 3. Test locally
# (Run tests, verify functionality)
# 4. When ready for release, merge to a version branch
git checkout -b v1.6.5
git merge fix/bug-description --no-ff
# 5. Continue with the release process
# (Update version numbers, etc.)
```
### Testing a Previous Version
```
# Checkout a specific tag for testing
git checkout v1.6.3
# Or create a test branch from a specific tag
git checkout v1.6.3 -b test/some-feature
```
-12
View File
@@ -1,12 +0,0 @@
# AI Workflows
This directory contains workflow documentation for AI assistants working with this repository.
## Contents
- **bug-fixing.md**: Guidelines for identifying and fixing bugs in the codebase
- **code-review.md**: Standards and procedures for reviewing code changes
- **feature-development.md**: Process for developing new features
- **release-process.md**: Steps for preparing and publishing new releases
These documents help ensure consistent quality and approach when using AI tools to assist with development tasks.
-195
View File
@@ -1,195 +0,0 @@
# Bug Fixing Guide for AI Assistants
This document provides guidance for AI assistants to help with bug fixing for the Fix Plugin Does Not Exist Notices plugin.
## Bug Fixing Workflow
### 1. Create a Bug Fix Branch
Always start by creating a bug fix branch from the main branch:
```bash
git checkout main
git pull github main
git checkout -b fix/bug-description
```
Use a descriptive name that clearly indicates what bug is being fixed.
### 2. Understand the Bug
Before fixing a bug, make sure you understand:
- What is the expected behavior?
- What is the actual behavior?
- What are the steps to reproduce the bug?
- What is the impact of the bug?
- What is the root cause of the bug?
### 3. Fix the Bug
When fixing a bug:
- Make minimal changes necessary to fix the bug
- Avoid introducing new features while fixing bugs
- Maintain backward compatibility
- Add appropriate comments explaining the fix
- Consider adding tests to prevent regression
### 4. Update Documentation
Update relevant documentation to reflect the bug fix:
- Add a description to CHANGELOG.md under an "Unreleased" section
- Update readme.txt if the bug fix affects user-facing functionality
### 5. Testing
Test the bug fix thoroughly:
- Verify that the bug is fixed
- Ensure no regression in related functionality
- Test with the latest WordPress version
- Test with the minimum supported WordPress version (5.0)
- Test with PHP 7.0+ (minimum supported version)
### 6. Commit Changes
Make atomic commits with clear messages:
```bash
git add .
git commit -m "Fix #123: Brief description of the bug fix"
```
If there's an issue number, reference it in the commit message.
### 7. Prepare for Release
When the bug fix is ready to be released:
1. Create a version branch for the release:
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
2. Merge your bug fix branch into the version branch:
```bash
git merge fix/bug-description --no-ff
```
3. Update version numbers and changelog entries
4. Follow the standard release process from this point
### 8. Push to Remote (Optional for Collaboration)
If you need to collaborate with others on the bug fix before it's ready for release:
```bash
git push github HEAD:fix/bug-description
git push gitea HEAD:fix/bug-description
```
### 9. Create Pull Request (Optional)
If the repository uses pull requests for code review, create a pull request from the bug fix branch to the version branch.
## Determining Version Increment
After fixing a bug, determine the appropriate version increment:
- **PATCH** (e.g., 1.6.0 → 1.6.1): For most bug fixes that don't change functionality
- **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
- **MINOR** (e.g., 1.6.0 → 1.7.0): For bug fixes that introduce new features or significant changes
- **MAJOR** (e.g., 1.6.0 → 2.0.0): For bug fixes that introduce breaking changes
## Testing Previous Versions
To test a previous version of the plugin:
```bash
# Checkout a specific tag for testing
git checkout v{MAJOR}.{MINOR}.{PATCH}
# Or create a test branch from a specific tag
git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
```
## Hotfix Process
For critical bugs that need immediate fixing in a released version:
### 1. Create a Hotfix Branch
```bash
git checkout v{MAJOR}.{MINOR}.{PATCH}
git checkout -b hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 2. Fix the Issues
Apply the minimal fix necessary to address the critical issue.
### 3. Update Version Numbers
Increment the PATCH version and update all version numbers:
- Main plugin file (fix-plugin-does-not-exist-notices.php)
- FPDEN_VERSION constant
- CHANGELOG.md
- readme.txt
- README.md
- languages/fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
### 4. Commit and Push
```bash
git add .
git commit -m "Hotfix: Brief description of the critical bug fix"
git push github HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 5. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH+1} -m "Hotfix release version {MAJOR}.{MINOR}.{PATCH+1}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
```
## Common Bug Types and Fixing Strategies
### WordPress Compatibility Issues
- Test with the specific WordPress version where the issue occurs
- Check for deprecated functions or hooks
- Review WordPress changelog for relevant changes
### PHP Compatibility Issues
- Test with the specific PHP version where the issue occurs
- Check for deprecated PHP functions or features
- Use appropriate polyfills if necessary
### JavaScript Issues
- Test in different browsers
- Check for browser console errors
- Consider browser-specific workarounds if necessary
### CSS Issues
- Test in different browsers and screen sizes
- Use browser developer tools to inspect elements
- Consider browser-specific workarounds if necessary
### Database Issues
- Use proper database prefixing
- Sanitize database inputs
- Use prepared statements for queries
- Consider database version differences
-163
View File
@@ -1,163 +0,0 @@
# Code Review Guide for AI Assistants
This document provides guidance for AI assistants to help with code review for the Fix Plugin Does Not Exist Notices plugin.
## Code Review Checklist
When reviewing code, check for the following:
### Functionality
- [ ] Does the code work as expected?
- [ ] Does it handle edge cases appropriately?
- [ ] Are there any logical errors?
- [ ] Is error handling implemented properly?
### Code Quality
- [ ] Does the code follow WordPress coding standards?
- [ ] Is the code well-organized and easy to understand?
- [ ] Are there any code smells (duplicate code, overly complex functions, etc.)?
- [ ] Are functions and variables named appropriately?
- [ ] Are there appropriate comments and documentation?
### Security
- [ ] Is user input properly validated and sanitized?
- [ ] Is output properly escaped?
- [ ] Are capability checks used for user actions?
- [ ] Are nonces used for form submissions?
- [ ] Are there any potential SQL injection vulnerabilities?
- [ ] Are there any potential XSS vulnerabilities?
### Performance
- [ ] Are there any performance bottlenecks?
- [ ] Are database queries optimized?
- [ ] Is caching used appropriately?
- [ ] Are assets (CSS, JS) properly enqueued?
### Compatibility
- [ ] Is the code compatible with the minimum supported WordPress version (5.0)?
- [ ] Is the code compatible with the minimum supported PHP version (7.0)?
- [ ] Are there any browser compatibility issues?
- [ ] Are there any conflicts with other plugins?
### Internationalization
- [ ] Are all user-facing strings translatable?
- [ ] Is the correct text domain used?
- [ ] Are translation functions used correctly?
### Accessibility
- [ ] Does the code follow accessibility best practices?
- [ ] Are ARIA attributes used appropriately?
- [ ] Is keyboard navigation supported?
- [ ] Is screen reader support implemented?
## Code Review Process
### 1. Understand the Context
Before reviewing code, understand:
- What problem is the code trying to solve?
- What are the requirements?
- What are the constraints?
### 2. Review the Code
Review the code with the checklist above in mind.
### 3. Provide Feedback
When providing feedback:
- Be specific and clear
- Explain why a change is needed
- Provide examples or suggestions when possible
- Prioritize feedback (critical issues vs. minor improvements)
- Be constructive and respectful
### 4. Follow Up
After the code has been updated:
- Review the changes
- Verify that issues have been addressed
- Provide additional feedback if necessary
## Common Issues to Look For
### PHP Issues
- Undefined variables or functions
- Incorrect function parameters
- Missing return statements
- Improper error handling
- Inefficient loops or conditionals
- Hardcoded values that should be configurable
### WordPress-Specific Issues
- Incorrect hook usage
- Missing or incorrect nonces
- Missing capability checks
- Direct database queries instead of using WordPress functions
- Improper enqueuing of scripts and styles
- Not using WordPress functions for common tasks
### JavaScript Issues
- Undefined variables or functions
- Event listener memory leaks
- jQuery conflicts
- Browser compatibility issues
- Missing error handling
### CSS Issues
- Browser compatibility issues
- Specificity issues
- Unused styles
- Overriding WordPress admin styles inappropriately
## Example Feedback
### Good Feedback Example
```
In function `handle_remove_reference()`:
1. The nonce check is missing, which could lead to CSRF vulnerabilities.
Consider adding:
```php
if (!isset($_GET['_wpnonce']) || !wp_verify_nonce($_GET['_wpnonce'], 'fpden_remove_reference')) {
wp_die(__('Security check failed.', 'fix-plugin-does-not-exist-notices'));
}
```
2. The user capability check should be more specific. Instead of:
```php
if (!current_user_can('manage_options')) {
```
Consider using:
```php
if (!current_user_can('activate_plugins')) {
```
This is more appropriate for the action being performed.
3. The success message should be translatable:
```php
// Change this:
add_settings_error('fpden', 'fpden_removed', 'Plugin reference removed successfully.', 'updated');
// To this:
add_settings_error('fpden', 'fpden_removed', __('Plugin reference removed successfully.', 'fix-plugin-does-not-exist-notices'), 'updated');
```
```
### Poor Feedback Example
```
This code has security issues and doesn't follow best practices. Fix it.
```
-152
View File
@@ -1,152 +0,0 @@
# Feature Development Guide for AI Assistants
This document provides guidance for AI assistants to help with feature development for the Fix Plugin Does Not Exist Notices plugin.
## Feature Development Workflow
### 1. Create a Feature Branch
Always start by creating a feature branch from the main branch:
```bash
git checkout main
git pull github main
git checkout -b feature/descriptive-name
```
Use a descriptive name that clearly indicates what the feature is about.
### 2. Implement the Feature
When implementing a new feature:
- Follow WordPress coding standards
- Ensure all strings are translatable
- Add appropriate comments
- Consider performance implications
- Maintain backward compatibility
- Review reference plugins in the `reference-plugins/` directory for inspiration and best practices
### 3. Update Documentation
Update relevant documentation to reflect the new feature:
- Add a description to CHANGELOG.md under an "Unreleased" section
- Update readme.txt if the feature affects user-facing functionality
- Update inline documentation/comments
- Remember that any feature addition will require a version increment in all relevant files
### 4. Testing
Test the feature thoroughly:
- Test with the latest WordPress version
- Test with the minimum supported WordPress version (5.0)
- Test with PHP 7.0+ (minimum supported version)
- Test in different environments (if possible)
### 5. Commit Changes
Make atomic commits with clear messages:
```bash
git add .
git commit -m "Add feature: descriptive name"
```
### 6. Prepare for Release
When the feature is ready to be released:
1. Create a version branch for the release:
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
2. Merge your feature branch into the version branch:
```bash
git merge feature/descriptive-name --no-ff
```
3. Update version numbers and changelog entries
4. Follow the standard release process from this point
### 7. Push to Remote (Optional for Collaboration)
If you need to collaborate with others on the feature before it's ready for release:
```bash
git push github HEAD:feature/descriptive-name
git push gitea HEAD:feature/descriptive-name
```
### 8. Create Pull Request (Optional)
If the repository uses pull requests for code review, create a pull request from the feature branch to the version branch.
## Code Standards and Best Practices
### PHP Coding Standards
- Follow [WordPress PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
- Use tabs for indentation, not spaces
- Use proper naming conventions:
- Class names: `Class_Name`
- Function names: `function_name`
- Variable names: `$variable_name`
### JavaScript Coding Standards
- Follow [WordPress JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
- Use tabs for indentation, not spaces
- Use proper naming conventions:
- Function names: `functionName`
- Variable names: `variableName`
### Internationalization (i18n)
- Wrap all user-facing strings in appropriate translation functions:
- `__()` for simple strings
- `_e()` for echoed strings
- `esc_html__()` for escaped strings
- `esc_html_e()` for escaped and echoed strings
- Always use the plugin's text domain: `fix-plugin-does-not-exist-notices`
### Security Best Practices
- Validate and sanitize all input
- Escape all output
- Use nonces for form submissions
- Use capability checks for user actions
## Feature Types and Implementation Guidelines
### Admin Interface Features
When adding features to the admin interface:
- Use WordPress admin UI components for consistency
- Follow WordPress admin UI patterns
- Ensure accessibility compliance
- Add appropriate help text
### Plugin Functionality Features
When adding core functionality:
- Ensure compatibility with WordPress hooks system
- Consider performance impact
- Maintain backward compatibility
- Add appropriate error handling
### Integration Features
When adding integration with other plugins or services:
- Make integrations optional when possible
- Check if the integrated plugin/service is available before using it
- Provide fallback functionality when the integration is not available
- Document the integration requirements
-19
View File
@@ -1,19 +0,0 @@
# Local Development Environment Variables
This file contains important paths and URLs for local development.
## Repository Paths
- Local development repository: ~/Git/wp-fix-plugin-does-not-exist-notices
- LocalWP plugin testing site storage: ~/Local/plugin-testing/app/wp-fix-plugin-does-not-exist-notices
- LocalWP plugin testing site configuration: ~/Local/plugin-testing/conf/
## URLs
- LocalWP plugin testing URL: http://plugin-testing.local/
- PHP details: http://plugin-testing.local/local-phpinfo.php
- XDebug info: http://plugin-testing.local/local-xdebuginfo.php
- Adminer Evo: http://localhost:10010/?username=root&db=local
- Mailpit: http://localhost:10000/
## Build and Deploy Scripts
- Build script: ~/Git/wp-fix-plugin-does-not-exist-notices/build.sh
- Local deploy script: ~/Git/wp-fix-plugin-does-not-exist-notices/deploy-local.sh
-228
View File
@@ -1,228 +0,0 @@
# Release Process for AI Assistants
This document provides step-by-step instructions for AI assistants to help with the release process for the Fix Plugin Does Not Exist Notices plugin.
## Pre-Release Checklist
- [ ] All features for this release are complete
- [ ] All bug fixes for this release are complete
- [ ] CHANGELOG.md is up to date
- [ ] readme.txt is up to date
- [ ] All tests pass
## Determining the New Version Number
Based on the changes made, determine the appropriate version increment:
1. **PATCH** (e.g., 1.6.0 → 1.6.1): For bug fixes and minor improvements
- **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
2. **MINOR** (e.g., 1.6.0 → 1.7.0): For new features and significant improvements
3. **MAJOR** (e.g., 1.6.0 → 2.0.0): For breaking changes
## Release Steps
### 1. Create a New Branch
```bash
git checkout -b v{MAJOR}.{MINOR}.{PATCH}
```
Example:
```bash
git checkout -b v1.7.0
```
### 2. Update Version Numbers
Update the version number in the following files:
#### a. Main Plugin File (wp-fix-plugin-does-not-exist-notices.php)
```php
/**
* Plugin Name: Fix 'Plugin file does not exist.' Notices
* Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: {MAJOR}.{MINOR}.{PATCH}
* ...
*/
```
Also update the FPDEN_VERSION constant:
```php
define( 'FPDEN_VERSION', '{MAJOR}.{MINOR}.{PATCH}' );
```
#### b. CHANGELOG.md
Add a new section at the top of the CHANGELOG.md file:
```markdown
## [{MAJOR}.{MINOR}.{PATCH}] - YYYY-MM-DD
### Added
- New feature 1
- New feature 2
### Changed
- Change 1
- Change 2
### Fixed
- Bug fix 1
- Bug fix 2
```
#### c. POT File (languages/wp-fix-plugin-does-not-exist-notices.pot)
Update the Project-Id-Version and POT-Creation-Date (IMPORTANT - don't forget this step!):
```
"Project-Id-Version: Fix 'Plugin file does not exist' Notices {MAJOR}.{MINOR}.{PATCH}\n"
"POT-Creation-Date: YYYY-MM-DDT00:00:00+00:00\n"
```
Note: Always use the current date for POT-Creation-Date in the format YYYY-MM-DD.
#### d. readme.txt
Update the stable tag:
```
Stable tag: {MAJOR}.{MINOR}.{PATCH}
```
Add a new entry to the changelog section:
```
= {MAJOR}.{MINOR}.{PATCH} =
* New feature 1
* New feature 2
* Change 1
* Change 2
* Fixed bug 1
* Fixed bug 2
```
Update the upgrade notice section:
```
= {MAJOR}.{MINOR}.{PATCH} =
Brief description of the most important changes in this release
```
### 3. Commit Changes
```bash
git add wp-fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt README.md languages/wp-fix-plugin-does-not-exist-notices.pot
git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"
```
### 4. Test Changes Locally
Test the changes thoroughly on the version branch to ensure everything works as expected:
- Test with the latest WordPress version
- Test with PHP 7.0+ (minimum supported version)
- Verify all features work as expected
- Check for any PHP warnings or notices
### 5. Merge to Main
When satisfied with testing, merge the version branch to main:
```bash
git checkout main
git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
```
The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
### 6. Push Main to Remotes
```bash
git push github main
git push gitea main
```
### 7. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
```
### 8. Monitor GitHub Actions
Open the GitHub Actions page to monitor the build and deployment process:
https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/actions
### 9. Verify Release
- [ ] Check that the GitHub release was created successfully
- [ ] Verify that the plugin was deployed to WordPress.org
- [ ] Test the plugin from WordPress.org to ensure it works correctly
## Testing Previous Versions
To test a previous version of the plugin:
```bash
# Checkout a specific tag for testing
git checkout v{MAJOR}.{MINOR}.{PATCH}
# Or create a test branch from a specific tag
git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
```
## Rollback Procedure (If Needed)
If issues are discovered after release:
### 1. Create a Hotfix Branch
```bash
git checkout v{MAJOR}.{MINOR}.{PATCH}
git checkout -b hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 2. Fix the Issues
Make the necessary changes to fix the issues.
### 3. Update Version Numbers
Increment the PATCH version and update all version numbers as described above.
### 4. Test the Hotfix
Test the hotfix thoroughly to ensure it resolves the issue without introducing new problems.
### 5. Commit Changes
```bash
git add .
git commit -m "Fix issues in v{MAJOR}.{MINOR}.{PATCH}"
```
### 6. Merge to Main
```bash
git checkout main
git merge hotfix/v{MAJOR}.{MINOR}.{PATCH+1} --no-ff
git push github main
git push gitea main
```
### 7. Create and Push Tag
```bash
git tag -a v{MAJOR}.{MINOR}.{PATCH+1} -m "Hotfix release version {MAJOR}.{MINOR}.{PATCH+1}"
git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
```
### 8. Monitor and Verify
Follow steps 8 and 9 from the release process to monitor and verify the hotfix release.
-19
View File
@@ -1,19 +0,0 @@
{
"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
View File
@@ -1,8 +0,0 @@
# 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
View File
@@ -1,8 +0,0 @@
# 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
View File
@@ -1,8 +0,0 @@
{
"_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
View File
@@ -1,8 +0,0 @@
# 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
View File
@@ -1,8 +0,0 @@
{
"_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
View File
@@ -1,8 +0,0 @@
# 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/
+1 -5
View File
@@ -1,7 +1,3 @@
# 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
@@ -52,4 +48,4 @@ Thumbs.db
*.tmp
*.zip
*~
._*
._*
+12 -12
View File
@@ -14,16 +14,16 @@ steps:
commands:
- apk add --no-cache bash zip
- VERSION=${DRONE_TAG#v}
- mkdir -p build/wp-fix-plugin-does-not-exist-notices
- cp wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
- cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
- cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
- cp README.md build/wp-fix-plugin-does-not-exist-notices/
- cp CHANGELOG.md build/wp-fix-plugin-does-not-exist-notices/
- 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/
- cd build
- zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
- zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
- cd ..
- name: release
image: plugins/gitea-release
settings:
@@ -31,9 +31,9 @@ steps:
from_secret: gitea_token
base_url: https://gitea.wpallstars.com
files:
- wp-fix-plugin-does-not-exist-notices-*.zip
- plugin-reference-cleaner-*.zip
title: Release ${DRONE_TAG}
note: |
Fix 'Plugin file does not exist.' Notices ${DRONE_TAG}
See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details.
Plugin Reference Cleaner ${DRONE_TAG}
See [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/plugin-reference-cleaner/src/branch/main/CHANGELOG.md) for details.
-8
View File
@@ -1,8 +0,0 @@
# 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/
+13 -82
View File
@@ -1,101 +1,32 @@
# This file configures how Git handles line endings and file types
# It is independent from .gitignore which controls which files are tracked
# Auto detect text files and perform LF normalization
* text=auto
# Text files that should be normalized with LF line endings
*.php text eol=lf
*.css text eol=lf
*.js text eol=lf
*.scss text eol=lf
*.htm text eol=lf
*.html text eol=lf
*.xml text eol=lf
*.txt text eol=lf
*.ini text eol=lf
*.inc text eol=lf
*.md text eol=lf
*.json text eol=lf
*.yml text eol=lf
*.yaml text eol=lf
*.po text eol=lf
*.pot text eol=lf
*.svg text eol=lf
.htaccess text eol=lf
# Text files that should be normalized
*.php text
*.css text
*.js text
*.htm text
*.html text
*.xml text
*.txt text
*.ini text
*.inc text
*.md text
.htaccess text
# Files that should be treated as binary
*.png binary
*.jpg binary
*.jpeg binary
*.gif binary
*.ico binary
*.webp binary
*.zip binary
*.gz binary
*.tar binary
*.ttf binary
*.eot binary
*.woff binary
*.woff2 binary
*.pxd binary
*.afdesign binary
*.afphoto binary
*.afpub binary
# Exclude files from export (for WordPress.org SVN and distribution packages)
.gitattributes export-ignore
.gitignore export-ignore
.github export-ignore
.wordpress-org export-ignore
README.md export-ignore
CHANGELOG.md export-ignore
composer.json export-ignore
composer.lock export-ignore
package.json export-ignore
package-lock.json export-ignore
phpcs.xml export-ignore
.phpcs.xml export-ignore
phpunit.xml export-ignore
.phpunit.xml export-ignore
.distignore export-ignore
.editorconfig export-ignore
.eslintrc export-ignore
.eslintignore export-ignore
.prettierrc export-ignore
.prettierignore export-ignore
.stylelintrc export-ignore
.stylelintignore export-ignore
.travis.yml export-ignore
.gitlab-ci.yml export-ignore
bitbucket-pipelines.yml export-ignore
bin export-ignore
tests export-ignore
assets/icon/*.svg export-ignore
assets/banner/*.svg export-ignore
assets/screenshots/*.pxd export-ignore
assets/icon/*.pxd export-ignore
assets/banner/*.pxd export-ignore
# AI assistant and workflow files
.ai-assistant.md export-ignore
.ai-workflows export-ignore
.augmentignore export-ignore
.cursorignore export-ignore
.v0ignore export-ignore
.clinerc export-ignore
.continuerc export-ignore
reference-plugins export-ignore
# Set the default behavior for GitHub language detection
*.css linguist-language=CSS
*.js linguist-language=JavaScript
*.php linguist-language=PHP
*.scss linguist-language=SCSS
*.pot linguist-language=Gettext Catalog
*.po linguist-language=Gettext Catalog
*.mo linguist-language=Gettext Catalog
# Merge driver for changelog files to prevent conflicts
CHANGELOG.md merge=union
readme.txt merge=union
*.php linguist-language=PHP
+3 -2
View File
@@ -6,6 +6,7 @@ on:
- main
paths:
- '.wordpress-org/**'
- 'assets/**'
jobs:
assets:
@@ -14,10 +15,10 @@ jobs:
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: WordPress.org plugin asset/readme update
uses: 10up/action-wordpress-plugin-asset-update@stable
env:
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SLUG: wp-fix-plugin-does-not-exist-notices
SLUG: fix-plugin-does-not-exist-notices
+10 -10
View File
@@ -20,20 +20,20 @@ jobs:
run: echo "VERSION=${GITHUB_REF#refs/tags/v}" >> $GITHUB_OUTPUT
- name: Create build directory
run: mkdir -p build/wp-fix-plugin-does-not-exist-notices
run: mkdir -p build/fix-plugin-does-not-exist-notices
- name: Copy plugin files
run: |
cp wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
cp README.md build/wp-fix-plugin-does-not-exist-notices/
cp -r assets build/wp-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 -r assets build/fix-plugin-does-not-exist-notices/
- name: Create ZIP file
run: |
cd build
zip -r ../wp-fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip wp-fix-plugin-does-not-exist-notices
zip -r ../fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip fix-plugin-does-not-exist-notices
- name: Create Release
id: create_release
@@ -43,11 +43,11 @@ jobs:
draft: false
prerelease: false
files: |
wp-fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip
fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip
body: |
Fix 'Plugin file does not exist.' Notices v${{ steps.get_version.outputs.VERSION }}
See [CHANGELOG.md](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/blob/main/CHANGELOG.md) for details.
See [CHANGELOG.md](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/blob/main/CHANGELOG.md) for details.
# Deploy to WordPress.org
wordpress:
@@ -66,4 +66,4 @@ jobs:
env:
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SLUG: wp-fix-plugin-does-not-exist-notices
SLUG: fix-plugin-does-not-exist-notices
+4 -93
View File
@@ -45,9 +45,6 @@ wp-content/backup-db/
wp-content/cache/
wp-content/backups/
# Reference plugins
reference-plugins/
# Log files
*.log
error_log
@@ -58,106 +55,20 @@ 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/ # Needed for GitHub Actions
.github/
.gitlab/
# .gitattributes # Needed for file handling
.gitattributes
.travis.yml
# .drone.yml # Needed for Drone CI
# .woodpecker.yml # Needed for Woodpecker CI
.drone.yml
.woodpecker.yml
codecov.yml
.babelrc
.browserslistrc
-8
View File
@@ -1,8 +0,0 @@
{
"_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
View File
@@ -1,8 +0,0 @@
# 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
View File
@@ -1,8 +0,0 @@
# 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
View File
@@ -1,8 +0,0 @@
# 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/
+13 -13
View File
@@ -9,28 +9,28 @@ steps:
commands:
- apk add --no-cache bash zip
- VERSION=${CI_COMMIT_TAG#v}
- mkdir -p build/wp-fix-plugin-does-not-exist-notices
- cp wp-fix-plugin-does-not-exist-notices.php build/wp-fix-plugin-does-not-exist-notices/
- cp readme.txt build/wp-fix-plugin-does-not-exist-notices/
- cp LICENSE build/wp-fix-plugin-does-not-exist-notices/
- cp README.md build/wp-fix-plugin-does-not-exist-notices/
- if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/wp-fix-plugin-does-not-exist-notices/; fi
- 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
- cd build
- zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
- zip -r ../plugin-reference-cleaner-$VERSION.zip plugin-reference-cleaner
- cd ..
- echo "Build completed - wp-fix-plugin-does-not-exist-notices-$VERSION.zip"
- echo "Build completed - plugin-reference-cleaner-$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: wp-fix-plugin-does-not-exist-notices-*.zip
PLUGIN_FILES: plugin-reference-cleaner-*.zip
PLUGIN_TITLE: "Release ${CI_COMMIT_TAG}"
PLUGIN_NOTE: "Fix 'Plugin file does not exist.' Notices ${CI_COMMIT_TAG}\n\nSee [CHANGELOG.md](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details."
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."
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]
+8 -53
View File
@@ -2,24 +2,14 @@
This directory contains assets specific to the WordPress.org plugin repository and is used for automatic deployment via GitHub Actions.
## Directory Structure
## Directory Contents
```
/.wordpress-org/
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
```
## Asset Organization
- **All Asset Files**: All files for WordPress.org are stored in this directory (`.wordpress-org/assets/`)
- PNG files (icon-256x256.png, banner-772x250.png, etc.)
- Source files (PXD, SVG)
- Documentation
- `icon.svg` - Plugin icon displayed in the WordPress.org plugin directory
- `banner-772x250.png` - Standard banner for plugin header
- `banner-1544x500.png` - Retina banner for plugin header
- `screenshot-1.png` - First screenshot displayed on plugin page
- `screenshot-2.png` - Second screenshot displayed on plugin page
- `screenshot-3.png` - Third screenshot displayed on plugin page
## Purpose
@@ -27,39 +17,4 @@ When using GitHub Actions for WordPress.org plugin deployments (via the 10up Wor
## Naming Conventions
Files must be named exactly as shown above to be properly recognized by the WordPress.org system during the deployment process:
### Banner Images
- `banner-772x250.png` - 772x250 pixel PNG banner (required for WordPress.org)
- `banner-1544x500.png` - 1544x500 pixel PNG banner for high-DPI displays (optional for WordPress.org)
### Icon Images
- `icon-256x256.png` - 256x256 pixel PNG icon (required for WordPress.org)
- `icon-128x128.png` - 128x128 pixel PNG icon (optional for WordPress.org)
### Screenshots
- `screenshot-1.png` - Main screenshot showing the plugin in action
## Right-to-Left (RTL) Support
For plugins that support Right-to-Left languages (like Hebrew and Arabic), you can provide RTL versions of assets by appending `-rtl` to the filename:
- `banner-772x250-rtl.png`
- `banner-1544x500-rtl.png`
- `icon-256x256-rtl.png`
Note that the `-rtl` suffix is specifically for Right-to-Left language support, not for dark mode versions of assets.
## Build Process
The build script (`build.sh`) is configured to:
1. Use all asset files from the `.wordpress-org/assets/` directory
2. Copy these files to the appropriate locations in the build directory
## Additional Resources
For more detailed information about WordPress.org plugin assets, please see:
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
- [WordPress.org Plugin Submission Assets Guide](./.wordpress-org/WORDPRESS_ORG_ASSETS.md)
Files must be named exactly as shown above to be properly recognized by the WordPress.org system during the deployment process.
-125
View File
@@ -1,125 +0,0 @@
# 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 `.wordpress-org/assets/`
### Banner
- **Format**: PNG
- **Sizes**:
- Required: 772x250 pixels (`banner-772x250.png`)
- Optional: 1544x500 pixels (`banner-1544x500.png`) for high-DPI displays
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `.wordpress-org/assets/`
### Screenshots
- **Format**: PNG
- **Naming**: `screenshot-1.png`
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `.wordpress-org/assets/`
## Submission Process
1. **Prepare Plugin Files**:
- Ensure all plugin files are ready in your local repository
- Make sure version numbers are consistent across all files
2. **Prepare Assets**:
- Ensure all assets follow the naming conventions above
- Verify that screenshots match the descriptions in readme.txt
3. **Upload to WordPress.org**:
- When you receive SVN access, use these commands:
```bash
# Check out the repository
svn checkout https://plugins.svn.wordpress.org/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 .wordpress-org/assets/icon-256x256.png fix-plugin-does-not-exist-notices/assets/
cp .wordpress-org/assets/icon-128x128.png fix-plugin-does-not-exist-notices/assets/
cp .wordpress-org/assets/banner-772x250.png fix-plugin-does-not-exist-notices/assets/
cp .wordpress-org/assets/banner-1544x500.png fix-plugin-does-not-exist-notices/assets/
cp .wordpress-org/assets/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 .wordpress-org/assets/icon.svg .wordpress-org/assets/icon-256x256.png
# For 128x128 icon
convert -background none -size 128x128 .wordpress-org/assets/icon.svg .wordpress-org/assets/icon-128x128.png
```
## Resources
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
@@ -1,81 +0,0 @@
# WordPress.org Plugin Submission Assets Guide
This document outlines the requirements for assets when submitting a plugin to the WordPress.org plugin repository.
## Asset Requirements
### Icon
- **Format**: PNG
- **Size**: 256x256 pixels
- **Filename**: `icon-256x256.png`
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Optional**: You can also include `icon-128x128.png` for backward compatibility
### Banner
- **Format**: PNG
- **Sizes**:
- Regular: 772x250 pixels (`banner-772x250.png`)
- High-DPI: 1544x500 pixels (`banner-1544x500.png`)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
### Screenshots
- **Format**: PNG
- **Naming**: Sequential numbers (`screenshot-1.png`, `screenshot-2.png`, etc.)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Important**: The number and order must match the descriptions in the `readme.txt` file
## Current Status
### Icon
- ✅ SVG source available in `.wordpress-org/assets/icon.svg`
- ✅ PNG files created in `.wordpress-org/assets/icon-256x256.png` and `.wordpress-org/assets/icon-128x128.png`
### Banner
- ✅ Both sizes available in `.wordpress-org/assets/`
- ✅ Properly named files: `banner-772x250.png` and `banner-1544x500.png`
### Screenshots
- ✅ One screenshot available in `.wordpress-org/assets/screenshot-1.png`
- ✅ Screenshot description in readme.txt updated to reference only one screenshot
## SVN Directory Structure
When submitting to WordPress.org, your SVN repository will have this structure:
```
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
/tags/
/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 .wordpress-org/assets/icon-256x256.png /path/to/wordpress-svn/assets/
cp .wordpress-org/assets/icon-128x128.png /path/to/wordpress-svn/assets/
cp .wordpress-org/assets/banner-772x250.png /path/to/wordpress-svn/assets/
cp .wordpress-org/assets/banner-1544x500.png /path/to/wordpress-svn/assets/
cp .wordpress-org/assets/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/)
Binary file not shown.

Before

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.7 KiB

File diff suppressed because one or more lines are too long

Before

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 392 KiB

+42 -370
View File
@@ -1,456 +1,128 @@
All notable changes to this project should be documented both here and in the main Readme files.
# Changelog
#### [2.2.0] - 2025-04-14
#### Added
- Completely refactored plugin to use OOP best practices
- New class structure with proper namespaces
- Improved code organization and maintainability
- Better separation of concerns with dedicated classes
All notable changes to this project will be documented in this file.
#### Changed
- Changed "Choose Update Source" link to just "Update Source"
- Fixed close button in the update source modal
- Added links to the main page for each update source in the modal
- Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
#### [2.1.1] - 2025-04-13
#### Added
- New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
- Modal dialog with detailed information about each update source option
- Visual indicator showing the currently selected update source
#### Fixed
- Updated heading styles in CHANGELOG.md for better readability
- Corrected dates in changelog to use 2025 instead of 2024
#### Improved
- Documentation improvements for better clarity
- Enhanced Git Updater integration with user-selectable update sources
#### [2.1.0] - 2025-04-13
#### Changed
- Minor version bump for Git Updater compatibility
#### Improved
- Error handling for Git Updater integration
- Type checking in branch fix functions
- Documentation for Git Updater installation and cache refreshing
#### [2.0.13] - 2025-04-12
#### Fixed
- Critical error when Git Updater passes an object instead of a string to API URL filter
- Type checking in branch fix functions to handle both string and object inputs
#### Improved
- Error handling for Git Updater integration
- Documentation for Git Updater installation and cache refreshing
#### [2.0.12] - 2025-04-11
#### Fixed
- Integrated Git Updater branch fix directly into main plugin
- Removed separate "GU Branch Fix" plugin (no longer needed)
#### Added
- Documentation explaining branch fix integration
#### Improved
- Compatibility with Git Updater plugin
- Deploy script to remove separate branch fix plugin
#### [2.0.11] - 2025-04-10
#### Added
- Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
- Added deploy script for local testing
#### Fixed
- Git Updater branch issues with 'main' vs 'master' branch names
- Improved compatibility with Git Updater plugin
#### [2.0.10] - 2025-04-09
#### Fixed
- Plugin details popup version display issue with Git Updater integration
- Added JavaScript-based solution to ensure correct version display in plugin details
#### Improved
- Version consistency across all plugin views
- Enhanced cache busting for plugin information API
#### [2.0.9] - 2025-04-08
#### Fixed
- Plugin details popup now correctly shows version and author information
- Added support for both old and new plugin slugs to fix caching issues
#### Improved
- Cache clearing mechanism to ensure plugin details are always up-to-date
- Enhanced version display in plugin details popup
#### [2.0.8] - 2025-04-07
#### Fixed
- Plugin details popup now correctly shows version and author information
- Added cache-busting mechanism to ensure plugin details are always up-to-date
#### Improved
- Author and contributor information display in plugin details
- Added WordPress 6.5 compatibility indicator
#### [2.0.7] - 2025-04-06
#### Changed
- Additional text improvements and minor fixes
#### [2.0.6] - 2025-04-05
#### Changed
- Text improvements and minor fixes
#### [2.0.5] - 2025-04-04
#### Fixed
- Display correct version in plugin details popup
#### [2.0.4] - 2025-04-03
#### Fixed
- Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
#### [2.0.2] - 2025-04-02
#### Changed
- Consolidated WordPress.org assets into .wordpress-org directory
- Improved organization of assets for WordPress.org submission
- Updated .wordpress-org/README.md with comprehensive information
#### [2.0.1] - 2025-04-01
#### Added
- Contributing section to readme.txt
- reference-plugins directory for plugin development inspiration
#### Changed
- Updated "tested up to" version to WordPress 6.7.2
- Improved .gitattributes with comprehensive file handling
- Enhanced documentation organization
#### [2.0.0] - 2025-03-31
#### Added
- Note clarifying that the plugin has no settings page
- Clarification that functionality is limited to the admin plugins page only
#### Changed
- Major version release for WordPress.org submission
- Finalized all assets and documentation for public release
#### [1.6.28] - 2025-03-30
#### Changed
- Consolidated asset documentation into a single comprehensive guide
- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
- Updated all asset README files to point to the main documentation
- Improved file organization and documentation structure
#### [1.6.27] - 2025-03-29
#### Changed
- Clarified RTL support in WordPress.org asset documentation
- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
- Consolidated asset files and improved documentation
#### [1.6.26] - 2025-03-28
#### Changed
- Updated screenshot references to use a single comprehensive screenshot
- Fixed asset directory paths in documentation
- Improved ImageMagick conversion commands for icon generation
- Clarified WordPress.org SVN repository structure
#### [1.6.25] - 2025-03-27
#### Added
- Comprehensive WordPress.org submission guide with SVN structure explanation
#### Changed
- Consolidated asset files into their respective directories
- Clarified asset requirements and submission process
- Improved organization of asset files
#### [1.6.24] - 2025-03-26
#### Added
- Properly named icon PNG files (icon-256x256.png and icon-128x128.png)
#### Changed
- Updated asset preparation documentation
- Improved WordPress.org submission readiness
#### [1.6.23] - 2025-03-25
#### Added
- Properly named icon, banner, and screenshot files for WordPress.org submission
- Comprehensive guide for WordPress.org asset requirements
#### Changed
- Fixed file naming to comply with WordPress.org standards
- Organized assets in separate directories for better management
#### [1.6.22] - 2025-03-24
#### Changed
- Enhanced support section with multiple support channel options
- Added encouragement for users to leave reviews on WordPress.org
- Improved documentation with clearer support instructions
#### [1.6.21] - 2025-03-23
#### Added
- Support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
- Links to supported AI IDEs in documentation
- Additional FAQs for better SEO
#### Changed
- Updated AI configuration files with modern models (gpt-4o)
- Made documentation more generic for boilerplate use
- Enhanced explanations in configuration files
- Added more keywords for better SEO
#### [1.6.20] - 2025-03-22
#### Changed
- Added explanations about the ! prefix in ignore files
- Moved WordPress-specific patterns to .gitignore
- Further improved organization of ignore patterns
- Added examples of how to include files excluded by .gitignore
#### [1.6.19] - 2025-03-21
#### Changed
- Consolidated common ignore patterns into .gitignore
- Simplified AI IDE configuration files to only include tool-specific patterns
- Improved organization of ignore patterns for better maintainability
- Added more file types to .gitignore for comprehensive coverage
#### [1.6.18] - 2025-03-20
#### Changed
- Optimized AI IDE configuration files to only include patterns not in .gitignore
- Improved efficiency of ignore files for better AI context management
- Enhanced compatibility with various AI-powered development tools
#### [1.6.17] - 2025-03-19
#### Added
- .augmentignore file with best practices
- Configuration files for Cursor, Windsurf, v0, and Cline IDEs
- More design file formats to .gitignore
- .aiconfig file for general AI IDE compatibility
#### [1.6.16] - 2025-03-18
#### Fixed
- Updated CI configuration files with correct plugin slugs
- Updated CHANGELOG.md with all recent versions
- Fixed outdated references to plugin-reference-cleaner
#### [1.6.15] - 2025-03-17
#### Changed
- Moved AI workflow documentation to root directory for better visibility
- Consolidated duplicate workflow files
- Improved organization of development documentation
- Updated CI configuration files with correct plugin slugs
#### [1.6.14] - 2025-03-16
#### Changed
- Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
- Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
- Improved explanation of how the plugin works
- Ensured consistent terminology across all documentation
#### [1.6.13] - 2025-03-15
#### Changed
- Code cleanup and optimization
- Improved Git Updater integration
- Fixed author display in plugin information
- Ensured compatibility with WordPress 6.4
#### [1.6.12] - 2025-03-14
#### Added
- Added WPALLSTARS as a co-author
- Updated author information and links
- Added author websites to plugin description
- Fixed issue with multiple author URLs
#### [1.6.11] - 2025-03-13
#### Fixed
- Improved Git Updater integration
- Fixed plugin header information
- Updated author information
#### [1.6.10] - 2025-03-12
#### Fixed
- Corrected plugin header information
- Improved Git Updater compatibility
- Updated documentation
#### [1.6.9] - 2025-03-11
#### Fixed
- Fixed Git Updater integration
- Updated plugin header information
- Improved documentation
#### [1.6.8] - 2025-03-10
#### Fixed
- Fixed Git Updater integration
- Updated plugin header information
#### [1.6.7] - 2025-03-09
#### Fixed
- Fixed Git Updater integration
- Updated plugin header information
#### [1.6.6] - 2025-03-08
#### Fixed
- Fixed Git Updater integration
- Updated plugin header information
#### [1.6.5] - 2025-03-07
#### Fixed
- Fixed Git Updater integration
- Updated plugin header information
#### [1.6.4] - 2025-03-06
#### Improved
- Version management to ensure consistent patch version increments
- Documentation for version update process
- AI workflow files with detailed version increment instructions
#### [1.6.3] - 2025-03-05
#### Fixed
- Git Updater repository URLs to use full repository paths
- Update URI configuration for proper update detection
- Version management following semantic versioning
#### Changed
- Updated organization name from 'WP All Stars' to 'WPALLSTARS'
- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
#### [1.6.2] - 2025-03-04
#### Changed
- Updated POT file version for consistency
- Improved JavaScript localization with proper fallbacks
- Enhanced code quality for WordPress.org submission
#### Added
- Git Updater configuration with Update URI
- Update server URL configuration
#### [1.6.1] - 2025-03-03
#### Added
- AI assistant guide and workflow documentation
- Detailed release process documentation
- Feature development guidelines
- Bug fixing procedures
- Code review standards
#### [1.6.0] - 2025-03-02
#### Added
## [1.6.0] - 2024-05-15
### Added
- Full translation support with POT file
- JavaScript localization for better multilingual support
- Plugin constants for improved code organization
- Git Updater support for updates from GitHub and Gitea
#### Changed
### Changed
- Updated code to follow WordPress internationalization best practices
- Improved asset loading with version constants
- Smart update detection based on installation source
#### [1.5.0] - 2025-03-01
#### Added
## [1.5.0] - 2024-05-15
### Added
- Improved compatibility with WordPress 6.4
- Enhanced error detection for plugin references
#### Fixed
### Fixed
- Minor UI improvements for better visibility
- Accessibility enhancements for screen readers
#### [1.4.1] - 2025-02-28
#### Added
## [1.4.1] - 2023-11-30
### Added
- FAQ about keeping the plugin installed after notices are cleared
#### [1.4.0] - 2025-02-27
#### Changed
## [1.4.0] - 2023-11-30
### Changed
- Updated plugin name and text domain
- Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
#### [1.3.3] - 2025-02-26
#### Added
## [1.3.3] - 2023-10-05
### Added
- "Click here to scroll" button to automatically find missing plugins
- Visual arrow pointing from notification to error message
- Smooth scrolling with highlighting of missing plugin rows
#### Improved
### Improved
- Notification reliability using multiple injection methods
- Earlier placement in page load cycle for better visibility
- Enhanced error detection for all WordPress error message formats
#### [1.3.2] - 2025-02-25
#### Added
## [1.3.2] - 2023-10-05
### Added
- Prominent notification that appears directly below WordPress error messages
- Visual styling to help users connect error message with solution
- Direction arrows and highlighted text to improve user guidance
#### [1.3.1] - 2025-02-24
#### Added
## [1.3.1] - 2023-10-05
### Added
- Instructional notification explaining how to use the plugin
- Step-by-step guidance for removing plugin references
- Clear visual indicators for missing plugins
#### [1.3.0] - 2025-02-23
#### Changed
## [1.3.0] - 2023-10-05
### Changed
- Complete redesign for maximum compatibility with all WordPress themes
- Now uses the plugins list table for missing plugin references
- Uses standard WordPress admin UI patterns and hooks
#### Added
### Added
- Missing plugins now appear directly in the plugins list
- "Remove Reference" action link in the plugins list
- Success/error notices after removing references
#### Fixed
### Fixed
- Compatibility issues with various WordPress admin themes
- Reliability issues with notification detection
#### [1.2.4] - 2025-02-22
#### Fixed
## [1.2.4] - 2023-10-05
### Fixed
- Compatibility with more WordPress admin UI variations
- Specific targeting for admin notices in various themes
#### Added
### Added
- Advanced DOM traversal using TreeWalker API
- Multiple fallback approaches to ensure button appears
- Enhanced console logging for troubleshooting
#### [1.2.3] - 2025-02-21
#### Fixed
## [1.2.3] - 2023-10-05
### Fixed
- Button not appearing in some WordPress admin themes
- Error message detection for greater theme compatibility
#### Improved
### Improved
- DOM traversal to find notification elements in various themes
- Added console logging for troubleshooting
#### [1.2.2] - 2025-02-20
#### Fixed
## [1.2.2] - 2023-10-05
### Fixed
- Timeout issue during plugin activation
- Potential infinite recursion in admin notices handling
#### Improved
### Improved
- Hook management to prevent performance issues
- Optimized by only loading on plugins page
#### [1.2.1] - 2025-04-07
#### Improved
## [1.2.1] - 2025-04-07
### Improved
- Fixed typos in documentation
- Improved text clarity
- Added question mark to first sentence for better readability
#### [1.2] - 2025-04-07
#### Added
## [1.2] - 2025-04-07
### Added
- Improved documentation with detailed explanation
- Added SQL reference for technical users
- Suggested potential inclusion in WordPress core
#### [1.1] - 2025-04-07
#### Added
## [1.1] - 2025-04-07
### Added
- Support for multisite WordPress installations
- Network admin page integration
- Woodpecker CI integration for automated releases
#### Improved
### Improved
- Error handling
- User experience with better confirmation messages
- Security by adding proper capability checks
#### [1.0] - 2025-03-15
#### Added
## [1.0] - 2025-03-15
### Added
- Initial release
- "Remove Reference" button for plugin deactivation error notices
- AJAX processing for reference removal
+41 -379
View File
@@ -1,8 +1,8 @@
# Fix 'Plugin file does not exist.' Notices
[![WordPress Plugin Version](https://img.shields.io/wordpress/plugin/v/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Rating](https://img.shields.io/wordpress/plugin/rating/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Downloads](https://img.shields.io/wordpress/plugin/dt/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Version](https://img.shields.io/wordpress/plugin/v/fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Rating](https://img.shields.io/wordpress/plugin/rating/fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Downloads](https://img.shields.io/wordpress/plugin/dt/fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/)
[![License](https://img.shields.io/badge/license-GPL--2.0%2B-blue.svg)](https://www.gnu.org/licenses/gpl-2.0.html)
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
@@ -13,19 +13,16 @@ 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 Notice" link, allowing you to safely clean up invalid plugin entries with one click.
**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
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.
### Key Features
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Notice" action link
* Provides a simple "Remove Reference" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
* Clean, user-friendly interface following WordPress design patterns
* Integrated Git Updater branch fix (changes 'master' to 'main' for proper updates)
### How It Works
@@ -33,10 +30,8 @@ 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 Notice" link to safely remove them
3. Provides a "Remove Reference" 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
@@ -64,34 +59,9 @@ 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 Notice" link next to any missing plugin
3. Click the "Remove Reference" link next to any missing plugin
4. The reference will be removed, and the error notification will disappear
### Using with Git Updater
If you've installed this plugin from GitHub or Gitea, you'll need Git Updater to receive updates:
1. Install the Git Updater plugin from [git-updater.com/git-updater/](https://git-updater.com/git-updater/)
2. Go to Settings > Git Updater > Remote Management
3. Click the "Refresh Cache" button to ensure Git Updater recognizes the latest version
4. Updates will now appear in your WordPress dashboard when available
### Choosing Your Update Source
This plugin allows you to choose where you want to receive updates from:
1. In the Plugins list, find "Fix 'Plugin file does not exist' Notices"
2. Click the "Choose Update Source" link next to the plugin
3. Select your preferred update source:
- **WordPress.org**: Updates from the official WordPress.org repository (has a version update delay due to the WP.org policy review and approval process, best for unmonitored auto-updates)
- **GitHub**: Updates directly from the GitHub repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates where the latest features and fixes are needed immediately)
- **Gitea**: Updates directly from the Gitea repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates and independence from big-tech)
4. Click "Save" to apply your preference
> **Note:** If no preference is set, the plugin will automatically use the source it was installed from.
> **Note:** GitHub and Gitea options require the Git Updater plugin to be installed and activated.
## Frequently Asked Questions
### Is it safe to remove plugin references?
@@ -108,7 +78,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 Notice" 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 Reference" 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?
@@ -122,61 +92,17 @@ 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. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
## Support
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
## Reviews
This utility plugin is released under the GPLv2 license as free open source software.
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org.
Your experience and feedback helps others discover the plugin, and encourages continued community-driven, open-source development and support.
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
## Developers
### Contributing
Contributions are welcome! Please follow these steps to set up a development environment:
1. Install [LocalWP](https://localwp.com/) and create a clean site called "Plugin Testing" using the "Preferred" setup option
2. Run "Site shell" once from the LocalWP page on the site's settings to ensure wp-cli is enabled
3. Run "Add Run Configurations to VS Code" to update site configuration files in: ~/Local/plugin-testing/conf/
4. Clone this repository to your local machine, in `~/Git/` or wherever you keep your Git repositories.
5. Use the build.sh and deploy-local.sh scripts to build and deploy the plugin for testing
[AugmentCode.com](https://augmentcode.com/) is recommended as a good all-in-one AI IDE for plugin development and testing.
Please feel free to submit a Pull Request with your improvements.
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository
2. Create your feature branch: `git checkout -b feature/amazing-feature`
@@ -184,316 +110,52 @@ Please feel free to submit a Pull Request with your improvements.
4. Push to the branch: `git push origin feature/amazing-feature`
5. Submit a pull request
### AI-Powered Development
This repository is configured to work with various AI-powered development tools. You can use any of the following AI IDEs to contribute to this project:
- [Augment Code](https://www.augmentcode.com/) - AI-powered coding assistant
- [Cursor](https://cursor.com/) - AI-first code editor
- [v0](https://v0.dev/) - AI-powered design and development tool
- [Windsurf](https://www.windsurf.com/) - AI coding assistant
- [Cline](https://cline.bot/) - AI terminal assistant
- [Roo Code](https://roocode.com/) - AI pair programmer
- [Loveable](https://lovable.dev/) - AI development environment
- [Bolt](https://www.bolt.new/) - AI-powered code editor
- [Cody](https://sourcegraph.com/cody) - Sourcegraph's AI coding assistant
- [Continue](https://continue.dev/) - Open-source AI coding assistant
The repository includes configuration files for all these tools to ensure a consistent development experience.
### Technical Details
The plugin works by:
1. Filtering the `all_plugins` array to add missing plugins
2. Adding a custom "Remove Notice" action link via `plugin_action_links`
2. Adding a custom "Remove Reference" action link via `plugin_action_links`
3. Adding helpful notifications near error messages
4. Providing a secure method to remove plugin references from the database
## Changelog
### 2.2.0
* Added: Completely refactored plugin to use OOP best practices
* Added: New class structure with proper namespaces
* Added: Improved code organization and maintainability
* Added: Better separation of concerns with dedicated classes
* Changed: "Choose Update Source" link to just "Update Source"
* Fixed: Close button in the update source modal
* Added: Links to the main page for each update source in the modal
* Changed: Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
### 1.4.1
- Added FAQ about keeping the plugin installed after notices are cleared
### 2.1.1
* Added: New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
* Added: Modal dialog with detailed information about each update source option
* Added: Visual indicator showing the currently selected update source
* Fixed: Updated heading styles in CHANGELOG.md for better readability
* Fixed: Corrected dates in changelog to use 2025 instead of 2024
* Improved: Documentation improvements for better clarity
* Improved: Enhanced Git Updater integration with user-selectable update sources
### 1.4.0
- Updated plugin name and text domain
- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
### 2.1.0
* Minor version bump for Git Updater compatibility
* Improved error handling for Git Updater integration
* Enhanced type checking in branch fix functions
* Updated documentation for Git Updater installation and cache refreshing
### 1.3.3
* Improved notification placement next to WordPress error messages
* Added "Click here to scroll" button that automatically locates missing plugins
* Enhanced reliability with multiple injection methods
* Added visual arrow pointing from notification to error message
### 2.0.13
* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
* Fixed: Type checking in branch fix functions to handle both string and object inputs
* Improved: Error handling for Git Updater integration
* Improved: Documentation for Git Updater installation and cache refreshing
### 1.3.2
* Added prominent notification directly below WordPress error messages
* Improved user guidance with visual cues to connect error and solution
* Added eye-catching styling to help users understand how to fix errors
### 2.0.12
* Fixed: Integrated Git Updater branch fix directly into main plugin
* Fixed: Removed separate "GU Branch Fix" plugin (no longer needed)
* Added: Documentation explaining branch fix integration
* Improved: Compatibility with Git Updater plugin
* Improved: Deploy script to remove separate branch fix plugin
### 1.3.1
* Added instructional notification explaining how to use the plugin
* Improved user guidance with step-by-step instructions
* Enhanced visual identification of missing plugins
### 2.0.11
* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
* Added: Deploy script for local testing
* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
* Improved: Compatibility with Git Updater plugin
### 2.0.10
* Fixed: Plugin details popup version display issue with Git Updater integration
* Added: JavaScript-based solution to ensure correct version display in plugin details
* Improved: Version consistency across all plugin views
* Improved: Cache busting for plugin information API
### 2.0.9
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Support for both old and new plugin slugs to fix caching issues
* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
* Improved: Version display in plugin details popup
### 2.0.8
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
* Improved: Author and contributor information display in plugin details
* Improved: Added WordPress 6.5 compatibility indicator
### 2.0.7
* Changed: Additional text improvements and minor fixes
### 2.0.6
* Changed: Text improvements and minor fixes
### 2.0.5
* Fixed: Display correct version in plugin details popup
### 2.0.4
* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
### 2.0.2
* Consolidated WordPress.org assets into .wordpress-org directory
* Improved organization of assets for WordPress.org submission
* Updated .wordpress-org/README.md with comprehensive information
### 2.0.1
* Added Contributing section to readme.txt
* Updated "tested up to" version to WordPress 6.7.2
* Added reference-plugins directory for plugin development inspiration
* Improved .gitattributes with comprehensive file handling
* Enhanced documentation organization
### 2.0.0
* Major version release for WordPress.org submission
* Added note clarifying that the plugin has no settings page
* Clarified that functionality is limited to the admin plugins page only
* Finalized all assets and documentation for public release
### 1.6.28
* Consolidated asset documentation into a single comprehensive guide
* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
* Updated all asset README files to point to the main documentation
* Improved file organization and documentation structure
### 1.6.27
* Clarified RTL support in WordPress.org asset documentation
* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
* Consolidated asset files and improved documentation
### 1.6.26
* Updated screenshot references to use a single comprehensive screenshot
* Fixed asset directory paths in documentation
* Improved ImageMagick conversion commands for icon generation
* Clarified WordPress.org SVN repository structure
### 1.6.25
* Consolidated asset files into their respective directories
* Created comprehensive WordPress.org submission guide
* Clarified SVN repository structure and asset requirements
* Improved organization of asset files
### 1.6.24
* Added properly named icon PNG files for WordPress.org submission
* Created icon-256x256.png and icon-128x128.png files
* Updated asset preparation documentation
### 1.6.23
* Prepared assets for WordPress.org plugin submission
* Added properly named icon, banner, and screenshot files
* Created comprehensive guide for WordPress.org asset requirements
* Fixed file naming to comply with WordPress.org standards
### 1.6.22
* Enhanced support section with multiple support channel options
* Added encouragement for users to leave reviews on WordPress.org
* Improved documentation with clearer support instructions
### 1.6.21
* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
* Updated documentation with links to supported AI IDEs
* Enhanced SEO with additional FAQs and keywords
* Made documentation more generic for boilerplate use
* Updated AI configuration files with modern models and better explanations
### 1.6.20
* Added explanations about the ! prefix in ignore files
* Moved WordPress-specific patterns to .gitignore
* Further improved organization of ignore patterns
* Added examples of how to include files excluded by .gitignore
### 1.6.19
* Consolidated common ignore patterns into .gitignore
* Simplified AI IDE configuration files to only include tool-specific patterns
* Improved organization of ignore patterns for better maintainability
* Added more file types to .gitignore for comprehensive coverage
### 1.6.18
* Optimized AI IDE configuration files to only include patterns not in .gitignore
* Improved efficiency of ignore files for better AI context management
* Enhanced compatibility with various AI-powered development tools
### 1.6.17
* Added .augmentignore file with best practices
* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
* Added more design file formats to .gitignore
* Added .aiconfig file for general AI IDE compatibility
### 1.6.16
* Updated CI configuration files with correct plugin slugs
* Updated CHANGELOG.md with all recent versions
* Fixed outdated references to plugin-reference-cleaner
### 1.6.15
* Moved AI workflow documentation to root directory for better visibility
* Consolidated duplicate workflow files
* Improved organization of development documentation
### 1.6.14
* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
* Improved explanation of how the plugin works
* Ensured consistent terminology across all documentation
### 1.6.13
* Code cleanup and optimization
* Improved Git Updater integration
* Fixed author display in plugin information
* Ensured compatibility with WordPress 6.4
### 1.6.12
* Added WPALLSTARS as a co-author
* Updated author information and links
* Added author websites to plugin description
* Fixed issue with multiple author URLs
### 1.6.11
* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
* Simplified plugin functionality to focus on core features only
* Improved compatibility with various WordPress configurations
* Ensured plugin works correctly when other plugins are deleted
### 1.6.10
* Fixed critical error that could occur when a plugin folder is deleted
* Improved error handling with try/catch blocks
* Added more specific checks for the plugins page
* Enhanced compatibility with various WordPress configurations
* Made the code more defensive to prevent potential issues
### 1.6.9
* Fixed issue with notices not appearing below WordPress error messages
* Improved JavaScript detection of WordPress error notices
* Prevented WordPress from automatically clearing error notices on page refresh
* Added multiple timing attempts to ensure notices appear correctly
* Enhanced error notice targeting for better compatibility
### 1.6.8
* Fixed notice positioning to appear directly below WordPress error messages
* Improved notice width to match WordPress error messages
* Updated explanatory text for better clarity
* Fixed issue with notices not appearing in some cases
* Improved JavaScript detection of WordPress error messages
### 1.6.7
* Fixed duplicate notices issue by removing PHP-generated notice
* Simplified notice system to only show one notice below WordPress error
* Ensured consistent terminology with "Remove Notice" text
* Optimized plugin detection with caching to improve performance
* Fixed JavaScript to correctly handle multiple error messages
### 1.6.6
* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
* Fixed issue with automatic removal of plugin references without user action
* Fixed notice positioning to ensure it appears below error messages
* Restored pointer triangle to indicate relationship with error message
* Improved detection of missing plugins in the plugin list
* Enhanced scroll functionality to work with all plugin types
### 1.6.5
* Fixed duplicate notices issue - now only one notice appears below error messages
* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
* Updated explanatory text to be more clear about the removal process
* Changed "Remove Reference" link text to "Remove Notice" for better clarity
* Made "(File Missing)" text bold and red for better visibility
* Fixed scroll functionality to work with all plugin rows
* Improved JavaScript to prevent multiple notices from appearing
### 1.6.4
* Updated version management to ensure consistent patch version increments
* Improved documentation for version update process
* Enhanced AI workflow files with detailed version increment instructions
### 1.6.3
* Fixed Git Updater repository URLs to use full repository paths
* Corrected Update URI configuration for proper update detection
* Improved version management following semantic versioning
* Updated organization name from 'WP All Stars' to 'WPALLSTARS'
* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
### 1.6.2
* Updated POT file version for consistency
* Improved JavaScript localization with proper fallbacks
* Enhanced code quality for WordPress.org submission
* Added Git Updater configuration with Update URI
* Added update server URL configuration
### 1.6.1
* Added AI assistant guide and workflow documentation
* Added detailed release process documentation
* Added feature development guidelines
* Added bug fixing procedures
* Added code review standards
### 1.6.0
* Added full translation support with POT file
* Added JavaScript localization for better multilingual support
* Added plugin constants for improved code organization
* Added Git Updater support for updates from GitHub and Gitea
* Updated code to follow WordPress internationalization best practices
* Improved asset loading with version constants
* Added smart update detection based on installation source
### 1.5.0
* Improved compatibility with WordPress 6.4
* Enhanced error detection for plugin references
* Minor UI improvements for better visibility
* Accessibility enhancements for screen readers
### 1.3.0
* Complete redesign for maximum compatibility with all WordPress themes
* Now adds missing plugins directly to the plugins list table
* Uses standard WordPress admin UI patterns instead of DOM manipulation
* Added "Remove Reference" action link in the plugins list
* Significantly improved reliability across all WordPress configurations
[View full changelog](CHANGELOG.md)
## License
This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE) file for details.
## Support
For support, please visit [WP All Stars](https://www.wpallstars.com).
-99
View File
@@ -1,99 +0,0 @@
/**
* Update Source Selector Styles
*/
#fpden-update-source-modal {
display: none;
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif;
}
#fpden-update-source-modal h2 {
margin-top: 0;
margin-bottom: 15px;
font-size: 1.3em;
font-weight: 600;
}
#fpden-update-source-modal p {
margin-bottom: 20px;
}
#fpden-update-source-form label {
display: block;
margin-bottom: 10px;
padding: 8px;
border-radius: 4px;
cursor: pointer;
}
#fpden-update-source-form label:hover {
background-color: #f0f0f1;
}
#fpden-update-source-form input[type="radio"] {
margin-right: 8px;
}
.fpden-source-description {
display: block;
margin-left: 24px;
font-size: 0.9em;
color: #666;
margin-top: 3px;
}
.fpden-submit-container {
margin-top: 20px;
text-align: right;
}
.fpden-submit-container button {
margin-left: 10px;
}
/* Remove explicit color to inherit from theme */
.fpden-update-source-toggle {
/* color is now inherited from theme */
}
.fpden-update-source-toggle:hover {
/* hover color is now inherited from theme */
}
/* Close button styles */
.fpden-close-modal {
position: absolute;
top: 10px;
right: 10px;
cursor: pointer;
font-size: 40px; /* Large size */
color: #666;
line-height: 30px;
text-decoration: none !important;
}
/* Source badges */
.fpden-source-badge {
display: inline-block;
padding: 2px 6px;
border-radius: 3px;
font-size: 0.8em;
margin-left: 5px;
color: white;
font-weight: normal;
}
.fpden-source-badge.wordpress, .fpden-source-badge.wordpress\.org {
background-color: #0073aa;
}
.fpden-source-badge.github {
background-color: #24292e;
}
.fpden-source-badge.gitea {
background-color: #609926;
}
.fpden-source-badge.auto {
background-color: #666;
}
-131
View File
@@ -1,131 +0,0 @@
(function() {
// Track if we've already added our notice
var noticeAdded = false;
// Function to inject our notice
function injectNotice() {
// If we've already added a notice, don't add another one
if (noticeAdded) {
return;
}
// Find all notification containers first
var noticeContainers = document.querySelectorAll('.notice, .error, .updated, div.error');
var targetNotice = null;
// Find all error notifications about missing plugins
noticeContainers.forEach(function(notice) {
if ((notice.textContent.includes('Plugin file does not exist') ||
notice.textContent.includes('has been deactivated due to an error')) &&
(notice.classList.contains('error') || notice.classList.contains('notice-error'))) {
// We'll use the last matching notice as our target
targetNotice = notice;
console.log('Found WordPress error notice:', notice.textContent);
}
});
// If we didn't find a specific error notice, look for the general WordPress error at the top
if (!targetNotice) {
// Try to find the WordPress error message at the top of the page
var wpError = document.querySelector('.error:not(.below-h2), div.error:not(.below-h2), .notice-error:not(.below-h2)');
if (wpError) {
targetNotice = wpError;
console.log('Found general WordPress error notice');
}
}
// If we found a target notice, add our custom notice after it
if (targetNotice) {
// Check if we already added our notice
if (targetNotice.nextElementSibling && targetNotice.nextElementSibling.classList.contains('prc-notice')) {
return;
}
// Create our custom notice
var ourNotice = document.createElement('div');
ourNotice.className = 'prc-notice';
// Add content using localized strings passed via wp_localize_script
var pluginMissingText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.pluginMissing ?
fpdenData.i18n.pluginMissing : 'File Missing';
var removeNoticeText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.removeNotice ?
fpdenData.i18n.removeNotice : 'Remove Notice';
var clickToScrollText = typeof fpdenData !== 'undefined' && fpdenData.i18n && fpdenData.i18n.clickToScroll ?
fpdenData.i18n.clickToScroll : 'Click here to scroll to and highlight missing plugins';
ourNotice.innerHTML = '<h3 style="margin-top:0;color:#826200;">Fix Plugin Does Not Exist Notices 👆</h3>' +
'<p>To remove these notices, scroll down to each plugin\'s row showing: plugin-name.php "<strong style="color:red">(' + pluginMissingText + ')</strong>". Then, click the "<strong>' + removeNoticeText + '</strong>" link for that plugin.</p>' +
'<p>This safely removes the missing active plugin reference from your database, using the standard WordPress function to update your active plugin options table, to leave the remaining plugins installed and active.</p>' +
'<p><a href="#" id="prc-scroll-to-plugin" style="font-weight:bold;text-decoration:underline;color:#826200;">' + clickToScrollText + '</a></p>';
// Insert our notice right after the error
targetNotice.parentNode.insertBefore(ourNotice, targetNotice.nextSibling);
// Make sure our notice has the same width as the WordPress error notice
ourNotice.style.width = targetNotice.offsetWidth + 'px';
ourNotice.style.maxWidth = '100%';
ourNotice.style.boxSizing = 'border-box';
// Mark that we've added our notice
noticeAdded = true;
// Add scroll behavior
var scrollLink = document.getElementById('prc-scroll-to-plugin');
if (scrollLink) {
scrollLink.addEventListener('click', function(e) {
e.preventDefault();
// Look for all plugin rows, not just inactive ones
var allPluginRows = document.querySelectorAll('tr.active, tr.inactive');
for (var i = 0; i < allPluginRows.length; i++) {
if (allPluginRows[i].textContent.includes('(File Missing)')) {
// Add a class for highlighting instead of direct style manipulation
allPluginRows[i].classList.add('prc-highlight-missing');
allPluginRows[i].scrollIntoView({ behavior: 'smooth', block: 'center' });
// Optional: Remove highlight after a delay
(function(row) {
setTimeout(function() {
row.classList.remove('prc-highlight-missing');
}, 3000); // Remove highlight after 3 seconds
})(allPluginRows[i]);
return;
}
}
});
}
}
}
// Try to inject notices on multiple events to ensure it works
document.addEventListener('DOMContentLoaded', function() {
// Delay the initial injection to ensure WordPress has fully loaded its notices
setTimeout(injectNotice, 100);
// Also set up a MutationObserver to watch for dynamically added notices
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(mutation) {
if (mutation.addedNodes && mutation.addedNodes.length > 0) {
// Check if added nodes are notices or contain notices
mutation.addedNodes.forEach(function(node) {
if (node.nodeType === 1 && (node.matches('.notice, .error, .updated, div.error') || node.querySelector('.notice, .error, .updated, div.error'))) {
setTimeout(injectNotice, 50); // Small delay to ensure the DOM is updated
}
});
}
});
});
// Start observing the body for changes in children
observer.observe(document.body, { childList: true, subtree: true });
});
// Backup attempt with window.onload (less reliable than DOMContentLoaded but good fallback)
window.addEventListener('load', function() {
setTimeout(injectNotice, 500); // Delay slightly to ensure dynamic content is loaded
});
// Additional attempt after a longer delay to catch late-loading notices
window.addEventListener('load', function() {
setTimeout(injectNotice, 1000); // Longer delay as final attempt
});
})();
-147
View File
@@ -1,147 +0,0 @@
/**
* Update Source Selector
*
* Handles the UI for selecting which source to use for plugin updates.
*/
jQuery(document).ready(function($) {
// Open modal when toggle is clicked
$(document).on('click', '.fpden-update-source-toggle', function(e) {
e.preventDefault();
// Add overlay
$('body').append('<div id="fpden-modal-overlay"></div>');
$('#fpden-modal-overlay').css({
'position': 'fixed',
'top': 0,
'left': 0,
'width': '100%',
'height': '100%',
'background-color': 'rgba(0,0,0,0.5)',
'z-index': 100000
});
// Position and show modal
var modal = $('#fpden-update-source-modal');
modal.css({
'position': 'fixed',
'top': '50%',
'left': '50%',
'transform': 'translate(-50%, -50%)',
'background-color': '#fff',
'padding': '20px',
'border-radius': '5px',
'box-shadow': '0 0 10px rgba(0,0,0,0.5)',
'z-index': 100001,
'width': '400px',
'max-width': '90%'
}).show();
// Add close button styles
$('.fpden-close-modal').css({
'position': 'absolute',
'top': '10px',
'right': '10px',
'cursor': 'pointer',
'font-size': '20px',
'color': '#666'
});
});
// Close modal when clicking overlay or close button
$(document).on('click', '#fpden-modal-overlay', function() {
$('#fpden-update-source-modal').hide();
$('#fpden-modal-overlay').remove();
});
// Separate handler for close button to ensure it works
$(document).on('click', '.fpden-close-modal', function(e) {
e.preventDefault();
e.stopPropagation(); // Prevent event bubbling
$('#fpden-update-source-modal').hide();
$('#fpden-modal-overlay').remove();
});
// Direct binding to the close button for extra reliability
$('.fpden-close-modal').on('click', function(e) {
e.preventDefault();
e.stopPropagation(); // Prevent event bubbling
$('#fpden-update-source-modal').hide();
$('#fpden-modal-overlay').remove();
});
// Prevent clicks inside modal from closing it
$('#fpden-update-source-modal').on('click', function(e) {
e.stopPropagation();
});
// Handle form submission
$('#fpden-update-source-form').on('submit', function(e) {
e.preventDefault();
var source = $('input[name="update_source"]:checked').val();
// Show loading state
var submitButton = $(this).find('button[type="submit"]');
var originalText = submitButton.text();
submitButton.text('Saving...').prop('disabled', true);
// Save via AJAX
$.post(ajaxurl, {
action: 'fpden_save_update_source',
source: source,
nonce: fpdenData.updateSourceNonce
}, function(response) {
submitButton.text(originalText).prop('disabled', false);
if (response.success) {
// Update the badge
var badgeText = source.charAt(0).toUpperCase() + source.slice(1);
if (source === 'wordpress.org') {
badgeText = 'WP.org';
}
// Remove all badge classes and add the new one
var badge = $('.fpden-update-source-toggle .fpden-source-badge');
badge.removeClass('auto wordpress github gitea')
.addClass(source)
.text(badgeText);
// Show success message
var message = $('<div class="fpden-success-message">Update source saved successfully!</div>');
message.css({
'color': 'green',
'margin-top': '10px',
'text-align': 'center'
});
$('#fpden-update-source-form').append(message);
// Hide message and modal after delay
setTimeout(function() {
message.fadeOut(function() {
$(this).remove();
$('#fpden-update-source-modal').hide();
$('#fpden-modal-overlay').remove();
});
}, 1500);
} else {
// Show error message
var message = $('<div class="fpden-error-message">Error saving update source.</div>');
message.css({
'color': 'red',
'margin-top': '10px',
'text-align': 'center'
});
$('#fpden-update-source-form').append(message);
// Hide message after delay
setTimeout(function() {
message.fadeOut(function() {
$(this).remove();
});
}, 3000);
}
});
});
});
-75
View File
@@ -1,75 +0,0 @@
/**
* Fix Plugin Version Display
*
* This script directly modifies the plugin details popup to show the correct version
* when the popup is opened for our plugin.
*/
(function($) {
'use strict';
// Current plugin version - this should match the version in the main plugin file
const CURRENT_VERSION = '2.2.0';
// Plugin slugs to check for
const OUR_SLUGS = ['wp-fix-plugin-does-not-exist-notices', 'fix-plugin-does-not-exist-notices'];
// Function to fix the version in the plugin details popup
function fixPluginDetailsVersion() {
// Check if we're on the plugins page
if (window.location.href.indexOf('plugins.php') === -1) {
return;
}
// Wait for the thickbox to be initialized
$(document).on('tb_init', function() {
// Set a timeout to allow the thickbox content to load
setTimeout(function() {
// Get the thickbox iframe
const $iframe = $('#TB_iframeContent');
if (!$iframe.length) return;
// Wait for iframe to load
$iframe.on('load', function() {
try {
const iframeDoc = this.contentDocument || this.contentWindow.document;
// Get the plugin title from the iframe
const $title = $(iframeDoc).find('h2.plugin-title');
if (!$title.length) return;
// Check if this is our plugin
const titleText = $title.text();
if (titleText.indexOf('Fix \'Plugin file does not exist\' Notices') !== -1) {
console.log('Found our plugin in the details popup, fixing version...');
// Find the version element
const $version = $(iframeDoc).find('.plugin-version-author-uri');
if ($version.length) {
// Update the version text
const versionText = $version.text();
const newVersionText = versionText.replace(/Version: [0-9.]+|Version: 0\.0\.0/, 'Version: ' + CURRENT_VERSION);
$version.text(newVersionText);
console.log('Updated version to: ' + CURRENT_VERSION);
}
// Also update the version in the header if it exists
const $versionHeader = $(iframeDoc).find('.wrap h2:contains("Version:")');
if ($versionHeader.length) {
$versionHeader.text('Version: ' + CURRENT_VERSION);
console.log('Updated version header to: ' + CURRENT_VERSION);
}
}
} catch (e) {
console.error('Error updating plugin version:', e);
}
});
}, 500);
});
}
// Initialize when the document is ready
$(document).ready(function() {
fixPluginDetailsVersion();
});
})(jQuery);
+53
View File
@@ -0,0 +1,53 @@
# Plugin Assets for WordPress.org
This directory contains assets for the WordPress.org plugin repository.
## Directory Structure
- `banner/` - Banner images for the plugin page header
- `banner-772x250.jpg` - Standard banner (772x250px)
- `banner-1544x500.jpg` - Retina banner (1544x500px)
- `icon/` - Plugin icon images
- `icon-128x128.jpg` - Standard icon (128x128px)
- `icon-256x256.jpg` - Retina icon (256x256px)
- `screenshots/` - Screenshots shown on the plugin page
- `screenshot-1.jpg` - Error message with explanation notification
- `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
### Required Image Dimensions
- **Banner**: 772x250px with 2x retina version at 1544x500px
- **Icon**: 128x128px with 2x retina version at 256x256px
- **Screenshots**: No specific size requirements, but they should be clear and readable
### Image Formats
- All images should be in JPG or PNG format
- Images should be optimized for web (compressed without losing quality)
### Additional Notes
- Screenshots should be numbered sequentially starting with 1
- They should match the descriptions in the `readme.txt` file
- Dark theme versions of banners and icons can be provided by appending `-rtl` to the filename
## Example Filenames
```
assets/
├── banner/
│ ├── banner-772x250.jpg
│ └── banner-1544x500.jpg
├── icon/
│ ├── icon-128x128.jpg
│ └── icon-256x256.jpg
└── screenshots/
├── screenshot-1.jpg
├── screenshot-2.jpg
└── screenshot-3.jpg
```
@@ -5,9 +5,6 @@
margin: 5px 0 15px;
font-size: 14px;
position: relative;
width: 100%;
box-sizing: border-box;
max-width: none;
}
.prc-notice h3 {
margin-top: 0;
@@ -26,13 +23,6 @@
}
/* Style for highlighting the missing plugin row */
tr.inactive.prc-highlight-missing,
tr.active.prc-highlight-missing {
tr.inactive.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;
}
+81
View File
@@ -0,0 +1,81 @@
(function() {
// Function to inject our notice
function injectNotice() {
// Find all notification containers first
var noticeContainers = document.querySelectorAll('.notice, .error, .updated');
// Find all error notifications about missing plugins
noticeContainers.forEach(function(notice) {
if (notice.textContent.includes('Plugin file does not exist') ||
notice.textContent.includes('has been deactivated due to an error')) {
// Check if we already added our notice
if (notice.nextElementSibling && notice.nextElementSibling.classList.contains('prc-notice')) {
return;
}
// Create our custom notice
var ourNotice = document.createElement('div');
ourNotice.className = 'prc-notice';
// Add content (using localized strings passed via wp_localize_script if needed, but simple for now)
ourNotice.innerHTML = '<h3 style="margin-top:0;color:#826200;">👉 Fix Plugin Does Not Exist Notices Can Fix This</h3>' +
'<p>To remove the above error notification, scroll down to find the plugin marked with "<strong style="color:red">(File Missing)</strong>" and click its "<strong>Remove Reference</strong>" link.</p>' +
'<p>This will permanently remove the missing plugin reference from your database.</p>' +
'<p><a href="#" id="prc-scroll-to-plugin" style="font-weight:bold;text-decoration:underline;color:#826200;">Click here to scroll to the missing plugin</a></p>';
// Insert our notice right after the error
notice.parentNode.insertBefore(ourNotice, notice.nextSibling);
// Add scroll behavior
var scrollLink = document.getElementById('prc-scroll-to-plugin');
if (scrollLink) {
scrollLink.addEventListener('click', function(e) {
e.preventDefault();
var missingPlugins = document.querySelectorAll('tr.inactive:not(.plugin-update-tr)');
for (var i = 0; i < missingPlugins.length; i++) {
if (missingPlugins[i].textContent.includes('(File Missing)')) {
// 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;
}
}
});
}
}
});
}
// Try to inject notices on multiple events to ensure it works
document.addEventListener('DOMContentLoaded', function() {
injectNotice();
// Also set up a MutationObserver to watch for dynamically added notices
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(mutation) {
if (mutation.addedNodes && mutation.addedNodes.length > 0) {
// 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();
}
});
}
});
});
// Start observing the body for changes in children
observer.observe(document.body, { childList: true, subtree: true });
});
// Backup attempt with window.onload (less reliable than DOMContentLoaded but good fallback)
window.addEventListener('load', function() {
setTimeout(injectNotice, 500); // Delay slightly to ensure dynamic content is loaded
});
})();
+3 -23
View File
@@ -10,7 +10,7 @@ if [ -z "$1" ]; then
fi
VERSION=$1
PLUGIN_SLUG="wp-fix-plugin-does-not-exist-notices"
PLUGIN_SLUG="fix-plugin-does-not-exist-notices"
BUILD_DIR="build/$PLUGIN_SLUG"
ZIP_FILE="${PLUGIN_SLUG}-${VERSION}.zip"
@@ -24,7 +24,7 @@ composer install --no-dev --optimize-autoloader
# Copy required files
echo "Copying plugin files..."
cp wp-fix-plugin-does-not-exist-notices.php $BUILD_DIR/
cp fix-plugin-does-not-exist-notices.php $BUILD_DIR/
cp readme.txt $BUILD_DIR/
cp LICENSE $BUILD_DIR/
cp README.md $BUILD_DIR/
@@ -37,24 +37,8 @@ mkdir -p $BUILD_DIR/includes
cp -r includes/* $BUILD_DIR/includes/
mkdir -p $BUILD_DIR/languages
cp -r languages/* $BUILD_DIR/languages/
# Copy admin assets
mkdir -p $BUILD_DIR/admin/css
cp -r admin/css/* $BUILD_DIR/admin/css/
mkdir -p $BUILD_DIR/admin/js
cp -r admin/js/* $BUILD_DIR/admin/js/
# Create assets directory structure
mkdir -p $BUILD_DIR/assets
# Copy PNG files from .wordpress-org/assets to the build directory
mkdir -p $BUILD_DIR/assets/banner
cp -r .wordpress-org/assets/banner-*.png $BUILD_DIR/assets/banner/ 2>/dev/null || :
mkdir -p $BUILD_DIR/assets/icon
cp -r .wordpress-org/assets/icon-*.png $BUILD_DIR/assets/icon/ 2>/dev/null || :
mkdir -p $BUILD_DIR/assets/screenshots
cp -r .wordpress-org/assets/screenshot-*.png $BUILD_DIR/assets/screenshots/ 2>/dev/null || :
cp -r assets/* $BUILD_DIR/assets/
mkdir -p $BUILD_DIR/vendor
cp -r vendor/* $BUILD_DIR/vendor/
@@ -68,10 +52,6 @@ cd ..
if [ -f "$ZIP_FILE" ]; then
echo "✅ Build successful: $ZIP_FILE created"
echo "File path: $(pwd)/$ZIP_FILE"
# Deploy to local WordPress installation
echo "\nDeploying to local WordPress installation..."
./scripts/deploy-local.sh
else
echo "❌ Build failed: ZIP file was not created"
exit 1
+1 -1
View File
@@ -1,5 +1,5 @@
{
"name": "wpallstars/wp-fix-plugin-does-not-exist-notices",
"name": "wpallstars/fix-plugin-does-not-exist-notices",
"description": "Adds missing plugins to the plugins list with a 'Remove Reference' link so you can permanently clean up invalid plugin entries and remove error notices.",
"type": "wordpress-plugin",
"license": "GPL-2.0-or-later",
+413
View File
@@ -0,0 +1,413 @@
<?php
/**
* Fix 'Plugin file does not exist.' Notices
*
* @package FixPluginDoesNotExistNotices
* @author Marcus Quinn
* @copyright 2023 WP All Stars
* @license GPL-2.0+
*
* @wordpress-plugin
* Plugin Name: Fix 'Plugin file does not exist.' Notices
* Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: 1.6.0
* Author: Marcus Quinn
* Author URI: https://www.wpallstars.com
* License: GPL-2.0+
* License URI: https://www.gnu.org/licenses/gpl-2.0.html
* Text Domain: fix-plugin-does-not-exist-notices
* Domain Path: /languages
* Requires at least: 5.0
* Requires PHP: 7.0
* GitHub Plugin URI: wpallstars/fix-plugin-does-not-exist-notices
* GitHub Branch: main
* Gitea Plugin URI: wpallstars/fix-plugin-does-not-exist-notices
* Gitea Branch: main
*
* This plugin is free software: you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation, either version 2 of the License, or
* any later version.
*
* This plugin is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this plugin. If not, see https://www.gnu.org/licenses/gpl-2.0.html.
*/
// Exit if accessed directly.
if ( ! defined( 'ABSPATH' ) ) {
exit;
}
// Define plugin constants
define( 'FPDEN_VERSION', '1.6.0' );
define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
define( 'FPDEN_PLUGIN_FILE', __FILE__ );
define( 'FPDEN_PLUGIN_BASENAME', plugin_basename( __FILE__ ) );
/**
* Load plugin text domain.
*
* @return void
*/
function fpden_load_textdomain() {
load_plugin_textdomain(
'fix-plugin-does-not-exist-notices',
false,
dirname( plugin_basename( __FILE__ ) ) . '/languages/'
);
}
add_action( 'plugins_loaded', 'fpden_load_textdomain' );
/**
* Main class for the plugin.
*/
class Fix_Plugin_Does_Not_Exist_Notices {
/**
* Constructor. Hooks into WordPress actions and filters.
*/
public function __construct() {
// Add our plugin to the plugins list.
add_filter( 'all_plugins', array( $this, 'add_missing_plugins_references' ) );
// Add our action link to the plugins list.
add_filter( 'plugin_action_links', array( $this, 'add_remove_reference_action' ), 20, 4 );
// Handle the remove reference action.
add_action( 'admin_init', array( $this, 'handle_remove_reference' ) );
// Add admin notices for operation feedback.
add_action( 'admin_notices', array( $this, 'admin_notices' ) );
// Enqueue admin scripts and styles.
add_action( 'admin_enqueue_scripts', array( $this, 'enqueue_admin_assets' ) );
}
/**
* Enqueue scripts and styles needed for the admin area.
*
* @param string $hook_suffix The current admin page hook.
* @return void
*/
public function enqueue_admin_assets( $hook_suffix ) {
// Only load on the plugins page.
if ( 'plugins.php' !== $hook_suffix ) {
return;
}
// Get invalid plugins to decide if assets are needed.
$invalid_plugins = $this->get_invalid_plugins();
if ( empty( $invalid_plugins ) ) {
return; // No missing plugins, no need for the special notice JS/CSS.
}
wp_enqueue_style(
'fpden-admin-styles',
FPDEN_PLUGIN_URL . 'assets/css/admin-styles.css',
array(),
FPDEN_VERSION
);
wp_enqueue_script(
'fpden-admin-scripts',
FPDEN_PLUGIN_URL . 'assets/js/admin-scripts.js',
array( 'jquery' ), // Add dependencies if needed, e.g., jQuery.
FPDEN_VERSION,
true // Load in footer.
);
// Add translation strings for JavaScript
wp_localize_script(
'fpden-admin-scripts',
'fpdenData',
array(
'i18n' => array(
'clickToScroll' => esc_html__( 'Click here to scroll to missing plugins', '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' ),
),
)
);
}
/**
* Find and add invalid plugin references to the plugins list.
*
* Filters the list of plugins displayed on the plugins page to include
* entries for active plugins whose files are missing.
*
* @param array $plugins An array of plugin data.
* @return array The potentially modified array of plugin data.
*/
public function add_missing_plugins_references( $plugins ) {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return $plugins;
}
// Get active plugins that don't exist.
$invalid_plugins = $this->get_invalid_plugins();
// Add each invalid plugin to the plugin list.
foreach ( $invalid_plugins as $plugin_path ) {
if ( ! isset( $plugins[ $plugin_path ] ) ) {
$plugin_name = basename( $plugin_path );
$plugins[ $plugin_path ] = array(
'Name' => $plugin_name . ' <span class="error">(File Missing)</span>',
/* translators: %s: Path to wp-content/plugins */
'Description' => sprintf(
__( 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Reference" to permanently remove it from your active plugins list and eliminate the error notice.', 'fix-plugin-does-not-exist-notices' ),
'<code>/wp-content/plugins/</code>'
),
'Version' => __( 'N/A', 'fix-plugin-does-not-exist-notices' ),
'Author' => '',
'PluginURI' => '',
'AuthorURI' => '',
'Title' => $plugin_name . ' (' . __( 'Missing', 'fix-plugin-does-not-exist-notices' ) . ')',
'AuthorName' => '',
);
}
}
return $plugins;
}
/**
* Add the Remove Reference 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.
*
* @param array $actions An array of plugin action links.
* @param string $plugin_file Path to the plugin file relative to the plugins directory.
* @param array $plugin_data An array of plugin data.
* @param string $context The plugin context (e.g., 'all', 'active', 'inactive').
* @return array The potentially modified array of plugin action links.
*/
public function add_remove_reference_action( $actions, $plugin_file, $plugin_data, $context ) {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return $actions;
}
// 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 ) {
// Clear existing actions like "Activate", "Deactivate", "Edit".
$actions = array();
// Add our custom action.
$nonce = wp_create_nonce( 'remove_plugin_reference_' . $plugin_file );
$remove_url = admin_url( 'plugins.php?action=remove_reference&plugin=' . urlencode( $plugin_file ) . '&_wpnonce=' . $nonce );
/* translators: %s: Plugin file path */
$aria_label = sprintf( __( 'Remove reference to missing plugin %s', '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>';
}
return $actions;
}
/**
* Handle the remove reference action triggered by the link.
*
* Checks for the correct action, verifies nonce and permissions,
* calls the removal function, and redirects back to the plugins page.
*
* @return void
*/
public function handle_remove_reference() {
// Check if our specific action is being performed.
if ( ! isset( $_GET['action'] ) || 'remove_reference' !== $_GET['action'] || ! isset( $_GET['plugin'] ) ) {
return;
}
// Verify user permissions.
if ( ! current_user_can( 'activate_plugins' ) ) {
wp_die( esc_html__( 'You do not have sufficient permissions to perform this action.', 'fix-plugin-does-not-exist-notices' ) );
}
// Sanitize and get the plugin file path.
$plugin_file = isset( $_GET['plugin'] ) ? sanitize_text_field( wp_unslash( $_GET['plugin'] ) ) : '';
if ( empty( $plugin_file ) ) {
wp_die( esc_html__( 'Invalid plugin specified.', 'fix-plugin-does-not-exist-notices' ) );
}
// Verify nonce for security.
check_admin_referer( 'remove_plugin_reference_' . $plugin_file );
// Attempt to remove the plugin reference.
$success = $this->remove_plugin_reference( $plugin_file );
// Prepare redirect URL with feedback query args.
$redirect_url = admin_url( 'plugins.php' );
$redirect_url = add_query_arg( $success ? 'reference_removed' : 'reference_removal_failed', '1', $redirect_url );
// Redirect and exit.
wp_safe_redirect( $redirect_url );
exit;
}
/**
* Remove a plugin reference from the active plugins list in the database.
*
* Handles both single site and multisite network activated plugins.
*
* @param string $plugin_file The plugin file path to remove.
* @return bool True on success, false on failure or if the plugin wasn't found.
*/
public function remove_plugin_reference( $plugin_file ) {
$success = false;
// Ensure plugin file path is provided.
if ( empty( $plugin_file ) ) {
return false;
}
// Handle multisite network admin context.
if ( is_multisite() && is_network_admin() ) {
$active_plugins = get_site_option( 'active_sitewide_plugins', array() );
// Network active plugins are stored as key => timestamp.
if ( isset( $active_plugins[ $plugin_file ] ) ) {
unset( $active_plugins[ $plugin_file ] );
$success = update_site_option( 'active_sitewide_plugins', $active_plugins );
}
} else { // Handle single site or non-network admin context.
$active_plugins = get_option( 'active_plugins', array() );
// Single site active plugins are stored as an indexed array.
$key = array_search( $plugin_file, $active_plugins, true ); // Use strict comparison.
if ( false !== $key ) {
unset( $active_plugins[ $key ] );
// Re-index the array numerically.
$active_plugins = array_values( $active_plugins );
$success = update_option( 'active_plugins', $active_plugins );
}
}
return $success;
}
/**
* Display admin notices on the plugins page.
*
* Shows informational notices about missing plugins and feedback
* messages after attempting to remove a reference.
*
* @return void
*/
public function admin_notices() {
// Only run on the plugins page.
if ( ! $this->is_plugins_page() ) {
return;
}
// Check for feedback messages from the remove action.
if ( isset( $_GET['reference_removed'] ) && '1' === $_GET['reference_removed'] ) {
?>
<div class="notice notice-success is-dismissible">
<p><?php esc_html_e( 'Plugin reference removed successfully.', 'fix-plugin-does-not-exist-notices' ); ?></p>
</div>
<?php
}
if ( isset( $_GET['reference_removal_failed'] ) && '1' === $_GET['reference_removal_failed'] ) {
?>
<div class="notice notice-error is-dismissible">
<p><?php esc_html_e( 'Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue.', 'fix-plugin-does-not-exist-notices' ); ?></p>
</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.
}
}
/**
* Check if the current admin page is the plugins page.
*
* @global string $pagenow WordPress global variable for the current admin page filename.
* @return bool True if the current page is plugins.php, false otherwise.
*/
private function is_plugins_page() {
global $pagenow;
// Check if it's an admin page and the filename is plugins.php.
return is_admin() && isset( $pagenow ) && 'plugins.php' === $pagenow;
}
/**
* Get a list of active plugin file paths that do not exist on the filesystem.
*
* Checks both single site and network active plugins based on the context.
*
* @return array An array of plugin file paths (relative to WP_PLUGIN_DIR) that are missing.
*/
private function get_invalid_plugins() {
$invalid_plugins = array();
$active_plugins = array();
// Determine which option to check based on context (Network Admin or single site).
if ( is_multisite() && is_network_admin() ) {
// Network active plugins are stored as keys in an associative array.
$active_plugins = array_keys( get_site_option( 'active_sitewide_plugins', array() ) );
} else {
// Single site active plugins are stored in a numerically indexed array.
$active_plugins = get_option( 'active_plugins', array() );
}
// Check if the file exists for each active plugin.
foreach ( $active_plugins as $plugin_file ) {
// Construct the full path to the main plugin file.
$plugin_path = WP_PLUGIN_DIR . '/' . $plugin_file;
// Use validate_file to prevent directory traversal issues, although less likely here.
if ( validate_file( $plugin_file ) === 0 && ! file_exists( $plugin_path ) ) {
$invalid_plugins[] = $plugin_file;
}
}
return $invalid_plugins;
}
} // End class Fix_Plugin_Does_Not_Exist_Notices
// Initialize the plugin class.
new Fix_Plugin_Does_Not_Exist_Notices();
// Initialize the updater if composer autoload exists
$autoloader = __DIR__ . '/vendor/autoload.php';
if (file_exists($autoloader)) {
require_once $autoloader;
// Initialize the updater if the class exists
if (class_exists('\WPAllStars\FixPluginDoesNotExistNotices\Updater')) {
new \WPAllStars\FixPluginDoesNotExistNotices\Updater(__FILE__);
}
}
-92
View File
@@ -1,92 +0,0 @@
<?php
/**
* Admin Functionality
*
* @package WPALLSTARS\FixPluginDoesNotExistNotices
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
/**
* Admin Class
*
* Handles admin-specific functionality.
*/
class Admin {
/**
* Core instance
*
* @var Core
*/
private $core;
/**
* Constructor
*
* @param Core $core Core instance.
*/
public function __construct($core) {
$this->core = $core;
// Enqueue admin scripts and styles
add_action('admin_enqueue_scripts', array($this, 'enqueue_admin_assets'));
}
/**
* Enqueue scripts and styles needed for the admin area.
*
* @param string $hook_suffix The current admin page hook.
* @return void
*/
public function enqueue_admin_assets($hook_suffix) {
// Only load on the plugins page
if ('plugins.php' !== $hook_suffix) {
return;
}
// Always load our version fix script on the plugins page
wp_enqueue_script(
'fpden-version-fix',
FPDEN_PLUGIN_URL . 'admin/js/version-fix.js',
array('jquery', 'thickbox'),
FPDEN_VERSION,
true // Load in footer
);
// Get invalid plugins to decide if other assets are needed
$invalid_plugins = $this->core->get_invalid_plugins();
if (empty($invalid_plugins)) {
return; // No missing plugins, no need for the special notice JS/CSS
}
wp_enqueue_style(
'fpden-admin-styles',
FPDEN_PLUGIN_URL . 'admin/css/admin-styles.css',
array(),
FPDEN_VERSION
);
wp_enqueue_script(
'fpden-admin-scripts',
FPDEN_PLUGIN_URL . 'admin/js/admin-scripts.js',
array('jquery'), // Add dependencies if needed, e.g., jQuery
FPDEN_VERSION,
true // Load in footer
);
// Add translation strings for JavaScript
wp_localize_script(
'fpden-admin-scripts',
'fpdenData',
array(
'i18n' => array(
'clickToScroll' => esc_html__('Click here to scroll to missing plugins', 'wp-fix-plugin-does-not-exist-notices'),
'pluginMissing' => esc_html__('File Missing', 'wp-fix-plugin-does-not-exist-notices'),
'removeNotice' => esc_html__('Remove Notice', 'wp-fix-plugin-does-not-exist-notices'),
),
'version' => FPDEN_VERSION, // Add version for the plugin details fix script
)
);
}
}
-619
View File
@@ -1,619 +0,0 @@
<?php
/**
* Core Functionality
*
* @package WPALLSTARS\FixPluginDoesNotExistNotices
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
/**
* Core Class
*
* Handles the core functionality of finding and fixing invalid plugin references.
*/
class Core {
/**
* Stores a list of invalid plugins found in the active_plugins option.
*
* @var array|null
*/
private $invalid_plugins = null;
/**
* Constructor
*/
public function __construct() {
// Add our plugin to the plugins list
add_filter('all_plugins', array($this, 'add_missing_plugins_references'));
// Add our action link to the plugins list
add_filter('plugin_action_links', array($this, 'add_remove_reference_action'), 20, 4);
// Handle the remove reference action
add_action('admin_init', array($this, 'handle_remove_reference'));
// Add admin notices for operation feedback
add_action('admin_notices', array($this, 'admin_notices'));
// Filter the plugin API to fix version display in plugin details popup
add_filter('plugins_api', array($this, 'filter_plugin_details'), 10, 3);
// Prevent WordPress from caching our plugin API responses
add_filter('plugins_api_result', array($this, 'prevent_plugins_api_caching'), 10, 3);
// Clear plugin API transients on plugin activation and when viewing plugins page
add_action('admin_init', array($this, 'maybe_clear_plugin_api_cache'));
}
/**
* Get a list of invalid plugins (plugins that are active but don't exist).
*
* @return array An array of plugin file paths that don't exist.
*/
public function get_invalid_plugins() {
// Return cached result if available
if (is_array($this->invalid_plugins)) {
return $this->invalid_plugins;
}
// Initialize empty array
$invalid_plugins = array();
// Handle multisite network admin context
if (is_multisite() && is_network_admin()) {
$active_plugins = get_site_option('active_sitewide_plugins', array());
// Network active plugins are stored as key => timestamp
$active_plugins = array_keys($active_plugins);
} else {
// Single site or non-network admin context
$active_plugins = get_option('active_plugins', array());
}
// Check each active plugin
foreach ($active_plugins as $plugin_file) {
$plugin_path = WP_PLUGIN_DIR . '/' . $plugin_file;
if (!file_exists($plugin_path)) {
$invalid_plugins[] = $plugin_file;
}
}
// Cache the result
$this->invalid_plugins = $invalid_plugins;
return $invalid_plugins;
}
/**
* Check if the current page is the plugins page.
*
* @return bool True if on the plugins page, false otherwise.
*/
public function is_plugins_page() {
global $pagenow;
return is_admin() && 'plugins.php' === $pagenow;
}
/**
* Find and add invalid plugin references to the plugins list.
*
* Filters the list of plugins displayed on the plugins page to include
* entries for active plugins whose files are missing.
*
* @param array $plugins An array of plugin data.
* @return array The potentially modified array of plugin data.
*/
public function add_missing_plugins_references($plugins) {
// Only run on the plugins page
if (!$this->is_plugins_page()) {
return $plugins;
}
// Get active plugins that don't exist
$invalid_plugins = $this->get_invalid_plugins();
// Add each invalid plugin to the plugin list
foreach ($invalid_plugins as $plugin_path) {
if (!isset($plugins[$plugin_path])) {
$plugin_name = basename($plugin_path);
$plugin_slug = dirname($plugin_path);
if ('.' === $plugin_slug) {
$plugin_slug = basename($plugin_path, '.php');
}
// Create a basic plugin data array
$plugins[$plugin_path] = array(
'Name' => $plugin_name . ' <span class="error">(File Missing)</span>',
/* translators: %s: Path to wp-content/plugins */
'Description' => sprintf(
__('This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices'),
'<code>/wp-content/plugins/</code>'
),
'Version' => FPDEN_VERSION, // Use our plugin version instead of 'N/A'
'Author' => 'Marcus Quinn & WPALLSTARS',
'PluginURI' => 'https://www.wpallstars.com',
'AuthorURI' => 'https://www.wpallstars.com',
'Title' => $plugin_name . ' (' . __('Missing', 'wp-fix-plugin-does-not-exist-notices') . ')',
'AuthorName' => 'Marcus Quinn & WPALLSTARS',
);
// Add the data needed for the "View details" link
$plugins[$plugin_path]['slug'] = $plugin_slug;
$plugins[$plugin_path]['plugin'] = $plugin_path;
$plugins[$plugin_path]['type'] = 'plugin';
// Add Git Updater fields
$plugins[$plugin_path]['GitHub Plugin URI'] = 'wpallstars/wp-fix-plugin-does-not-exist-notices';
$plugins[$plugin_path]['GitHub Branch'] = 'main';
$plugins[$plugin_path]['TextDomain'] = 'wp-fix-plugin-does-not-exist-notices';
}
}
return $plugins;
}
/**
* Add the Remove Notice action link to invalid plugins.
*
* Filters the action links displayed for each plugin on the plugins page.
* Adds a "Remove Notice" link for plugins identified as missing.
*
* @param array $actions An array of plugin action links.
* @param string $plugin_file Path to the plugin file relative to the plugins directory.
* @param array $plugin_data An array of plugin data.
* @param string $context The plugin context (e.g., 'all', 'active', 'inactive').
* @return array The potentially modified array of plugin action links.
*/
public function add_remove_reference_action($actions, $plugin_file, $plugin_data, $context) {
// Only run on the plugins page
if (!$this->is_plugins_page()) {
return $actions;
}
// Get our list of invalid plugins
$invalid_plugins = $this->get_invalid_plugins();
// Check if this plugin file is in our list of invalid plugins
if (in_array($plugin_file, $invalid_plugins, true)) {
// Clear existing actions like "Activate", "Deactivate", "Edit"
$actions = array();
// Add our custom action
$nonce = wp_create_nonce('remove_plugin_reference_' . $plugin_file);
$remove_url = admin_url('plugins.php?action=remove_reference&plugin=' . urlencode($plugin_file) . '&_wpnonce=' . $nonce);
/* translators: %s: Plugin file path */
$aria_label = sprintf(__('Remove reference to missing plugin %s', 'wp-fix-plugin-does-not-exist-notices'), esc_attr($plugin_file));
$actions['remove_reference'] = '<a href="' . esc_url($remove_url) . '" class="delete" aria-label="' . $aria_label . '">' . esc_html__('Remove Notice', 'wp-fix-plugin-does-not-exist-notices') . '</a>';
}
return $actions;
}
/**
* Handle the remove reference action triggered by the link.
*
* Checks for the correct action, verifies nonce and permissions,
* calls the removal function, and redirects back to the plugins page.
*
* @return void
*/
public function handle_remove_reference() {
// Check if our specific action is being performed
if (!isset($_GET['action']) || 'remove_reference' !== $_GET['action'] || !isset($_GET['plugin'])) {
return;
}
// Verify user permissions
if (!current_user_can('activate_plugins')) {
wp_die(esc_html__('You do not have sufficient permissions to perform this action.', 'wp-fix-plugin-does-not-exist-notices'));
}
// Sanitize and get the plugin file path
$plugin_file = isset($_GET['plugin']) ? sanitize_text_field(wp_unslash($_GET['plugin'])) : '';
if (empty($plugin_file)) {
wp_die(esc_html__('Invalid plugin specified.', 'wp-fix-plugin-does-not-exist-notices'));
}
// Verify nonce for security
check_admin_referer('remove_plugin_reference_' . $plugin_file);
// Attempt to remove the plugin reference
$success = $this->remove_plugin_reference($plugin_file);
// Prepare redirect URL with feedback query args
$redirect_url = admin_url('plugins.php');
$redirect_url = add_query_arg($success ? 'reference_removed' : 'reference_removal_failed', '1', $redirect_url);
// Redirect and exit
wp_safe_redirect($redirect_url);
exit;
}
/**
* Remove a plugin reference from the active plugins list in the database.
*
* Handles both single site and multisite network activated plugins.
*
* @param string $plugin_file The plugin file path to remove.
* @return bool True on success, false on failure or if the plugin wasn't found.
*/
public function remove_plugin_reference($plugin_file) {
$success = false;
// Ensure plugin file path is provided
if (empty($plugin_file)) {
return false;
}
// Handle multisite network admin context
if (is_multisite() && is_network_admin()) {
$active_plugins = get_site_option('active_sitewide_plugins', array());
// Network active plugins are stored as key => timestamp
if (isset($active_plugins[$plugin_file])) {
unset($active_plugins[$plugin_file]);
$success = update_site_option('active_sitewide_plugins', $active_plugins);
}
} else { // Handle single site or non-network admin context
$active_plugins = get_option('active_plugins', array());
// Single site active plugins are stored as an indexed array
$key = array_search($plugin_file, $active_plugins, true); // Use strict comparison
if (false !== $key) {
unset($active_plugins[$key]);
// Re-index the array numerically
$active_plugins = array_values($active_plugins);
$success = update_option('active_plugins', $active_plugins);
}
}
return $success;
}
/**
* Display admin notices on the plugins page.
*
* Shows feedback messages after attempting to remove a reference.
* The main informational notice is handled by JavaScript to position it
* directly below the WordPress error message.
*
* @return void
*/
public function admin_notices() {
// Only run on the plugins page
if (!$this->is_plugins_page()) {
return;
}
// Check for feedback messages from the remove action
if (isset($_GET['reference_removed']) && '1' === $_GET['reference_removed']) {
?>
<div class="notice notice-success is-dismissible">
<p><?php esc_html_e('Plugin reference removed successfully.', 'wp-fix-plugin-does-not-exist-notices'); ?></p>
</div>
<?php
}
if (isset($_GET['reference_removal_failed']) && '1' === $_GET['reference_removal_failed']) {
?>
<div class="notice notice-error is-dismissible">
<p><?php esc_html_e('Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue.', 'wp-fix-plugin-does-not-exist-notices'); ?></p>
</div>
<?php
}
}
/**
* Filter plugin details API response to provide custom data for our plugin.
*
* @param object|WP_Error $result The result object or WP_Error.
* @param string $action The type of information being requested.
* @param object $args Plugin API arguments.
* @return object|WP_Error The result object or WP_Error.
*/
public function filter_plugin_details($result, $action, $args) {
// Only modify plugin_information requests
if ('plugin_information' !== $action) {
return $result;
}
// Check if we have a slug to work with
if (empty($args->slug)) {
return $result;
}
// Get our list of invalid plugins
$invalid_plugins = $this->get_invalid_plugins();
// Check if this is our plugin or a missing plugin
$our_plugin = in_array($args->slug, array('wp-fix-plugin-does-not-exist-notices', 'fix-plugin-does-not-exist-notices'), true);
$is_missing_plugin = $this->is_missing_plugin($args->slug, $invalid_plugins);
// Only modify the result if this is our plugin or a missing plugin
if ($our_plugin || $is_missing_plugin) {
// Create a new result object
$new_result = new \stdClass();
// Set all the properties we need
$new_result->name = $our_plugin ? 'Fix \'Plugin file does not exist\' Notices' : (isset($result->name) ? $result->name : $args->slug);
$new_result->slug = $args->slug;
$new_result->version = FPDEN_VERSION;
$new_result->author = '<a href="https://www.wpallstars.com">Marcus Quinn & WPALLSTARS</a>';
$new_result->author_profile = 'https://www.wpallstars.com';
$new_result->requires = '5.0';
$new_result->tested = '6.7.2'; // Updated to match readme.txt
$new_result->requires_php = '7.0';
$new_result->last_updated = date('Y-m-d H:i:s');
// Add a cache buster timestamp
$new_result->cache_buster = time();
// Get full readme content for our plugin
$readme_file = FPDEN_PLUGIN_DIR . 'readme.txt';
$readme_content = '';
$description = '';
$changelog = '';
$faq = '';
$installation = '';
$screenshots = '';
if (file_exists($readme_file) && $our_plugin) {
$readme_content = file_get_contents($readme_file);
// Extract description
if (preg_match('/== Description ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
$description = trim($matches[1]);
}
// Extract changelog
if (preg_match('/== Changelog ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
$changelog = trim($matches[1]);
}
// Extract FAQ
if (preg_match('/== Frequently Asked Questions ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
$faq = trim($matches[1]);
}
// Extract installation
if (preg_match('/== Installation ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
$installation = trim($matches[1]);
}
// Extract screenshots
if (preg_match('/== Screenshots ==(.+?)(?:==|$)/s', $readme_content, $matches)) {
$screenshots = trim($matches[1]);
}
} else {
// Fallback content if readme.txt doesn't exist or for missing plugins
$changelog = '<h2>' . FPDEN_VERSION . '</h2><ul><li>Fixed: Plugin details popup version display issue with Git Updater integration</li><li>Added: JavaScript-based solution to ensure correct version display in plugin details</li><li>Improved: Version consistency across all plugin views</li><li>Enhanced: Cache busting for plugin information API</li></ul>';
}
// Set description based on whether this is our plugin or a missing plugin
if ($our_plugin) {
$description = !empty($description) ? wpautop($description) : 'Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.';
} else {
$description = sprintf(
__('This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Use the "Remove Notice" link on the plugins page to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices'),
'<code>/wp-content/plugins/</code>'
);
}
// Prepare sections
$new_result->sections = array(
'description' => $description,
'changelog' => !empty($changelog) ? wpautop($changelog) : $changelog,
'faq' => !empty($faq) ? wpautop($faq) : '<h3>Is it safe to remove plugin references?</h3><p>Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists.</p>',
);
// Add installation section if available
if (!empty($installation)) {
$new_result->sections['installation'] = wpautop($installation);
}
// Add screenshots section if available
if (!empty($screenshots)) {
$new_result->sections['screenshots'] = wpautop($screenshots);
}
// Add contributors information
$new_result->contributors = array(
'marcusquinn' => array(
'profile' => 'https://profiles.wordpress.org/marcusquinn/',
'avatar' => 'https://secure.gravatar.com/avatar/',
'display_name' => 'Marcus Quinn'
),
'wpallstars' => array(
'profile' => 'https://profiles.wordpress.org/wpallstars/',
'avatar' => 'https://secure.gravatar.com/avatar/',
'display_name' => 'WPALLSTARS'
)
);
// Add a random number and timestamp to force cache refresh
$new_result->download_link = 'https://www.wpallstars.com/plugins/wp-fix-plugin-does-not-exist-notices.zip?v=' . FPDEN_VERSION . '&cb=' . mt_rand(1000000, 9999999) . '&t=' . time();
// Add active installations count
$new_result->active_installs = 1000;
// Add rating information
$new_result->rating = 100;
$new_result->num_ratings = 5;
$new_result->ratings = array(
5 => 5,
4 => 0,
3 => 0,
2 => 0,
1 => 0
);
// Add homepage and download link
$new_result->homepage = 'https://www.wpallstars.com';
// Set no caching
$new_result->cache_time = 0;
// Return our completely new result object
return $new_result;
}
return $result;
}
/**
* Check if a slug matches one of our missing plugins.
*
* @param string $slug The plugin slug to check.
* @param array $invalid_plugins List of invalid plugin paths.
* @return bool True if the slug matches a missing plugin.
*/
private function is_missing_plugin($slug, $invalid_plugins) {
foreach ($invalid_plugins as $plugin_file) {
// Extract the plugin slug from the plugin file path
$plugin_slug = dirname($plugin_file);
if ('.' === $plugin_slug) {
$plugin_slug = basename($plugin_file, '.php');
}
if ($slug === $plugin_slug) {
return true;
}
}
return false;
}
/**
* Prevent WordPress from caching our plugin API responses.
*
* @param object|WP_Error $result The result object or WP_Error.
* @param string $action The type of information being requested.
* @param object $args Plugin API arguments.
* @return object|WP_Error The result object or WP_Error.
*/
public function prevent_plugins_api_caching($result, $action, $args) {
// Only modify plugin_information requests
if ('plugin_information' !== $action) {
return $result;
}
// Check if we have a slug to work with
if (empty($args->slug)) {
return $result;
}
// Get our list of invalid plugins
$invalid_plugins = $this->get_invalid_plugins();
// Check if the requested plugin is one of our missing plugins
foreach ($invalid_plugins as $plugin_file) {
// Extract the plugin slug from the plugin file path
$plugin_slug = dirname($plugin_file);
if ('.' === $plugin_slug) {
$plugin_slug = basename($plugin_file, '.php');
}
// If this is one of our missing plugins, prevent caching
if ($args->slug === $plugin_slug) {
// Add a filter to prevent caching of this response
add_filter('plugins_api_result_' . $args->slug, '__return_false');
// Add a timestamp to force cache busting
if (is_object($result)) {
$result->last_updated = current_time('mysql');
$result->cache_time = 0;
}
}
}
return $result;
}
/**
* Clear plugin API cache when viewing the plugins page.
*
* @return void
*/
public function maybe_clear_plugin_api_cache() {
// Only run on the plugins page
if (!$this->is_plugins_page()) {
return;
}
// Get our list of invalid plugins
$invalid_plugins = $this->get_invalid_plugins();
// Clear transients for each invalid plugin
foreach ($invalid_plugins as $plugin_file) {
// Extract the plugin slug from the plugin file path
$plugin_slug = dirname($plugin_file);
if ('.' === $plugin_slug) {
$plugin_slug = basename($plugin_file, '.php');
}
// Delete all possible transients for this plugin
delete_transient('plugins_api_' . $plugin_slug);
delete_site_transient('plugins_api_' . $plugin_slug);
delete_transient('plugin_information_' . $plugin_slug);
delete_site_transient('plugin_information_' . $plugin_slug);
// Clear any other transients that might be caching plugin info
$this->clear_all_plugin_transients();
}
// Also clear our own plugin's cache
$this->clear_own_plugin_cache();
}
/**
* Clear all plugin-related transients that might be caching information.
*
* @return void
*/
private function clear_all_plugin_transients() {
// Clear update cache
delete_site_transient('update_plugins');
delete_site_transient('update_themes');
delete_site_transient('update_core');
// Clear plugins API cache
delete_site_transient('plugin_information');
// Clear plugin update counts
delete_transient('plugin_updates_count');
delete_site_transient('plugin_updates_count');
// Clear plugin slugs cache
delete_transient('plugin_slugs');
delete_site_transient('plugin_slugs');
}
/**
* Clear cache specifically for our own plugin.
*
* @return void
*/
private function clear_own_plugin_cache() {
// Clear our own plugin's cache (both old and new slugs)
$our_slugs = array('wp-fix-plugin-does-not-exist-notices', 'fix-plugin-does-not-exist-notices');
foreach ($our_slugs as $slug) {
delete_transient('plugins_api_' . $slug);
delete_site_transient('plugins_api_' . $slug);
delete_transient('plugin_information_' . $slug);
delete_site_transient('plugin_information_' . $slug);
}
// Clear plugin update transients
delete_site_transient('update_plugins');
delete_site_transient('plugin_information');
// Force refresh of plugin update information if function exists
if (function_exists('wp_clean_plugins_cache')) {
wp_clean_plugins_cache(true);
}
// Clear object cache if function exists
if (function_exists('wp_cache_flush')) {
wp_cache_flush();
}
}
}
-167
View File
@@ -1,167 +0,0 @@
<?php
/**
* Modal Functionality
*
* @package WPALLSTARS\FixPluginDoesNotExistNotices
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
/**
* Modal Class
*
* Handles the update source selector modal.
*/
class Modal {
/**
* Constructor
*/
public function __construct() {
// Add filter for plugin action links to add our update source selector
add_filter('plugin_action_links_' . plugin_basename(FPDEN_PLUGIN_DIR . 'wp-fix-plugin-does-not-exist-notices.php'), array($this, 'add_update_source_link'));
// Add AJAX handler for saving update source
add_action('wp_ajax_fpden_save_update_source', array($this, 'save_update_source'));
// Add the update source modal to admin footer
add_action('admin_footer', array($this, 'add_update_source_modal'));
}
/**
* Add the "Update Source" link to plugin action links
*
* @param array $links Array of plugin action links
* @return array Modified array of plugin action links
*/
public function add_update_source_link($links) {
if (!current_user_can('manage_options')) {
return $links;
}
// Get current update source
$current_source = get_option('fpden_update_source', 'auto');
// Add a badge to show the current source
$badge_class = 'fpden-source-badge ' . $current_source;
$badge_text = ucfirst($current_source);
if ($current_source === 'auto') {
$badge_text = 'Auto';
} elseif ($current_source === 'wordpress.org') {
$badge_text = 'WP.org';
}
// Add the link with the badge
$update_source_link = '<a href="#" class="fpden-update-source-toggle">Update Source <span class="' . $badge_class . '">' . $badge_text . '</span></a>';
$links[] = $update_source_link;
return $links;
}
/**
* Add the update source modal to the admin footer
*/
public function add_update_source_modal() {
if (!is_admin() || !current_user_can('manage_options')) {
return;
}
// Only show on plugins page
$screen = get_current_screen();
if (!$screen || $screen->id !== 'plugins') {
return;
}
// Get current source
$current_source = get_option('fpden_update_source', 'auto');
// Enqueue the CSS and JS
wp_enqueue_style(
'fpden-update-source-selector',
FPDEN_PLUGIN_URL . 'admin/css/update-source-selector.css',
array(),
FPDEN_VERSION
);
wp_enqueue_script(
'fpden-update-source-selector',
FPDEN_PLUGIN_URL . 'admin/js/update-source-selector.js',
array('jquery'),
FPDEN_VERSION,
true
);
// Add nonce to the existing fpdenData object or create it if it doesn't exist
$nonce = wp_create_nonce('fpden_update_source');
wp_localize_script(
'fpden-update-source-selector',
'fpdenData',
array(
'updateSourceNonce' => $nonce,
)
);
// Modal HTML
?>
<div id="fpden-update-source-modal">
<a href="#" class="fpden-close-modal" aria-label="Close modal">×</a>
<h2>Choose Update Source</h2>
<p>Select where you want to receive plugin updates from:</p>
<form id="fpden-update-source-form">
<label>
<input type="radio" name="update_source" value="wordpress.org" <?php checked($current_source, 'wordpress.org'); ?>>
<a href="https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/" target="_blank" rel="noopener noreferrer">WordPress.org</a>
<span class="fpden-source-description">Updates from the official WordPress.org plugin repository. Has a version update delay, to allow for the WP.org policy review and approval process. Best for unmonitored auto-updates.</span>
</label>
<label>
<input type="radio" name="update_source" value="github" <?php checked($current_source, 'github'); ?>>
<a href="https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices" target="_blank" rel="noopener noreferrer">GitHub</a>
<span class="fpden-source-description">Update directly from the GitHub repo main branch for the latest stable release. Git Updater plugin must be installed & active. Best for monitored updates, where the latest features and fixes are required as soon as they are merged into the main branch.</span>
</label>
<label>
<input type="radio" name="update_source" value="gitea" <?php checked($current_source, 'gitea'); ?>>
<a href="https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices" target="_blank" rel="noopener noreferrer">Gitea</a>
<span class="fpden-source-description">Update directly from the Gitea repo main branch for the latest stable release. Git Updater plugin must be installed & active. Best for monitored updates, where the latest features and fixes are required as soon as they are merged into the main branch, and independence from big-tech.</span>
</label>
<div class="fpden-submit-container">
<button type="submit" class="button button-primary">Save</button>
</div>
</form>
</div>
<?php
}
/**
* Handle AJAX request to save update source
*/
public function save_update_source() {
// Check nonce
check_ajax_referer('fpden_update_source', 'nonce');
// Check permissions
if (!current_user_can('manage_options')) {
wp_send_json_error('Permission denied');
}
// Get and sanitize source
$source = isset($_POST['source']) ? sanitize_text_field($_POST['source']) : '';
// Validate source
$valid_sources = ['wordpress.org', 'github', 'gitea'];
if (!in_array($source, $valid_sources)) {
$source = ''; // Empty means use auto-detection
}
// Save option
update_option('fpden_update_source', $source);
// Clear update cache
delete_site_transient('update_plugins');
wp_send_json_success();
}
}
-293
View File
@@ -1,293 +0,0 @@
<?php
/**
* Main Plugin Class
*
* @package WPALLSTARS\FixPluginDoesNotExistNotices
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
/**
* Main Plugin Class
*
* Initializes all components of the plugin.
*/
class Plugin {
/**
* Plugin version
*
* @var string
*/
private $version;
/**
* Plugin file path
*
* @var string
*/
private $plugin_file;
/**
* Plugin directory path
*
* @var string
*/
private $plugin_dir;
/**
* Plugin directory URL
*
* @var string
*/
private $plugin_url;
/**
* Core functionality instance
*
* @var Core
*/
private $core;
/**
* Admin functionality instance
*
* @var Admin
*/
private $admin;
/**
* Updater instance
*
* @var Updater
*/
private $updater;
/**
* Constructor
*
* @param string $plugin_file Main plugin file path.
* @param string $version Plugin version.
*/
public function __construct($plugin_file, $version) {
$this->plugin_file = $plugin_file;
$this->version = $version;
$this->plugin_dir = plugin_dir_path($plugin_file);
$this->plugin_url = plugin_dir_url($plugin_file);
$this->define_constants();
$this->load_dependencies();
$this->init_components();
}
/**
* Define plugin constants
*
* @return void
*/
private function define_constants() {
if (!defined('FPDEN_VERSION')) {
define('FPDEN_VERSION', $this->version);
}
if (!defined('FPDEN_PLUGIN_DIR')) {
define('FPDEN_PLUGIN_DIR', $this->plugin_dir);
}
if (!defined('FPDEN_PLUGIN_URL')) {
define('FPDEN_PLUGIN_URL', $this->plugin_url);
}
}
/**
* Load dependencies
*
* @return void
*/
private function load_dependencies() {
// Load composer autoloader if it exists
$autoloader = $this->plugin_dir . 'vendor/autoload.php';
if (file_exists($autoloader)) {
require_once $autoloader;
}
// Load required files
require_once $this->plugin_dir . 'includes/Core.php';
require_once $this->plugin_dir . 'includes/Admin.php';
require_once $this->plugin_dir . 'includes/Modal.php';
}
/**
* Initialize plugin components
*
* @return void
*/
private function init_components() {
// Initialize core functionality
$this->core = new Core();
// Initialize admin functionality
$this->admin = new Admin($this->core);
// Initialize Git Updater fixes
$this->init_git_updater_fixes();
// Initialize the updater if the class exists
if (class_exists('\WPALLSTARS\FixPluginDoesNotExistNotices\Updater')) {
$this->updater = new Updater($this->plugin_file);
}
// Initialize the modal for update source selection
new Modal();
}
/**
* Initialize Git Updater fixes
*
* This function adds filters to fix Git Updater's handling of 'main' vs 'master' branches
*
* @return void
*/
private function init_git_updater_fixes() {
// Fix for Git Updater looking for 'master' branch instead of 'main'
add_filter('gu_get_repo_branch', array($this, 'override_branch'), 999, 3);
// Fix for Git Updater API URLs
add_filter('gu_get_repo_api', array($this, 'override_api_url'), 999, 3);
// Fix for Git Updater download URLs
add_filter('gu_download_link', array($this, 'override_download_link'), 999, 3);
// Fix for Git Updater repository metadata
add_filter('gu_get_repo_meta', array($this, 'override_repo_meta'), 999, 2);
// Fix for Git Updater API responses
add_filter('gu_api_repo_type_data', array($this, 'override_repo_type_data'), 999, 3);
}
/**
* Override the branch name for our plugin
*
* @param string $branch The current branch name
* @param string $git The git service (github, gitlab, etc.)
* @param object|null $repo The repository object (optional)
* @return string The modified branch name
*/
public function override_branch($branch, $git, $repo = null) {
// If repo is null or not an object, just return the branch unchanged
if (!is_object($repo)) {
return $branch;
}
if (isset($repo->slug) &&
(strpos($repo->slug, 'wp-fix-plugin-does-not-exist-notices') !== false ||
strpos($repo->slug, 'fix-plugin-does-not-exist-notices') !== false)) {
return 'main';
}
return $branch;
}
/**
* Override the API URL for our plugin
*
* @param mixed $api_url The current API URL (can be string or object)
* @param string $git The git service (github, gitlab, etc.)
* @param object|null $repo The repository object (optional)
* @return mixed The modified API URL (same type as input)
*/
public function override_api_url($api_url, $git, $repo = null) {
// If repo is null or not an object, just return the URL unchanged
if (!is_object($repo)) {
return $api_url;
}
// Check if this is our plugin
if (isset($repo->slug) &&
(strpos($repo->slug, 'wp-fix-plugin-does-not-exist-notices') !== false ||
strpos($repo->slug, 'fix-plugin-does-not-exist-notices') !== false)) {
// Only apply str_replace if $api_url is a string
if (is_string($api_url)) {
return str_replace('/master/', '/main/', $api_url);
}
// If $api_url is an object, just return it unchanged
// This handles the case where Git Updater passes a GitHub_API object
return $api_url;
}
// Return unchanged if not our plugin
return $api_url;
}
/**
* Override the download link for our plugin
*
* @param string $download_link The current download link
* @param string $git The git service (github, gitlab, etc.)
* @param object|null $repo The repository object (optional)
* @return string The modified download link
*/
public function override_download_link($download_link, $git, $repo = null) {
// If repo is null or not an object, just return the link unchanged
if (!is_object($repo)) {
return $download_link;
}
if (isset($repo->slug) &&
(strpos($repo->slug, 'wp-fix-plugin-does-not-exist-notices') !== false ||
strpos($repo->slug, 'fix-plugin-does-not-exist-notices') !== false)) {
return str_replace('/master.zip', '/main.zip', $download_link);
}
return $download_link;
}
/**
* Override repository metadata for our plugin
*
* @param array $repo_meta The repository metadata
* @param object $repo The repository object
* @return array The modified repository metadata
*/
public function override_repo_meta($repo_meta, $repo) {
if (isset($repo->slug) &&
(strpos($repo->slug, 'wp-fix-plugin-does-not-exist-notices') !== false ||
strpos($repo->slug, 'fix-plugin-does-not-exist-notices') !== false)) {
// Set the correct repository information
$repo_meta['github_updater_repo'] = 'wp-fix-plugin-does-not-exist-notices';
$repo_meta['github_updater_branch'] = 'main';
$repo_meta['github_updater_api'] = 'https://api.github.com';
$repo_meta['github_updater_raw'] = 'https://raw.githubusercontent.com/wpallstars/wp-fix-plugin-does-not-exist-notices/main';
}
return $repo_meta;
}
/**
* Override repository type data for our plugin
*
* @param array $data The repository data
* @param object $response The API response
* @param object|null $repo The repository object (optional)
* @return array The modified repository data
*/
public function override_repo_type_data($data, $response, $repo = null) {
// If repo is null or not an object, just return the data unchanged
if (!is_object($repo)) {
return $data;
}
// Check if this is our plugin
if (isset($repo->slug) &&
(strpos($repo->slug, 'wp-fix-plugin-does-not-exist-notices') !== false ||
strpos($repo->slug, 'fix-plugin-does-not-exist-notices') !== false)) {
// Set the correct branch
if (isset($data['branch'])) {
$data['branch'] = 'main';
}
// Set the correct version
if (isset($data['version'])) {
$data['version'] = FPDEN_VERSION;
}
}
return $data;
}
}
+16 -64
View File
@@ -3,17 +3,13 @@
* Plugin Updater
*
* @package FixPluginDoesNotExistNotices
* @noinspection PhpUndefinedFunctionInspection
* @noinspection PhpUndefinedClassInspection
*/
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
use function add_filter;
namespace WPAllStars\FixPluginDoesNotExistNotices;
/**
* Class Updater
*
*
* Handles plugin updates from different sources based on installation origin.
*/
class Updater {
@@ -61,17 +57,9 @@ class Updater {
* @return string Installation source: 'github', 'gitea', or 'wordpress.org'
*/
private function determine_installation_source() {
// Check for user preference first
$user_preference = \get_option('fpden_update_source', '');
// If user has set a preference, use it
if (!empty($user_preference)) {
return $user_preference;
}
// Otherwise, auto-detect the installation source
$source = 'wordpress.org'; // Default to WordPress.org if unidentifiable
// Default to WordPress.org
$source = 'wordpress.org';
// Check if the plugin was installed from GitHub
if ($this->is_github_installation()) {
$source = 'github';
@@ -80,7 +68,7 @@ class Updater {
elseif ($this->is_gitea_installation()) {
$source = 'gitea';
}
return $source;
}
@@ -88,12 +76,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')) {
$git_config = @file_get_contents($plugin_dir . '.git/config');
@@ -101,12 +88,12 @@ class Updater {
return true;
}
}
// Check for GitHub-specific files that might indicate it was downloaded from GitHub
if (file_exists($plugin_dir . '.github')) {
return true;
}
return false;
}
@@ -114,12 +101,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')) {
$git_config = @file_get_contents($plugin_dir . '.git/config');
@@ -127,7 +113,7 @@ class Updater {
return true;
}
}
return false;
}
@@ -135,8 +121,6 @@ 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)
@@ -151,47 +135,15 @@ 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') {
return 'https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // GitHub repository URL
return 'https://wpallstars.com'; // GitHub update server
} elseif ($this->source === 'gitea') {
return 'https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // Gitea repository URL
return 'https://wpallstars.com'; // Gitea update server
}
return '';
});
// Add filter to trigger Git Updater cache refresh when a version update is detected
\add_filter('site_transient_update_plugins', function($transient) {
// Check if our plugin has an update
$plugin_basename = \plugin_basename($this->plugin_file);
if (isset($transient->response) && isset($transient->response[$plugin_basename])) {
// Check if Git Updater is active by looking for its functions
if (function_exists('\\Fragen\\Git_Updater\\flush_git_updater_cache') ||
class_exists('\\Fragen\\Git_Updater\\API\\API')) {
// Try to call the flush cache function if it exists
if (function_exists('\\Fragen\\Git_Updater\\flush_git_updater_cache')) {
\Fragen\Git_Updater\flush_git_updater_cache();
} elseif (class_exists('\\Fragen\\Git_Updater\\API\\API')) {
// Try to use the API class if available
try {
$api = new \Fragen\Git_Updater\API\API();
if (method_exists($api, 'flush_cache_site_transient')) {
$api->flush_cache_site_transient();
}
} catch (\Exception $e) {
// Silently fail if API class can't be instantiated
}
}
// Also delete the update plugins transient to force a refresh
\delete_site_transient('update_plugins');
}
}
return $transient;
});
// Initialize Git Updater Lite
if (class_exists('\\Fragen\\Git_Updater\\Lite')) {
(new \Fragen\Git_Updater\Lite($this->plugin_file))->run();
@@ -0,0 +1,114 @@
# Copyright (C) 2024 Marcus Quinn
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.0\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"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"X-Generator: WP-CLI 2.8.1\n"
"X-Domain: fix-plugin-does-not-exist-notices\n"
#. Plugin Name of the plugin
msgid "Fix 'Plugin file does not exist.' Notices"
msgstr ""
#. Plugin URI of the plugin
msgid "https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/"
msgstr ""
#. Description of the plugin
msgid "Adds missing plugins to the plugins list with a \"Remove Reference\" link so you can permanently clean up invalid plugin entries and remove error notices."
msgstr ""
#. Author of the plugin
msgid "Marcus Quinn"
msgstr ""
#. Author URI of the plugin
msgid "https://www.wpallstars.com"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:127
msgid "Click here to scroll to missing plugins"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:128
msgid "Plugin file missing"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:129
#: fix-plugin-does-not-exist-notices.php:205
msgid "Remove Reference"
msgstr ""
#. translators: %s: Path to wp-content/plugins
#: fix-plugin-does-not-exist-notices.php:161
msgid "This plugin is still marked as \"Active\" in your database — but its folder and files can't be found in %s. Click \"Remove Reference\" to permanently remove it from your active plugins list and eliminate the error notice."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:164
msgid "N/A"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:168
msgid "Missing"
msgstr ""
#. translators: %s: Plugin file path
#: fix-plugin-does-not-exist-notices.php:204
msgid "Remove reference to missing plugin %s"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:227
msgid "You do not have sufficient permissions to perform this action."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:233
msgid "Invalid plugin specified."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:308
msgid "Plugin reference removed successfully."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:316
msgid "Failed to remove plugin reference. The plugin may already have been removed, or there was a database issue."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:331
msgid "Fix Plugin Does Not Exist Notices"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:333
msgid "Missing plugin files detected:"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:334
msgid "The plugins listed below with a"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:335
msgid "File Missing"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:336
msgid "tag no longer exist but are still referenced in your database."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:339
msgid "How to fix:"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:340
msgid "Click the \"Remove Reference\" link next to each missing plugin to safely remove it from your active plugins list."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:342
msgid "This will clean up your database and remove the error notifications."
msgstr ""
@@ -1,59 +0,0 @@
# Copyright (C) 2024 Marcus Quinn & WP ALLSTARS
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.1.1\n"
"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"POT-Creation-Date: 2025-04-13T00:00:00+00:00\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"X-Generator: WP-CLI 2.9.0\n"
"X-Domain: wp-fix-plugin-does-not-exist-notices\n"
#. Plugin Name of the plugin
msgid "Fix 'Plugin file does not exist' Notices"
msgstr ""
#. Plugin URI of the plugin
msgid "https://www.wpallstars.com"
msgstr ""
#. Description of the plugin
msgid "Adds missing plugins to your plugins list with a \"Remove Notice\" action link, allowing you to safely clean up invalid plugin references."
msgstr ""
#. Author of the plugin
msgid "Marcus Quinn & WP ALLSTARS"
msgstr ""
#. Author URI of the plugin
msgid "https://www.wpallstars.com"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:168
msgid "This plugin is still marked as \"Active\" in your database — but its folder and files can't be found in %s. Click \"Remove Notice\" to permanently remove it from your active plugins list and eliminate the error notice."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:227
msgid "Remove Notice"
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:264
msgid "Invalid plugin specified."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:318
msgid "Plugin reference removed successfully."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:325
msgid "Failed to remove plugin reference. Please try again."
msgstr ""
#: wp-fix-plugin-does-not-exist-notices.php:456
msgid "This plugin is still marked as \"Active\" in your database — but its folder and files can't be found in %s. Use the \"Remove Notice\" link on the plugins page to permanently remove it from your active plugins list and eliminate the error notice."
msgstr ""
+21 -450
View File
@@ -1,15 +1,15 @@
=== Fix 'Plugin file does not exist.' Notices ===
Contributors: surferking, wpallstars
Donate link: https://www.wpallstars.com/
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist, wordpress error, plugin error, deactivated plugin, remove plugin reference, fix plugin error, plugin does not exist, plugin file does not exist error
Contributors: marcusquinn
Donate link: https://www.wpallstars.com
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist
Requires at least: 5.0
Tested up to: 6.7.2
Tested up to: 6.4
Requires PHP: 7.0
Stable tag: 2.2.0
Stable tag: 1.6.0
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WPALLSTARS (wpallstars.com).
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
== Description ==
@@ -17,19 +17,16 @@ 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 Notice" link, allowing you to safely clean up invalid plugin entries with one click.
**Note:** This plugin doesn't have a settings page. Its functionality is limited to running on the WordPress admin plugins page only.
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.
= Key Features =
* Adds missing plugins directly to your plugins list
* Provides a simple "Remove Notice" action link
* Provides a simple "Remove Reference" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
* Clean, user-friendly interface following WordPress design patterns
* Integrated Git Updater branch fix (changes 'master' to 'main' for proper updates)
= How It Works =
@@ -37,10 +34,8 @@ 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 Notice" link to safely remove them
3. Provides a "Remove Reference" 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,79 +44,12 @@ When WordPress detects a plugin file that no longer exists but is still referenc
* You've migrated from another site and have leftover plugin references
* Your hosting provider removed a plugin but didn't clean the database
= Support & Feedback =
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
= Reviews =
This utility plugin is released under the GPLv2 license as free open source software.
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org.
Your experience and feedback helps others discover the plugin, and encourages continued community-driven, open-source development and support.
= Contributing =
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository on [GitHub](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/) or [Gitea](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/)
2. Create your feature branch: `git checkout -b feature/amazing-feature`
3. Commit your changes: `git commit -m 'Add some amazing feature'`
4. Push to the branch: `git push origin feature/amazing-feature`
5. Submit a pull request
The plugin is designed to be a best-practice example for WordPress plugin development and can be used as a boilerplate for your own plugins.
== Installation ==
1. Upload the `wp-fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
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 Notice" links
= Using with Git Updater =
If you've installed this plugin from GitHub or Gitea, you'll need Git Updater to receive updates:
1. Install the Git Updater plugin from [https://git-updater.com/git-updater/](https://git-updater.com/git-updater/)
2. Go to Settings > Git Updater > Remote Management
3. Click the "Refresh Cache" button to ensure Git Updater recognizes the latest version
4. Updates will now appear in your WordPress dashboard when available
= Choosing Your Update Source =
This plugin allows you to choose where you want to receive updates from:
1. In the Plugins list, find "Fix 'Plugin file does not exist' Notices"
2. Click the "Update Source" link next to the plugin
3. Select your preferred update source:
* **WordPress.org**: Updates from the official WordPress.org repository (has a version update delay due to the WP.org policy review and approval process, best for unmonitored auto-updates)
* **GitHub**: Updates directly from the GitHub repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates where the latest features and fixes are needed immediately)
* **Gitea**: Updates directly from the Gitea repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates and independence from big-tech)
4. Click "Save" to apply your preference
If no preference is set, the plugin will automatically use the source it was installed from.
**Note:** GitHub and Gitea options require the Git Updater plugin to be installed and activated.
== Contributing ==
Contributions are welcome! Please follow these steps to set up a development environment:
1. Install [LocalWP](https://localwp.com/) and create a clean site called "Plugin Testing" using the "Preferred" setup option
2. Run "Site shell" once from the LocalWP page on the site's settings to ensure wp-cli is enabled
3. Run "Add Run Configurations to VS Code" to update site configuration files in: ~/Local/plugin-testing/conf/
4. Clone this repository to your local machine
5. Use the build.sh and deploy-local.sh scripts to build and deploy the plugin for testing
[AugmentCode.com](https://augmentcode.com/) is recommended as a good all-in-one AI IDE for plugin development and testing.
Please feel free to submit a Pull Request with your improvements.
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Reference" links
== Frequently Asked Questions ==
@@ -139,7 +67,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 Notice" 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 Reference" 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? =
@@ -153,297 +81,14 @@ 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. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
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
== Changelog ==
= 2.2.0 =
* Added: Completely refactored plugin to use OOP best practices
* Added: New class structure with proper namespaces
* Added: Improved code organization and maintainability
* Added: Better separation of concerns with dedicated classes
* Changed: "Choose Update Source" link to just "Update Source"
* Fixed: Close button in the update source modal
* Added: Links to the main page for each update source in the modal
* Changed: Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
= 2.1.1 =
* Added: New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
* Added: Modal dialog with detailed information about each update source option
* Added: Visual indicator showing the currently selected update source
* Fixed: Updated heading styles in CHANGELOG.md for better readability
* Fixed: Corrected dates in changelog to use 2025 instead of 2024
* Improved: Documentation improvements for better clarity
* Improved: Enhanced Git Updater integration with user-selectable update sources
= 2.1.0 =
* Minor version bump for Git Updater compatibility
* Improved error handling for Git Updater integration
* Enhanced type checking in branch fix functions
* Updated documentation for Git Updater installation and cache refreshing
= 2.0.13 =
* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
* Improved: Type checking in branch fix functions to handle both string and object inputs
* Enhanced: Error handling for Git Updater integration
* Removed: Redundant GU Branch Fix plugin (fully integrated into main plugin)
= 2.0.12 =
* Fixed: Integrated Git Updater branch fix directly into main plugin
* Removed: Separate "GU Branch Fix" plugin (no longer needed)
* Updated: Deploy script to remove separate branch fix plugin
* Added: Documentation explaining branch fix integration
* Improved: Compatibility with Git Updater plugin
= 2.0.11 =
* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
* Added: Deploy script for local testing
* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
* Improved: Compatibility with Git Updater plugin
= 2.0.10 =
* Fixed: Plugin details popup version display issue with Git Updater integration
* Added: JavaScript-based solution to ensure correct version display in plugin details
* Improved: Version consistency across all plugin views
* Enhanced: Cache busting for plugin information API
= 2.0.9 =
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Support for both old and new plugin slugs to fix caching issues
* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
* Enhanced: Version display in plugin details popup
= 2.0.8 =
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
* Improved: Author and contributor information display in plugin details
= 2.0.7 =
* Additional text improvements and minor fixes
= 2.0.6 =
* Text improvements and minor fixes
= 2.0.5 =
* Fixed: Display correct version in plugin details popup
= 2.0.4 =
* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
= 2.0.2 =
* Consolidated WordPress.org assets into .wordpress-org directory
* Improved organization of assets for WordPress.org submission
* Updated .wordpress-org/README.md with comprehensive information
= 2.0.1 =
* Added Contributing section to readme.txt
* Updated "tested up to" version to WordPress 6.7.2
* Added reference-plugins directory for plugin development inspiration
* Improved .gitattributes with comprehensive file handling
* Enhanced documentation organization
= 2.0.0 =
* Major version release for WordPress.org submission
* Added note clarifying that the plugin has no settings page
* Clarified that functionality is limited to the admin plugins page only
* Finalized all assets and documentation for public release
= 1.6.28 =
* Consolidated asset documentation into a single comprehensive guide
* Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
* Updated all asset README files to point to the main documentation
* Improved file organization and documentation structure
= 1.6.27 =
* Clarified RTL support in WordPress.org asset documentation
* Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
* Consolidated asset files and improved documentation
= 1.6.26 =
* Updated screenshot references to use a single comprehensive screenshot
* Fixed asset directory paths in documentation
* Improved ImageMagick conversion commands for icon generation
* Clarified WordPress.org SVN repository structure
= 1.6.25 =
* Consolidated asset files into their respective directories
* Created comprehensive WordPress.org submission guide
* Clarified SVN repository structure and asset requirements
* Improved organization of asset files
= 1.6.24 =
* Added properly named icon PNG files for WordPress.org submission
* Created icon-256x256.png and icon-128x128.png files
* Updated asset preparation documentation
= 1.6.23 =
* Prepared assets for WordPress.org plugin submission
* Added properly named icon, banner, and screenshot files
* Created comprehensive guide for WordPress.org asset requirements
* Fixed file naming to comply with WordPress.org standards
= 1.6.22 =
* Enhanced support section with multiple support channel options
* Added encouragement for users to leave reviews on WordPress.org
* Improved documentation with clearer support instructions
= 1.6.21 =
* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
* Updated documentation with links to supported AI IDEs
* Enhanced SEO with additional FAQs and keywords
* Made documentation more generic for boilerplate use
* Updated AI configuration files with modern models and better explanations
= 1.6.20 =
* Added explanations about the ! prefix in ignore files
* Moved WordPress-specific patterns to .gitignore
* Further improved organization of ignore patterns
* Added examples of how to include files excluded by .gitignore
= 1.6.19 =
* Consolidated common ignore patterns into .gitignore
* Simplified AI IDE configuration files to only include tool-specific patterns
* Improved organization of ignore patterns for better maintainability
* Added more file types to .gitignore for comprehensive coverage
= 1.6.18 =
* Optimized AI IDE configuration files to only include patterns not in .gitignore
* Improved efficiency of ignore files for better AI context management
* Enhanced compatibility with various AI-powered development tools
= 1.6.17 =
* Added .augmentignore file with best practices
* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
* Added more design file formats to .gitignore
* Added .aiconfig file for general AI IDE compatibility
= 1.6.16 =
* Updated CI configuration files with correct plugin slugs
* Updated CHANGELOG.md with all recent versions
* Fixed outdated references to plugin-reference-cleaner
= 1.6.15 =
* Moved AI workflow documentation to root directory for better visibility
* Consolidated duplicate workflow files
* Improved organization of development documentation
= 1.6.14 =
* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
* Improved explanation of how the plugin works
* Ensured consistent terminology across all documentation
= 1.6.13 =
* Code cleanup and optimization
* Improved Git Updater integration
* Fixed author display in plugin information
* Ensured compatibility with WordPress 6.4
= 1.6.12 =
* Added WP ALLSTARS as a co-author
* Updated author information and links
* Added author websites to plugin description
* Fixed issue with multiple author URLs
= 1.6.11 =
* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
* Simplified plugin functionality to focus on core features only
* Improved compatibility with various WordPress configurations
* Ensured plugin works correctly when other plugins are deleted
= 1.6.10 =
* Fixed critical error that could occur when a plugin folder is deleted
* Improved error handling with try/catch blocks
* Added more specific checks for the plugins page
* Enhanced compatibility with various WordPress configurations
* Made the code more defensive to prevent potential issues
= 1.6.9 =
* Fixed issue with notices not appearing below WordPress error messages
* Improved JavaScript detection of WordPress error notices
* Prevented WordPress from automatically clearing error notices on page refresh
* Added multiple timing attempts to ensure notices appear correctly
* Enhanced error notice targeting for better compatibility
= 1.6.8 =
* Fixed notice positioning to appear directly below WordPress error messages
* Improved notice width to match WordPress error messages
* Updated explanatory text for better clarity
* Fixed issue with notices not appearing in some cases
* Improved JavaScript detection of WordPress error messages
= 1.6.7 =
* Fixed duplicate notices issue by removing PHP-generated notice
* Simplified notice system to only show one notice below WordPress error
* Ensured consistent terminology with "Remove Notice" text
* Optimized plugin detection with caching to improve performance
* Fixed JavaScript to correctly handle multiple error messages
= 1.6.6 =
* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
* Fixed issue with automatic removal of plugin references without user action
* Fixed notice positioning to ensure it appears below error messages
* Restored pointer triangle to indicate relationship with error message
* Improved detection of missing plugins in the plugin list
* Enhanced scroll functionality to work with all plugin types
= 1.6.5 =
* Fixed duplicate notices issue - now only one notice appears below error messages
* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
* Updated explanatory text to be more clear about the removal process
* Changed "Remove Reference" link text to "Remove Notice" for better clarity
* Made "(File Missing)" text bold and red for better visibility
* Fixed scroll functionality to work with all plugin rows
* Improved JavaScript to prevent multiple notices from appearing
= 1.6.4 =
* Updated version management to ensure consistent patch version increments
* Improved documentation for version update process
* Enhanced AI workflow files with detailed version increment instructions
= 1.6.3 =
* Fixed Git Updater repository URLs to use full repository paths
* Corrected Update URI configuration for proper update detection
* Improved version management following semantic versioning
* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
= 1.6.2 =
* Updated POT file version for consistency
* Improved JavaScript localization with proper fallbacks
* Enhanced code quality for WordPress.org submission
* Added Git Updater configuration with Update URI
* Added update server URL configuration
= 1.6.1 =
* Added AI assistant guide and workflow documentation
* Added detailed release process documentation
* Added feature development guidelines
* Added bug fixing procedures
* Added code review standards
= 1.6.0 =
* Added full translation support with POT file
* Added JavaScript localization for better multilingual support
@@ -464,7 +109,7 @@ Manually editing the WordPress database is risky and requires technical knowledg
= 1.4.0 =
* Updated plugin name and text domain
* Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
* Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
= 1.3.3 =
* Improved notification placement next to WordPress error messages
@@ -525,84 +170,6 @@ Manually editing the WordPress database is risky and requires technical knowledg
== Upgrade Notice ==
= 2.1.1 =
Added new "Choose Update Source" feature allowing you to select where to receive plugin updates from (WordPress.org, GitHub, or Gitea).
= 2.1.0 =
Minor version bump with improved Git Updater compatibility and error handling.
= 2.0.2 =
Improved organization of assets for WordPress.org submission.
= 2.0.1 =
Improved documentation with Contributing section and updated WordPress compatibility to 6.7.2.
= 2.0.0 =
Major version release for WordPress.org submission with improved documentation and clarification about plugin functionality.
= 1.6.28 =
Improved asset documentation and clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode.
= 1.6.27 =
Clarified RTL support in WordPress.org asset documentation and improved asset organization.
= 1.6.26 =
Updated screenshot references and improved WordPress.org submission documentation.
= 1.6.25 =
Improved organization of asset files and created comprehensive WordPress.org submission guide.
= 1.6.24 =
Added properly named icon PNG files for WordPress.org submission.
= 1.6.23 =
Prepared assets for WordPress.org plugin submission with properly named icon, banner, and screenshot files.
= 1.6.22 =
Improved support documentation with multiple support channel options and encouragement for users to leave reviews.
= 1.6.21 =
Added support for more AI-powered development tools and enhanced documentation with links to supported AI IDEs.
= 1.6.20 =
Added explanations about using the ! prefix in ignore files to include files excluded by .gitignore.
= 1.6.19 =
Improved organization of ignore patterns with consolidated .gitignore and simplified AI IDE configuration files.
= 1.6.18 =
Optimized AI IDE configuration files for better efficiency and compatibility.
= 1.6.17 =
Added configuration files for AI-powered IDEs and improved compatibility with development tools.
= 1.6.16 =
Updated CI configuration files and fixed outdated references to the previous plugin name.
= 1.6.15 =
Improved organization of development documentation with consolidated AI workflow files.
= 1.6.14 =
Improved documentation with consistent terminology and better explanation of how the plugin works.
= 1.6.13 =
Code cleanup, improved Git Updater integration, and ensured compatibility with WordPress 6.4.
= 1.6.12 =
Added WP ALLSTARS as a co-author and updated author information.
= 1.6.11 =
URGENT CRITICAL FIX: Completely removes code that was causing fatal errors. If you're experiencing the "critical error" message, this update will resolve it.
= 1.6.3 =
Fixed Git Updater repository URLs and updated organization naming for consistent branding across all platforms!
= 1.6.2 =
Improved JavaScript localization, enhanced code quality, and added Git Updater configuration for seamless updates!
= 1.6.1 =
Added comprehensive AI assistant guide and workflow documentation for improved development processes!
= 1.6.0 =
Added full translation support and Git Updater compatibility for direct updates from GitHub and Gitea!
@@ -616,4 +183,8 @@ Major usability improvement with auto-scroll feature to help find missing plugin
Completely redesigned for better compatibility with all WordPress themes - now works with any WordPress installation!
= 1.2.2 =
Important stability fix - resolves timeout issues during plugin activation!
Important stability fix - resolves timeout issues during plugin activation!
== Support ==
For support, please visit https://wpallstars.com
-46
View File
@@ -1,46 +0,0 @@
#!/bin/bash
# Exit on error
set -e
# Define paths
PLUGIN_SLUG="wp-fix-plugin-does-not-exist-notices"
SOURCE_DIR="/Users/marcusquinn/Git/wp-fix-plugin-does-not-exist-notices/build/$PLUGIN_SLUG"
DEST_DIR="/Users/marcusquinn/Local/plugin-testing/app/public/wp-content/plugins/$PLUGIN_SLUG"
WP_CLI="/Users/marcusquinn/Local/plugin-testing/app/bin/wp"
# Check if build directory exists
if [ ! -d "$SOURCE_DIR" ]; then
echo "Build directory not found. Running build script first..."
cd /Users/marcusquinn/Git/wp-fix-plugin-does-not-exist-notices
./build.sh "$(grep -m 1 "Version:" wp-fix-plugin-does-not-exist-notices.php | awk -F': ' '{print $2}' | tr -d '[:space:]')"
# Exit if build failed
if [ ! -d "$SOURCE_DIR" ]; then
echo "❌ Build failed: Build directory was not created"
exit 1
fi
fi
# Check if destination directory exists, create if not
if [ ! -d "$DEST_DIR" ]; then
echo "Creating destination directory..."
mkdir -p "$DEST_DIR"
fi
# Rsync the plugin files to the local WordPress installation
echo "Deploying to local WordPress installation..."
rsync -av --delete "$SOURCE_DIR/" "$DEST_DIR/"
# Clear WordPress transients to ensure fresh plugin data
echo "Clearing WordPress transients..."
if [ -f "$WP_CLI" ]; then
cd /Users/marcusquinn/Local/plugin-testing/app/public
"$WP_CLI" transient delete --all
"$WP_CLI" cache flush
echo "✅ WordPress transients cleared"
else
echo "⚠️ WP-CLI not found, skipping transient clearing"
fi
echo "✅ Local deployment successful!"
echo "Plugin deployed to: $DEST_DIR"
-32
View File
@@ -1,32 +0,0 @@
<?php
/**
* Plugin Name: Fix 'Plugin file does not exist' Notices
* Plugin URI: https://www.wpallstars.com
* Description: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
* Version: 2.2.0
* Author: Marcus Quinn & The WPALLSTARS Team
* Author URI: https://www.wpallstars.com
* License: GPL-2.0+
* License URI: http://www.gnu.org/licenses/gpl-2.0.txt
* Text Domain: wp-fix-plugin-does-not-exist-notices
* Domain Path: /languages
* GitHub Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
* GitHub Branch: main
* Primary Branch: main
* Release Branch: main
* Release Asset: true
* Update URI: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
*
* @package WPALLSTARS\FixPluginDoesNotExistNotices
*/
// If this file is called directly, abort.
if (!defined('WPINC')) {
die;
}
// Load the main plugin class
require_once plugin_dir_path(__FILE__) . 'includes/Plugin.php';
// Initialize the plugin
new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '2.2.0');