How do i stock based on attribute or remove attribute one sold

[vvomble]

I want to sell each item by bonus ball using numbers 1-49. I've got all my attributes setup and each attribute should be the same price.

However when say number 3 is sold i want that attribute to only have a stock level of 1 so it should remove itself from selectable attributes. Is this possible with zen carts current config? or do i need a plugin if so which.

just incase it wasn't clear what i wanted here is an example.

I have balls 1~49 each with one available. Jimmy buys ball number 49 so now only 1~48 should show as available.

[mc12345678]

There is stock by attributes available from github at https://github.com/potteryhouse and there is a commercial mod available by a different name that escapes mme at the moment. You would want version 1.5.4 for your current ZC.

[vvomble]

well that's utter junk I've now got to reinstall my backup

[mc12345678]

well that's utter junk I've now got to reinstall my backup

Really, why? What issue did you encounter?

[mc12345678]

FWIW (which from the above name calling and utter lack of description of the issue encountered I doubt it matters), I reviewed the manual change that was made two days ago and saw that in the three added sections of code that a variable in all three uses was missing a letter m in a variable similar to $dispMmessage.

[vvomble]

well took the whole site down and the admin page appears blank.

That last message made no sense and am I supposed to know what that acronym actually means? FWIW???

[mc12345678]

When properly merged with the existing files, I have yet to have taken a site down during installation. In fact there were even checks added to allow installation in advance of performing the admin install to prevent interruption of site traffic while it was being installed...

So, for what it's worth (FWIW), it would seem that 1) any chance of identifying if there was an issue with the software or the installation has been lost, 2) it was installed to a live site without any testing/verification of what might happen if installed using the method that caused the issue which explains the disgruntlement...

All in the mean while it *will* provide the options for which you are/were looking... In fact the requested condition is a perfect example of when to use SBA even if that configuration would be the easiest/simplest method of attribute control. X sub products with a quantity of 1 each to either show out-of-stock or hide the attribute upon purchase... Done... Couldn't be much easier to address/handle in the code.