Compare commits

..

5 Commits

34 changed files with 622 additions and 311 deletions
+19 -8
View File
@@ -29,6 +29,17 @@ All these files respect `.gitignore` patterns and only include additional tool-s
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.
## 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
@@ -59,7 +70,7 @@ We follow [Semantic Versioning](https://semver.org/):
### Version Update Checklist
When updating the version number, always update these files:
1. `fix-plugin-does-not-exist-notices.php` (Plugin header)
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)
@@ -96,11 +107,11 @@ Before creating a new release, verify the following:
1. Create a new branch for the version: `git checkout -b v{MAJOR}.{MINOR}.{PATCH}`
2. Update version numbers in ALL required files:
- `fix-plugin-does-not-exist-notices.php` (Plugin header)
- `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/fix-plugin-does-not-exist-notices.pot` (Project-Id-Version)
- `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
@@ -141,9 +152,9 @@ To manually build the plugin:
## Remote Repositories
The plugin is hosted on multiple repositories:
- GitHub: https://github.com/wpallstars/fix-plugin-does-not-exist-notices
- Gitea: https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices
- WordPress.org: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
- 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.
@@ -173,11 +184,11 @@ git checkout main
git checkout -b v1.7.0
# 2. Update version numbers in ALL required files
# - fix-plugin-does-not-exist-notices.php
# - wp-fix-plugin-does-not-exist-notices.php
# - CHANGELOG.md
# - readme.txt
# - README.md
# - languages/fix-plugin-does-not-exist-notices.pot
# - languages/wp-fix-plugin-does-not-exist-notices.pot
# - FPDEN_VERSION constant
# 3. Commit changes
+1
View File
@@ -25,6 +25,7 @@ When implementing a new feature:
- 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
-39
View File
@@ -1,39 +0,0 @@
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/fix-plugin-does-not-exist-notices
- cp fix-plugin-does-not-exist-notices.php build/fix-plugin-does-not-exist-notices/
- cp readme.txt build/fix-plugin-does-not-exist-notices/
- cp LICENSE build/fix-plugin-does-not-exist-notices/
- cp README.md build/fix-plugin-does-not-exist-notices/
- cp CHANGELOG.md build/fix-plugin-does-not-exist-notices/
- cd build
- zip -r ../fix-plugin-does-not-exist-notices-$VERSION.zip 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:
- 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/fix-plugin-does-not-exist-notices/src/branch/main/CHANGELOG.md) for details.
-35
View File
@@ -1,35 +0,0 @@
# This file configures how Git handles line endings and file types
# It is independent from .gitignore which controls which files are tracked
# Auto detect text files and perform LF normalization
* text=auto
# Text files that should be normalized
*.php text
*.css text
*.js text
*.htm text
*.html text
*.xml text
*.txt text
*.ini text
*.inc text
*.md text
.htaccess text
# Files that should be treated as binary
*.png binary
*.jpg binary
*.gif binary
*.ico binary
*.zip binary
*.gz binary
*.tar binary
*.ttf binary
*.eot binary
*.woff binary
# Set the default behavior for GitHub language detection
*.css linguist-language=CSS
*.js linguist-language=JavaScript
*.php linguist-language=PHP
-24
View File
@@ -1,24 +0,0 @@
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: fix-plugin-does-not-exist-notices
-69
View File
@@ -1,69 +0,0 @@
name: Build Release
on:
push:
tags:
- 'v*'
jobs:
build:
name: Build and Create Release
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: Get version
id: get_version
run: echo "VERSION=${GITHUB_REF#refs/tags/v}" >> $GITHUB_OUTPUT
- name: Create build directory
run: mkdir -p build/fix-plugin-does-not-exist-notices
- name: Copy plugin files
run: |
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 ../fix-plugin-does-not-exist-notices-${{ steps.get_version.outputs.VERSION }}.zip fix-plugin-does-not-exist-notices
- name: Create Release
id: create_release
uses: softprops/action-gh-release@v1
with:
name: Release v${{ steps.get_version.outputs.VERSION }}
draft: false
prerelease: false
files: |
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/fix-plugin-does-not-exist-notices/blob/main/CHANGELOG.md) for details.
# Deploy to WordPress.org
wordpress:
name: Deploy to WordPress.org
needs: build
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v3
- name: WordPress Plugin Deploy
id: deploy
uses: 10up/action-wordpress-plugin-deploy@stable
with:
generate-zip: true
env:
SVN_USERNAME: ${{ secrets.SVN_USERNAME }}
SVN_PASSWORD: ${{ secrets.SVN_PASSWORD }}
SLUG: fix-plugin-does-not-exist-notices
+3
View File
@@ -45,6 +45,9 @@ wp-content/backup-db/
wp-content/cache/
wp-content/backups/
# Reference plugins
reference-plugins/
# Log files
*.log
error_log
-41
View File
@@ -1,41 +0,0 @@
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/fix-plugin-does-not-exist-notices
- cp fix-plugin-does-not-exist-notices.php build/fix-plugin-does-not-exist-notices/
- cp readme.txt build/fix-plugin-does-not-exist-notices/
- cp LICENSE build/fix-plugin-does-not-exist-notices/
- cp README.md build/fix-plugin-does-not-exist-notices/
- if [ -f CHANGELOG.md ]; then cp CHANGELOG.md build/fix-plugin-does-not-exist-notices/; fi
- cd build
- zip -r ../fix-plugin-does-not-exist-notices-$VERSION.zip fix-plugin-does-not-exist-notices
- cd ..
- echo "Build completed - fix-plugin-does-not-exist-notices-$VERSION.zip"
- ls -la *.zip
release:
image: plugins/gitea-release
environment:
PLUGIN_API_KEY:
from_secret: gitea_token
PLUGIN_BASE_URL: https://gitea.wpallstars.com
PLUGIN_FILES: 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/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]
+27 -8
View File
@@ -2,14 +2,16 @@
This directory contains assets specific to the WordPress.org plugin repository and is used for automatic deployment via GitHub Actions.
## Directory Contents
## Directory Structure
- `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
```
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
```
## Purpose
@@ -17,4 +19,21 @@ 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.
Files must be named exactly as shown above to be properly recognized by the WordPress.org system during the deployment process.
## 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.
## 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/)
Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 392 KiB

+76 -1
View File
@@ -2,6 +2,81 @@
All notable changes to this project will be documented in this file.
## [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
- 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
- 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] - 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
- Major version release for WordPress.org submission
- Finalized all assets and documentation for public release
## [1.6.28] - 2024-05-17
### Changed
- Consolidated asset documentation into a single comprehensive guide
- Clarified that `-rtl` suffix is for Right-to-Left languages, not dark mode
- Updated all asset README files to point to the main documentation
- Improved file organization and documentation structure
## [1.6.27] - 2024-05-17
### Changed
- Clarified RTL support in WordPress.org asset documentation
- Corrected information about `-rtl` suffix for assets (for right-to-left languages, not dark themes)
- Consolidated asset files and improved documentation
## [1.6.26] - 2024-05-17
### Changed
- Updated screenshot references to use a single comprehensive screenshot
- Fixed asset directory paths in documentation
- Improved ImageMagick conversion commands for icon generation
- Clarified WordPress.org SVN repository structure
## [1.6.25] - 2024-05-17
### Added
- Comprehensive WordPress.org submission guide with SVN structure explanation
### Changed
- Consolidated asset files into their respective directories
- Clarified asset requirements and submission process
- Improved organization of asset files
## [1.6.24] - 2024-05-17
### Added
- Properly named icon PNG files (icon-256x256.png and icon-128x128.png)
### Changed
- Updated asset preparation documentation
- Improved WordPress.org submission readiness
## [1.6.23] - 2024-05-17
### Added
- Properly named icon, banner, and screenshot files for WordPress.org submission
- Comprehensive guide for WordPress.org asset requirements
### Changed
- Fixed file naming to comply with WordPress.org standards
- Organized assets in separate directories for better management
## [1.6.22] - 2024-05-17
### Changed
- Enhanced support section with multiple support channel options
@@ -180,7 +255,7 @@ All notable changes to this project will be documented in this file.
## [1.4.0] - 2023-11-30
### Changed
- Updated plugin name and text domain
- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
- Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
## [1.3.3] - 2023-10-05
### Added
+72 -18
View File
@@ -1,8 +1,8 @@
# Fix 'Plugin file 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/)
[![WordPress Plugin Version](https://img.shields.io/wordpress/plugin/v/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Rating](https://img.shields.io/wordpress/plugin/rating/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![WordPress Plugin Downloads](https://img.shields.io/wordpress/plugin/dt/wp-fix-plugin-does-not-exist-notices)](https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/)
[![License](https://img.shields.io/badge/license-GPL--2.0%2B-blue.svg)](https://www.gnu.org/licenses/gpl-2.0.html)
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin.
@@ -15,6 +15,8 @@ Have you ever deleted a plugin directly from the server or database and then bee
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.
### Key Features
* Adds missing plugins directly to your plugins list
@@ -116,9 +118,7 @@ Manually editing the WordPress database is risky and requires technical knowledg
## Screenshots
1. Error message with explanation notification
2. Missing plugin shown in the plugins list with "Remove Notice" link
3. Auto-scroll feature that highlights the missing plugin
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
## Developers
@@ -136,15 +136,14 @@ Contributions are welcome! Please feel free to submit a Pull Request.
This repository is configured to work with various AI-powered development tools. You can use any of the following AI IDEs to contribute to this project:
- [Augment](https://augment.dev/) - AI-powered coding assistant
- [Cursor](https://cursor.sh/) - AI-first code editor
- [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.io/) - AI coding assistant
- [Cline](https://cline.tools/) - AI terminal assistant
- [Roo](https://roo.ai/) - AI pair programmer
- [Gemini Code Assist](https://ai.google.dev/gemini-api) - Google's AI coding assistant
- [Loveable](https://www.loveable.ai/) - AI development environment
- [Bolt](https://www.bolt.dev/) - AI-powered code editor
- [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
@@ -160,6 +159,61 @@ The plugin works by:
## Changelog
### 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
@@ -325,8 +379,8 @@ This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE)
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [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)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.
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 feedback helps others discover the plugin and encourages continued development and support.
+4 -7
View File
@@ -7,15 +7,13 @@ This directory contains assets for the WordPress.org plugin repository.
- `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
@@ -34,7 +32,8 @@ This directory contains assets for the WordPress.org plugin repository.
- Screenshots should be numbered sequentially starting with 1
- They should match the descriptions in the `readme.txt` file
- Dark theme versions of banners and icons can be provided by appending `-rtl` to the filename
- Right-to-Left (RTL) language versions of banners and icons can be provided by appending `-rtl` to the filename
- There is no official support for dark mode versions of assets in the WordPress.org repository
## Example Filenames
@@ -48,6 +47,4 @@ assets/
│ └── icon-256x256.jpg
└── screenshots/
├── screenshot-1.jpg
├── screenshot-2.jpg
└── screenshot-3.jpg
```
```
+126
View File
@@ -0,0 +1,126 @@
# WordPress.org Plugin Submission Assets Guide
This document explains how to prepare and upload assets for WordPress.org plugin submission. This is the main reference document for all asset-related information.
## WordPress.org SVN Repository Structure
When submitting a plugin to WordPress.org, you'll work with an SVN repository that has this structure:
```
/assets/ # Contains assets for the WordPress.org plugin page
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
/tags/ # Contains tagged releases
/1.6.27/
[plugin files]
/1.6.26/
[plugin files]
/trunk/ # Contains the current version of the plugin
[plugin files]
```
## Right-to-Left (RTL) Support
For languages that read from right to left (like Hebrew and Arabic), you can provide RTL-specific versions of your assets by appending `-rtl` to the filename. For example:
- `banner-772x250-rtl.png`
- `icon-256x256-rtl.png`
Note: `-rtl` is specifically for Right-to-Left language support, not for dark theme versions.
## Asset Requirements
### Icon
- **Format**: PNG
- **Sizes**:
- Required: 256x256 pixels (`icon-256x256.png`)
- Optional: 128x128 pixels (`icon-128x128.png`)
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `assets/icon/`
### Banner
- **Format**: PNG
- **Sizes**:
- Required: 772x250 pixels (`banner-772x250.png`)
- Optional: 1544x500 pixels (`banner-1544x500.png`) for high-DPI displays
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY - Files are in `assets/banner/`
### Screenshots
- **Format**: PNG
- **Naming**: `screenshot-1.png`
- **Location**: Upload to the `/assets/` directory in the WordPress.org SVN repository
- **Status**: ✅ READY
- `screenshot-1.png` is available in `assets/screenshots/`
## Submission Process
1. **Prepare Plugin Files**:
- Ensure all plugin files are ready in your local repository
- Make sure version numbers are consistent across all files
2. **Prepare Assets**:
- Ensure all assets follow the naming conventions above
- Verify that screenshots match the descriptions in readme.txt
3. **Upload to WordPress.org**:
- When you receive SVN access, use these commands:
```bash
# Check out the repository
svn checkout https://plugins.svn.wordpress.org/fix-plugin-does-not-exist-notices/
# Copy plugin files to trunk
cp -r [your-local-plugin-files]/* fix-plugin-does-not-exist-notices/trunk/
# Copy assets to assets directory
cp assets/icon/icon-256x256.png fix-plugin-does-not-exist-notices/assets/
cp assets/icon/icon-128x128.png fix-plugin-does-not-exist-notices/assets/
cp assets/banner/banner-772x250.png fix-plugin-does-not-exist-notices/assets/
cp assets/banner/banner-1544x500.png fix-plugin-does-not-exist-notices/assets/
cp assets/screenshots/screenshot-1.png fix-plugin-does-not-exist-notices/assets/
# Add new files
cd fix-plugin-does-not-exist-notices
svn add --force trunk/*
svn add --force assets/*
# Commit changes
svn commit -m "Initial plugin submission"
```
## Image Conversion Tools
For converting SVG to PNG or creating different sizes of images, you can use:
- **Graphic Design Software**:
- Adobe Photoshop
- Adobe Illustrator
- Affinity Designer
- Affinity Photo
- GIMP (free, open-source)
- Inkscape (free, open-source)
- Pixelmator
- **Online Converters**:
- [SVG to PNG Converter](https://svgtopng.com/)
- [Convertio](https://convertio.co/svg-png/)
- [CloudConvert](https://cloudconvert.com/svg-to-png)
- **Command Line** (using ImageMagick):
```bash
# For 256x256 icon
convert -background none -size 256x256 assets/icon/icon.svg assets/icon/icon-256x256.png
# For 128x128 icon
convert -background none -size 128x128 assets/icon/icon.svg assets/icon/icon-128x128.png
```
## Resources
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
+81
View File
@@ -0,0 +1,81 @@
# WordPress.org Plugin Submission Assets Guide
This document outlines the requirements for assets when submitting a plugin to the WordPress.org plugin repository.
## Asset Requirements
### Icon
- **Format**: PNG
- **Size**: 256x256 pixels
- **Filename**: `icon-256x256.png`
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Optional**: You can also include `icon-128x128.png` for backward compatibility
### Banner
- **Format**: PNG
- **Sizes**:
- Regular: 772x250 pixels (`banner-772x250.png`)
- High-DPI: 1544x500 pixels (`banner-1544x500.png`)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
### Screenshots
- **Format**: PNG
- **Naming**: Sequential numbers (`screenshot-1.png`, `screenshot-2.png`, etc.)
- **Location**: SVN `/assets` directory (not included in the plugin zip)
- **Important**: The number and order must match the descriptions in the `readme.txt` file
## Current Status
### Icon
- ✅ SVG source available in `assets/icon/icon.svg`
- ✅ PNG files created in `assets/icon/icon-256x256.png` and `assets/icon/icon-128x128.png`
### Banner
- ✅ Both sizes available in `assets/banner/`
- ✅ Properly named files: `banner-772x250.png` and `banner-1544x500.png`
### Screenshots
- ✅ One screenshot available in `assets/screenshots/screenshot-1.png`
- ✅ Screenshot description in readme.txt updated to reference only one screenshot
## SVN Directory Structure
When submitting to WordPress.org, your SVN repository will have this structure:
```
/assets/
icon-256x256.png
icon-128x128.png
banner-772x250.png
banner-1544x500.png
screenshot-1.png
/tags/
/1.6.27/
[plugin files]
/1.6.26/
[plugin files]
/trunk/
[current plugin files]
```
## Action Items
1. Ensure all files follow the proper naming convention
2. Upload all assets to the WordPress.org SVN repository in the `/assets` directory using these commands:
```bash
# Copy assets to WordPress.org SVN assets directory
cp assets/icon/icon-256x256.png /path/to/wordpress-svn/assets/
cp assets/icon/icon-128x128.png /path/to/wordpress-svn/assets/
cp assets/banner/banner-772x250.png /path/to/wordpress-svn/assets/
cp assets/banner/banner-1544x500.png /path/to/wordpress-svn/assets/
cp assets/screenshots/screenshot-1.png /path/to/wordpress-svn/assets/
```
## Resources
- [WordPress Plugin Developer Handbook - Plugin Assets](https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/)
- [WordPress Plugin Directory README.txt Standard](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
+15
View File
@@ -0,0 +1,15 @@
# WordPress.org Banner Files
This directory contains banner files for the WordPress.org plugin repository.
## Files in this Directory
- `banner-772x250.png` - 772x250 pixel PNG banner (required for WordPress.org)
- `banner-1544x500.png` - 1544x500 pixel PNG banner for high-DPI displays (optional for WordPress.org)
- `banner-1544x500.pxd` - Source file for editing in Pixelmator
## WordPress.org Submission
For detailed information about WordPress.org banner requirements and submission process, please see the main asset documentation:
[WordPress.org Plugin Submission Assets Guide](../WORDPRESS_ORG_ASSETS.md)
Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

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

After

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.7 KiB

File diff suppressed because one or more lines are too long

After

Width:  |  Height:  |  Size: 30 KiB

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

After

Width:  |  Height:  |  Size: 392 KiB

+2 -2
View File
@@ -10,7 +10,7 @@ if [ -z "$1" ]; then
fi
VERSION=$1
PLUGIN_SLUG="fix-plugin-does-not-exist-notices"
PLUGIN_SLUG="wp-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 fix-plugin-does-not-exist-notices.php $BUILD_DIR/
cp wp-fix-plugin-does-not-exist-notices.php $BUILD_DIR/
cp readme.txt $BUILD_DIR/
cp LICENSE $BUILD_DIR/
cp README.md $BUILD_DIR/
+1 -1
View File
@@ -1,5 +1,5 @@
{
"name": "wpallstars/fix-plugin-does-not-exist-notices",
"name": "wpallstars/wp-fix-plugin-does-not-exist-notices",
"description": "Adds missing plugins to the plugins list with a 'Remove Reference' link so you can permanently clean up invalid plugin entries and remove error notices.",
"type": "wordpress-plugin",
"license": "GPL-2.0-or-later",
+4 -2
View File
@@ -9,6 +9,8 @@
namespace WPALLSTARS\FixPluginDoesNotExistNotices;
use function add_filter;
/**
* Class Updater
*
@@ -143,9 +145,9 @@ class Updater {
// Set the update server based on the installation source
\add_filter('gul_update_server', function() {
if ($this->source === 'github') {
return 'https://github.com/wpallstars/fix-plugin-does-not-exist-notices'; // GitHub repository URL
return 'https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // GitHub repository URL
} elseif ($this->source === 'gitea') {
return 'https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices'; // Gitea repository URL
return 'https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices'; // Gitea repository URL
}
return '';
});
@@ -2,24 +2,24 @@
# This file is distributed under the GPL-2.0+.
msgid ""
msgstr ""
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.22\n"
"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices\n"
"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 2.0.4\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-16T12:00:00+00:00\n"
"POT-Creation-Date: 2024-05-17T12: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"
"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://wordpress.org/plugins/fix-plugin-does-not-exist-notices/"
msgid "https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/"
msgstr ""
#. Description of the plugin
@@ -34,81 +34,81 @@ msgstr ""
msgid "https://www.wpallstars.com"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:127
#: wp-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
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:129
#: wp-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
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:164
msgid "N/A"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:168
#: wp-fix-plugin-does-not-exist-notices.php:168
msgid "Missing"
msgstr ""
#. translators: %s: Plugin file path
#: fix-plugin-does-not-exist-notices.php:204
#: wp-fix-plugin-does-not-exist-notices.php:204
msgid "Remove reference to missing plugin %s"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:227
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:233
msgid "Invalid plugin specified."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:308
#: wp-fix-plugin-does-not-exist-notices.php:308
msgid "Plugin reference removed successfully."
msgstr ""
#: fix-plugin-does-not-exist-notices.php:316
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:331
msgid "Fix Plugin Does Not Exist Notices"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:333
#: wp-fix-plugin-does-not-exist-notices.php:333
msgid "Missing plugin files detected:"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:334
#: wp-fix-plugin-does-not-exist-notices.php:334
msgid "The plugins listed below with a"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:335
#: wp-fix-plugin-does-not-exist-notices.php:335
msgid "File Missing"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:336
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:339
msgid "How to fix:"
msgstr ""
#: fix-plugin-does-not-exist-notices.php:340
#: wp-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
#: wp-fix-plugin-does-not-exist-notices.php:342
msgid "This will clean up your database and remove the error notifications."
msgstr ""
+105 -11
View File
@@ -3,9 +3,9 @@ Contributors: marcusquinn, wpallstars
Donate link: https://www.marcusquinn.com
Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file does not exist, wordpress error, plugin error, deactivated plugin, remove plugin reference, fix plugin error, plugin does not exist, plugin file does not exist error
Requires at least: 5.0
Tested up to: 6.4
Tested up to: 6.7.2
Requires PHP: 7.0
Stable tag: 1.6.22
Stable tag: 2.0.4
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -19,6 +19,8 @@ Have you ever deleted a plugin directly from the server or database and then bee
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.
= Key Features =
* Adds missing plugins directly to your plugins list
@@ -48,7 +50,7 @@ When WordPress detects a plugin file that no longer exists but is still referenc
== Installation ==
1. Upload the `fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
1. Upload the `wp-fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. No configuration needed - the plugin works automatically
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
@@ -105,12 +107,65 @@ Manually editing the WordPress database is risky and requires technical knowledg
== Screenshots ==
1. Error message with explanation notification
2. Missing plugin shown in the plugins list with "Remove Notice" link
3. Auto-scroll feature that highlights the missing plugin
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
== Changelog ==
= 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
@@ -271,7 +326,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 fix-plugin-does-not-exist-notices
* Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
= 1.3.3 =
* Improved notification placement next to WordPress error messages
@@ -332,6 +387,33 @@ Manually editing the WordPress database is risky and requires technical knowledg
== Upgrade Notice ==
= 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.
@@ -392,12 +474,24 @@ Completely redesigned for better compatibility with all WordPress themes - now w
= 1.2.2 =
Important stability fix - resolves timeout issues during plugin activation!
== 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.
== Support ==
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices/issues)
* [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)
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices/reviews/) on WordPress.org. Your feedback helps others discover the plugin and encourages continued development and support.
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 feedback helps others discover the plugin and encourages continued development and support.
@@ -11,21 +11,21 @@
*
* @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. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
* Version: 1.6.22
* Plugin URI: https://wordpress.org/plugins/wp-fix-plugin-does-not-exist-notices/
* Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
* Version: 2.0.4
* Author: Marcus Quinn & WP ALLSTARS
* Author URI: https://www.wpallstars.com
* License: GPL-2.0+
* License URI: https://www.gnu.org/licenses/gpl-2.0.html
* Text Domain: fix-plugin-does-not-exist-notices
* Text Domain: wp-fix-plugin-does-not-exist-notices
* Domain Path: /languages
* Requires at least: 5.0
* Requires PHP: 7.0
* Update URI: https://git-updater.wpallstars.com
* GitHub Plugin URI: wpallstars/fix-plugin-does-not-exist-notices
* GitHub Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
* GitHub Branch: main
* Gitea Plugin URI: wpallstars/fix-plugin-does-not-exist-notices
* Gitea Plugin URI: wpallstars/wp-fix-plugin-does-not-exist-notices
* Gitea Branch: main
*
* This plugin is free software: you can redistribute it and/or modify
@@ -48,7 +48,7 @@ if ( ! defined( 'ABSPATH' ) ) {
}
// Define plugin constants
define( 'FPDEN_VERSION', '1.6.22' );
define( 'FPDEN_VERSION', '2.0.4' );
define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
define( 'FPDEN_PLUGIN_FILE', __FILE__ );
@@ -61,7 +61,7 @@ define( 'FPDEN_PLUGIN_BASENAME', plugin_basename( __FILE__ ) );
*/
function fpden_load_textdomain() {
load_plugin_textdomain(
'fix-plugin-does-not-exist-notices',
'wp-fix-plugin-does-not-exist-notices',
false,
dirname( plugin_basename( __FILE__ ) ) . '/languages/'
);
@@ -142,9 +142,9 @@ class Fix_Plugin_Does_Not_Exist_Notices {
'fpdenData',
array(
'i18n' => array(
'clickToScroll' => esc_html__( 'Click here to scroll to missing plugins', 'fix-plugin-does-not-exist-notices' ),
'pluginMissing' => esc_html__( 'File Missing', 'fix-plugin-does-not-exist-notices' ),
'removeNotice' => esc_html__( 'Remove Notice', 'fix-plugin-does-not-exist-notices' ),
'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' ),
),
)
);
@@ -176,14 +176,14 @@ class Fix_Plugin_Does_Not_Exist_Notices {
'Name' => $plugin_name . ' <span class="error">(File Missing)</span>',
/* translators: %s: Path to wp-content/plugins */
'Description' => sprintf(
__( 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'fix-plugin-does-not-exist-notices' ),
__( 'This plugin is still marked as "Active" in your database — but its folder and files can\'t be found in %s. Click "Remove Notice" to permanently remove it from your active plugins list and eliminate the error notice.', 'wp-fix-plugin-does-not-exist-notices' ),
'<code>/wp-content/plugins/</code>'
),
'Version' => __( 'N/A', 'fix-plugin-does-not-exist-notices' ),
'Version' => FPDEN_VERSION, // Use our plugin version instead of 'N/A'
'Author' => '',
'PluginURI' => '',
'AuthorURI' => '',
'Title' => $plugin_name . ' (' . __( 'Missing', 'fix-plugin-does-not-exist-notices' ) . ')',
'Title' => $plugin_name . ' (' . __( 'Missing', 'wp-fix-plugin-does-not-exist-notices' ) . ')',
'AuthorName' => '',
);
}
@@ -223,8 +223,8 @@ class Fix_Plugin_Does_Not_Exist_Notices {
$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 Notice', 'fix-plugin-does-not-exist-notices' ) . '</a>';
$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;
@@ -246,13 +246,13 @@ class Fix_Plugin_Does_Not_Exist_Notices {
// 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' ) );
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.', 'fix-plugin-does-not-exist-notices' ) );
wp_die( esc_html__( 'Invalid plugin specified.', 'wp-fix-plugin-does-not-exist-notices' ) );
}
// Verify nonce for security.
@@ -328,7 +328,7 @@ class Fix_Plugin_Does_Not_Exist_Notices {
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>
<p><?php esc_html_e( 'Plugin reference removed successfully.', 'wp-fix-plugin-does-not-exist-notices' ); ?></p>
</div>
<?php
}
@@ -336,7 +336,7 @@ class Fix_Plugin_Does_Not_Exist_Notices {
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>
<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
}