Stock by Attribute v4.0 addon for v1.3.5-1.3.9

I can't get the SQL file for this mod to upload, it keeps giving the following error:

1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"zen_cfg_select_option(array('true', 'false'),"' at line 1
in:
[INSERT INTO zen_configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Show available stock level in cart when less than order', 'STOCK_SHOW_LOW_IN_CART', 'false', 'When customer places more items in cart than are available, show the available amount on the shopping cart page:', '9', '6', NULL, now(), NULL, "zen_cfg_select_option(array('true', 'false'),"]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.

Does anyone know how to fix this? It's for a 1.3.9g store.

Thanks!

Please ignore. I posted to the wrong thread.

Ive just noticed that my SBA is not working after upgrading to 1.39f
So I downloaded the latest SBA from the downloads area today, and uploaded the files, replacing the necessary core files as instructed. I went to the admin area and when I click on the products with attributes stock via CP, I get a a page with a search box, sync link, but otherwise its empty, with no products showing. However there is an error code...

1054 Unknown column 'sort' in 'order clause'
in:
[select * from products_with_attributes_stock where products_id="52" order by sort ASC;]

Ive inspected the item 52 and it does have attributes associated with it, but like the other products, does not show up in the SBA Admin. Attributes do show up in the (frontend) dropdown of the product page however, but quantity per attribute cannot be adjusted.
As per the instructions, I did no database patching, but what seems to be causing this error?
Sorry if I have missed a previous answer to the issue at hand..I did try search for this error via this site and google...but nothing?

Thanks..Any help/direction appreciated!

Just noticed there was an sql file with the download, altho not mentioned in the instructions. File was update_1_4_10.sql
So, not having anything to lose, and knowing I had not updated the SBA in over a year..I gave it a shot. But nothing. Still have the same condition now as described in my post above.

I really need to get this corrected, as there already have been orders for sizes which are supposed to be out of stock.

Thanks!

OK..guess I will give this one last bump.
I know the help here is all volunteer, but come on now, surely there is something one of you can suggest????

@fireball

Sounds to me like you jumped to 4.10 or later of the mod without applying the upgrade sql which adds that missing sort column to the products_with_attributes_stock table.

Thanks Kuroi :smile:

Well, that may be..I wanted to check the version level, but the core files were over written with the update. I did run the update sql as mentioned above, and it did add one row/table, but I still have the same error.
Because the instructions say no changes needed to your database with a previous 4.x installation, Ive been avoiding running any other sql patch until I got some input.

Thanks again!

Yes, looks to me like the changelog, but not the instructions have been updated.

There are two parts to the upgrade sql. One adds a row to the config table, which it sounds as though your have done. The other adds a column called "sort" to the products_with_attributes_stock table which your error message is saying hasn't been done.

Thanks Kuroi, I found the problem.
It seems the update_1_4_10.sql was indeed the issue and while I assumed it had ran completely, it had not created the sort table. It did however add the other elements to the database when ran previously, but my remote sql query software, seems to only run single parts of the script, apparently, because I had to highlight the "add sort" part of the query, then run..affected 34 rows. Now it appears that its working now..or at the least, I do not get that error anymore and can see my attributes for items.

THANKS AGAIN for the input!!! :clap:

hi, i have quite strange problem. ive been using stock by attribute with only one attribute with no problems. but when i add second attribute, ie. size+color, all entries in first categories get doubled, so i have 2 smalls, 2 mediums, etc to choose from, but second dropdown/radio button is empty and i cant choose anything and there`s nothing displayed...

help:)

What and who's version are you using???

it says 4.7ajax

There many version, a few that available via forum only such as mine...

The ones in the contribution are old and not updated.

creinold:

There many version, a few that available via forum only such as mine...

The ones in the contribution are old and not updated.Will you be submitting your version to the download section eventually??

Yes... I will be updating it to work with 1.3.9G this week then I will submit it. Sorry just been crazy last few months.

Had to move our store, then the mall caught fire... Its been hetic.

http://www.washingtonpost.com/wp-dyn/content/video/2010/10/21/VI2010102106938.html

well, im using yours, the one u have in your signature.
btw , sorry to hear about the fire:/

I swear that this mod used to not show the attributes when they were out of stock. Am I going crazy?

If I'm not going crazy, how can that be put back in?

Folks are checking out with out of stock inventory!

You sure its not this flaw: http://www.zen-cart.com/forum/showthread.php?t=40664

creinold, any idea what can i do to fix it? or how to remove it ? i could have another go later on...

creinold:

You sure its not this flaw: http://www.zen-cart.com/forum/showthread.php?t=40664

creinold, you keep posting everywhere about "this flaw", and pointing to that particular thread. But, that thread discusses about 6 quite different issues.

If there's a particular issue that's really a "bug", then post a bug report about it.

If there's something you just don't like, then why not post a code fix for it?

Or at least specifically explain the issue, instead of randomly passing the buck.