Juliette Reinders Folmer

Based on the link you gave, try adding this classname to the list: post-971

For more information about class names, you may want to dive into this: https://www.w3schools.com/tags/att_global_class.asp

This is being discussed on GitHub: https://github.com/eagerterrier/MimeTypes-Link-Icons/issues/29

@romanbon If it helps, you may want to follow the TGMPA twitter account which will announce new releases: https://twitter.com/tgmpa

Version 2.6.1 was released over a year ago.
FYI: v2.6.2 is expected to be released some time over the next month or so.

@ironfish2 As long as the TGMPA version the theme includes is fairly recent (2.6.0 or higher), the admin notice will only be shown to users with “author” level or higher, not to “ordinary” users.

I just checked, but unfortunately, the Sydney theme uses an outdated version (2.5.2).

@romanbon Presuming you are the maintainer of the theme: Please download a fresh copy of TGMPA using the correct settings – i.e choose ””www.remarpro.com”” as distribution channel in the Custom TGMPA Generator and distribute it with the next version of the theme.
Keeping the included software in your theme up-to-date is always a good idea.

@ironfish2 Once the theme has updated the included version of TGMPA, you can use a filter to change the user capability needed for displaying the TGMPA admin notice, like so:
add_filter( 'tgmpa_show_admin_notice_capability', create_function( '$cap', 'return \'edit_pages\';' ) );

For more information, see the first entries in the “enhancements” section of TGMPA 2.6.0: https://github.com/TGMPA/TGM-Plugin-Activation/blob/develop/CHANGELOG.md#260-2016-05-14

This was fixed 8 months ago….

Hijacking someone else’s issue is frowned upon. Open your own instead.

• This reply was modified 7 years, 3 months ago by Juliette Reinders Folmer.

@huykon3006 Hijacking someone else’s issue is frowned upon. Open your own instead. Or better yet: read the previously provided answers as that should solve your issue already.

Hi @nabetse, Thanks for reporting this. Your webhost has disabled one of the PHP functions the plugin uses. You could ask the webhost to enable it.

In the mean time, I’m hoping to get a work-around accepted for the next release of the Debug Bar, so at least you shouldn’t get the warning anymore: https://github.com/dd32/debug-bar/pull/37

I look forward to your pull request in that case.

@mac2net Not sure if you mean me, but I don’t recognize myself in your words at all. And **nothing** ever takes 5 minutes to sort.

If someone has some time & a solution, you’re welcome to contribute to the plugin: https://github.com/mjangda/plugin-notes

Are you still seeing this error when using Debug Bar version 0.9 ?

The current version of the Debug Bar should work fine on WP 4.6.x

Just in case you’re still wondering – or for the next person who has the same question -:

The Debug Bar in a multi-site setup will show only to super admins.

Since version 0.9, however, you can selectively overrule this using the debug_bar_enable filter.

In code, this would be something like:

// Make sure you add this filter before the <code>admin_bar_init</code> action is run!
add_filter( 'debug_bar_enable', 'my_debug_bar_enabler' );

function my_debug_bar_enable( $enabled ) {
	if ( current_user_can( 'manage_options' ) ) {
		$enabled = true;
	}

	return $enabled;
}

Hope this helps ??

The only reason you should get that error, is that the plugin is already active. Could it be that the vagrant box you use comes with the Debug Bar plugin set up in the must-use plugins by default ?

Not sure whether this is still relevant for you, but just in case:

Even using WP_DEBUG to get errors to display, you may still miss some errors as they are in hidden divs etc.

Your best bet to get a full insight in all the errors generated by a WP install, including plugins and themes, is to turn on error logging.

For example code on how to do this, see https://gist.github.com/jrfnl/5925642

While the Debug Bar still does not play nice with error logging, this is expected to be fixed in an upcoming future release.