[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fyYjIA7AvOsk2QK3k2gVn1FBk8mh2Tu1SGEGU_olH1IM":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":22,"download_link":23,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":34,"analysis":105,"fingerprints":174},"dismiss-server-nag","Dismiss Serve Happy Nag","1.0.2","luciano-croce","https:\u002F\u002Fprofiles.wordpress.org\u002Fluciano-croce\u002F","\u003Cp>Dismiss \u003Cem>coming soon\u003C\u002Fem> “\u003Cstrong>Serve Happy\u003C\u002Fstrong>” nag, PHP dashboard widget, when it is activated, or automatically, if it is in mu-plugins directory.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>this plugin use \u003Ca href=\"https:\u002F\u002Fsemver.org\u002F\" rel=\"nofollow ugc\">Semantic Versioning\u003C\u002Fa> MAJOR.MINOR.PATCH\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-server-nag.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Also, for translation functionality, put all files of the single languages (dismiss-server-nag-en_US.mo for example) that you need (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) and will be loaded by default, they also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin is not written with a PHP framework, but manually, with a simple PHP editor compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor. This author is exonerated from any responsibility or damage (directly or indirectly) caused and due to the use of this bad practice.\u003C\u002Fp>\n\u003Ch4>About me\u003C\u002Fh4>\n\u003Cp>Admin footer Version (rebranded) is developed by Luciano Croce, 13-years “officially” WordPress Plugins & Themes Developer Senior, Co-Autor of plugin Classic Editor, polyglot (based on english, french, spanish, german, portuguese, italian, ligurian), GTE en_GB & en_CA, PTE for Plugins & Themes in more languages, PTE for Italian WordPress.org & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for WordPress.com, translator for my & other projects, book author of TRUE DOS (the dark side of its history from the dark side of its users) Code Tweaker & Bug Hunter, Security Mechanic & WPMU Lover, Freelancer & Volunteer.\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cp>Translated by: \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fluciano-croce\u002F\" rel=\"nofollow ugc\">Luciano Croce\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Translators, except the similar strings “Release Date: January 11, 2019” or strings before latest version number “1.0.2” (for example), remember to leave all the other changelog strings commented in GlotPress “Meta” as “Found in changelog list item section” in english (copy from original -> suggest new translation) according to my disclaimer (read it after this section) all contributes are appreciated, and are credited!\u003C\u002Fp>\n\u003Ch4>Acknowledgements\u003C\u002Fh4>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fgarrett-eclipse\u002F\" rel=\"nofollow ugc\">Garrett Hyder\u003C\u002Fa> for \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Fdismiss-server-nag\" rel=\"nofollow ugc\">English (Canada)\u003C\u002Fa> translation approval, and code contributions.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fswissspidy\u002F\" rel=\"nofollow ugc\">Pascal Birchler\u003C\u002Fa> for code contributions.\u003C\u002Fp>\n\u003Ch4>Disclaimer\u003C\u002Fh4>\n\u003Cp>Given that the more languages in which the readme.txt file is translated, the greater the possibility of reaching a larger number of people, even through the use of search engines, with the exception of the main descriptions, it is a good practice, not to translate the changelog of the file readme.txt file in the various languages different from en_US (except for the other English languages derived from English – this is not a rule – everyone is free to translate or not translate according to the indications of their own polyglots community) to standardize the understanding of its technical content, and not to introduce new errors due to the misunderstanding of its correct translation. It should also be added that a good compilation of it can be represented by the perspective of offering the best description possible on what it does, on its characteristics, and its functioning. This does not represent a condition \u002F suggestion, but it indicates the motivation for which the changelog of this plugin was left in English.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, does not set any cookies, and it does not connect to any third-party websites. It only uses functionality that is available in WordPress. In that terms does not affect your website’s users privacy in any way.\u003C\u002Fp>\n\u003Ch4>GDPR\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, but does not do anything to make your site less GDPR compliant. I have done my best to ensure that is 100% GDPR compliant, but I’m not a lawyer, so can’t guarantee anything. To determine if your site is GDPR compliant, please consult an attorney.\u003C\u002Fp>\n","dismiss serve happy nag php dashboard widget when it is activated or if it is in mu-plugins directory -- By Luciano Croce",0,1285,"2019-01-14T22:45:00.000Z","5.1.22","4.9","5.2.4",[18,19,7,20,21],"disable-serve-happy-nag","dismiss-serve-happy-nag","remove-serve-happy-nag","servehappy","https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-server-nag\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-server-nag.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":29,"total_installs":30,"avg_security_score":31,"avg_patch_time_days":32,"trust_score":24,"computed_at":33},8,100,87,30,"2026-04-04T02:44:44.756Z",[35,48,64,79,95],{"slug":36,"name":37,"version":38,"author":7,"author_profile":8,"description":39,"short_description":40,"active_installs":11,"downloaded":41,"rating":11,"num_ratings":11,"last_updated":42,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":43,"homepage":46,"download_link":47,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"dismiss-wsod-protection","Dismiss WSoD Protection","1.0.0","\u003Cp>Dismiss \u003Cem>coming soon\u003C\u002Fem> “\u003Cstrong>WSoD\u003C\u002Fstrong>” Protection (White Screen of Death) when it is activated, or if it is in mu-plugins directory.\u003C\u002Fp>\n\u003Cp>Development takes place at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-wsod-protection\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Ftravis-ci.org\u002Fluciano-croce\u002Fdismiss-wsod-protection\u002F\" rel=\"nofollow ugc\">Travis CI\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Compatible with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdismiss-wsod-protection\u002F\" rel=\"nofollow ugc\">GlotPress Translations\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Approved in the repository of the plugin directory on 2019-02-01\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>this plugin use \u003Ca href=\"https:\u002F\u002Fsemver.org\u002F\" rel=\"nofollow ugc\">Semantic Versioning\u003C\u002Fa> MAJOR.MINOR.PATCH\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Because I made this?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>If you are not “interested” in this feature.\u003C\u002Fli>\n\u003Cli>For security purpose. Read more on \u003Ca href=\"https:\u002F\u002Fwww.zdnet.com\u002Farticle\u002Fconcerns-raised-about-wordpress-new-white-screen-of-death-protection-feature\u002F\" rel=\"nofollow ugc\">ZDNet here\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2019\u002F01\u002F14\u002Fphp-site-health-mechanisms-in-5-1\u002F\" rel=\"nofollow ugc\">Felix Arntz here\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>White Screen of Death (WSoD) was posponed to WP 5.2 instead of 5.1\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Also consult the Codex about how to “fix” the \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FCommon_WordPress_Errors\u002F\" rel=\"nofollow ugc\">White Screen of Death\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-wsod-protection.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Also, for translation functionality, put all files of the single languages (dismiss-wsod-protection-en_US.mo for example) that you need (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) and will also be loaded by default, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin is not written with a PHP framework, but manually, with a simple PHP editor compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor. This author is exonerated from any responsibility or damage (directly or indirectly) caused and due to the use of this bad practice.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>super light secure and fast plugin easy on server resources\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>About me\u003C\u002Fh4>\n\u003Cp>Dismiss WSoD Protection is developed by Luciano Croce, 13-years “officially” WordPress Plugins & Themes Developer Senior, Co-Author of plugin Classic Editor, polyglot (based on English, French, Spanish, German, Portuguese, Italian, Ligurian), Local Manager of WP Community Ligurian Language LIJ, GTE en_GB & en_CA, CLPTE for en_AU, PTE for Plugins & Themes in more other languages, PTE for Italian WordPress.org & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for WordPress.com, translator for my & other projects, book author of TRUE DOS (the dark side of its history from the dark side of its users) Code Tweaker & Bug Hunter, Security Mechanic & WPMU Lover, Freelancer & Volunteer.\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cp>Translated by: \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fluciano-croce\u002F\" rel=\"nofollow ugc\">Luciano Croce\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Translators, except the similar strings “Release Date: February 01, 2019” or strings before latest version number “1.0.0” (for example), remember to leave all the other changelog strings commented in GlotPress “Meta” as “Found in changelog list item section” in english (copy from original -> suggest new translation) according to my disclaimer (read it after this section) all contributes are appreciated, and are credited!\u003C\u002Fp>\n\u003Ch4>Disclaimer\u003C\u002Fh4>\n\u003Cp>Given that the more languages in which the readme.txt file is translated, the greater the possibility of reaching a larger number of people, even through the use of search engines, with the exception of the main descriptions, it is a good practice, not to translate the changelog of the file readme.txt file in the various languages different from en_US (except for the other English languages derived from English – this is not a rule – everyone is free to translate or not translate according to the indications of their own polyglots community) to standardize the understanding of its technical content, and not to introduce new errors due to the misunderstanding of its correct translation. It should also be added that a good compilation of it can be represented by the perspective of offering the best description possible on what it does, on its characteristics, and its functioning. This does not represent a condition \u002F suggestion, but it indicates the motivation for which the changelog of this plugin was left in English.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, does not set any cookies, and it does not connect to any third-party websites. It only uses functionality that is available in WordPress. In those terms, it does not affect your website users’ privacy in any way.\u003C\u002Fp>\n\u003Ch4>GDPR\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, but does not do anything to make your site less GDPR compliant. I have done my best to ensure that is 100% GDPR compliant, but I’m not a lawyer, so can’t guarantee anything. To determine if your site is GDPR compliant, please consult a lawyer.\u003C\u002Fp>\n","dismiss wordpress wsod (white screen of death) protection introduced in wp 5.1-beta1 for security purpose -- By Luciano Croce",1392,"2019-02-12T11:30:00.000Z",[44,36,7,21,45],"disable-wsod-protection","white-screen-of-death","https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-wsod-protection\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-wsod-protection.zip",{"slug":49,"name":50,"version":51,"author":7,"author_profile":8,"description":52,"short_description":53,"active_installs":54,"downloaded":55,"rating":11,"num_ratings":11,"last_updated":56,"tested_up_to":57,"requires_at_least":15,"requires_php":16,"tags":58,"homepage":62,"download_link":63,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"dismiss-gutenberg-nag","Dismiss Gutenberg Nag","1.0.5","\u003Cp>Dismiss \u003Cstrong>try Gutenberg\u003C\u002Fstrong> nag, \u003Cstrong>dashboard widget\u003C\u002Fstrong>, and demo menu, when it is activated, or automatically, if it is in mu-plugins directory. Development for this plugin, takes place at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-gutenberg-nag\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Ftravis-ci.org\u002Fluciano-croce\u002Fdismiss-gutenberg-nag\u002F\" rel=\"nofollow ugc\">Travis CI\u003C\u002Fa>. \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-gutenberg-nag\u002F\" rel=\"ugc\">Dismiss Gutenberg Nag\u003C\u002Fa> is the best companion of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-welcome-nag\u002F\" rel=\"ugc\">Dismiss Welcome Panel Nag\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-browser-nag\u002F\" rel=\"ugc\">Dismiss Browser Update Nag\u003C\u002Fa>. Compatible with GlotPress \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fit\u002Fdefault\u002Fwp-plugins\u002Fdismiss-gutenberg-nag\" rel=\"nofollow ugc\">translations\u003C\u002Fa>. Work with Single and Multisite installation. Plugin approved in the repository of the plugin directory on 2017-11-05\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>This is not a replacement but just a tool for those who need it.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>To date\u003C\u002Fstrong>, \u003Cstrong>try Gutenberg\u003C\u002Fstrong>, preliminarily introduced in WP \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fnews\u002F2017\u002F10\u002Fwordpress-4-9-beta-3\u002F\" rel=\"ugc\">4.9-beta3\u003C\u002Fa>, in WP \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fchangeset\u002F42869\u002F\" rel=\"nofollow ugc\">4.9.5-beta1-42869\u003C\u002Fa>, and WP \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fchangeset\u002F43502\u002F\" rel=\"nofollow ugc\">4.9.8-beta1-43502\u003C\u002Fa>, respectively removed in WP 4.9-beta4, in WP 4.9-RC1, in WP 4.9-RC2, in WP 4.9-RC3, in WP 4.9.0, in WP 4.9.1, in WP 4.9.2, in WP 4.9.3, in WP 4.9.4, in WP \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fchangeset\u002F42883\u002F\" rel=\"nofollow ugc\">4.9.5-beta1-42883\u003C\u002Fa>, in WP 4.9.5, in WP 4.9.6, in WP 4.9.7, in WP 4.9.9, in WP 5.0-alpha, and in WP 5.1-alpha, \u003Cstrong>is embedded in core of WP 4.9.8 and WP 5.0+\u003C\u002Fstrong> according with this \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F41316\u002F\" rel=\"nofollow ugc\">ticket\u003C\u002Fa> and this \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F45063\u002F\" rel=\"nofollow ugc\">ticket\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>This plugin use \u003Ca href=\"https:\u002F\u002Fsemver.org\u002F\" rel=\"nofollow ugc\">Semantic Versioning\u003C\u002Fa> MAJOR.MINOR.PATCH\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>Future version 1.0.6 disable Gutenberg Editor and replace it with Classic Editor.\u003C\u002Fp>\n\u003Cp>Please note that this plugin does not add its custom code to WordPress (just to not create unexpected incompatibilities with Gutenberg or Classic Editor), but is limited only to the management and configuration of its functions, to offer the maximum of its experience of use, without introducing possible additional problems. Enjoy!\u003C\u002Fp>\n\u003Ch4>How Work?\u003C\u002Fh4>\n\u003Cp>By default try Gutenberg is displayed only for users with administrator capability in WordPress 4.9.8 but when the Gutenberg plugin is installed and activated, is displayed for all user capability type.\u003C\u002Fp>\n\u003Cp>An option configuration page is added to the settings -> writing menu so that you can set the callout display according to your needs. Stick to the screenshots for more details.\u003C\u002Fp>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-gutenberg-nag.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Ch4>Explanation\u003C\u002Fh4>\n\u003Cp>This, is different from the other similar plugins, because uses the filter hook, and not the action hook. Filters should filter information, thus receiving information\u002Fdata, applying the filter and returning information\u002Fdata, and then used. However, filters are still action hooks. WordPress defines add_filter\u002Fremove_filter as “hooks a function to a specific filter action”, and add_action\u002Fremove_action as “hooks a function on to a specific action”.\u003C\u002Fp>\n\u003Ch4>What is Gutenberg?\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgutenberg\u002F\" rel=\"ugc\">Gutenberg\u003C\u002Fa> is new block editor editing experience for WordPress 5.0+\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin, is not written with a php framework, but with a simple php editor, manually, compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor.\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cp>Translated by: \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fluciano-croce\u002F\" rel=\"nofollow ugc\">Luciano Croce\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>This is a stable project, but it is still in full development (in progress). The translations in the various languages will be done only for all the parts that certainly will not be changed several times in this phase.\u003C\u002Fp>\n\u003Cp>Available soon in: American, Australian, Belgian FR, Brazilian, Canadian EN, Canadian FR, Catalan, Chilean, Colombian, English, French, German, Italian, New Zealander, Peruvian, Portuguese, Spanish, Swiss DE, Venezuelan, and more other languages in becoming.\u003C\u002Fp>\n\u003Ch4>Acknowledgements\u003C\u002Fh4>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fandg\u002F\" rel=\"nofollow ugc\">Andrea Gandino\u003C\u002Fa> for preliminary \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fit\u002Fdefault\u002Fwp-plugins\u002Fdismiss-gutenberg-nag\u002F\" rel=\"nofollow ugc\">Italian\u003C\u002Fa> translation approval, before I became italian PTE of my plugins.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fgarrett-eclipse\u002F\" rel=\"nofollow ugc\">Garrett Hyder\u003C\u002Fa> for \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Fdismiss-gutenberg-nag\u002F\" rel=\"nofollow ugc\">English (Canada)\u003C\u002Fa> translation approval, and code contributions.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fswissspidy\u002F\" rel=\"nofollow ugc\">Pascal Birchler\u003C\u002Fa> for code contributions.\u003C\u002Fp>\n","dismiss try gutenberg nag dashboard widget and demo menu disable gutenberg editor and replace with classic editor remove code — by Luciano Croce",50,4721,"2018-11-25T18:04:00.000Z","5.0.25",[59,49,60,61,7],"dismiss-dashboard-widget","dismiss-gutenberg-widget","gutenberg","https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-gutenberg-nag\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-gutenberg-nag.zip",{"slug":65,"name":66,"version":67,"author":7,"author_profile":8,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":11,"num_ratings":11,"last_updated":72,"tested_up_to":57,"requires_at_least":73,"requires_php":16,"tags":74,"homepage":77,"download_link":78,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"dismiss-browser-nag","Dismiss Browser Update Nag Dashboard Widget","1.0.1","\u003Cp>Dismiss \u003Cstrong>Browser Update\u003C\u002Fstrong> nag, \u003Cstrong>dashboard widget\u003C\u002Fstrong>, when it is activated, or automatically, if it is in mu-plugins directory. Development for this plugin, takes place at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-browser-nag\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Ftravis-ci.org\u002Fluciano-croce\u002Fdismiss-browser-nag\u002F\" rel=\"nofollow ugc\">Travis CI\u003C\u002Fa>. \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-browser-nag\u002F\" rel=\"ugc\">Dismiss Browser Update Nag\u003C\u002Fa> is the best companion of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-gutenberg-nag\u002F\" rel=\"ugc\">Dismiss Gutenberg Nag\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-welcome-nag\u002F\" rel=\"ugc\">Dismiss Welcome Panel Nag\u003C\u002Fa>. Compatible with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdismiss-browser-nag\" rel=\"nofollow ugc\">GlotPress Translations\u003C\u002Fa>. Plugin approved in the repository of the plugin directory on 2017-11-18\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Removing browser update widget, speeds up the loading of dashboard and yours operations on it.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-browser-nag.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Ch4>Explanation\u003C\u002Fh4>\n\u003Cp>This, is different from the other similar plugins, because uses the filter hook, and not the action hook. Filters should filter information, thus receiving information\u002Fdata, applying the filter and returning information\u002Fdata, and then used. However, filters are still action hooks. WordPress defines add_filter\u002Fremove_filter as “hooks a function to a specific filter action”, and add_action\u002Fremove_action as “hooks a function on to a specific action”.\u003C\u002Fp>\n\u003Ch4>What is Browser Update?\u003C\u002Fh4>\n\u003Cp>Browser Update is a way to find out what are the latest versions of the major browsers around, and also learn about alternative browsers that may fit even better than the one are currently using: an outdated browser makes computer unsafe. This function use \u003Ca href=\"https:\u002F\u002Fbrowsehappy.com\u002F\" rel=\"nofollow ugc\">Browse Happy\u003C\u002Fa>, a website created by the Web Standards Project in August 2004, to convince internet users to use a web browser other than Microsoft’s Internet Explorer. It focuses on security issues in Internet Explorer and suggests four alternatives: Mozilla Firefox, Opera, Safari and Google Chrome. The core of the site is a collection of stories of people who have switched from Internet Explorer to alternative web browsers. WordPress automatically implements this feature with an annoying widget that is displayed on the dashboard without administrator control, even when you consciously use an out-of-date browser for the most varied reasons.\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin, is not written with a php framework, but with a simple php editor, manually, compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor.\u003C\u002Fp>\n\u003Ch4>Translation\u003C\u002Fh4>\n\u003Cp>Translated by: \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fluciano-croce\u002F\" rel=\"nofollow ugc\">Luciano Croce\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Acknowledgements\u003C\u002Fh4>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fandg\u002F\" rel=\"nofollow ugc\">Andrea Gandino (andg)\u003C\u002Fa> for \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fit\u002Fdefault\u002Fwp-plugins\u002Fdismiss-browser-nag\" rel=\"nofollow ugc\">Italian\u003C\u002Fa> translation approval.\u003C\u002Fp>\n\u003Cp>Thanks to \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fgarrett-eclipse\u002F\" rel=\"nofollow ugc\">Garrett Hyder\u003C\u002Fa> for \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Flocale\u002Fen-ca\u002Fdefault\u002Fwp-plugins\u002Fdismiss-browser-nag\" rel=\"nofollow ugc\">English (Canada)\u003C\u002Fa> translation approval.\u003C\u002Fp>\n","dismiss browser update nag dashboard widget when it is activated or if it is in mu-plugins directory",10,1501,"2018-06-12T23:19:00.000Z","3.2",[75,76,65,59,7],"browser-update-nag","browser-update-widget","https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-browser-nag\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-browser-nag.zip",{"slug":80,"name":81,"version":6,"author":7,"author_profile":8,"description":82,"short_description":83,"active_installs":70,"downloaded":84,"rating":11,"num_ratings":11,"last_updated":85,"tested_up_to":14,"requires_at_least":86,"requires_php":16,"tags":87,"homepage":92,"download_link":93,"security_score":30,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":94},"dismiss-privacy-nag","Dismiss Privacy Nag","\u003Cp>Dismiss \u003Cstrong>Privacy Pointer\u003C\u002Fstrong> Nag, (added in version 4.9.6 — partially GDPR OFF) and admin notification, when it is activated, or if it is in mu-plugins directory.\u003C\u002Fp>\n\u003Cp>Development takes place at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-privacy-nag\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Ftravis-ci.org\u002Fluciano-croce\u002Fdismiss-privacy-nag\" rel=\"nofollow ugc\">Travis CI\u003C\u002Fa>. Compatible with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdismiss-privacy-nag\" rel=\"nofollow ugc\">GlotPress Translations\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Approved in the repository of the plugin directory on 2018-05-09\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If you need to completely disable and remove all Privacy Tools, Privacy Pointers, Privacy Notifications Nag, you can use\u003C\u002Fstrong> “\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-privacy-tools\" rel=\"ugc\">Dismiss Privacy Tools\u003C\u002Fa>“.\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cp>Based to the \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fplugins\u002Fwordpress-org\u002Fdetailed-plugin-guidelines\u002F#11-plugins-should-not-hijack-the-admin-dashboard\" rel=\"nofollow ugc\">Detailed Guidelines 11\u003C\u002Fa> principle: should not hijack the admin dashboard.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Users prefer and expect plugins to feel like part of WordPress.\u003C\u002Fli>\n\u003Cli>Constant nags and overwhelming the admin dashboard with unnecessary alerts detract from this experience.\u003C\u002Fli>\n\u003Cli>Upgrade prompts, notices, alerts, and the like must be limited in scope and used sparingly, be that contextually or only on the plugin’s setting page.\u003C\u002Fli>\n\u003Cli>Site wide notices or embedded dashboard widgets must be dismissible or self-dismiss when resolved.\u003C\u002Fli>\n\u003Cli>Error messages and alerts must include information on how to resolve the situation, and remove themselves when completed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because I made this?\u003C\u002Fp>\n\u003Cp>Seem that the new privacy pointer is not totally auto dismissible when is clicked one of the any admin menu links, for example:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If one of the any admin menu links was clicked, the privacy pointer disappear.\u003C\u002Fli>\n\u003Cli>If the dasboard admin menu link was clicked, the privacy pointer not disappear, return visible, and nagging user.\u003C\u002Fli>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F44136\" rel=\"nofollow ugc\">privacy pointer covers the thing it’s pointing at\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F43961\" rel=\"nofollow ugc\">privacy pointer popup covers collapsed admin menu\u003C\u002Fa>?\u003C\u002Fli>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F43996\" rel=\"nofollow ugc\">privacy pointer is misaligned to admin menu\u003C\u002Fa> when exist other admin menu items of 3rd party?\u003C\u002Fli>\n\u003Cli>Don’t show privacy feature pointer to new users: \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F44062\" rel=\"nofollow ugc\">doesn’t add the new callback to the dismissed_wp_pointers meta\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>The suggested code to auto dismiss it seem to not working well — remove_action( ‘admin_print_footer_scripts’, array( ‘WP_Internal_Pointers’, ‘pointer_wp496_privacy’ ) );\u003C\u002Fli>\n\u003Cli>The remove_action for pointer_wp496_privacy needed to be called from the admin_enqueue_scripts action with a priority of 11.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Add an admin pointer for new privacy features in version 4.9.6:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The new features are very important for some users, because of their GDPR obligations.\u003C\u002Fli>\n\u003Cli>They’re also spread across multiple top-level menus, making them less discoverable.\u003C\u002Fli>\n\u003Cli>An admin pointer will help to ensure that users are aware of the new tools and how to find them.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Props desrosj, andreamiddleton, allendav, xkon. Fixes #43942?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbuild.trac.wordpress.org\u002Fbrowser\u002Fbranches\u002F4.9?rev=42988\" rel=\"nofollow ugc\">4.9.6-alpha-43159\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fbrowser\u002Fbranches\u002F4.9?rev=43159\" rel=\"nofollow ugc\">4.9.6-alpha-42959-src\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbuild.trac.wordpress.org\u002Fbrowser\u002Ftrunk?rev=42987\" rel=\"nofollow ugc\">5.0-alpha-43158\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fbrowser\u002Ftrunk?rev=43158\" rel=\"nofollow ugc\">5.0-alpha-42970-src\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Technical References\u003C\u002Fh3>\n\u003Cp>Translators: leave all technical references in English!\u003C\u002Fp>\n\u003Cp>Dismiss all the new feature pointers.\u003C\u002Fp>\n\u003Cp>@since 3.3.0\u003C\u002Fp>\n\u003Cp>All pointers can be disabled using the following:\u003C\u002Fp>\n\u003Cp>remove_action( ‘admin_enqueue_scripts’, array( ‘WP_Internal_Pointers’, ‘enqueue_scripts’ ) ); # This work but “unfortunately” as alternative solution that remove all pointers!\u003C\u002Fp>\n\u003Cp>@param string $hook_suffix The current admin page.\u003C\u002Fp>\n\u003Cp>Dismiss a pointer for the new privacy tools.\u003C\u002Fp>\n\u003Cp>@since 4.9.6\u003C\u002Fp>\n\u003Cp>Privacy pointer can be disabled using the following:\u003C\u002Fp>\n\u003Cp>remove_action( ‘admin_print_footer_scripts’, array( ‘WP_Internal_Pointers’, ‘pointer_wp496_privacy’ ) ); # This for now not work: due a bug? Investigating… wp496_privacy ???\u003C\u002Fp>\n\u003Cp>@param string $hook_suffix The current admin page.\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cp>Issue (bug) \u003Cstrong>fixed by my brother Garrett Hyder\u003C\u002Fstrong> and tested from Pascal Birchler (swissspidy): refer to \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F45529\u002F\" rel=\"nofollow ugc\">Ticket 45529\u003C\u002Fa> opened by \u003Ca href=\"https:\u002F\u002Fprofile.wordpress.org\u002Fdaleharrison\" rel=\"nofollow ugc\">Dale Harrison\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Thanks to Ross McKay (webaware) and Stephen Edgar (netweb) to support me in New Zealander (English) translations, in some typo errors, and some minor (English) error stuff.\u003C\u002Fp>\n\u003Cp>Thanks to Fernando Tellado (fernandot) and Nilo Velez to support me in Spanish translations.\u003C\u002Fp>\n\u003Cp>Thanks to all!\u003C\u002Fp>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-privacy-nag.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Also, for translation functionality, put all files of the single languages (dismiss-privacy-nag-en_US.mo for example) that you need (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) and will also be loaded by default, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin is not written with a PHP framework, but manually, with a simple PHP editor compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor. This author is exonerated from any responsibility or damage (directly or indirectly) caused and due to the use of this bad practice.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>super light secure and fast plugin easy on server resources\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>About me\u003C\u002Fh4>\n\u003Cp>Dismiss Privacy Nag is developed by Luciano Croce, 13-years “officially” WordPress Plugins & Themes Developer Senior, Co-Author of plugin Classic Editor, polyglot (based on English, French, Spanish, German, Portuguese, Italian, Ligurian), GTE en_GB & en_CA, PTE for Plugins & Themes in more languages, PTE for Italian WordPress.org & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for WordPress.com, translator for my & other projects, book author of TRUE DOS (the dark side of its history from the dark side of its users) Code Tweaker & Bug Hunter, Security Mechanic & WPMU Lover, Freelancer & Volunteer.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, does not set any cookies, and it does not connect to any third-party websites. It only uses functionality that is available in WordPress. In those terms, it does not affect your website users’ privacy in any way.\u003C\u002Fp>\n\u003Ch4>GDPR\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, but does not do anything to make your site less GDPR compliant. I have done my best to ensure that is 100% GDPR compliant, but I’m not a lawyer, so can’t guarantee anything. To determine if your site is GDPR compliant, please consult a lawyer.\u003C\u002Fp>\n","dismiss privacy pointer nag and admin notification when it is activated or if it is in mu-plugins directory",2027,"","4.9.6",[88,7,89,90,91],"gdpr","personal-data-erase","personal-data-export","privacy-policy","https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-privacy-nag\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-privacy-nag.zip","2026-03-15T14:44:11.924Z",{"slug":96,"name":97,"version":6,"author":7,"author_profile":8,"description":98,"short_description":99,"active_installs":70,"downloaded":100,"rating":11,"num_ratings":11,"last_updated":101,"tested_up_to":14,"requires_at_least":86,"requires_php":16,"tags":102,"homepage":103,"download_link":104,"security_score":24,"vuln_count":11,"unpatched_count":11,"last_vuln_date":25,"fetched_at":26},"dismiss-privacy-tools","Dismiss Privacy Tools","\u003Cp>Disable and remove \u003Cstrong>Privacy Tools\u003C\u002Fstrong>, (added in version 4.9.6 — completely GDPR OFF) and reset options to default, when it is activated, or if it is in mu-plugins directory.\u003C\u002Fp>\n\u003Cp>Development takes place at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-privacy-tools\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Ftravis-ci.org\u002Fluciano-croce\u002Fdismiss-privacy-tools\" rel=\"nofollow ugc\">Travis CI\u003C\u002Fa>. Compatible with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fdismiss-privacy-tools\" rel=\"nofollow ugc\">GlotPress Translations\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Approved in the repository of the plugin directory on 2018-06-28\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If you need to partially disable only Privacy Pointers, Privacy Notification Nag, without removing Privacy Tools, you can use\u003C\u002Fstrong> “\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdismiss-privacy-nag\" rel=\"ugc\">Dismiss Privacy Nag\u003C\u002Fa>“.\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable Privacy Tool \u002Fwp-admin\u002Fprivacy.php\u003C\u002Fli>\n\u003Cli>Disable Erase Personal Data \u002Fwp-admin\u002Ftools.php?page=erase_personal_data\u003C\u002Fli>\n\u003Cli>Disable Export Personal Data \u002Fwp-admin\u002Ftools.php?page=export_personal_data\u003C\u002Fli>\n\u003Cli>Remove scheduled action used to delete old export files.\u003C\u002Fli>\n\u003Cli>Remove scheduled event used to delete old export files.\u003C\u002Fli>\n\u003Cli>Remove scheduled hook used to delete old export files.\u003C\u002Fli>\n\u003Cli>Short circuits the option for the privacy policy page to always return 0 to avoid unneeded database query.\u003C\u002Fli>\n\u003Cli>Delete unnecessary database options.\u003C\u002Fli>\n\u003Cli>Reset all options to default.\u003C\u002Fli>\n\u003Cli>Don’t show the privacy feature pointer to new users.\u003C\u002Fli>\n\u003Cli>The suggested code to auto dismiss it seem to not working well — remove_action( ‘admin_print_footer_scripts’, array( ‘WP_Internal_Pointers’, ‘pointer_wp496_privacy’ ) );\u003C\u002Fli>\n\u003Cli>The remove_action for pointer_wp496_privacy needed to be called from the admin_enqueue_scripts action with a priority of 11.\u003C\u002Fli>\n\u003Cli>NEW – Dismiss pointer for the new privacy tools. FIXED!\u003C\u002Fli>\n\u003Cli>NEW – Disable comments cookies opt-in and remove related option.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because I made this?\u003C\u002Fp>\n\u003Cp>Simply because is different to the other similar plugins.\u003C\u002Fp>\n\u003Ch3>Technical References\u003C\u002Fh3>\n\u003Cp>Translators: leave all technical references in English!\u003C\u002Fp>\n\u003Cp>Dismiss all the new feature pointers.\u003C\u002Fp>\n\u003Cp>@since 3.3.0\u003C\u002Fp>\n\u003Cp>All pointers can be disabled using the following:\u003C\u002Fp>\n\u003Cp>remove_action( ‘admin_enqueue_scripts’, array( ‘WP_Internal_Pointers’, ‘enqueue_scripts’ ) ); # This work but “unfortunately” as alternative solution that remove all pointers!\u003C\u002Fp>\n\u003Cp>@param string $hook_suffix The current admin page.\u003C\u002Fp>\n\u003Cp>Dismiss a pointer for the new privacy tools.\u003C\u002Fp>\n\u003Cp>@since 4.9.6\u003C\u002Fp>\n\u003Cp>Privacy pointer can be disabled using the following:\u003C\u002Fp>\n\u003Cp>remove_action( ‘admin_print_footer_scripts’, array( ‘WP_Internal_Pointers’, ‘pointer_wp496_privacy’ ) ); # This for now not work: due a bug? Investigating… wp496_privacy ???\u003C\u002Fp>\n\u003Cp>@param string $hook_suffix The current admin page.\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cp>Issue (bug) \u003Cstrong>fixed by my brother Garrett Hyder\u003C\u002Fstrong> and tested from Pascal Birchler (swissspidy): refer to \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F45529\u002F\" rel=\"nofollow ugc\">Ticket 45529\u003C\u002Fa> opened by \u003Ca href=\"https:\u002F\u002Fprofile.wordpress.org\u002Fdaleharrison\" rel=\"nofollow ugc\">Dale Harrison\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Thanks to Ross McKay (webaware) and Stephen Edgar (netweb) to support me in New Zealander (English) translations, in some typo errors, and some minor (English) error stuff.\u003C\u002Fp>\n\u003Cp>Thanks to Fernando Tellado (fernandot) and Nilo Velez to support me in Spanish translations.\u003C\u002Fp>\n\u003Cp>Thanks to all!\u003C\u002Fp>\n\u003Ch4>Tips\u003C\u002Fh4>\n\u003Cp>A neat trick, is to put this single file dismiss-privacy-tools.php (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) so you won’t even have to enable it, and will be loaded by default, also, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Also, for translation functionality, put all files of the single languages (dismiss-privacy-tools-en_US.mo for example) that you need (not its parent directory) in the \u002Fwp-content\u002Fmu-plugins\u002F directory (create it if not exists) and will also be loaded by default, since first step installation of WordPress setup!\u003C\u002Fp>\n\u003Cp>Note that mu-plugins functionality is available since WP 2.8+ or greater and is not present in WP 2.7+ or previous.\u003C\u002Fp>\n\u003Ch4>About it\u003C\u002Fh4>\n\u003Cp>The code of this plugin is not written with a PHP framework, but manually, with a simple PHP editor compatible UTF-8 without BOM, and Unix LF. To avoid code corruption, do not edit it with WordPress embedded editor, or with any specifications incompatible editor. This author is exonerated from any responsibility or damage (directly or indirectly) caused and due to the use of this bad practice.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>super light secure and fast plugin easy on server resources\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>About me\u003C\u002Fh4>\n\u003Cp>Dismiss Privacy Tools is developed by Luciano Croce, 13-years “officially” WordPress Plugins & Themes Developer Senior, Co-Author of plugin Classic Editor, polyglot (based on English, French, Spanish, German, Portuguese, Italian, Ligurian), GTE en_GB & en_CA, PTE for Plugins & Themes in more languages, PTE for Italian WordPress.org & Plugins & Themes Directory, Local Manager of Ligurian Language Community for WP LIJ, Validator English (UK) for WordPress.com, translator for my & other projects, book author of TRUE DOS (the dark side of its history from the dark side of its users) Code Tweaker & Bug Hunter, Security Mechanic & WPMU Lover, Freelancer & Volunteer.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, does not set any cookies, and it does not connect to any third-party websites. It only uses functionality that is available in WordPress. In those terms, it does not affect your website users’ privacy in any way.\u003C\u002Fp>\n\u003Ch4>GDPR\u003C\u002Fh4>\n\u003Cp>This plugin does not collect or store any user related data or personally identifying information, but does not do anything to make your site less GDPR compliant. I have done my best to ensure that is 100% GDPR compliant, but I’m not a lawyer, so can’t guarantee anything. To determine if your site is GDPR compliant, please consult a lawyer.\u003C\u002Fp>\n","disable and remove privacy tools added in 4.9.6 completely GDPR OFF reset options to default when it is activated or if it is in mu-plugins directory",2011,"2019-01-25T02:47:00.000Z",[88,7,89,90,91],"https:\u002F\u002Fgithub.com\u002Fluciano-croce\u002Fdismiss-privacy-tools\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdismiss-privacy-tools.zip",{"attackSurface":106,"codeSignals":161,"taintFlows":169,"riskAssessment":170,"analyzedAt":173},{"hooks":107,"ajaxHandlers":157,"restRoutes":158,"shortcodes":159,"cronEvents":160,"entryPointCount":11,"unprotectedCount":11},[108,114,118,121,124,127,129,134,137,141,144,147,150,154],{"type":109,"name":110,"callback":111,"priority":11,"file":112,"line":113},"action","admin_init","ddwsun_psd_php_version_init","dismiss-server-nag.php",129,{"type":109,"name":115,"callback":116,"file":112,"line":117},"admin_notices","ddwsun_ant_php_version_init",130,{"type":109,"name":119,"callback":116,"file":112,"line":120},"network_admin_notices",131,{"type":109,"name":110,"callback":122,"priority":11,"file":112,"line":123},"ddwsun_psd_wp_version_init",178,{"type":109,"name":115,"callback":125,"file":112,"line":126},"ddwsun_ant_wp_version_init",179,{"type":109,"name":119,"callback":125,"file":112,"line":128},180,{"type":130,"name":131,"callback":132,"file":112,"line":133},"filter","plugins_loaded","ddwsun_load_plugin_textdomain",217,{"type":130,"name":131,"callback":135,"file":112,"line":136},"ddwsun_load_muplugin_textdomain",219,{"type":130,"name":138,"callback":139,"priority":70,"file":112,"line":140},"plugin_row_meta","ddwsun_adds_row_meta_build",221,{"type":130,"name":138,"callback":142,"priority":70,"file":112,"line":143},"ddwsun_adds_row_meta_links",223,{"type":130,"name":138,"callback":145,"priority":70,"file":112,"line":146},"ddwsun_adds_row_meta_details",227,{"type":130,"name":110,"callback":148,"file":112,"line":149},"remove_dashboard_widget_serve_happy_nag",251,{"type":130,"name":151,"callback":152,"file":112,"line":153},"wp_dashboard_setup","dismiss_dashboard_widget_serve_happy_nag",252,{"type":130,"name":151,"callback":155,"file":112,"line":156},"disable_dashboard_widget_serve_happy_nag",253,[],[],[],[],{"dangerousFunctions":162,"sqlUsage":163,"outputEscaping":165,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":167,"bundledLibraries":168},[],{"prepared":11,"raw":11,"locations":164},[],{"escaped":11,"rawEcho":11,"locations":166},[],1,[],[],{"summary":171,"deductions":172},"The \"dismiss-server-nag\" plugin v1.0.2 exhibits a strong security posture based on the provided static analysis.  It demonstrates adherence to good development practices by having no identified dangerous functions, all SQL queries utilizing prepared statements, and all output being properly escaped.  Furthermore, the absence of file operations and external HTTP requests minimizes potential attack vectors. The plugin also shows an awareness of security by including one capability check, although the lack of nonce checks on potential AJAX handlers (which are themselves absent) is a theoretical weakness if they were to be introduced without proper authentication.\n\nThe vulnerability history for this plugin is entirely clean, with zero recorded CVEs. This, combined with the robust static analysis findings, suggests a well-maintained and secure codebase. The plugin has no significant known vulnerabilities, past or present. While the absence of any reported vulnerabilities is excellent, it's also worth noting that a very small or inactive plugin might not have been subjected to the same level of scrutiny as a more popular one. However, based solely on the provided data, the plugin is considered highly secure.",[],"2026-03-17T06:16:02.319Z",{"wat":175,"direct":181},{"assetPaths":176,"generatorPatterns":178,"scriptPaths":179,"versionParams":180},[177],"\u002Fwp-content\u002Fplugins\u002Fdismiss-server-nag\u002Fdismiss-server-nag.php",[],[],[],{"cssClasses":182,"htmlComments":189,"htmlAttributes":191,"restEndpoints":194,"jsGlobals":195,"shortcodeOutput":196},[183,184,185,186,187,188],"notice","notice-error","is-dismissible","error","notice-warning","updated",[190],"\u003C!-- This script remove update message when plugin is auto deactivated -->",[192,193],"data-plugin-name","data-plugin-version",[],[116],[]]