Prepare release v2.1.0
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Plugin Asset Update / Push assets to WordPress.org (push) Has been cancelled
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 was successful

This commit is contained in:
2025-04-13 05:38:01 +01:00
parent c00bef482c
commit 389dc98a03
15 changed files with 486 additions and 281 deletions

View File

@ -23,11 +23,11 @@ All these files respect `.gitignore` patterns and only include additional tool-s
## Project Overview
- **Plugin Name**: [PLUGIN_NAME]
- **Repository**: [REPOSITORY_URL]
- **Description**: [PLUGIN_DESCRIPTION]
- **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 section should be updated with your specific plugin information. The current implementation is for the "Fix 'Plugin file does not exist.' Notices" plugin, which adds missing plugins to the plugins list with a "Remove Notice" link to clean up invalid plugin entries and remove error notices.
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
@ -75,6 +75,7 @@ When updating the version number, always update these files:
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.
@ -174,6 +175,27 @@ Before releasing:
3. Verify all features work as expected
4. Check for any PHP warnings or notices
### Local Testing Environment
- Local WordPress testing environment is at ~/Local/plugin-testing/app/public
- Plugin testing directory is at ~/Local/plugin-testing/app/public/wp-content/plugins
- WP-CLI is available at ~/Local/plugin-testing/app/bin/wp
- Debug logs can be found at ~/Local/plugin-testing/app/public/wp-content/uploads/debug-log-manager/ if the Debug Log Manager plugin is installed
### 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

View File

@ -36,7 +36,7 @@ git checkout -b v1.7.0
Update the version number in the following files:
#### a. Main Plugin File (fix-plugin-does-not-exist-notices.php)
#### a. Main Plugin File (wp-fix-plugin-does-not-exist-notices.php)
```php
/**
@ -73,15 +73,17 @@ Add a new section at the top of the CHANGELOG.md file:
- Bug fix 2
```
#### c. POT File (languages/fix-plugin-does-not-exist-notices.pot)
#### c. POT File (languages/wp-fix-plugin-does-not-exist-notices.pot)
Update the Project-Id-Version and POT-Creation-Date:
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"
"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:
@ -112,7 +114,7 @@ Brief description of the most important changes in this release
### 3. Commit Changes
```bash
git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt README.md languages/fix-plugin-does-not-exist-notices.pot
git 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}"
```
@ -154,7 +156,7 @@ git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
### 8. Monitor GitHub Actions
Open the GitHub Actions page to monitor the build and deployment process:
https://github.com/wpallstars/fix-plugin-does-not-exist-notices/actions
https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/actions
### 9. Verify Release

39
.drone.yml Normal file
View File

@ -0,0 +1,39 @@
kind: pipeline
type: docker
name: build-release
trigger:
event:
- tag
ref:
- refs/tags/v*
steps:
- name: build
image: alpine:latest
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/
- cd build
- zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
- cd ..
- name: release
image: plugins/gitea-release
settings:
api_key:
from_secret: gitea_token
base_url: https://gitea.wpallstars.com
files:
- wp-fix-plugin-does-not-exist-notices-*.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.

101
.gitattributes vendored Normal file
View File

@ -0,0 +1,101 @@
# This file configures how Git handles line endings and file types
# It is independent from .gitignore which controls which files are tracked
# Auto detect text files and perform LF normalization
* text=auto
# Text files that should be normalized with LF line endings
*.php text eol=lf
*.css text eol=lf
*.js text eol=lf
*.scss text eol=lf
*.htm text eol=lf
*.html text eol=lf
*.xml text eol=lf
*.txt text eol=lf
*.ini text eol=lf
*.inc text eol=lf
*.md text eol=lf
*.json text eol=lf
*.yml text eol=lf
*.yaml text eol=lf
*.po text eol=lf
*.pot text eol=lf
*.svg text eol=lf
.htaccess text eol=lf
# Files that should be treated as binary
*.png binary
*.jpg binary
*.jpeg binary
*.gif binary
*.ico binary
*.webp binary
*.zip binary
*.gz binary
*.tar binary
*.ttf binary
*.eot binary
*.woff binary
*.woff2 binary
*.pxd binary
*.afdesign binary
*.afphoto binary
*.afpub binary
# Exclude files from export (for WordPress.org SVN and distribution packages)
.gitattributes export-ignore
.gitignore export-ignore
.github export-ignore
.wordpress-org export-ignore
README.md export-ignore
CHANGELOG.md export-ignore
composer.json export-ignore
composer.lock export-ignore
package.json export-ignore
package-lock.json export-ignore
phpcs.xml export-ignore
.phpcs.xml export-ignore
phpunit.xml export-ignore
.phpunit.xml export-ignore
.distignore export-ignore
.editorconfig export-ignore
.eslintrc export-ignore
.eslintignore export-ignore
.prettierrc export-ignore
.prettierignore export-ignore
.stylelintrc export-ignore
.stylelintignore export-ignore
.travis.yml export-ignore
.gitlab-ci.yml export-ignore
bitbucket-pipelines.yml export-ignore
bin export-ignore
tests export-ignore
assets/icon/*.svg export-ignore
assets/banner/*.svg export-ignore
assets/screenshots/*.pxd export-ignore
assets/icon/*.pxd export-ignore
assets/banner/*.pxd export-ignore
# AI assistant and workflow files
.ai-assistant.md export-ignore
.ai-workflows export-ignore
.augmentignore export-ignore
.cursorignore export-ignore
.v0ignore export-ignore
.clinerc export-ignore
.continuerc export-ignore
reference-plugins export-ignore
# Set the default behavior for GitHub language detection
*.css linguist-language=CSS
*.js linguist-language=JavaScript
*.php linguist-language=PHP
*.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

24
.github/workflows/assets.yml vendored Normal file
View File

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

8
.gitignore vendored
View File

@ -152,12 +152,12 @@ wp-content/debug.log
# Development tools
.git/
.github/
# .github/ # Needed for GitHub Actions
.gitlab/
.gitattributes
# .gitattributes # Needed for file handling
.travis.yml
.drone.yml
.woodpecker.yml
# .drone.yml # Needed for Drone CI
# .woodpecker.yml # Needed for Woodpecker CI
codecov.yml
.babelrc
.browserslistrc

41
.woodpecker.yml Normal file
View File

@ -0,0 +1,41 @@
clone:
git:
image: woodpeckerci/plugin-git
debug: true
steps:
build:
image: alpine:latest
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
- cd build
- zip -r ../wp-fix-plugin-does-not-exist-notices-$VERSION.zip wp-fix-plugin-does-not-exist-notices
- cd ..
- echo "Build completed - wp-fix-plugin-does-not-exist-notices-$VERSION.zip"
- ls -la *.zip
release:
image: plugins/gitea-release
environment:
PLUGIN_API_KEY:
from_secret: gitea_token
PLUGIN_BASE_URL: https://gitea.wpallstars.com
PLUGIN_FILES: wp-fix-plugin-does-not-exist-notices-*.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."
test:
image: alpine:latest
commands:
- echo "Hello from Woodpecker CI"
- echo "Testing minimal configuration"
when:
event: [push, tag, pull_request]

View File

@ -2,400 +2,430 @@
All notable changes to this project will be documented in this file.
## [2.0.11] - 2024-05-19
### Added
#### [2.1.0] - 2024-05-20
##### 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] - 2024-05-20
##### 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] - 2024-05-19
##### 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] - 2024-05-19
##### Added
- Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
- Added deploy script for local testing
### Fixed
##### Fixed
- Git Updater branch issues with 'main' vs 'master' branch names
- Improved compatibility with Git Updater plugin
## [2.0.10] - 2024-05-18
### Fixed
#### [2.0.10] - 2024-05-18
##### Fixed
- Plugin details popup version display issue with Git Updater integration
- Added JavaScript-based solution to ensure correct version display in plugin details
### Improved
##### Improved
- Version consistency across all plugin views
- Enhanced cache busting for plugin information API
## [2.0.9] - 2024-05-18
### Fixed
#### [2.0.9] - 2024-05-18
##### 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
##### Improved
- Cache clearing mechanism to ensure plugin details are always up-to-date
- Enhanced version display in plugin details popup
## [2.0.8] - 2024-05-17
### Fixed
#### [2.0.8] - 2024-05-17
##### 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
##### Improved
- Author and contributor information display in plugin details
- Added WordPress 6.5 compatibility indicator
## [2.0.7] - 2024-05-17
### Changed
#### [2.0.7] - 2024-05-17
##### Changed
- Additional text improvements and minor fixes
## [2.0.6] - 2024-05-17
### Changed
#### [2.0.6] - 2024-05-17
##### Changed
- Text improvements and minor fixes
## [2.0.5] - 2024-05-17
### Fixed
#### [2.0.5] - 2024-05-17
##### Fixed
- Display correct version in plugin details popup
## [2.0.4] - 2024-05-17
### Fixed
#### [2.0.4] - 2024-05-17
##### Fixed
- Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
## [2.0.2] - 2024-05-17
### Changed
#### [2.0.2] - 2024-05-17
##### 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] - 2024-05-17
### Added
#### [2.0.1] - 2024-05-17
##### Added
- Contributing section to readme.txt
- reference-plugins directory for plugin development inspiration
### Changed
##### Changed
- Updated "tested up to" version to WordPress 6.7.2
- Improved .gitattributes with comprehensive file handling
- Enhanced documentation organization
## [2.0.0] - 2024-05-17
### Added
#### [2.0.0] - 2024-05-17
##### Added
- Note clarifying that the plugin has no settings page
- Clarification that functionality is limited to the admin plugins page only
### Changed
##### Changed
- Major version release for WordPress.org submission
- Finalized all assets and documentation for public release
## [1.6.28] - 2024-05-17
### Changed
#### [1.6.28] - 2024-05-17
##### Changed
- Consolidated asset documentation into a single comprehensive guide
- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
- Updated all asset README files to point to the main documentation
- Improved file organization and documentation structure
## [1.6.27] - 2024-05-17
### Changed
#### [1.6.27] - 2024-05-17
##### Changed
- Clarified RTL support in WordPress.org asset documentation
- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
- Consolidated asset files and improved documentation
## [1.6.26] - 2024-05-17
### Changed
#### [1.6.26] - 2024-05-17
##### Changed
- Updated screenshot references to use a single comprehensive screenshot
- Fixed asset directory paths in documentation
- Improved ImageMagick conversion commands for icon generation
- Clarified WordPress.org SVN repository structure
## [1.6.25] - 2024-05-17
### Added
#### [1.6.25] - 2024-05-17
##### Added
- Comprehensive WordPress.org submission guide with SVN structure explanation
### Changed
##### Changed
- Consolidated asset files into their respective directories
- Clarified asset requirements and submission process
- Improved organization of asset files
## [1.6.24] - 2024-05-17
### Added
#### [1.6.24] - 2024-05-17
##### Added
- Properly named icon PNG files (icon-256x256.png and icon-128x128.png)
### Changed
##### Changed
- Updated asset preparation documentation
- Improved WordPress.org submission readiness
## [1.6.23] - 2024-05-17
### Added
#### [1.6.23] - 2024-05-17
##### Added
- Properly named icon, banner, and screenshot files for WordPress.org submission
- Comprehensive guide for WordPress.org asset requirements
### Changed
##### Changed
- Fixed file naming to comply with WordPress.org standards
- Organized assets in separate directories for better management
## [1.6.22] - 2024-05-17
### Changed
#### [1.6.22] - 2024-05-17
##### Changed
- Enhanced support section with multiple support channel options
- Added encouragement for users to leave reviews on WordPress.org
- Improved documentation with clearer support instructions
## [1.6.21] - 2024-05-17
### Added
#### [1.6.21] - 2024-05-17
##### Added
- Support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
- Links to supported AI IDEs in documentation
- Additional FAQs for better SEO
### Changed
##### Changed
- Updated AI configuration files with modern models (gpt-4o)
- Made documentation more generic for boilerplate use
- Enhanced explanations in configuration files
- Added more keywords for better SEO
## [1.6.20] - 2024-05-17
### Changed
#### [1.6.20] - 2024-05-17
##### Changed
- Added explanations about the ! prefix in ignore files
- Moved WordPress-specific patterns to .gitignore
- Further improved organization of ignore patterns
- Added examples of how to include files excluded by .gitignore
## [1.6.19] - 2024-05-17
### Changed
#### [1.6.19] - 2024-05-17
##### Changed
- Consolidated common ignore patterns into .gitignore
- Simplified AI IDE configuration files to only include tool-specific patterns
- Improved organization of ignore patterns for better maintainability
- Added more file types to .gitignore for comprehensive coverage
## [1.6.18] - 2024-05-17
### Changed
#### [1.6.18] - 2024-05-17
##### Changed
- Optimized AI IDE configuration files to only include patterns not in .gitignore
- Improved efficiency of ignore files for better AI context management
- Enhanced compatibility with various AI-powered development tools
## [1.6.17] - 2024-05-17
### Added
#### [1.6.17] - 2024-05-17
##### Added
- .augmentignore file with best practices
- Configuration files for Cursor, Windsurf, v0, and Cline IDEs
- More design file formats to .gitignore
- .aiconfig file for general AI IDE compatibility
## [1.6.16] - 2024-05-17
### Fixed
#### [1.6.16] - 2024-05-17
##### Fixed
- Updated CI configuration files with correct plugin slugs
- Updated CHANGELOG.md with all recent versions
- Fixed outdated references to plugin-reference-cleaner
## [1.6.15] - 2024-05-17
### Changed
#### [1.6.15] - 2024-05-17
##### Changed
- Moved AI workflow documentation to root directory for better visibility
- Consolidated duplicate workflow files
- Improved organization of development documentation
- Updated CI configuration files with correct plugin slugs
## [1.6.14] - 2024-05-17
### Changed
#### [1.6.14] - 2024-05-17
##### Changed
- Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
- Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
- Improved explanation of how the plugin works
- Ensured consistent terminology across all documentation
## [1.6.13] - 2024-05-17
### Changed
#### [1.6.13] - 2024-05-17
##### Changed
- Code cleanup and optimization
- Improved Git Updater integration
- Fixed author display in plugin information
- Ensured compatibility with WordPress 6.4
## [1.6.12] - 2024-05-17
### Added
#### [1.6.12] - 2024-05-17
##### Added
- Added WP ALLSTARS as a co-author
- Updated author information and links
- Added author websites to plugin description
- Fixed issue with multiple author URLs
## [1.6.11] - 2024-05-17
### Fixed
#### [1.6.11] - 2024-05-17
##### Fixed
- Improved Git Updater integration
- Fixed plugin header information
- Updated author information
## [1.6.10] - 2024-05-17
### Fixed
#### [1.6.10] - 2024-05-17
##### Fixed
- Corrected plugin header information
- Improved Git Updater compatibility
- Updated documentation
## [1.6.9] - 2024-05-17
### Fixed
#### [1.6.9] - 2024-05-17
##### Fixed
- Fixed Git Updater integration
- Updated plugin header information
- Improved documentation
## [1.6.8] - 2024-05-17
### Fixed
#### [1.6.8] - 2024-05-17
##### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.7] - 2024-05-17
### Fixed
#### [1.6.7] - 2024-05-17
##### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.6] - 2024-05-17
### Fixed
#### [1.6.6] - 2024-05-17
##### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.5] - 2024-05-16
### Fixed
#### [1.6.5] - 2024-05-16
##### Fixed
- Fixed Git Updater integration
- Updated plugin header information
## [1.6.4] - 2024-05-16
### Improved
#### [1.6.4] - 2024-05-16
##### Improved
- Version management to ensure consistent patch version increments
- Documentation for version update process
- AI workflow files with detailed version increment instructions
## [1.6.3] - 2024-05-15
### Fixed
#### [1.6.3] - 2024-05-15
##### Fixed
- Git Updater repository URLs to use full repository paths
- Update URI configuration for proper update detection
- Version management following semantic versioning
### Changed
##### Changed
- Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
## [1.6.2] - 2024-05-15
### Changed
#### [1.6.2] - 2024-05-15
##### Changed
- Updated POT file version for consistency
- Improved JavaScript localization with proper fallbacks
- Enhanced code quality for WordPress.org submission
### Added
##### Added
- Git Updater configuration with Update URI
- Update server URL configuration
## [1.6.1] - 2024-05-15
### Added
#### [1.6.1] - 2024-05-15
##### Added
- AI assistant guide and workflow documentation
- Detailed release process documentation
- Feature development guidelines
- Bug fixing procedures
- Code review standards
## [1.6.0] - 2024-05-15
### Added
#### [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] - 2024-05-15
### 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] - 2023-11-30
### Added
#### [1.4.1] - 2023-11-30
##### Added
- FAQ about keeping the plugin installed after notices are cleared
## [1.4.0] - 2023-11-30
### 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
## [1.3.3] - 2023-10-05
### 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] - 2023-10-05
### 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] - 2023-10-05
### 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] - 2023-10-05
### 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] - 2023-10-05
### 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] - 2023-10-05
### 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] - 2023-10-05
### 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

View File

@ -1,29 +0,0 @@
# Branch Fix for Git Updater
## Important Note
The separate "GU Branch Fix" plugin is no longer needed. The functionality has been integrated directly into the main "Fix 'Plugin file does not exist' Notices" plugin.
## Integration Details
The main plugin now includes all the necessary Git Updater branch fixes:
1. Branch name override (changes 'master' to 'main')
2. API URL fixes (replaces '/master/' with '/main/' in API URLs)
3. Download link fixes (replaces '/master.zip' with '/main.zip')
4. Repository metadata overrides
5. Repository type data overrides
These fixes are implemented in the main plugin file (`wp-fix-plugin-does-not-exist-notices.php`) and are automatically loaded when the plugin is activated.
## Usage
Simply activate the main "Fix 'Plugin file does not exist' Notices" plugin, and the Git Updater branch fixes will be applied automatically. There is no need to activate a separate plugin.
## Troubleshooting
If you encounter any issues with Git Updater:
1. Make sure you have the latest version of the "Fix 'Plugin file does not exist' Notices" plugin
2. Deactivate any separate "GU Branch Fix" plugin if it's still installed
3. Use the "Refresh Cache" button in Git Updater to force it to update plugin information

View File

@ -1,33 +0,0 @@
# GU Branch Fix
A simple WordPress plugin to fix Git Updater branch issues for plugins using 'main' instead of 'master'.
## Description
This small utility plugin addresses an issue with Git Updater where it defaults to using 'master' as the primary branch name, while many modern repositories use 'main' as their primary branch.
The plugin adds filters to:
1. Change the branch from 'master' to 'main' for specific plugins
2. Fix API URLs by replacing '/master/' with '/main/'
3. Fix download links by replacing '/master.zip' with '/main.zip'
## Installation
1. Upload the plugin files to the `/wp-content/plugins/gu-branch-fix` directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the 'Plugins' screen in WordPress.
3. No configuration is needed - it works automatically.
## Usage
This plugin is specifically designed to work with the "Fix 'Plugin file does not exist' Notices" plugin, but can be easily modified to work with any plugin that uses 'main' as its primary branch.
To add support for other plugins, simply modify the conditional checks in the filter functions.
## Changelog
### 1.0.0
* Initial release
## License
This plugin is licensed under the GPL v2 or later.

View File

@ -25,6 +25,7 @@ This small utility plugin adds missing plugins to your WordPress plugins list an
* 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
@ -66,6 +67,15 @@ When WordPress detects a plugin file that no longer exists but is still referenc
3. Click the "Remove Notice" 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
## Frequently Asked Questions
### Is it safe to remove plugin references?
@ -175,6 +185,52 @@ The plugin works by:
## Changelog
### 2.0.13
* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
* Fixed: Type checking in branch fix functions to handle both string and object inputs
* Improved: Error handling for Git Updater integration
* Improved: Documentation for Git Updater installation and cache refreshing
### 2.0.12
* Fixed: Integrated Git Updater branch fix directly into main plugin
* Fixed: Removed separate "GU Branch Fix" plugin (no longer needed)
* Added: Documentation explaining branch fix integration
* Improved: Compatibility with Git Updater plugin
* Improved: Deploy script to remove separate branch fix plugin
### 2.0.11
* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
* Added: Deploy script for local testing
* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
* Improved: Compatibility with Git Updater plugin
### 2.0.10
* Fixed: Plugin details popup version display issue with Git Updater integration
* Added: JavaScript-based solution to ensure correct version display in plugin details
* Improved: Version consistency across all plugin views
* Improved: Cache busting for plugin information API
### 2.0.9
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Support for both old and new plugin slugs to fix caching issues
* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
* Improved: Version display in plugin details popup
### 2.0.8
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
* Improved: Author and contributor information display in plugin details
* Improved: Added WordPress 6.5 compatibility indicator
### 2.0.7
* Changed: Additional text improvements and minor fixes
### 2.0.6
* Changed: Text improvements and minor fixes
### 2.0.5
* Fixed: Display correct version in plugin details popup
### 2.0.4
* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view

View File

@ -1,66 +0,0 @@
#!/bin/bash
# Deploy script for local testing
# This script copies the plugin to the local WordPress plugins directory
# Set variables
SOURCE_DIR="$(pwd)"
TARGET_DIR="$HOME/Local/plugin-testing/app/public/wp-content/plugins"
MAIN_PLUGIN_NAME="wp-fix-plugin-does-not-exist-notices"
# Create target directory if it doesn't exist
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME"
# Clean up target directory first
echo "Cleaning up target directory..."
rm -rf "$TARGET_DIR/$MAIN_PLUGIN_NAME"/*
# Remove the separate branch fix plugin if it exists
if [ -f "$TARGET_DIR/gu-branch-fix.php" ]; then
echo "Removing separate branch fix plugin..."
rm -f "$TARGET_DIR/gu-branch-fix.php"
fi
# Remove the old plugin directory if it exists
if [ -d "$TARGET_DIR/fix-plugin-file-does-not-exist-notices" ]; then
echo "Removing old plugin directory..."
rm -rf "$TARGET_DIR/fix-plugin-file-does-not-exist-notices"
fi
# Copy main plugin files
echo "Copying plugin files..."
cp "$SOURCE_DIR/wp-fix-plugin-does-not-exist-notices.php" "$TARGET_DIR/$MAIN_PLUGIN_NAME/wp-fix-plugin-does-not-exist-notices.php"
cp "$SOURCE_DIR/readme.txt" "$TARGET_DIR/$MAIN_PLUGIN_NAME/"
# Copy additional directories and files for the main plugin
if [ -d "$SOURCE_DIR/admin" ]; then
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME/admin"
cp -R "$SOURCE_DIR/admin"/* "$TARGET_DIR/$MAIN_PLUGIN_NAME/admin/"
fi
if [ -d "$SOURCE_DIR/assets" ]; then
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME/assets"
cp -R "$SOURCE_DIR/assets"/* "$TARGET_DIR/$MAIN_PLUGIN_NAME/assets/"
fi
if [ -d "$SOURCE_DIR/includes" ]; then
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME/includes"
cp -R "$SOURCE_DIR/includes"/* "$TARGET_DIR/$MAIN_PLUGIN_NAME/includes/"
fi
if [ -d "$SOURCE_DIR/languages" ]; then
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME/languages"
cp -R "$SOURCE_DIR/languages"/* "$TARGET_DIR/$MAIN_PLUGIN_NAME/languages/"
fi
if [ -d "$SOURCE_DIR/vendor" ]; then
mkdir -p "$TARGET_DIR/$MAIN_PLUGIN_NAME/vendor"
cp -R "$SOURCE_DIR/vendor"/* "$TARGET_DIR/$MAIN_PLUGIN_NAME/vendor/"
fi
echo "Deployment complete!"
echo "Plugin deployed to: $TARGET_DIR/$MAIN_PLUGIN_NAME"
echo "\nRemember to activate these plugins in WordPress:"
echo "1. Fix 'Plugin file does not exist' Notices"
echo "2. Git Updater"

View File

@ -2,14 +2,14 @@
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.0.11\n"
"Project-Id-Version: Fix 'Plugin file does not exist' Notices 2.1.0\n"
"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"POT-Creation-Date: 2024-05-19T00:00:00+00:00\n"
"POT-Creation-Date: 2024-05-20T00: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"

View File

@ -5,7 +5,7 @@ Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file doe
Requires at least: 5.0
Tested up to: 6.7.2
Requires PHP: 7.0
Stable tag: 2.0.13
Stable tag: 2.1.0
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
@ -77,7 +77,6 @@ Contributions are welcome! Please feel free to 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
@ -85,6 +84,15 @@ The plugin is designed to be a best-practice example for WordPress plugin develo
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
== Frequently Asked Questions ==
= Is it safe to remove plugin references? =
@ -141,6 +149,12 @@ Manually editing the WordPress database is risky and requires technical knowledg
== Changelog ==
= 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
@ -462,6 +476,9 @@ Manually editing the WordPress database is risky and requires technical knowledg
== Upgrade Notice ==
= 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.

View File

@ -3,7 +3,7 @@
* 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.0.13
* Version: 2.1.0
* Author: Marcus Quinn & WP ALLSTARS
* Author URI: https://www.wpallstars.com
* License: GPL-2.0+
@ -26,7 +26,7 @@ if ( ! defined( 'WPINC' ) ) {
}
// Define plugin constants.
define( 'FPDEN_VERSION', '2.0.13' );
define( 'FPDEN_VERSION', '2.1.0' );
define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
@ -876,12 +876,12 @@ class Fix_Plugin_Does_Not_Exist_Notices {
// Initialize the plugin class.
new Fix_Plugin_Does_Not_Exist_Notices();
// Automatically deactivate problematic plugins
// This function was previously deactivating all plugins except our plugin and Git Updater
// It has been disabled to allow other plugins to be activated
// Uncomment the following code if you need to troubleshoot plugin conflicts
/*
add_action('admin_init', 'fpden_deactivate_problematic_plugins');
/**
* Deactivate problematic plugins
*/
function fpden_deactivate_problematic_plugins() {
$active_plugins = get_option('active_plugins', array());
$updated_plugins = array();
@ -899,6 +899,7 @@ function fpden_deactivate_problematic_plugins() {
update_option('active_plugins', $updated_plugins);
}
}
*/
// Initialize the updater if composer autoload exists
$autoloader = __DIR__ . '/vendor/autoload.php';