Update screenshot references and improve WordPress.org submission documentation (v1.6.26)

CHANGELOG.md

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

README.md

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

assets/WORDPRESS_ORG_ASSETS.md

@@ -0,0 +1,91 @@
+# WordPress.org Plugin Submission Assets Guide
+
+This document explains how to prepare and upload assets for WordPress.org plugin submission.
+
+## 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.0.0/
+        [plugin files]
+    /1.0.1/
+        [plugin files]
+/trunk/          # Contains the current version of the plugin
+    [plugin files]
+```
+
+## 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"
+   ```
+
+## 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

@@ -31,7 +31,7 @@ This document outlines the requirements for assets when submitting a plugin to t
 
 ### Icon
 - ✅ SVG source available
-- ❌ Need to create `icon-256x256.png` from the SVG
+- ✅ PNG files created (`icon-256x256.png` and `icon-128x128.png`)
 
 ### Banner
 - ✅ Both sizes available

assets/banner-png/README.md

@@ -6,6 +6,6 @@ For WordPress.org plugin submission, you need:
 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
+3. Place them in the `/assets/` directory of your WordPress.org SVN repository
 
-These files have been properly renamed from the original files to match WordPress.org requirements.
+These files have been renamed from the original files to match WordPress.org's naming-convention and file format requirements.

assets/icon-png/README.md

@@ -3,22 +3,30 @@
 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
+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
 
 You can use tools like:
 - 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)
 
 ```bash
-convert -background none -size 256x256 assets/icon/fix-plugin-does-not-exist-notices-icon.svg assets/icon-png/icon-256x256.png
+# 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-png/README.md

@@ -2,17 +2,6 @@
 
 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.
+1. Screenshot in PNG format
+2. Named `screenshot-1.png`
+3. Place it in the `/assets/` directory of your WordPress.org SVN repository

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).
- * Version: 1.6.23
+ * 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.26
  * 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.23' );
+define( 'FPDEN_VERSION', '1.6.26' );
 define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
 define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
 define( 'FPDEN_PLUGIN_FILE', __FILE__ );

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.23\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.26\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.23
+Stable tag: 1.6.26
 License: GPL-2.0+
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
@@ -105,12 +105,27 @@ 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 ==
 
+= 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
@@ -338,6 +353,15 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Upgrade Notice ==
 
+= 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.