For professional developers working with WordPress, the first steps in any new build frequently involve deleting default content and turning off built-in settings. This plugin encapsulates many of those tasks on a single, clean configuration screen.<\/p>\n\n\n
After installing the plugin, navigate to Settings > No Nonsense<\/strong> to choose which built-in WordPress features you want to turn off. Be sure to click Save Changes<\/strong> when you're done.<\/p><\/dd>\n\n<\/dl>\n\n\n Note: If your locale is set to Germany or the Netherlands, the incomplete, community-translated files for these languages may load instead of the ones embedded in the plugin, or the plugin's versions may get replaced by the community versions if you click Update Translations<\/strong> on the Updates page. Manually deleting the No Nonsense-related files from 3.6.5 - 2026.01.06<\/h4>\n\n
\n
$type<\/code> parameter was not success<\/code> (i.e. allowing both fail<\/code> and critical<\/code>, as well as an empty value). Now this setting only sends if $type<\/code> is equal to fail<\/code>. Added the Also send \"critical\" messages<\/strong> checkbox to revert to the previous functionality.<\/li>\n$type<\/code> parameter.)<\/li>\n<\/ul>\n\n3.6.4 - 2025.10.29<\/h4>\n\n
\n
3.6.3.1 - 2025.04.22<\/h4>\n\n
\n
r34nono_require_login()<\/code> function to treat request URIs beginning with \/wp-json\/<\/code> as allowed requests even if wp_is_json_request()<\/code> returns false. This is due to an issue observed with another Room 34 plugin (ICS Calendar Pro) where the REST API is being used but the response is (intentionally) not in JSON format.<\/li>\n<\/ul>\n\n3.6.3 - 2025.04.15<\/h4>\n\n
\n
3.6.2 - 2025.03.26<\/h4>\n\n
\n
3.6.1.1 - 2025.02.07<\/h4>\n\n
\n
r34nono_i18n_locales()<\/code> function added in 3.6.1 runs on a logged-out front-end page.<\/li>\n<\/ul>\n\n3.6.1 - 2025.02.06<\/h4>\n\n
\n
3.6.0 - 2025.02.04<\/h4>\n\n
\n
wp_dashboard_recent_comments()<\/code>), and the one that calls it (wp_dashboard_site_activity()<\/code>), contain no hooks.<\/em><\/li>\n3.5.1 - 2024.12.02<\/h4>\n\n
\n
plugins_loaded<\/code> hook, to prevent _load_textdomain_just_in_time<\/code>-related notices after changes in WordPres 6.7:\n\n\n
R34NoNo::settings<\/code> array to put all translation strings into a deferred method that only loads on the No Nonsense admin page, which also eliminates unnecessary translation processing.<\/li>\nR34NoNo::functions<\/code> property and replaced R34NoNo::utilities<\/code> with an array that is only defined when the admin page is being loaded, since the information is only needed on that page.<\/li>\n<\/ul><\/li>\nis_plugin_active()<\/code> function before defining plugin-specific settings. (This had not previously revealed itself to be an issue, because the R34NoNo::_get_version()<\/code> method already loads the wp-admin\/includes\/plugin.php<\/code> file. This change alleviates the unintended dependence on that method.)<\/li>\n\n
no-nonsense.pot<\/code> file with new translation strings.<\/li>\nwp-content\/languages\/plugins<\/code> will revert to using the plugin-embedded versions. We are currently investigating the issue.<\/em><\/p>\n\n3.5.0.2 - 2024.12.02<\/h4>\n\n
\n
3.5.0.1 - 2024.12.02<\/h4>\n\n
\n
get_plugin_data()<\/code> issue.<\/li>\n<\/ul>\n\n3.5.0 - 2024.10.03<\/h4>\n\n
\n
load_plugin_textdomain()<\/code> call, and set $translate<\/code> input parameter to false<\/code> on get_plugin_data()<\/code> call, as it may cause PHP notices as of WordPress 6.7. See the WordPress Trac<\/a> for more details.<\/li>\nno-nonsense.pot<\/code> with new translation strings.<\/li>\n<\/ul>\n\n3.4.0 - 2024.08.22<\/h4>\n\n
\n
no-nonsense.pot<\/code> with new translation strings.<\/li>\n<\/ul>\n\n3.3.3 - 2024.08.16<\/h4>\n\n
\n
r34nono_xmlrpc_disabled()<\/code> function and into a conditional that runs directly in the no-nonsense.php<\/code> file when the plugin is loading. The previous approach did not kill the request early enough, and would still return a WordPress XML-RPC status message with an HTTP 405 status. The new approach correctly returns a blank page with a 403 status.<\/li>\n<\/ul>\n\n3.3.2.2 - 2024.07.25<\/h4>\n\n
\n
r34nono_admin_bar_logout_link_admin_bar_menu_callback()<\/code> and r34nono_remove_howdy()<\/code> to PHP_INT_MAX - 100<\/code>, to account for changes introduced in WP core version 6.6.1. In wp-includes\/class-wp-admin-bar.php<\/code>, priorities for three actions in the WP_Admin_Bar::add_menus()<\/code> method were changed from 4, 7, and 8 to 9991, 9992, and 9999. See Trac tickets #61615<\/a> and #61738<\/a> for discussion of this change, and the issues it introduces. At this point it is possible the core team may revert the change, but our modified priority should continue to work either way.<\/li>\nr34nono_remove_howdy()<\/code> to prevent possible PHP warnings if $wp_admin_bar<\/code> node my-account<\/code> is undefined when the function runs. (In practice this should be resolved by the aforementioned priority change.)<\/li>\n3.3.2.1 - 2024.06.04<\/h4>\n\n
\n
R34NoNo::settings<\/code> property to prevent deprecation notices.<\/li>\n<\/ul>\n\n3.3.2 - 2024.04.23<\/h4>\n\n
\n
3.3.1 - 2023.11.20<\/h4>\n\n
\n
WHERE<\/code> clause to SQL queries in Disable all comments and trackbacks<\/em>, to only alter records where the status equals open<\/code>.<\/li>\n<\/ul>\n\n3.3.0 - 2023.11.08<\/h4>\n\n
\n
no-nonsense.pot<\/code> with new translation strings.<\/li>\n3.2.2 - 2023.04.21<\/h4>\n\n
\n
filter_var()<\/code> using the FILTER_SANITIZE_STRING<\/code> (deprecated in PHP 8.1) with a new custom r34nono_sanitize_string()<\/code> function, which runs both strip_tags()<\/code> and htmlspecialchars()<\/code> on the input string.<\/li>\n3.2.1.2 - 2022.12.29<\/h4>\n\n
\n
r34nono_admin_colors_css_variables()<\/code> to prevent PHP notice, and added default values for the CSS variables, if user's admin color palette can't be loaded.<\/li>\n<\/ul>\n\n3.2.1.1 - 2022.12.21<\/h4>\n\n