search

myparcelnl / magento1-End-of-life

MyParcel plugin for Magento 1
Other
7 stars 5 forks source link

Uncaught RangeError: Maximum call stack size exceeded Magento 1.9 #465

Closed EnigmaWebdesign closed 5 years ago

EnigmaWebdesign commented 5 years ago

Hi all,

We are using the latest Myparcel extension 1.17.4 with OneStepCheckout 5.0.1 (OneStepCheckout.com) At the moment we have a serious error where the loader keeps on loading for 20 - 30 seconds in the checkout. After the page finally loads we see this error:

Uncaught RangeError: Maximum call stack size exceeded. at Object.mapExternalWebshopTriggers (myparcel.js:413) at Object.triggerDefaultOptionDelivery (myparcel.js:523) at Object.addDeliveryToMagentoInput (myparcel.js:497) at Object.mapExternalWebshopTriggers (myparcel.js:416) at Object.triggerDefaultOptionDelivery (myparcel.js:523) at Object.addDeliveryToMagentoInput (myparcel.js:497) at Object.mapExternalWebshopTriggers (myparcel.js:416) at Object.triggerDefaultOptionDelivery (myparcel.js:523) at Object.addDeliveryToMagentoInput (myparcel.js:497) at Object.mapExternalWebshopTriggers (myparcel.js:416)

This is Magento 1.9.4.1 CE.

What is going wrong here and why does the loader take that long to resolve.

br,

Steve

RichardPerdaan commented 5 years ago

Hi @EnigmaWebdesign,

We currently do not support version 5.0.1 of the OneStepCheckout.

Configuration : System : Magento Admin 2019-06-12 13-26-38

I will find out what exactly needs to be changed and what the impact will be.

RichardPerdaan commented 5 years ago

Hi @EnigmaWebdesign,

I have tested the plugin with the data you specified and I see the following:

myparcel

The page is fully loaded in 18 seconds en there are no errors. Perhaps it has to do with specific OneStepCheckout settings. I used the standard OneStepCheckout settings and see no problems.

EnigmaWebdesign commented 5 years ago

Problem was solved. Seems there is an API bug with PostNL. This was triggered if a national holiday was also active on a Monday. I hope PostNL has fixed this bug.

Cheers,

Steve