Why This Matters
Abandoned plugins and themes can create problems for your sites:How MainWP Detects Abandonment
MainWP checks the last-updated date on wordpress.org for each plugin and theme. If no update has been released within your configured threshold, the item is flagged as possibly abandoned.WordPress.org dates are the default source. Items without usable dates can be checked with the optional local-file fallback described below.
Local File Date Fallback in 6.3
MainWP Dashboard 6.3 adds Abandoned check by local file date under top-right user menu > MainWP Settings > General Settings > Updates Settings (/wp-admin/admin.php?page=Settings). It is disabled by default and requires MainWP Child 6.3 or later. Enable it, save settings, and sync the affected sites before checking again.
When WordPress.org cannot provide a usable last-updated date, MainWP Child compares a local file’s modification date with Abandoned plugins/themes tolerance:
- Plugins use their main plugin file.
- Themes use
style.css.
Where to View Abandoned Items
Find abandoned items at:- Sites > Plugins > Abandoned Plugins (
/wp-admin/admin.php?page=PluginsAbandoned) - Sites > Themes > Abandoned Themes (
/wp-admin/admin.php?page=ThemesAbandoned)
What to Do with Abandoned Items
- Assess the risk - Consider if the plugin is critical and if alternatives exist
- Check GitHub - Some plugins have active development on GitHub even without wordpress.org updates
- Find alternatives - Search for actively maintained replacements
- Plan migration - Replace abandoned items before they cause issues
Adjust the Threshold
To change the number of days or disable this check, see How to change tolerance for Abandoned Plugins and Themes.Related Resources
- Check for Abandoned Plugins and Themes - Manual abandonment checks
- Change Abandoned Tolerance - Adjust the threshold
