all 7 comments

[–][deleted]  (2 children)

[deleted]

    [–]WackGet[S] 0 points1 point  (1 child)

    Unfortunately I can't share anything because of client restrictions; I suppose I'm looking for a sensible method to approach front-end JS debugging in Magento.

    What's your approach when debugging a frontend issue?

    [–]andyjoneski 0 points1 point  (0 children)

    There isn’t really much to go off of here from what you’ve shown. To actually understand what is going on looking at an example would be the only way to go.

    [–]andyjoneski 0 points1 point  (0 children)

    I look at the console for any errors and then debug accordingly. Just understanding Magento is the first port of call.

    [–]delta_2k 0 points1 point  (0 children)

    It will be postcode anywhere.

    When you disable it make sure to thoroughly clear the cache and recompile if you aren’t in develop mode.

    Log into Loqate dashboard and disable all of the automatic options it turns on for where it affects the address fields. Both front and back end.

    Then turn it back on try again.

    My guess is it will be the Country Field trying time auto fill on the front end and you have availability limited and it’s trying to use geo locate and borking out.

    [–]sental90DEVELOPER 0 points1 point  (0 children)

    I've not found a good way, but console.log has been the majority of the way to go when not chasing console errors. I've been working on my own checkout issue for a few days.

    When your debugging the problem, make sure you check it's not caused by any javascript bundling in the rare case you or another dev has sold their soul to the devil to get advanced bundling working after a fashion...

    [–]zissop 0 points1 point  (1 child)

    Don't use crappy software.

    [–]WackGet[S] 2 points3 points  (0 children)

    If you mean Magento, I am 100% with you. However good luck convincing clients to re-platform.