Hi
I have version 1.2.14 installed and upgraded from 1.2.13 and previous versions and decided to do a fresh installation of 1.2.14 on a testing site so that in future upgrades i will test the upgrade before upgrading the live site and here what i found as an issue but don't if it is something important.
In the live site, the upgraded version, in the database table "custom_lists" the available fields are
(`rowid`, `custom_block_id`, `data_type`, `id`, `store_id`, `sort_order`, `date_added`, `date_modified`)
while in the 1.2.14 version fresh installation the available fields are
(`rowid`, `custom_block_id`, `data_type`, `id`, `sort_order`, `date_added`, `date_modified`)
note the [store_id] column is not available!!
Possibly that this is an issue or bug that affects the cart??
1.2.14 upgrade script does contain alter to this table
ALTER TABLE `ac_custom_lists`
ADD COLUMN `store_id` INT NULL DEFAULT 0 AFTER `id`;
Did you get any error during upgrade?
The upgrade version of 1.2.14 does contain the column [store_id] but the fresh installation of 1.2.14 does not. teh question is which is correct?? to have the column [store_id] or without??
Are you sure? I can see this column in 1.2.14 right now:
https://github.com/abantecart/abantecart-src/blob/master/public_html/install/abantecart_database.sql#L10256
Where do you see it missing?
When i did the installation this column was missing possibly an error in the installation process
Quote from: hani on May 07, 2019, 08:07:31 AM
while in the 1.2.14 version fresh installation the available fields are
(`rowid`, `custom_block_id`, `data_type`, `id`, `sort_order`, `date_added`, `date_modified`)
Hi. I am just install 1.2.14 from the source https://github.com/abantecart/abantecart-src/archive/1.2.14.zip and store_id column present in database so where did you get you installation files or what way you use to install AbanteCart (cPanel installer, bitnami or any other)?
I had it downloaded when it was released in the beginning and installed it but never mind i just wanted to bring your attention to this issue.
Installation process would not have this issue, if install SQL is correct.
Very strange.
Keep us posted if you encounter this again.