Files
marcusquinn a3c675c617
Some checks failed
Build Release / Build and Create Release (push) Has been cancelled
Build Release / Deploy to WordPress.org (push) Has been cancelled
ci/woodpecker/push/woodpecker Pipeline failed
ci/woodpecker/tag/woodpecker Pipeline was successful
Version 2.4.0 - Add documentation for multi-repository workspaces
2025-04-17 04:29:02 +01:00

664 lines
30 KiB
Plaintext

=== Fix 'Plugin file does not exist.' Notices ===
Contributors: surferking, wpallstars
Donate link: https://www.wpallstars.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.8
Requires PHP: 7.0
Stable tag: 2.4.0
License: GPL-2.0+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Easily remove references to deleted plugins that cause "Plugin file does not exist" errors in your WordPress admin. By Marcus Quinn (marcusquinn.com) & WPALLSTARS (wpallstars.com).
== Description ==
Have you ever deleted a plugin directly from the server or database and then been stuck with annoying error notifications that can't be cleared?
"The plugin folder-name/file-name.php has been deactivated due to an error: Plugin file does not exist."
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
* Provides a simple "Remove Notice" action link
* Works with both single site and multisite WordPress installations
* Includes helpful notifications explaining how to fix plugin errors
* One-click auto-scroll to find missing plugins in large sites
* Clean, user-friendly interface following WordPress design patterns
* Integrated Git Updater branch fix (changes 'master' to 'main' for proper updates)
= How It Works =
When WordPress detects a plugin file that no longer exists but is still referenced in the database as active, it displays an error notice. This plugin:
1. Detects all missing plugin references in your database
2. Adds them to your plugins list with "(File Missing)" indicators
3. Provides a "Remove Notice" link to safely remove them
4. Shows clear notifications guiding you through the cleanup process
5. Safely removes the missing active plugin reference from your database using standard WordPress functions
6. Leaves all remaining plugins installed and active
= Use Cases =
* You've accidentally deleted a plugin via FTP
* A plugin was removed by another admin but references remain
* You've migrated from another site and have leftover plugin references
* Your hosting provider removed a plugin but didn't clean the database
= Support & Feedback =
If you need help with this plugin, there are several ways to get support:
* [WordPress.org Support Forums](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/)
* [GitHub Issues](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
* [Gitea Issues](https://gitea.wpallstars.com/wpallstars/wp-fix-plugin-does-not-exist-notices/issues)
= Reviews =
This utility plugin is released under the GPLv2 license as free open source software.
If you find this plugin helpful, please consider [leaving a review](https://wordpress.org/support/plugin/wp-fix-plugin-does-not-exist-notices/reviews/) on WordPress.org.
Your experience and feedback helps others discover the plugin, and encourages continued community-driven, open-source development and support.
= Contributing =
Contributions are welcome! Please feel free to submit a Pull Request.
1. Fork the repository on [GitHub](https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/) or [Gitea](https://gitea.wpallstars.com/wpallstars/wp-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.
== Installation ==
1. Upload the `wp-fix-plugin-does-not-exist-notices` folder to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. No configuration needed - the plugin works automatically
4. If you have missing plugin errors, you'll immediately see them in your plugins list with "Remove Notice" links
= Using with Git Updater =
If you've installed this plugin from GitHub or Gitea, you'll need Git Updater to receive updates:
1. Install the Git Updater plugin from [https://git-updater.com/git-updater/](https://git-updater.com/git-updater/)
2. Go to Settings > Git Updater > Remote Management
3. Click the "Refresh Cache" button to ensure Git Updater recognizes the latest version
4. Updates will now appear in your WordPress dashboard when available
= Choosing Your Update Source =
This plugin allows you to choose where you want to receive updates from:
1. In the Plugins list, find "Fix 'Plugin file does not exist' Notices"
2. Click the "Update Source" link next to the plugin
3. Select your preferred update source:
* **WordPress.org**: Updates from the official WordPress.org repository (has a version update delay due to the WP.org policy review and approval process, best for unmonitored auto-updates)
* **GitHub**: Updates directly from the GitHub repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates where the latest features and fixes are needed immediately)
* **Gitea**: Updates directly from the Gitea repo main branch for the latest stable release (requires Git Updater plugin, best for monitored updates and independence from big-tech)
4. Click "Save" to apply your preference
If no preference is set, the plugin will automatically use the source it was installed from.
**Note:** GitHub and Gitea options require the Git Updater plugin to be installed and activated.
== Contributing ==
Contributions are welcome! Please follow these steps to set up a development environment:
1. Install [LocalWP](https://localwp.com/) and create a clean site called "Plugin Testing" using the "Preferred" setup option
2. Run "Site shell" once from the LocalWP page on the site's settings to ensure wp-cli is enabled
3. Run "Add Run Configurations to VS Code" to update site configuration files in: ~/Local/plugin-testing/conf/
4. Clone this repository to your local machine
5. Use the build.sh and deploy-local.sh scripts to build and deploy the plugin for testing
[AugmentCode.com](https://augmentcode.com/) is recommended as a good all-in-one AI IDE for plugin development and testing.
Please feel free to submit a Pull Request with your improvements.
== Frequently Asked Questions ==
= Is it safe to remove plugin references? =
Yes, this plugin only removes entries from the WordPress active_plugins option, which is safe to modify when a plugin no longer exists. It doesn't modify any other database tables or settings.
= What happens after I remove a reference? =
The plugin entry will be removed from your active plugins list, and the corresponding error notification will no longer appear after you refresh the page.
= Can I use this plugin on a multisite installation? =
Yes, the plugin works on both single sites and multisite installations. It properly handles network-activated plugins as well.
= How do I know which plugin references should be removed? =
The plugin will only show "Remove Notice" links for plugins that are listed in your database but don't actually exist in your plugins directory. These are safe to remove.
= Will this break my site? =
No. Since the plugin is only removing references to plugins that no longer exist, removing these references won't affect your site's functionality. In fact, it's cleaning up remnants that might be causing issues.
= What if I accidentally remove a reference I shouldn't have? =
If you remove a reference to a plugin that you later want to reinstall, simply install the plugin again and activate it normally.
= Do I need to keep this plugin installed and active after notices are cleared? =
Although this plugin consumes minimal disk space, and doesn't run unless you are on the /wp-admin/plugins.php page, you don't need to keep it active or installed if you don't have this notice to clear — but it is safe to, if you just want it as a part of your overall WordPress stack of enhancements and conveniences.
= How do I fix the "Plugin file does not exist" error in WordPress? =
This error occurs when WordPress has a reference to a plugin in its database, but the actual plugin files are missing. Our plugin provides a simple one-click solution: it adds these missing plugins to your plugins list with a "Remove Notice" button that lets you safely remove the database reference.
= Why do I see "The plugin has been deactivated due to an error: Plugin file does not exist"? =
This error appears when you've deleted a plugin's files (via FTP or file manager) without properly deactivating it first through the WordPress admin. WordPress still thinks the plugin should be active but can't find its files. Our plugin helps you clean up these references.
= Can this plugin fix errors after migrating a WordPress site? =
Yes! After migrating a site, you might see plugin errors if some plugins weren't transferred correctly. This plugin will help you identify and clean up those references without having to edit the database directly.
= Is it safe to remove plugin references that show "Plugin file does not exist"? =
Absolutely. If WordPress is showing this error, it means the plugin files are already gone, and you're just cleaning up a database reference. Our plugin uses WordPress's standard functions to safely remove these references without affecting other plugins or site functionality.
= How is this different from manually editing the database? =
Manually editing the WordPress database is risky and requires technical knowledge. Our plugin provides a safe, user-friendly way to remove plugin references directly from the WordPress admin interface without any SQL knowledge or database access.
== Screenshots ==
1. Plugin in action - showing error message, explanation notification, and "Remove Notice" link
== Changelog ==
= 2.4.0 =
* Added: Comprehensive documentation for working in multi-repository workspaces
* Added: Guidelines to prevent feature hallucination in multi-repo environments
* Added: New .ai-workflows/multi-repo-workspace.md file with detailed best practices
* Improved: AI assistant documentation with repository context verification
* Improved: Wiki documentation to accurately reflect plugin functionality
= 2.3.1 =
* Updated: Tested compatibility with WordPress 6.8
* Improved: Documentation to reflect WordPress 6.8 compatibility
= 2.3.0 =
* Added: Improved time-efficient development workflow documentation
* Added: New git workflow guidelines for better branch management
* Added: Comprehensive incremental development approach
* Improved: Documentation for local vs. remote testing
* Improved: Version management process for more efficient development
= 2.2.5 =
* Added: Documentation for the developer preferences memory file in .ai-workflows/
* Improved: AI assistant instructions for maintaining developer preferences
* Updated: Version numbers across all files for consistency
= 2.2.4 =
* Added: Developer preferences memory file for AI assistants
* Improved: AI assistant documentation with instructions for maintaining developer preferences
* Updated: WordPress.org documentation with correct plugin slug and version numbers
= 2.2.3 =
* Improved: Moved admin-specific files to admin/lib directory for better organization
* Improved: Updated namespaces to reflect the new file locations
* Added: Comprehensive folder structure documentation
* Fixed: File references in the main plugin file
= 2.2.2-stable =
* Changed: Renamed includes files to lowercase for consistency with the rest of the codebase
* Removed: Redundant Git Updater patches and version-fix.js as they're no longer needed
* Improved: Documentation for Git Updater integration and release process
* Fixed: Token-efficient documentation with references to .ai-workflows files
* Added: Comprehensive release process documentation with emphasis on merging to main branch
= 2.2.1 =
* Changed: Commented out version-fix.js script as it's no longer needed after refactoring
* Fixed: Version consistency across all files
= 2.2.0 =
* Added: Completely refactored plugin to use OOP best practices
* Added: New class structure with proper namespaces
* Added: Improved code organization and maintainability
* Added: Better separation of concerns with dedicated classes
* Changed: "Choose Update Source" link to just "Update Source"
* Fixed: Close button in the update source modal
* Added: Links to the main page for each update source in the modal
* Changed: Replaced all instances of "WP ALLSTARS" with "WPALLSTARS"
= 2.1.1 =
* Added: New "Choose Update Source" feature allowing users to select their preferred update source (WordPress.org, GitHub, or Gitea)
* Added: Modal dialog with detailed information about each update source option
* Added: Visual indicator showing the currently selected update source
* Fixed: Updated heading styles in CHANGELOG.md for better readability
* Fixed: Corrected dates in changelog to use 2025 instead of 2024
* Improved: Documentation improvements for better clarity
* Improved: Enhanced Git Updater integration with user-selectable update sources
= 2.1.0 =
* Minor version bump for Git Updater compatibility
* Improved error handling for Git Updater integration
* Enhanced type checking in branch fix functions
* Updated documentation for Git Updater installation and cache refreshing
= 2.0.13 =
* Fixed: Critical error when Git Updater passes an object instead of a string to API URL filter
* Improved: Type checking in branch fix functions to handle both string and object inputs
* Enhanced: Error handling for Git Updater integration
* Removed: Redundant GU Branch Fix plugin (fully integrated into main plugin)
= 2.0.12 =
* Fixed: Integrated Git Updater branch fix directly into main plugin
* Removed: Separate "GU Branch Fix" plugin (no longer needed)
* Updated: Deploy script to remove separate branch fix plugin
* Added: Documentation explaining branch fix integration
* Improved: Compatibility with Git Updater plugin
= 2.0.11 =
* Added: Created separate "GU Branch Fix" plugin to fix Git Updater branch issues
* Added: Deploy script for local testing
* Fixed: Git Updater branch issues with 'main' vs 'master' branch names
* Improved: Compatibility with Git Updater plugin
= 2.0.10 =
* Fixed: Plugin details popup version display issue with Git Updater integration
* Added: JavaScript-based solution to ensure correct version display in plugin details
* Improved: Version consistency across all plugin views
* Enhanced: Cache busting for plugin information API
= 2.0.9 =
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Support for both old and new plugin slugs to fix caching issues
* Improved: Cache clearing mechanism to ensure plugin details are always up-to-date
* Enhanced: Version display in plugin details popup
= 2.0.8 =
* Fixed: Plugin details popup now correctly shows version and author information
* Added: Cache-busting mechanism to ensure plugin details are always up-to-date
* Improved: Author and contributor information display in plugin details
= 2.0.7 =
* Additional text improvements and minor fixes
= 2.0.6 =
* Text improvements and minor fixes
= 2.0.5 =
* Fixed: Display correct version in plugin details popup
= 2.0.4 =
* Fixed: Display actual plugin version instead of 'N/A' for missing plugins in plugin details view
= 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
* Updated asset preparation documentation
= 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
* Improved documentation with clearer support instructions
= 1.6.21 =
* Added support for more AI-powered development tools (Roo, Gemini, Loveable, Bolt, Cody, Continue)
* Updated documentation with links to supported AI IDEs
* Enhanced SEO with additional FAQs and keywords
* Made documentation more generic for boilerplate use
* Updated AI configuration files with modern models and better explanations
= 1.6.20 =
* Added explanations about the ! prefix in ignore files
* Moved WordPress-specific patterns to .gitignore
* Further improved organization of ignore patterns
* Added examples of how to include files excluded by .gitignore
= 1.6.19 =
* Consolidated common ignore patterns into .gitignore
* Simplified AI IDE configuration files to only include tool-specific patterns
* Improved organization of ignore patterns for better maintainability
* Added more file types to .gitignore for comprehensive coverage
= 1.6.18 =
* Optimized AI IDE configuration files to only include patterns not in .gitignore
* Improved efficiency of ignore files for better AI context management
* Enhanced compatibility with various AI-powered development tools
= 1.6.17 =
* Added .augmentignore file with best practices
* Added configuration files for Cursor, Windsurf, v0, and Cline IDEs
* Added more design file formats to .gitignore
* Added .aiconfig file for general AI IDE compatibility
= 1.6.16 =
* Updated CI configuration files with correct plugin slugs
* Updated CHANGELOG.md with all recent versions
* Fixed outdated references to plugin-reference-cleaner
= 1.6.15 =
* Moved AI workflow documentation to root directory for better visibility
* Consolidated duplicate workflow files
* Improved organization of development documentation
= 1.6.14 =
* Updated documentation to consistently use "Remove Notice" instead of "Remove Reference"
* Added design file extensions to .gitignore (.pxd, .afdesign, .afphoto, .afpub)
* Improved explanation of how the plugin works
* Ensured consistent terminology across all documentation
= 1.6.13 =
* Code cleanup and optimization
* Improved Git Updater integration
* Fixed author display in plugin information
* Ensured compatibility with WordPress 6.4
= 1.6.12 =
* Added WP ALLSTARS as a co-author
* Updated author information and links
* Added author websites to plugin description
* Fixed issue with multiple author URLs
= 1.6.11 =
* CRITICAL FIX: Completely removed auto-deactivation prevention code that was causing fatal errors
* Simplified plugin functionality to focus on core features only
* Improved compatibility with various WordPress configurations
* Ensured plugin works correctly when other plugins are deleted
= 1.6.10 =
* Fixed critical error that could occur when a plugin folder is deleted
* Improved error handling with try/catch blocks
* Added more specific checks for the plugins page
* Enhanced compatibility with various WordPress configurations
* Made the code more defensive to prevent potential issues
= 1.6.9 =
* Fixed issue with notices not appearing below WordPress error messages
* Improved JavaScript detection of WordPress error notices
* Prevented WordPress from automatically clearing error notices on page refresh
* Added multiple timing attempts to ensure notices appear correctly
* Enhanced error notice targeting for better compatibility
= 1.6.8 =
* Fixed notice positioning to appear directly below WordPress error messages
* Improved notice width to match WordPress error messages
* Updated explanatory text for better clarity
* Fixed issue with notices not appearing in some cases
* Improved JavaScript detection of WordPress error messages
= 1.6.7 =
* Fixed duplicate notices issue by removing PHP-generated notice
* Simplified notice system to only show one notice below WordPress error
* Ensured consistent terminology with "Remove Notice" text
* Optimized plugin detection with caching to improve performance
* Fixed JavaScript to correctly handle multiple error messages
= 1.6.6 =
* Fixed issue with "Remove Notice" link not appearing on missing plugin rows
* Fixed issue with automatic removal of plugin references without user action
* Fixed notice positioning to ensure it appears below error messages
* Restored pointer triangle to indicate relationship with error message
* Improved detection of missing plugins in the plugin list
* Enhanced scroll functionality to work with all plugin types
= 1.6.5 =
* Fixed duplicate notices issue - now only one notice appears below error messages
* Changed notice heading to "Fix Plugin Does Not Exist Notices ☝️"
* Updated explanatory text to be more clear about the removal process
* Changed "Remove Reference" link text to "Remove Notice" for better clarity
* Made "(File Missing)" text bold and red for better visibility
* Fixed scroll functionality to work with all plugin rows
* Improved JavaScript to prevent multiple notices from appearing
= 1.6.4 =
* Updated version management to ensure consistent patch version increments
* Improved documentation for version update process
* Enhanced AI workflow files with detailed version increment instructions
= 1.6.3 =
* Fixed Git Updater repository URLs to use full repository paths
* Corrected Update URI configuration for proper update detection
* Improved version management following semantic versioning
* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
= 1.6.2 =
* Updated POT file version for consistency
* Improved JavaScript localization with proper fallbacks
* Enhanced code quality for WordPress.org submission
* Added Git Updater configuration with Update URI
* Added update server URL configuration
= 1.6.1 =
* Added AI assistant guide and workflow documentation
* Added detailed release process documentation
* Added feature development guidelines
* Added bug fixing procedures
* Added code review standards
= 1.6.0 =
* Added full translation support with POT file
* Added JavaScript localization for better multilingual support
* Added plugin constants for improved code organization
* Added Git Updater support for updates from GitHub and Gitea
* Updated code to follow WordPress internationalization best practices
* Improved asset loading with version constants
* Added smart update detection based on installation source
= 1.5.0 =
* Improved compatibility with WordPress 6.4
* Enhanced error detection for plugin references
* Minor UI improvements for better visibility
* Accessibility enhancements for screen readers
= 1.4.1 =
* Added FAQ about keeping the plugin installed after notices are cleared
= 1.4.0 =
* Updated plugin name and text domain
* Repository rename from plugin-reference-cleaner to wp-fix-plugin-does-not-exist-notices
= 1.3.3 =
* Improved notification placement next to WordPress error messages
* Added "Click here to scroll" button that automatically locates missing plugins
* Enhanced reliability with multiple injection methods
* Added visual arrow pointing from notification to error message
= 1.3.2 =
* Added prominent notification directly below WordPress error messages
* Improved user guidance with visual cues to connect error and solution
* Added eye-catching styling to help users understand how to fix errors
= 1.3.1 =
* Added instructional notification explaining how to use the plugin
* Improved user guidance with step-by-step instructions
* Enhanced visual identification of missing plugins
= 1.3.0 =
* Complete redesign for maximum compatibility with all WordPress themes
* Now adds missing plugins directly to the plugins list table
* Uses standard WordPress admin UI patterns instead of DOM manipulation
* Added "Remove Reference" action link in the plugins list
* Significantly improved reliability across all WordPress configurations
= 1.2.4 =
* Fixed compatibility with more WordPress admin themes
* Added advanced DOM traversal to find error messages
* Implemented fallback mechanisms to ensure button appears
* Added detailed console logging for troubleshooting
= 1.2.3 =
* Fixed button not appearing in some WordPress admin themes
* Improved error message detection for greater compatibility
* Enhanced DOM traversal to find notification elements
= 1.2.2 =
* Fixed timeout issue during plugin activation
* Improved hook management to prevent potential infinite recursion
* Optimized performance by only loading on plugins page
= 1.2.1 =
* Fixed typos in documentation
* Improved text clarity
* Added question mark to first sentence for better readability
= 1.2 =
* Improved documentation with detailed explanation
* Added SQL reference for technical users
* Suggested potential inclusion in WordPress core
= 1.1 =
* Improved error handling
* Added support for multisite installations
* Enhanced security with proper capability checks
= 1.0 =
* Initial release
== Upgrade Notice ==
= 2.1.1 =
Added new "Choose Update Source" feature allowing you to select where to receive plugin updates from (WordPress.org, GitHub, or Gitea).
= 2.1.0 =
Minor version bump with improved Git Updater compatibility and error handling.
= 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.
= 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.
= 1.6.21 =
Added support for more AI-powered development tools and enhanced documentation with links to supported AI IDEs.
= 1.6.20 =
Added explanations about using the ! prefix in ignore files to include files excluded by .gitignore.
= 1.6.19 =
Improved organization of ignore patterns with consolidated .gitignore and simplified AI IDE configuration files.
= 1.6.18 =
Optimized AI IDE configuration files for better efficiency and compatibility.
= 1.6.17 =
Added configuration files for AI-powered IDEs and improved compatibility with development tools.
= 1.6.16 =
Updated CI configuration files and fixed outdated references to the previous plugin name.
= 1.6.15 =
Improved organization of development documentation with consolidated AI workflow files.
= 1.6.14 =
Improved documentation with consistent terminology and better explanation of how the plugin works.
= 1.6.13 =
Code cleanup, improved Git Updater integration, and ensured compatibility with WordPress 6.4.
= 1.6.12 =
Added WP ALLSTARS as a co-author and updated author information.
= 1.6.11 =
URGENT CRITICAL FIX: Completely removes code that was causing fatal errors. If you're experiencing the "critical error" message, this update will resolve it.
= 1.6.3 =
Fixed Git Updater repository URLs and updated organization naming for consistent branding across all platforms!
= 1.6.2 =
Improved JavaScript localization, enhanced code quality, and added Git Updater configuration for seamless updates!
= 1.6.1 =
Added comprehensive AI assistant guide and workflow documentation for improved development processes!
= 1.6.0 =
Added full translation support and Git Updater compatibility for direct updates from GitHub and Gitea!
= 1.5.0 =
Improved compatibility with WordPress 6.4 and accessibility enhancements for screen readers!
= 1.3.3 =
Major usability improvement with auto-scroll feature to help find missing plugins in your list!
= 1.3.0 =
Completely redesigned for better compatibility with all WordPress themes - now works with any WordPress installation!
= 1.2.2 =
Important stability fix - resolves timeout issues during plugin activation!