ereckers

I marked this as resolved, as it was an issue with the Stream plugin using this deprecated function:

https://www.ads-software.com/support/topic/php-deprecated-from-yoast-seo/

This ticket can even be deleted (if that’s a thing) as I added it here in err.

I’m seeing the same thing. I’m using Yoast + Yoast Premium.. I’m up-to-date:

+------------------------------+-------------+-------------+---------+
| name                         | old_version | new_version | status  |
+------------------------------+-------------+-------------+---------+
| wordpress-seo                | 23.5        | 23.6        | Updated |
| wordpress-seo-premium        | 23.5        | 23.6        | Updated |
+------------------------------+-------------+-------------+---------+

I can see it runs in file: stream/connectors/class-connector-wordpress-seo.php

/**
 * Logs WordPress SEO meta activity
 *
 * @param int    $object_id   Object ID.
 * @param int    $meta_key    Meta key.
 * @param string $meta_value  Meta value.
 */
private function meta( $object_id, $meta_key, $meta_value ) {
    $prefix = \WPSEO_Meta::$meta_prefix;

    \WPSEO_Metabox::translate_meta_boxes();

I’m seeing it mostly in the backend/dashboard. A Google search of the notice shows that it’s apparently coming up on the front end of many sites.

• This reply was modified 1 month, 1 week ago by ereckers.
• This reply was modified 1 month, 1 week ago by ereckers.

Yes. That does answer my questions. Makes sense. Thank you for replying.

@kasparsd yes. I can confirm this fixes the notice. Thank you!

I’m seeing the same issue.

Leland, just downloaded the latest update and I can confirm that the Notice no longer appears.

Thanks Leland.

I’ll let you guys mark as resolved once the fix is out?

Here’s a screenshot of the Notice that appears at the top of a blog post page: https://s3-us-west-1.amazonaws.com/redbridgenet/addthis-notice-screenshot.png

It’s a “Notice” that appears both in the Dashboard and prints to the top of the page on the frontend. The HTML looks like this:

<br />
<b>Notice</b>:  register_uninstall_hook was called <strong>incorrectly</strong>. Only a static class method or function can be used in an uninstall hook. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.1.0.) in <b>/srv/www/mysite/htdocs/wp-includes/functions.php</b> on line <b>4147</b><br />

This is in local development with the following wp-config.php settings:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'WP_DEBUG_LOG', true );
define( 'SCRIPT_DEBUG', true );

I haven’t yet updated in production and I’m not displaying Notices live so a URL to the website wouldn’t help.

This Notice does not affect the display or functionality of the AddThis plugin and sharing buttons.

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

Great! Just updated with 3.0.3 and it’s fixed. Thanks!

Thanks for the resources Jeremy.

I went back in a day later and I was able to gain access normally. I should have provided the IP address in the original, but I do know it was unrecognizable to me.

As far as any other caching plugins. I didn’t have any other implemented, no CDNs like CloudFlare, etc.. Just vanilla WP Engine.

As for the plugin by Mark: https://www.ads-software.com/plugins/manual-control/.

This is a WordPress plugin development question, but can I do a pull request to simply help test that it’s “Compatible up to: ***”? Though Jaquith is a big WordPress guy, the “hasn’t been updated in over 2 years” notice is something that should be knocked out.

I’m chiming in to say I’ve got the same issue.

I’m also getting “Your IP (xxx.xxx.xxx.xxx) has been flagged for potential security violations”.

The IP address returned is not my IP address.

Worst of all. I didn’t want this Jetpack service enabled.

I’m hosting at WP Engine if that helps. I’ve cleared the WP Engine cache with no help.

Still looking into a solution, but just wanted to register the issue and my general displeasure.

Thank you for the fix @amor. I can confirm that it works.

This is the first time I ever found I needed to load my own child theme’s stylesheet.

Looks, like the Storefront folks are on a fix, but if in a pinch, @amor’s fix works for me.

Alright thanks.

@wslade,

Thanks. I’m looking over a few plugins and themes now. If anyone else has worked with anything they were happy with, be sure to mention it.

I’ll be sure to updated this with what I find.