Prepare release v2.1.0
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Plugin Asset Update / Push assets to WordPress.org (push) Has been cancelled
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline was successful
Some checks failed
ci/woodpecker/push/woodpecker Pipeline is pending
Plugin Asset Update / Push assets to WordPress.org (push) Has been cancelled
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/tag/woodpecker Pipeline was successful
This commit is contained in:
@ -23,11 +23,11 @@ All these files respect `.gitignore` patterns and only include additional tool-s
|
||||
|
||||
## Project Overview
|
||||
|
||||
- **Plugin Name**: [PLUGIN_NAME]
|
||||
- **Repository**: [REPOSITORY_URL]
|
||||
- **Description**: [PLUGIN_DESCRIPTION]
|
||||
- **Plugin Name**: Fix 'Plugin file does not exist' Notices
|
||||
- **Repository**: https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices
|
||||
- **Description**: Adds missing plugins to your plugins list with a "Remove Notice" action link, allowing you to safely clean up invalid plugin references.
|
||||
|
||||
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.
|
||||
This plugin helps users clean up references to deleted plugins that cause "Plugin file does not exist" errors in the WordPress admin. It adds missing plugins to the plugins list with a "Remove Notice" link to safely remove invalid plugin entries.
|
||||
|
||||
## Reference Plugins
|
||||
|
||||
@ -75,6 +75,7 @@ When updating the version number, always update these files:
|
||||
3. `readme.txt` (Stable tag and Changelog section)
|
||||
4. `README.md` (Update Changelog section to match readme.txt)
|
||||
5. Update `FPDEN_VERSION` constant in the main plugin file
|
||||
6. Update `languages/wp-fix-plugin-does-not-exist-notices.pot` (Project-Id-Version and POT-Creation-Date)
|
||||
|
||||
**IMPORTANT**: Always ensure README.md is kept in sync with readme.txt for consistency across platforms.
|
||||
|
||||
@ -174,6 +175,27 @@ Before releasing:
|
||||
3. Verify all features work as expected
|
||||
4. Check for any PHP warnings or notices
|
||||
|
||||
### Local Testing Environment
|
||||
|
||||
- Local WordPress testing environment is at ~/Local/plugin-testing/app/public
|
||||
- Plugin testing directory is at ~/Local/plugin-testing/app/public/wp-content/plugins
|
||||
- WP-CLI is available at ~/Local/plugin-testing/app/bin/wp
|
||||
- Debug logs can be found at ~/Local/plugin-testing/app/public/wp-content/uploads/debug-log-manager/ if the Debug Log Manager plugin is installed
|
||||
|
||||
### Using WP-CLI with LocalWP
|
||||
|
||||
WP-CLI can be used with LocalWP for various tasks:
|
||||
|
||||
```bash
|
||||
# Navigate to the WordPress directory
|
||||
cd ~/Local/plugin-testing/app/public
|
||||
|
||||
# Run WP-CLI commands
|
||||
~/Local/plugin-testing/app/bin/wp plugin list
|
||||
~/Local/plugin-testing/app/bin/wp transient delete --all
|
||||
~/Local/plugin-testing/app/bin/wp cache flush
|
||||
```
|
||||
|
||||
## Common Tasks for AI Assistants
|
||||
|
||||
### Creating a New Release
|
||||
|
Reference in New Issue
Block a user