Warning after 5.5 WordPress Upgrade

  • Resolved taylakay

    (@taylakay)


    4 years, 3 months ago

    Hi there. Thank you for producing a fantastic plugin. I am using a Migrate Helper Plugin after the 5.5 update and I just reactivated your plugin and updated to your latest version.

    I did however get this warning: /wp-content/plugins/ns-cloner-site-copier/js/ns-cloner.js: jQuery.fn.load() is deprecated

    Will you be providing an update? Or would this potentially be showing up due to a cache issue. Do you think it is still safe to clone a site with the above error? Thanks for your advice.

    • This topic was modified 4 years, 3 months ago by taylakay.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Never Settle

    (@neversettle)

    Hi @taylakay – thanks for the question. It’s correct that jQuery’s .load event handler is deprecated with jQuery 1.8, but:

    1) The default jQuery version included in the WP core (even WP 5.5) is jQuery 1.12.4, so I’m guessing you have a plugin or something besides the jQuery Migrate Helper plugin that’s replacing the default version with a newer one (the error doesn’t appear with out-of-the-box WP 5.5).
    2) It won’t affect cloning at all – if it did, you’d know right away because the button to start cloning just wouldn’t work.

    So, we will take note to update that handler in our next release for future compatibility (and thanks for the heads up) but the plugin is fine to use as-is.

    Hi,

    Just to verify, after an upgrade to WP 5.5, I get a blank screen for Cloner unless I activate a migrate plugin. This will be taken care of in a future release?

    I verified that jQuery 1.12.4 is the only file being loaded.

    Plugin Author Never Settle

    (@neversettle)

    Hi @timswm – sounds like you’re getting something totally different than described by the OP. Can you check your browser console and PHP error log and provide a specific error message?

    HI,

    Thanks for getting back to me, and sorry about hijacking the post. In looking at the console, I see it was another plugin causing the issue. I failed to notice it as it was not part of the network admin, but still active. Sorry about that!

    Plugin Author Never Settle

    (@neversettle)

    No problem, thanks for the update!

    Thread Starter taylakay

    (@taylakay)

    @timswm what plugin was it out of curiousity causing the issue?

    @taylakay It ended up being an internal plugin that was updated in other locations, but not this particular instance.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Warning after 5.5 WordPress Upgrade’ is closed to new replies.