Plugin updates for any plugin not running when this plugin activated

  • Resolved Joel Lisenby

    (@joellisenby)


    7 months, 1 week ago

    For some reason there is a javascript error with this plugin when I try to run plugin updates. Has anyone else experienced this? Sorry I disabled the plugin and ran updates and it worked, so I can’t get the exact JS error, but it went away after disabling this plugin. Perhaps scripts are loading on the plugin update page that should not be loading there.

    This is happening up to the 5.0.0 version of the plugin for me.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author ibsofts

    (@ibsofts)

    We have checked it on our end and everything appears to be working fine. If you still encounter issue, you can reach out to our support portal on https://support.ibsofts.com/ .
    We’d like to resolve this as soon as possible for you.

    Thread Starter Joel Lisenby

    (@joellisenby)

    Hello, some updates were out today so I re-tried running updates to plugins and here are the two errors in the JS console that block updates from running when I check the select all checkbox then click the “Update Plugins” button.

    Line 100 in /wp-content/plugins/go-high-level-extension-for-gravity-form/admin/js/ghl-gf-extension-admin.js?ver=5.0.0

    ghl-gf-extension-admin.js?ver=5.0.0:100 
    Uncaught TypeError: $ is not a function
        at HTMLDocument.<anonymous> (ghl-gf-extension-adm…js?ver=5.0.0:100:13)
        at HTMLDocument.dispatch (jquery.min.js?ver=3.7.1:2:40035)
        at v.handle (jquery.min.js?ver=3.7.1:2:38006)
    (anonymous)	@	ghl-gf-extension-admin.js?ver=5.0.0:100
    dispatch	@	jquery.min.js?ver=3.7.1:2
    v.handle	@	jquery.min.js?ver=3.7.1:2

    Line 100 in /wp-content/plugins/go-high-level-extension-for-gravity-form/admin/js/ghl-gf-extension-admin.js?ver=5.0.0

    ghl-gf-extension-admin.js?ver=5.0.0:100 
    Uncaught TypeError: $ is not a function
        at HTMLDocument.<anonymous> (ghl-gf-extension-adm…js?ver=5.0.0:100:13)
        at HTMLDocument.dispatch (jquery.min.js?ver=3.7.1:2:40035)
        at v.handle (jquery.min.js?ver=3.7.1:2:38006)
        at Object.trigger (jquery.min.js?ver=3.7.1:2:70124)
        at HTMLInputElement.<anonymous> (jquery.min.js?ver=3.7.1:2:70726)
        at Function.each (jquery.min.js?ver=3.7.1:2:3129)
        at e.<computed>.each (jquery.min.js?ver=3.7.1:2:1594)
        at e.<computed>.trigger (jquery.min.js?ver=3.7.1:2:70701)
        at e.<computed>.<anonymous> (jquery-migrate.min.js?ver=3.4.1:2:10514)
        at e.<computed> [as click] (jquery-migrate.min.js?ver=3.4.1:2:1582)
    (anonymous)	@	ghl-gf-extension-admin.js?ver=5.0.0:100
    dispatch	@	jquery.min.js?ver=3.7.1:2
    v.handle	@	jquery.min.js?ver=3.7.1:2
    trigger	@	jquery.min.js?ver=3.7.1:2
    (anonymous)	@	jquery.min.js?ver=3.7.1:2
    each	@	jquery.min.js?ver=3.7.1:2
    each	@	jquery.min.js?ver=3.7.1:2
    trigger	@	jquery.min.js?ver=3.7.1:2
    (anonymous)	@	jquery-migrate.min.js?ver=3.4.1:2
    e.<computed>	@	jquery-migrate.min.js?ver=3.4.1:2
    (anonymous)	@	wpe-common.js?ver=5.0.1:101
    (anonymous)	@	wpe-common.js?ver=5.0.1:273
    dispatch	@	jquery.min.js?ver=3.7.1:2
    v.handle	@	jquery.min.js?ver=3.7.1:2
        $('a.exit--toast').click(function() {
            $("#openToast").fadeOut(1000, 0);
        });

        $(document).on('click', function (e) {
            if ($(e.target).closest(".notification--reminder").length === 0) {
                $("#openToast").fadeOut(1000, 0);
            }
        });

        $(document).ready(function() {
            $('#location-table').DataTable();
        });
    });

    I see at the top of this file you have

    $ = jQuery;
    $(document).ready(function(){

    Perhaps instead you should use the more common method here:

    jQuery(document).ready(function($) {
    Plugin Author ibsofts

    (@ibsofts)

    Apologies for the inconvenience caused, we have fixed this issue in our updated version (5.0.1)
    Thank you.

    Thread Starter Joel Lisenby

    (@joellisenby)

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin updates for any plugin not running when this plugin activated’ is closed to new replies.