[wp-trac] [WordPress Trac] #57310: Possibility to dismiss plugin update notification until next version or forever
WordPress Trac
noreply at wordpress.org
Wed Jan 11 12:20:53 UTC 2023
#57310: Possibility to dismiss plugin update notification until next version or
forever
-----------------------------+------------------------------
Reporter: abitofmind | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version: 6.1.1
Severity: normal | Resolution:
Keywords: 2nd-opinion | Focuses:
-----------------------------+------------------------------
Comment (by costdev):
Hi @abitofmind, splitting this up with titles as I'm currently limited to
mobile use at the moment.
=== Must-Use plugin
Must-Use plugins load from a single file in the `mu-plugins` folder, so if
you wanted to convert Better Admin Bar to a Must-Use plugin (**which I do
not recommend but will of course not refuse you the knowledge**), you can
do the following:
1. Copy the `better-admin-bar` plugin folder from `wp-content/plugins/` to
`wp-content/mu-plugins/`.
2. Create a new file directly in the `mu-plugins` folder called `better-
admin-bar.php` with the following contents:
{{{#!php
<?php
/*
Plugin Name: Better Admin Bar
Plugin URI: https://kubiq.sk
Description: Better Admin Bar
Version: 3.4
Author: KubiQ
Author URI: https://kubiq.sk
Text Domain: better_admin_bar
Domain Path: /languages
*/
require_once __DIR__ . '/better-admin-bar/better-admin-bar.php';
}}}
3. Check everything works as expected.
=== Via Plugin
Options such as those you proposed are very much within the territory of
plugins, so this is a good idea for anyone who wants these options.
As you said, as opposed to Must-Use plugins, this would have the benefit
that updates would still be possible, but simply be delayed for the
selected duration, and all could be restored simply by disabling the
options plugin.
I really appreciate that you're mindful of language such as "Advanced"
rather than "Disable" to try to minimise negative use. However, despite
this, as these options still run counter to Core's philosophy, the plugin
wouldn't be a Canonical plugin. That is, it would not be developed by the
WordPress Core team.
So, a plugin to offer those options would need to be submitted by a third-
party developer - who has either created the plugin using their own
initiative, or has been hired to create the plugin.
Of course, anyone coming across this ticket should be mindful that a
third-party plugin developer to create such a plugin should be looked for
somewhere other than WordPress Core Trac/Slack instances.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57310#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list