• Resolved artifexmedia

    (@artifexmedia)


    The plug-in immediatly throws this error when visiting the check-out page, and does the same when details are being changed.

    It is trying to split the address but complains the second part (number) is missing, while it’s not. I did see that it is also trying to get shipping address, even though the ‘Ship to anther address’ is NOT checked, meaning for new clients and guests the address field there will be empty – resulting into PostNL not being able to split it – as there is nothing to split..

    I am not sure wether this error is causing the plugin to break, but after adding details as a guest there is nothing appearing from PostNL, no error message, nothing. Probably because it is trying to do something with shipping details.

    While logged in, the error remains but the process does work.

    Full error:

    postnl.js?ver=3.1.7:898 Uncaught TypeError: Cannot read property '1' of null
        at Object.splitFullStreetFromInput (postnl.js?ver=3.1.7:898)
        at Object.getAddressInputValues (postnl.js?ver=3.1.7:875)
        at Object.setAddressFromInputFields (postnl.js?ver=3.1.7:845)
        at Object.callDeliveryOptions (postnl.js?ver=3.1.7:917)
        at Object.init (postnl.js?ver=3.1.7:55)
        at postnl.js?ver=3.1.7:988

    URL:
    https://checkout.artifexmedia.nl/

    Yes, everything is up-to-date and the issue remains the same with just only WooCommerce, Storefront and PostNL active.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author PostNL

    (@postnl)

    We are currently making a new plugin. This problem will be solved in this version.

    Thread Starter artifexmedia

    (@artifexmedia)

    Hi PostNL,

    Thanks, as I need to fix all problems myself (there are 3 major issues more that I haven’t posted yet, but will wait with those), could you let me know if there is a roadmap for the new plugin, or a estimated release month/period and what the changes will be?

    We currently integrated the current version with slight changes, but if the new plugin is going to be different a lot, I’d like to know if it still has use for me (and my clients money) to continue implementing and changing the current plugin|

    And also, by your comment I can assume there will no longer be support on the current plugin? As in; bugs will not be fixed untill the new plugin arrives?

    • This reply was modified 4 years, 3 months ago by artifexmedia.
    Plugin Author PostNL

    (@postnl)

    Hi @artifexmedia,

    A new version of the plug-in has been released last week. There have been substantial changes to the plugin, not only in functionality and improvements but also in the software architecture. You can find the changes in the changelog:

    https://github.com/postnl/woocommerce/releases/tag/v4.0.1

    Also before upgrading we recommend checking out the reported unresolved issues of last week.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Uncaught TypeError: Cannot read property ‘1’ of null’ is closed to new replies.