Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter andrealddedit

    (@andrealddedit)

    A long as you have access to your file directory, you can remove the plugin. I had to switch to another plugin, and then we switched payment providers anyway, so it was a moot point.

    Thread Starter andrealddedit

    (@andrealddedit)

    Greetings,

    Any further work on this plugin? I have not re-updated to the 1.0.4 version, since the last time I did my staging site malfunctioned, but I am willing to try again. Thank you~

    Thread Starter andrealddedit

    (@andrealddedit)

    Oh dear! I just installed the 1.0.4 update and broke my staging site! I am making a new site, and reverting to an earlier install of the plugin.

    Edit to add:
    “Broke my staging site” means it simply loaded a “fatal error” message box and I could not load it up to edit it. I have created a new staging site, reverting the NMI plugin to the previous version (1.0.3) and set the checkout page to “classic”.

    the new staging site is number 7381 with all other elements of the original website address the same.

    • This reply was modified 2 months, 1 week ago by andrealddedit. Reason: more information to give to developer
    Thread Starter andrealddedit

    (@andrealddedit)

    As promised, the attempt to paste the error:

    nmicheckout.js?ver=1.1:272 Uncaught ReferenceError: CollectJS is not defined
    at trigger_nmi_checkout (nmicheckout.js?ver=1.1:272:13)
    at HTMLBodyElement. (nmicheckout.js?ver=1.1:527:9)
    at HTMLBodyElement.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 HTMLBodyElement. (jquery.min.js?ver=3.7.1:2:70726)
    at ce.each (jquery.min.js?ver=3.7.1:2:3129)
    at e..each (jquery.min.js?ver=3.7.1:2:1594)
    at e..trigger (jquery.min.js?ver=3.7.1:2:70701)
    at HTMLInputElement.payment_method_selected (checkout.min.js?ver=10.6.1:1:4655)

    Thread Starter andrealddedit

    (@andrealddedit)

    Yes, that is how I set them, because that was the pathway I saw in the user interface.

    Our WooCommerce version is 10.6.1 – the latest, as far as I can tell. I updated everything I could when the issue was first discovered because our host tech support would not give assistance until I did!

    It looks like 7 errors, if I am interpreting this correctly?
    SyntaxError at Gateway.js & Collect.js, and 5 different instances of ReferenceError: CollectJS is not defined

    I’m going to attempt to copy-paste one of the referenceerrors in my next reply and hopefully it doesn’t break the thread…

    Thread Starter andrealddedit

    (@andrealddedit)

    Thank you for working on the plugin, but I still have errors.

    Firstly: I have to use “Classic Checkout” because in the updated Checkout Block for WooCommerce it says: Network Merchants Inc – NMI CC does not yet support this block. 
    When I use the Checkout Block with the plugin the user side of the website displays the message: There are no payment methods available. Please contact us for help placing your order.

    Secondly, when I switch the checkout page back to classic mode, the backend of the website no longer appears to error (unless it is buried in code), but the user experience displays the error: Payment Token not received. is a required field.

    Is there something I need to adjust on my end? I have a private security key, a public tokenization key and a public checkout key in the appropriate boxes in the plugin settings.

    Thank you~

Viewing 6 replies - 1 through 6 (of 6 total)