Home>Support>Known error? Notice: class-wp-upgrader-skins.php is deprecated

Known error? Notice: class-wp-upgrader-skins.php is deprecated

Hi there,

After updating WordPress to 4.7.5 and Vantage Premium to 2.6 I’m getting a message on the top of my screen:

Notice: class-wp-upgrader-skins.php is deprecated since version 4.7.0! Use class-wp-upgrader.php instead.

I’ve searched around, but didn’t find how to fix this.

Any advice how to solve this problem? How harmful is it to ignore this (though annoying) message?

Hope you help me.

Cheers, Martin

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 7 years, 3 months ago Alex S
    Hi, I Work Here

    Hi Martin,

    That’s odd. Under what context are you seeing this? Does this issue occur if you temporarily change the theme? I ask as I can’t seem to experience this issue.

    This is safe for you to personally ignore at this time but we’ll look to resolve this to prevent issues down the line when the functionality is completely removed.

  2. 7 years, 3 months ago martin1509

    Hi Alex,

    Thank you and good to know it can be ignored.

    I’m getting the message in every context: on login-page, backend and frontend as well. Changing the theme to Twenty Seventeen didn’t have an impact: the notice didn’t disappear. It is always next to a same kind of notice stating my JetPack connection is broken.

  3. 7 years, 3 months ago Alex S
    Hi, I Work Here

    Hi Martin,

    If the error remains after changing theme it means something else is causing it. Can you please run a general plugin conflict test to try and work out the cause?

    Try disabling all plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.

    Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

  4. 7 years, 3 months ago martin1509

    Hi Alex,

    Thank you for giving this approach, definately a great way to diagnose which configuration is causing the issue. I will do this.

    I’ve read on the internet more about this kind of notices, advice was given to turn off debugging. My site works fine now, although I know this error message is still present (although under the surface).

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More