The Try Gutenberg callout was removed in https://core.trac.wordpress.org/changeset/43807.

That means we should remove the option to hide it when the WordPress version is higher or equal 5.0-alpha-43807.

Before:

After:

Somehow Antispam Bee isn't available in the list of dashboard widgets to disable. Investigate.

Doesn't work. Totally strange. Very sad.

WordPress 4.8 is scheduled to be released on June 8.

We should check if this plugin is ready and update the readme accordingly.

Field Guide: https://make.wordpress.org/core/2017/05/26/wordpress-4-8-field-guide/

The GitHub link in the "Contribute" section points to WP Widget Disable.

It's a WordPress plugin so the "WP" prefix isn't really necessary IMO.

The success message is always displayed twice.

WordPress 4.9 being released this week we should check if this plugin is ready and update the readme accordingly.

Field Guide: https://make.wordpress.org/core/2017/11/07/wordpress-4-9-field-guide/

Issues we could solve at the same time: #23.

Needs similar treatment as the welcome panel:

WordPress somehow doesn't allow me to get the dashboard widgets without having to send the user to the Dashboard once to save them as an option.

Any idea how to fix this?

The settings error messages get showed twice.

https://plugins.svn.wordpress.org/wp-widget-disable/assets/banner-1544x500.png doesn't show the current version of the plugin.

Reported here: https://wordpress.org/support/topic/debug-errors-please/

Screenshot:

$widget['title'] doesn't seem to exist in all cases. The line in question:

Probably doesn't hurt to add some hardening there. We can do this while flattening the array:

Same goes for get_default_dashboard_widgets():

We should check whether the array key exists / is set in this section:

Core has a wp_dashboard_browser_nag() and wp_dashboard_php_nag() widget. Both are registered depending on an API call, wp_check_browser_version() and wp_check_php_version(). Thus both are not collected by the current collector.

I'm proposing to add both widgets as hardcoded settings like we did with the Gutenberg callout. To disable the widgets, when set, we can use the site transient filter to prevent the API call which finally prevents registering the dashboard widgets.

// Browser nag
$key = md5( $_SERVER['HTTP_USER_AGENT'] );
add_filter( 'pre_site_transient_browser_' . $key, '__return_null' );

// PHP nag
$key = md5( phpversion() );
add_filter( 'pre_site_transient_php_check_' . $key, '__return_null' );

They were added to core in https://core.trac.wordpress.org/changeset/40052 for 4.8.

Related commit: 1745805

Once removed it will look like this for <= 4.7:

Not that bad.

With PHP 7.4 and WordPress 5.4.2 I'm seeing a few PHP notices on the dashboard when some widgets are disabled.

You should be able to reproduce the issue by installing the plugin and disabling any dashboard widget which is not welcome_panel, dashboard_browser_nag and dashboard_php_nag.

Should we consider adding an option to disable editor blocks across the board?

There are plugins like https://wordpress.org/plugins/manager-for-gutenberg/ that offer this as well, but perhaps our users would like to have this integrated into this plugin.

Current HTML looks like:

	<form method="post" action="options.php">
		<input type='hidden' name='option_page' value='rplus_wp_widget_disable_dashboard_option' /><input type="hidden" name="action" value="update" /><input type="hidden" id="_wpnonce" name="_wpnonce" value="5c5298378c" /><input type="hidden" name="_wp_http_referer" value="/wp-admin/themes.php?page=wp-widget-disable&amp;tab=dashboard" /><h2>Disable Dashboard Widgets</h2>
<p>Choose the dashboard widgets you would like to disable.</p><table class="form-table"><tr><th scope="row">Dashboard Widgets</th><td>		<p>
			<input type="checkbox" id="wp_widget_disable_select_all"/>
			<label for="wp_widget_disable_select_all">Select all</label>
		</p>
		<p>
			<input type="checkbox" id="dashboard_welcome_panel"
			       name="rplus_wp_widget_disable_dashboard_option[dashboard_welcome_panel]"
			       value="normal"
				 checked='checked'>
			<label for="dashboard_welcome_panel">
			<label for="dashboard_welcome_panel">
				Welcome panel (<code>welcome_panel</code>)			</label>
		</p>
		<p><input type="checkbox" id="dashboard_right_now" name="rplus_wp_widget_disable_dashboard_option[dashboard_right_now]" value="normal"  checked='checked'><label for="dashboard_right_now">At a Glance (<code>dashboard_right_now</code>)</label></p><p><input type="checkbox" id="dashboard_activity" name="rplus_wp_widget_disable_dashboard_option[dashboard_activity]" value="normal"  checked='checked'><label for="dashboard_activity">Activity (<code>dashboard_activity</code>)</label></p><p><input type="checkbox" id="dashboard_quick_press" name="rplus_wp_widget_disable_dashboard_option[dashboard_quick_press]" value="side"  checked='checked'><label for="dashboard_quick_press"><span class="hide-if-no-js">Quick Draft</span> <span class="hide-if-js">Drafts</span> (<code>dashboard_quick_press</code>)</label></p><p><input type="checkbox" id="dashboard_primary" name="rplus_wp_widget_disable_dashboard_option[dashboard_primary]" value="side"  checked='checked'><label for="dashboard_primary">WordPress News (<code>dashboard_primary</code>)</label></p></td></tr></table><p class="submit"><input type="submit" name="submit" id="submit" class="button button-primary" value="Save Changes"  /></p>	</form>

Right now it doesn't matter if you activate the plugin for the whole network or for each site individually.

However, if you network activate it, it's currently not possible to disable widgets in the network admin dashboard. Shouldn't be too hard to allow this.

In WordPress 5.8 the sidebar area has moved to a block area. The old core widgets cannot be added.

Do we hide the Widget settings if the classic area is not enabled?

Do we create a new setting to disable the blocks for the widget area?

rplus_wp_widget_disable_default_dashboard_filter gives you back the list (array) of all dashboard widgets before we sotre them, so you could basically remove dashboard widgets from being disabled.

store

Makes it easier to select lots of widgets.

Perhaps shift-select makes sense too? See this SO thread for an example.

• Do not add version to composer.json
• Leverage https://github.com/wearerequired/wp-requirements-check
• Remove unneeded Grunt tasks

Couldn't find any issues so far. There are only a few cosmetic bugs: https://github.com/wearerequired/WP-Widget-Disable/milestone/2?closed=1

• Update changelog
• Update meta data
• Bump versions

A few dashboard widgets I have are not detected and I cannot disable them-
-WPForms
-Post Views Counter

Add the actual textdomain instead of $this->plugin_slug in the strings related to this, because it won't work otherwise.

https://github.com/wearerequired/WP-Widget-Disable/blob/1.6.0/views/admin.php#L17

See https://make.wordpress.org/core/2015/10/28/headings-hierarchy-changes-in-the-admin-screens/

Once #31 is merged, we can prepare releasing version 1.9.0

• Bump version in wp-widget-disable.php
• Add changelog and upgrade notice in readme.txt
• Add changelog CHANGELOG.md
• Commit to trunk on plugins.svn.wordpress.org
• Tag 1.9.0 on plugins.svn.wordpress.org

To create the gettext files and maybe generate the readme

Contrary to the widgets screen, widgets are not sorted in any particular way on the plugin's settings screen.