Every WordPress release quietly retires a few things \u2014 a function, a class, a core file, an action or filter. Nothing is removed the day it is deprecated, so a plugin that still calls a retired function keeps working for a while. Then a later release finally drops it and something breaks, often with no error you can see \u2014 just a button that no longer does anything.<\/p>\n\n
RobArt Update Guard tells you, before that happens, which of your installed plugins still lean on something WordPress has retired \u2014 with the file, the line, and what to use instead.<\/strong><\/p>\n\n WordPress marks its own retirements directly in its source code. A single line like Because the answer comes from your own WordPress install, it is as authoritative as your site itself \u2014 no changelog parsing, no external service, no guesswork, and no AI.<\/p>\n\n Retired functions, classes, core files, and actions\/filters \u2014 each with a real, exact line number, because all four can be found unambiguously in source.<\/p>\n\n Update Guard is honest about its edges rather than padding the report with guesses:<\/p>\n\n Everything is read from the copy of WordPress and the plugins already on your site. No code leaves your server, nothing is fetched from the network, and no AI is involved. Update Guard bundles no third-party libraries. It only reads \u2014 it never edits a plugin or makes changes for you.<\/p>\n\n Update Guard cleans up after itself. When you delete the plugin from the Plugins screen, it removes everything it stored:<\/p>\n\n It creates no custom database tables, writes nothing outside your own site, and leaves no orphaned data behind. Deactivating the plugin keeps your settings and last report; only deleting the plugin runs the clean-up.<\/p>\n\n Update Guard performs all of its scanning locally on your own server. It makes no automatic network requests and sends no data anywhere.<\/p>\n\n The plugin displays a few ordinary links to information pages for other Rob Art plugins, hosted at Support and review links point to WordPress.org, which is governed by the WordPress.org privacy policy.<\/p>\n\n\n It means nothing your plugins call has been retired. It cannot promise an update is safe, because a function can change what it does while keeping its name \u2014 the commonest cause of breakage, and something no code reader can detect. Treat a clean report as \"no known retirements,\" not \"guaranteed safe.\"<\/p><\/dd>\n Class methods are excluded on purpose. Many share everyday names, and distinguishing a retired one from an unrelated method needs runtime type information a static scan doesn't have. Flagging them would produce more noise than signal.<\/p><\/dd>\n No. Nothing runs on the front end. A scan happens only when you click the button, and the result is cached for a day.<\/p><\/dd>\n No. Update Guard only reads. It never edits a plugin \u2014 it points you to the file and line so you can decide.<\/p><\/dd>\n No. It reads only the WordPress and plugin files already on your server. Nothing is sent to any external service and no AI is involved.<\/p><\/dd>\n\n<\/dl>\n\n\nHow it works<\/h4>\n\n
_deprecated_function( __FUNCTION__, '5.5.0', 'add_allowed_options()' )<\/code> carries all three facts a report needs: what was retired, when, and what to use instead. Update Guard reads those markings from the copy of WordPress already on your site, builds an index, then walks the PHP of your installed plugins for anything that still calls one.<\/p>\n\nWhat it does<\/h4>\n\n
\n
What it covers reliably<\/h4>\n\n
What it deliberately leaves out<\/h4>\n\n
\n
reset()<\/code>, render()<\/code>); telling a retired one from an unrelated method needs runtime type information a static scan doesn't have.<\/li>\nload<\/code> and error<\/code> and matching them loosely would bury real findings in noise.<\/li>\nvendor\/<\/code>, node_modules\/<\/code>) \u2014 not yours to change, and they would dominate the results.<\/li>\n<\/ul>\n\nPrivacy<\/h4>\n\n
Uninstall<\/h3>\n\n
\n
External services<\/h3>\n\n
robsnow.eu<\/code>. These are plain links you may choose to click; the plugin never contacts any external service on its own, and no data is transmitted unless you follow a link.<\/p>\n\n\n
\/wp-content\/plugins\/robart-update-guard<\/code>, or install it from the Plugins screen in your WordPress admin.<\/li>\n\n
Does a clean report mean it is safe to update?<\/h3><\/dt>\n
Why didn't it flag a method I know is deprecated?<\/h3><\/dt>\n
Will it slow my site down?<\/h3><\/dt>\n
Does it change any of my files?<\/h3><\/dt>\n
Does it send my code anywhere or use AI?<\/h3><\/dt>\n
0.0.2<\/h4>\n\n
\n
0.0.1<\/h4>\n\n
\n