Warning on my WordPress Admin Dashboard

To rule out any theme/plugin conflict, try:
– deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
– switching to the unedited default Theme (Twenty Seventeen, etc.) for a moment using the WP dashboard to rule out any theme-specific issue (theme functions can interfere like plugins).

Alternately, if you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

Looks like an IPv6 error. Check with your host to make sure it is enabled/compiled with PHP.

Disabled everything including themes, still the warning shows on the admin screen.

On Dashboard activity it shows:

Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /hermes/bosnaweb24a/b1101/ipg.ecorporatemarketing92637/social/wp-includes/functions.php on line 4147 Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /hermes/bosnaweb24a/b1101/ipg.ecorporatemarketing92637/social/wp-includes/functions.php on line 4147

What did you before this error occurred?

nothing. just 2 days before i connected my site to cloudfare.com

That’s a new warning that will probably disappear when you re-enable plugins.

The original error is about IPv6. To check that your server was compiled with IPv6 support, load a page up into your site with following code:
<?php phpinfo(); ?>

Load the page and check if *IPv6 Support* is set to “disabled”, if so, that is the cause of the error.

Check your wp-config.php file for this line :
define('WP_DEBUG', true);

If you do, change it to define('WP_DEBUG', false);

Yes. On Phpinfo page: IPv6 Support is disabled.

OK. i have changed WP_DEBUG to False and its gone now.

Hope it will not affect my site. Thanks for all the quick help.

Server not being configured for IPv6 is probably not the issue. The above script handles both IPv4 & IPv6 and 6 to 4 conversion. HOWEVER problem might be due to other known bugs in the script. Proposed fix (for WP5.0?) here: Dashboard: Strip more extraneous IP parts to prevent PHP warnings.

Other possibilities:

The WordPress script checks for “visitor” IP address in some BUT NOT ALL relevant server IP address variables. Surprisingly the script does not look for an IP address in $_SERVER[‘HTTP_X_REAL_IP’] which is sometimes (often?) the only variable containing the “actual” visitor IP on sites that are behind NGINX servers.

If familiar with PHP you can copy and run this [link redacted] script to identify which IP address variables are set and contain valid visitor IP addresses. (I wrote it for my own use).

Are these errors appearing when you are logged in over the internet or only if your device is “directly” connected to your server? e.g. via inTRAnet in which case your device may be assigned a private IP address.

• This reply was modified 6 years, 6 months ago by Andrew Nevins.

@wrigs1, We appreciate that you took the time to help out. Can we just make a little suggestion; that information is kept inside this thread and not linked to on other blogs?

@anevins Apologies. I wasn’t aware relevant external links were frowned upon. I accept the slap on the wrist! In my defence; it was code I published long ago, I only mentioned it as an afterthought when I realised it would be a helpful supplement to my answer. (I’m used to Stackoverflow where inclusion of useful links is common).

• This reply was modified 6 years, 6 months ago by wrigs1.
• This reply was modified 6 years, 6 months ago by wrigs1.