Conflict with GiveWP? (backend error message)

  • Resolved photoMaldives

    (@photomaldives)


    11 months, 3 weeks ago

    Hi Jeff.

    I spotted a weird error just now – WP backend, working on the GiveWP plugin, an error message breaks onto screen that seems to come from your plugin? >

    <div id="mceu_62" class="mce-widget mce-notification mce-notification-error mce-has-close mce-in"...

Failed to initialize plugin: sdc_download

    Browser console error below >

    tinymce.min.js?ver=49110-20201110:2  Failed to initialize plugin: sdc_download ReferenceError: download_counter is not defined
    at t.<computed>.t.<computed>.init (tinymce.js?wp-mce-49110-20201110:14:13)
    at Ew (tinymce.min.js?ver=49110-20201110:2:330514)
    at Array.<anonymous> (tinymce.min.js?ver=49110-20201110:2:332223)
    at Object.jt [as each] (tinymce.min.js?ver=49110-20201110:2:29356)
    at Aw (tinymce.min.js?ver=49110-20201110:2:332173)
    at tN.<anonymous> (tinymce.min.js?ver=49110-20201110:2:333551)
    at Array.<anonymous> (tinymce.min.js?ver=49110-20201110:2:96969)
    at jt (tinymce.min.js?ver=49110-20201110:2:29356)
    at u (tinymce.min.js?ver=49110-20201110:2:96914)
    at n (tinymce.min.js?ver=49110-20201110:2:96402)

    Thanks, and keep up the great work. ??

Viewing 5 replies - 31 through 35 (of 35 total)
  • Plugin Author Jeff Starr

    (@specialk)

    You did most of the work, so thank YOU. It is my pleasure to implement this solution next update. Cheers, @garrettm30.

    Thread Starter photoMaldives

    (@photomaldives)

    Great work, @garrettm30 ! I have been following your updates with interest.

    And thanks Jeff @specialk for engaging with interest and professionalism (and for your upcoming fix!)

    Plugin Author Jeff Starr

    (@specialk)

    Just to follow up with this: version 1.9 of SDC resolves this issue. Should be available later today or tomorrow. Thanks again @garrettm30.

    Sorry for the delay in getting this tested. I have done a simple test to confirm that the issue is resolved as I was seeing it.

    1. Before the updated, I loaded an admin page where the problem could be seen to confirm I identified the problem.
    2. I updated the plugin.
    3. I refreshed the admin page where the problem was.
    4. Problem gone.

    Thanks.

    Plugin Author Jeff Starr

    (@specialk)

    Perfect, thank you for confirming the issue is resolved.

    Cheers.

Viewing 5 replies - 31 through 35 (of 35 total)
  • You must be logged in to reply to this topic.