Prepare assets for WordPress.org plugin submission (v1.6.23)

CHANGELOG.md

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

README.md

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

assets/WORDPRESS_ORG_SUBMISSION.md

@@ -0,0 +1,76 @@
+# 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
+- ❌ Need to create `icon-256x256.png` from the SVG
+
+### Banner
+- ✅ Both sizes available
+- ✅ Properly renamed versions created in `assets/banner-png/`
+
+### Screenshots
+- ❌ Only 1 of 3 referenced screenshots available
+- ❌ Need to create `screenshot-2.png` and `screenshot-3.png`
+- ✅ Properly renamed version of the first screenshot created in `assets/screenshots-png/`
+
+## SVN Directory Structure
+
+When submitting to WordPress.org, your SVN repository will have this structure:
+
+```
+/assets/
+    icon-256x256.png
+    banner-772x250.png
+    banner-1544x500.png
+    screenshot-1.png
+    screenshot-2.png
+    screenshot-3.png
+/tags/
+    /1.0.0/
+        [plugin files]
+    /1.0.1/
+        [plugin files]
+/trunk/
+    [current plugin files]
+```
+
+## Action Items
+
+1. Convert the SVG icon to a 256x256 PNG file
+2. Create the missing screenshots (2 and 3)
+3. Ensure all files follow the proper naming convention
+4. Upload all assets to the WordPress.org SVN repository in the `/assets` directory
+
+## 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/banner-png/README.md

@@ -0,0 +1,11 @@
+# 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/icon-png/README.md

@@ -0,0 +1,24 @@
+# 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/screenshots-png/README.md

@@ -0,0 +1,18 @@
+# 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.

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. By Marcus Quinn (marcusquinn.com) & WP ALLSTARS (wpallstars.com).
- * Version: 1.6.22
+ * Version: 1.6.23
  * 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.22' );
+define( 'FPDEN_VERSION', '1.6.23' );
 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.22\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.23\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.22
+Stable tag: 1.6.23
 License: GPL-2.0+
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
@@ -111,6 +111,12 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Changelog ==
 
+= 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
@@ -332,6 +338,9 @@ Manually editing the WordPress database is risky and requires technical knowledg
 
 == Upgrade Notice ==
 
+= 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.