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

cefyn:

I’m afraid I can’t get the latest clamav to run on my computer, out of date OS, sorry. Just in case you’re interested, the file is Stock_By_Attributes_Combined- master\admin\products_with_attributes_stock.php from https://github.com/mc12345678/Stock_By_Attributes_Combined
Went through the process to install the latest version (1.4.3 windows x64) and though I didn't set it up on a "server" where it could possibly monitor file operation and/or routinely test, I went ahead and took the questionable file by itself, placed it in a directory and ran the clamscan on the file. No issues identified, so the next question is how to "open it up" to possibly detect the issue that has been reported so that I can figure out how to ensure even for false positives that it isn't identified as an issue... I thought I modified settings to try to use all possible means of review, but not sure...

I'm not aware of any/much difference in how this file collects/receives information as compared to other admin style/type files. Unfortunately, as stated above, this isn't the first time the file has been "identified".

Sure, can report as a false negative, and probably is a really great idea, but I'd rather the code not meet some condition that needs bypassing than to report a particular file name as being ok... Really kind of just makes it possible for others to take advantage. In the little searching I did on this, it appears there may be a (perceived?) issue with $_POST processing...

I may try the other scanner; however, sounds like that one doesn't report the same issue with that file... IF anyone is able to call out a line or code segment that is causing the false positive report, I'd be glad to correct/fix it.

How do you convert Stock by Attributes to POSM? I saw it mentioned, but can't see the process in the wiki or readme? I have tested one product, my attributes have a display only attribute (for Google Merchant feeder category), and its blank for the actual attribute (size, colour etc). I think its a glitch due to my rare setup, though there are others that must have Numinix Google Product Search feeder to, and have set their attributes this way. Thanks in advance.

HeathenMagic:

How do you convert Stock by Attributes to POSM? I saw it mentioned, but can't see the process in the wiki or readme? I have tested one product, my attributes have a display only attribute (for Google Merchant feeder category), and its blank for the actual attribute (size, colour etc). I think its a glitch due to my rare setup, though there are others that must have Numinix Google Product Search feeder to, and have set their attributes this way. Thanks in advance.
in your admin menus do you have "Extras :: Convert SBA to POSM"?

HeathenMagic:

How do you convert Stock by Attributes to POSM? I saw it mentioned, but can't see the process in the wiki or readme? I have tested one product, my attributes have a display only attribute (for Google Merchant feeder category), and its blank for the actual attribute (size, colour etc). I think its a glitch due to my rare setup, though there are others that must have Numinix Google Product Search feeder to, and have set their attributes this way. Thanks in advance.
See the wiki article here: https://github.com/lat9/options_stock_support/wiki/Admin-User-Interface-Changes#extras--convert-sba-to-posm

Note, too, that POSM doesn't track display-only attributes.

barco57:

in your admin menus do you have "Extras :: Convert SBA to POSM"?

Ah I see, thanks I can see that! Much appreciated, I must have missed it due to this third summer heatwave and not thinking properly lol.

lat9:

See the wiki article here: https://github.com/lat9/options_stock_support/wiki/Admin-User-Interface-Changes#extras--convert-sba-to-posm

Note, too, that POSM doesn't track display-only attributes.

Thanks for the tip. Its done 60, and its got ✗ Missing options for the remainder. I guess if I remove the display only categories, somehow en masse, then I re-run the script and it will do the remainder? Thats what I Think I should do anyway. The ones with just ticks are showing in the POSM under catalog. Great script! Doing away with the google product / display ones might reduce strain on cpu for site, might help with the weird overload logs I am getting.

Hey Guys, I’m running version 1.3.8a of zencart with the “products with attributes stock” add on. This creates a 4 digit “OptionID” number which I then use to generate an SKU. I’m nearing 9999 for the OptionID number. Does anyone have any experience of what happens after 9999. Does it go to 10000 or back to 0001? Or? Thanks in advance… Mike

mikedaly4130:

Hey Guys, I’m running version 1.3.8a of zencart with the “products with attributes stock” add on. This creates a 4 digit “OptionID” number which I then use to generate an SKU. I’m nearing 9999 for the OptionID number. Does anyone have any experience of what happens after 9999. Does it go to 10000 or back to 0001? Or? Thanks in advance… Mike
Kind of depends.

For one, it's difficult in this day and age to predetermine what will happen on such an old version of everything needed to operate a site at Zen Cart version 1.3.8a.

That site is LONG overdue for an upgrade and is highly prone to issues.

That all said, it really depends on your process for generating your upcoming serial numbers. E.g. is the four digit number generated by truncating the existing number to at most four digits to then pad with zeros or does it take the existing number and pad with zeros to get four digits, etc.

I would expect even with such an old system that the associated "counter" can handle greater than 9999 such that the next number would be 10000 and be just fine, depending on the code that uses that new number.

Duplicate of above