It seems that the number of different products that can be processed through the checkout is limited by the memory and execution time available on the server encrypting and saving the data.
In the situation where the resources available are insufficient to process the number of products in the cart, the customer simply receives an "Internal Server Error" message. No information is provided on why this has occurred or what to do about it and there is the near certainty of a lost sale.
While increasing the resources available to the script may be a workaround, I do not believe that this is the correct way to deal with an error condition of this type. The software seems able to build orders on a completely open ended basis and of a size that cannot be processed, no matter how much resource is available. I'm not sure that this conforms to what might be considered good software design.
Could I suggest that the process of transmitting the order data to the server is broken down into a series of small, discrete transactions and that a configurable option is added to Actinic to limit the number of products that can be presented to the checkout process.
This should enable large orders to be handled without the dependency of a correspondingly large amount of resource on the server and give the shop administrator the option to limit the size of the basket if they wish.
Thanks,
Alan
In the situation where the resources available are insufficient to process the number of products in the cart, the customer simply receives an "Internal Server Error" message. No information is provided on why this has occurred or what to do about it and there is the near certainty of a lost sale.
While increasing the resources available to the script may be a workaround, I do not believe that this is the correct way to deal with an error condition of this type. The software seems able to build orders on a completely open ended basis and of a size that cannot be processed, no matter how much resource is available. I'm not sure that this conforms to what might be considered good software design.
Could I suggest that the process of transmitting the order data to the server is broken down into a series of small, discrete transactions and that a configurable option is added to Actinic to limit the number of products that can be presented to the checkout process.
This should enable large orders to be handled without the dependency of a correspondingly large amount of resource on the server and give the shop administrator the option to limit the size of the basket if they wish.
Thanks,
Alan
Comment