Update version numbers and changelog for v2.0.2

V1.6.6

.ai-assistant.md

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

.ai-workflows/feature-development.md

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

.gitattributes

@@ -4,32 +4,98 @@
 # Auto detect text files and perform LF normalization
 * text=auto
 
-# Text files that should be normalized
+# Text files that should be normalized with LF line endings
-*.php text
+*.php text eol=lf
-*.css text
+*.css text eol=lf
-*.js text
+*.js text eol=lf
-*.htm text
+*.scss text eol=lf
-*.html text
+*.htm text eol=lf
-*.xml text
+*.html text eol=lf
-*.txt text
+*.xml text eol=lf
-*.ini text
+*.txt text eol=lf
-*.inc text
+*.ini text eol=lf
-*.md text
+*.inc text eol=lf
-.htaccess text
+*.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

.gitignore

@@ -45,6 +45,9 @@ wp-content/backup-db/
 wp-content/cache/
 wp-content/backups/
 
+# Reference plugins
+reference-plugins/
+
 # Log files
 *.log
 error_log

.wordpress-org/README.md

@@ -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
+/assets/
-- `banner-1544x500.png` - Retina banner for plugin header
+    icon-256x256.png
-- `screenshot-1.png` - First screenshot displayed on plugin page
+    icon-128x128.png
-- `screenshot-2.png` - Second screenshot displayed on plugin page
+    banner-772x250.png
-- `screenshot-3.png` - Third screenshot displayed on plugin page
+    banner-1544x500.png
+    screenshot-1.png
+```
 
 ## Purpose
 
@@ -18,3 +20,20 @@ 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.
+
+## 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/)

CHANGELOG.md

@@ -2,6 +2,60 @@
 
 All notable changes to this project will be documented in this file.
 
+## [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)

README.md

@@ -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
+1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
-2. Missing plugin shown in the plugins list with "Remove Notice" link
-3. Auto-scroll feature that highlights the missing plugin
 
 ## 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
+- [Augment Code](https://www.augmentcode.com/) - AI-powered coding assistant
-- [Cursor](https://cursor.sh/) - AI-first code editor
+- [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
+- [Windsurf](https://www.windsurf.com/) - AI coding assistant
-- [Cline](https://cline.tools/) - AI terminal assistant
+- [Cline](https://cline.bot/) - AI terminal assistant
-- [Roo](https://roo.ai/) - AI pair programmer
+- [Roo Code](https://roocode.com/) - AI pair programmer
-- [Gemini Code Assist](https://ai.google.dev/gemini-api) - Google's AI coding assistant
+- [Loveable](https://lovable.dev/) - AI development environment
-- [Loveable](https://www.loveable.ai/) - AI development environment
+- [Bolt](https://www.bolt.new/) - AI-powered code editor
-- [Bolt](https://www.bolt.dev/) - AI-powered code editor
 - [Cody](https://sourcegraph.com/cody) - Sourcegraph's AI coding assistant
 - [Continue](https://continue.dev/) - Open-source AI coding assistant
 
@@ -160,6 +159,47 @@ The plugin works by:
 
 ## Changelog
 
+### 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

assets/README.md

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

assets/WORDPRESS_ORG_ASSETS.md

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

assets/WORDPRESS_ORG_SUBMISSION.md

@@ -30,17 +30,16 @@ This document outlines the requirements for assets when submitting a plugin to t
 ## Current Status
 
 ### Icon
-- ✅ SVG source available
+- ✅ SVG source available in `assets/icon/icon.svg`
-- ✅ PNG files created (`icon-256x256.png` and `icon-128x128.png`)
+- ✅ PNG files created in `assets/icon/icon-256x256.png` and `assets/icon/icon-128x128.png`
 
 ### Banner
-- ✅ Both sizes available
+- ✅ Both sizes available in `assets/banner/`
-- ✅ Properly renamed versions created in `assets/banner-png/`
+- ✅ Properly named files: `banner-772x250.png` and `banner-1544x500.png`
 
 ### Screenshots
-- ❌ Only 1 of 3 referenced screenshots available
+- ✅ One screenshot available in `assets/screenshots/screenshot-1.png`
-- ❌ Need to create `screenshot-2.png` and `screenshot-3.png`
+- ✅ Screenshot description in readme.txt updated to reference only one screenshot
-- ✅ Properly renamed version of the first screenshot created in `assets/screenshots-png/`
 
 ## SVN Directory Structure
 
@@ -49,15 +48,14 @@ 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
-    screenshot-2.png
-    screenshot-3.png
 /tags/
-    /1.0.0/
+    /1.6.27/
         [plugin files]
-    /1.0.1/
+    /1.6.26/
         [plugin files]
 /trunk/
     [current plugin files]
@@ -65,10 +63,17 @@ When submitting to WordPress.org, your SVN repository will have this structure:
 
 ## Action Items
 
-1. Convert the SVG icon to a 256x256 PNG file
+1. Ensure all files follow the proper naming convention
-2. Create the missing screenshots (2 and 3)
+2. Upload all assets to the WordPress.org SVN repository in the `/assets` directory using these commands:
-3. Ensure all files follow the proper naming convention
+
-4. Upload all assets to the WordPress.org SVN repository in the `/assets` directory
+```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
 

assets/banner-png/README.md

@@ -1,11 +0,0 @@
-# WordPress.org Banner Requirements
-
-For WordPress.org plugin submission, you need:
-
-1. Banner images in PNG format
-2. Two sizes:
-   - `banner-772x250.png` (for regular display)
-   - `banner-1544x500.png` (for high-resolution/retina displays)
-3. Place them in the root of your SVN assets directory
-
-These files have been properly renamed from the original files to match WordPress.org requirements.

assets/banner/README.md

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

assets/icon-png/README.md

@@ -1,24 +0,0 @@
-# WordPress.org Icon Requirements
-
-For WordPress.org plugin submission, you need to:
-
-1. Convert the SVG icon to PNG format
-2. Create a 256x256 pixel version
-3. Name it `icon-256x256.png`
-4. Place it in the root of your SVN assets directory
-
-## How to Convert
-
-You can use tools like:
-- Inkscape (free, open-source)
-- Adobe Illustrator
-- GIMP
-- Online converters like https://svgtopng.com/
-
-## Command Line Conversion (if you have ImageMagick installed)
-
-```bash
-convert -background none -size 256x256 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon-png/icon-256x256.png
-```
-
-After creating the PNG file, it should be uploaded to the WordPress.org SVN repository in the assets directory.

assets/icon/README.md

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

assets/screenshots-png/README.md

@@ -1,18 +0,0 @@
-# WordPress.org Screenshot Requirements
-
-For WordPress.org plugin submission, you need:
-
-1. Screenshots in PNG format
-2. Named sequentially: `screenshot-1.png`, `screenshot-2.png`, etc.
-3. Place them in the root of your SVN assets directory
-
-## Important Note
-
-The readme.txt file references 3 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
-
-However, only one screenshot file is currently available. You need to create and add the other two screenshots to match the descriptions in the readme.txt file.
-
-After creating all three screenshots with the proper naming convention, they should be uploaded to the WordPress.org SVN repository in the assets directory.

assets/screenshots/README.md

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

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

@@ -12,8 +12,8 @@
  * @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).
+ * Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
- * Version: 1.6.24
+ * Version: 2.0.2
  * Author: Marcus Quinn & WP ALLSTARS
  * Author URI: https://www.wpallstars.com
  * License: GPL-2.0+
@@ -48,7 +48,7 @@ if ( ! defined( 'ABSPATH' ) ) {
 }
 
 // Define plugin constants
-define( 'FPDEN_VERSION', '1.6.24' );
+define( 'FPDEN_VERSION', '2.0.2' );
 define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
 define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
 define( 'FPDEN_PLUGIN_FILE', __FILE__ );

includes/Updater.php

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

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

@@ -2,7 +2,7 @@
 # This file is distributed under the GPL-2.0+.
 msgid ""
 msgstr ""
-"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.24\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 2.0.2\n"
 "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

readme.txt

@@ -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.24
+Stable tag: 2.0.2
 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
@@ -105,12 +107,51 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Screenshots ==
 
-1. Error message with explanation notification
+1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
-2. Missing plugin shown in the plugins list with "Remove Notice" link
-3. Auto-scroll feature that highlights the missing plugin
 
 == Changelog ==
 
+= 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
@@ -343,6 +384,27 @@ 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.
 
@@ -409,6 +471,18 @@ 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/fix-plugin-does-not-exist-notices/) or [Gitea](https://gitea.wpallstars.com/wpallstars/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: