AbleCommerce Shopping Cart Software

When we tell our accounting/business software to remove an item from the web store. The auto process is not doing this.
The question is when removing an item through the database which tables need to be updated to remove the item or just hide it, so it can not be viewed or sold?
Thank you.

Its the ac_Products table. You can also set the desired item visibility to private in order to hide and disable its purchase.

Our devoloper asks, "Visibility ID (basically this state that products visibility on the web. The values that appear in this column is 0, 1 and 2. Can you please let us know the description of these values and its behavior on the web)".

0 = Public //Product is visible people can access it
1 = Hidden //Product is hidden but still if anyone have a direct link he/she can access it
2 = Private //Product is hidden and no one can access it even via direct URL.

Why isn't this information in the wiki? I have had to figure out codes out by deduction and trial and error. Is information like this (codes for database fields, etc.) available somewhere else?

mazhar wrote:0 = Public //Product is visible people can access it
1 = Hidden //Product is hidden but still if anyone have a direct link he/she can access it
2 = Private //Product is hidden and no one can access it even via direct URL.

If an item is marked "Private" can it still be ordered from the administrative interface? I need to hide some items from the public but still be able to create orders administratively that include these items.

You can not place order for item with private visibility as stand alone item from merchant side but if this private item is a part of kit then private item will be included in placed order. In fact upon checkout basket is validated and if it sees private item added as stand alone item then it will remove it from the list.

DerlinStiles wrote:Why isn't this information in the wiki? I have had to figure out codes out by deduction and trial and error. Is information like this (codes for database fields, etc.) available somewhere else?

The assumption is most people are using Visual Studio for making changes to their AC7 storefront. In Visual Studio, you can quickly and easily see what values are associated with these types of "ID" fields, thus documenting them only adds another layer of effort and the potential for stale documentation. In .Net programming, we call them "ENUM" values.

Determining the values for each choice is pretty quick and simple if you have access to the SQL database. The sticky part is when you're trying to run an external report writer to expose your store data in a different format. Then you only see the underlying values such as "0", or "2" and have to make the report translate those values into meaniful text.