Help for integrating the Laravel package
Forum rules: Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
#3985 by George Horvath
03 Mar 2017, 11:10

I was spent a lot of time to research why customers table are empty.

I found the logic how you store addresses for customers from the checkout page in the orders table. It stored in there anyway the user chose to register an account or not on the checkout last page.

I want to make a profile page where you can add or modify any of addresses what they have in the system for billing or shipping, and I want these addresses make selectable on checkout address page.

I found customer/address manager what is ready and fully functional how i see, but never used to store addresses in mshop_customer_address table on the checkout process.

I would like to ask some help which method I have to choose:

1-if somebody registering an account on checkout process i have to search in the orders table for any stored addresses to the user and where to store if the user want to add another address to his account or change an existing address ?
In this case what happens if somebody delete the order from extadm (with stored addresses)?

2-i have to change the core checkout process and if somebody registering on checkout process i have to store it in customer table and its easyly manage on profile page because addresses are independent from any existing orders. But the core changes in this case and on an update its possibily disappear from core if any file updated by you guys.

Thank you for any help or idea!

#3990 by aimeos
03 Mar 2017, 14:32
The "mshop_customer*" tables are not used by the Aimeos Laravel integration. Instead, the standard Laravel "users" table is populated and the related "users_address" table. The accounts created in the checkout process are already stored in these tables, so you only need to access and save the data back using the Aimeos customer/address manager.