Fix screenshot references in README.md to match readme.txt

V1.6.6

CHANGELOG.md

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

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
 
@@ -160,6 +160,18 @@ The plugin works by:
 
 ## Changelog
 
+### 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)

assets/README.md

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

assets/WORDPRESS_ORG_ASSETS.md

@@ -1,6 +1,6 @@
 # WordPress.org Plugin Submission Assets Guide
 
-This document explains how to prepare and upload assets for WordPress.org plugin submission.
+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
 
@@ -14,9 +14,9 @@ When submitting a plugin to WordPress.org, you'll work with an SVN repository th
     banner-1544x500.png
     screenshot-1.png
 /tags/           # Contains tagged releases
-    /1.0.0/
+    /1.6.27/
         [plugin files]
-    /1.0.1/
+    /1.6.26/
         [plugin files]
 /trunk/          # Contains the current version of the plugin
     [plugin files]
@@ -93,6 +93,33 @@ Note: `-rtl` is specifically for Right-to-Left language support, not for dark th
    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/)

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/README.md

@@ -1,11 +1,15 @@
-# WordPress.org Banner Requirements
+# WordPress.org Banner Files
 
-For WordPress.org plugin submission, you need:
+This directory contains banner files for the WordPress.org plugin repository.
 
-1. Banner images in PNG format
+## Files in this Directory
-2. Two sizes:
-   - `banner-772x250.png` (for regular display)
-   - `banner-1544x500.png` (for high-resolution/retina displays)
-3. Place them in the `/assets/` directory of your WordPress.org SVN repository
 
-These files have been renamed from the original files to match WordPress.org's naming-convention and file format requirements.
+- `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/README.md

@@ -1,32 +1,16 @@
-# WordPress.org Icon Requirements
+# WordPress.org Icon Files
 
-For WordPress.org plugin submission, you need to:
+This directory contains icon files for the WordPress.org plugin repository.
 
-1. Convert the SVG icon to PNG format
+## Files in this Directory
-2. Create a 256x256 and 128x128 pixel version
-3. Name them `icon-256x256.png` and `icon-128x128.png`
-4. Place them in the `/assets/` directory of your WordPress.org SVN repository
 
-## How to Convert
+- `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
 
-You can use tools like:
+## WordPress.org Submission
-- Inkscape (free, open-source)
-- Adobe Illustrator
-- Adobe Photoshop
-- Affinity Designer
-- Affinity Photo
-- GIMP
-- Pixelmator
-- Online converters like https://svgtopng.com/
 
-## Command Line Conversion (if you have ImageMagick installed)
+For detailed information about WordPress.org icon requirements and submission process, please see the main asset documentation:
 
-```bash
+[WordPress.org Plugin Submission Assets Guide](../WORDPRESS_ORG_ASSETS.md)
-# For 256x256 icon
-convert -background none -size 256x256 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon/icon-256x256.png
-
-# For 128x128 icon
-convert -background none -size 128x128 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon/icon-128x128.png
-```
-
-After creating the PNG file, it should be uploaded to the WordPress.org SVN repository in the assets directory.

assets/screenshots/README.md

@@ -1,7 +1,14 @@
-# WordPress.org Screenshot Requirements
+# WordPress.org Screenshot Files
 
-For WordPress.org plugin submission, you need:
+This directory contains screenshot files for the WordPress.org plugin repository.
 
-1. Screenshot in PNG format
+## Files in this Directory
-2. Named `screenshot-1.png`
+
-3. Place it in the `/assets/` directory of your WordPress.org SVN repository
+- `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

@@ -13,7 +13,7 @@
  * Plugin Name: Fix 'Plugin file does not exist.' Notices
  * Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
  * Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
- * Version: 1.6.27
+ * Version: 2.0.0
  * 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.27' );
+define( 'FPDEN_VERSION', '2.0.0' );
 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.27\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 2.0.0\n"
 "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"

readme.txt

@@ -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.4
 Requires PHP: 7.0
-Stable tag: 1.6.27
+Stable tag: 2.0.0
 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
@@ -109,6 +111,18 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Changelog ==
 
+= 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)
@@ -358,6 +372,12 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Upgrade Notice ==
 
+= 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.