Page 1 of 1
Errors Shipment and Add to Cart after Login
Posted: 14 Apr 2022, 13:45
by immcom
Hello,
using J4, everything seems to work nice, but after login i have following errors:
Steps: Login in frontend > select a product > button Add to Cart does not work.
When enabling shipment rule
Steps: Select a product > Add to Cart > Checkout > Login > error 1364 Field 'params_shipping' doesn't have a default value
Please, how to fix?
Thanks!
Re: Errors Shipment and Add to Cart after Login
Posted: 15 Apr 2022, 22:50
by Jan
Hi, which "add to cart" method do you use (ajax or standard)? Try to see Javascript console if there is no Javascript error on your site which prevents from running AJAX (
https://www.phoca.cz/documents/16-jooml ... -conflicts )
params_shipping - did you install the component from scratch or did you migrate from Joomla 3 version?
Jan
Re: Errors Shipment and Add to Cart after Login
Posted: 18 Apr 2022, 19:08
by immcom
Hi Jan, thanks for the reply.
All is installed from scratch: J4, Helix, Phoca Cart. The site is under development. There are no javascript errors. The only error that appears in console when clicking on Add to cart is - XHR POST https: // .... HTTP / 2 1364 No Reason Phrase.
It appears only after login. I have tried to verify all the settings, I have tried Add to cart with Standard metod but I cannot solve the problem.
Re: Errors 1364 on Add to Cart after Login
Posted: 19 Apr 2022, 09:29
by immcom
Hello Jan,
I found that the field "params_shipping" is present in 2 tables: 'cart_multiple' and 'orders' where the value is empty.
So, I set 0 (zero, as on other similar fields) into 'cart_multiple' for the fields "params_shipping" and "params_payment" for the same error that appeared later. I'm not sure that this is the correct solution but for the moment it works without problems.
If you consider that it is correct solution or maybe you can explain us how to do better and close the post as Solved, it could be useful for other users.
Thanks!
Re: Errors Shipment and Add to Cart after Login
Posted: 23 Apr 2022, 00:32
by Jan
This could be related to rules set in database (some strict rules can limit the text field). The problematic part is when this will be changed for some database type, then it can be in another conflict with other database type (or the rules set there).
Jan