Actually, thought it best to confirm, for you and others, that yes your code change does resolve the issue.
Actually, thought it best to confirm, for you and others, that yes your code change does resolve the issue.
Simon
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
So I caught on somewhat on what you are talking about. I'm building the site now so the products are being created now without attributes. I knew I could make one and copy attributes to others. when it comes to sql i'm lost that last part you were talking about sounds like what i want to do.
I thought that option might be more along what you are wanting, just hadn't thought of it being used that way. :) users can be so creative!
Suggest taking a look at/around post 2725. There had been a new feature added and it does require executing some SQL to make it work, but hopefully it isn't too complicated to figure out. Generally speaking you'll need to look at either/both of the options names manager and/or options values manager to identify the value associated with the needed options.
Hmm, that did remind me. I don't think I implemented copying of product specific information when using that feature and copying product and it's attributes. Will start a new issue on that.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
So I looked at 2725 I seethis is kinda the opposite of what I want to do.Originally Posted by Christian_Wagner View Post
Is there a way to have dropdowns on a page have independent quantities that aren't affected by each other? ie. I'm selling a product (dropdown #1)
So I made two test products. one I assigned all the colors and linked to SBA, for the second one I copied all the attributes to it. I guess it needs to be dumed down a little more for me.
The final "result" is still the same thing. You want to have an option that is always available (until you decide to make it not available) no matter what else is going on around it. In your case though, you want an option value to always be available (many option values really), but each one to be "assigned" as necessary... Now, considering that you've said that you don't really track the stock *quantity* AND when say "blue" is gone, it is to be gone everywhere, I suggest *not* assigning variants to the SBA tracked product. If you do, then the existence of the stock quantity will make the option available until the stock quantity is set to 0. And if you set the quantity to 0 (with the code as written), then the option will be unavailable even with the appropriate SQL statement. I do have a "comment" in the code that would work in an opposite way to this, but haven't assigned a constant to it yet.
Anyways, for your situation where options_value_id 143 is to be available for all product that have it assigned in the attributes controller and the product is tracked by SBA, then one sql statement (to address a single option value) would be:
Where the option value id for your color is 143. The option value id can be found in the catalog->Option Values Manager section and is the number to the left of the option value's name... Then, when you want the item to be out-of-stock or "non-existent" you would do a SQL statement like this:Code:INSERT INTO products_with_attributes_stock_attributes_non_stock (attribute_type, attribute_type_id, attribute_type_source_id) VALUES ('OV', 143, 0);
Code:DELETE FROM products_with_attributes_stock_attributes_non_stock WHERE attribute_type = 'OV' AND attribute_type_id = 143 AND attribute_type_source_id = 0;
Hmmm.. Btw, just thinking about this, because I haven't tried it is that you may need to assign at least one variant to a product to be so tracked... Just thinking a little about the overall assignment(s)/operation(s) that basically the SBA code doesn't kick in unless a product is found in the SBA table which is to have a products_id in the list even if there is otherwise useless information.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
So I ran the following code and replace # for the Option Value Name. I did this for all 59 colors.
I made two test products, added all the colors to one and then copied that attribute to the second one.Code:INSERT INTO zc_products_with_attributes_stock_attributes_non_stock (attribute_type, attribute_type_id, attribute_type_source_id) VALUES ('OV', #, 0);
I ran the full upgrade script along with the Add all Product Attributes
I can see all colors on my two products.
next I ran the following code
2 is the id for white. White still showing as a color option. I have both test products linked to SBACode:DELETE FROM zc_products_with_attributes_stock_attributes_non_stock WHERE attribute_type = 'OV' AND attribute_type_id = 2 AND attribute_type_source_id = 0;
my site is http://www.visionsinvinyldesigns.com...=index&cPath=1
click on test or test 2 for products
I just went in and add qty as 100 for variant of pick color on test2 product
I want to be sure that we are both considering addressing the same aspect of operation. In absence of the latest message where a variant quantity ended up being applied against an attribute selection, SBA basically would have not been a factor in this display. Now that every attribute variant has been provided a quantity of 100 (though it only needed one of them to have a quantity applied) test2 is actually a product tracked by SBA.
So it seems to me that you're trying to validate that the non-stock feature can be used across the product. While that may be the ultimate goal, there are a few things yet to consider.
At last check all attributes of the test2 product had quantity assigned. As a result of that the non-stock field setting presence/absence will not change the existence of the applicable option. Having stock overrides that an attribute is non-stock tracked as far as being displayed or not.
Then there is the issue of whether an attribute is to be displayed or not and whether it is to be identified as out-of-stock. These other settings can affect whether an option is displayed or not. The important part as far as purchasing is whether the associated selection can be added to the cart. Ie. If the store can not be oversold and a selected combination is entered as not existing, then that combination should not be able to be added to the cart.
Again at my last look, I would say that the test of the "white" attribute would require removing the quantity from the white variant (ie. Removing the variant that has that attribute.)
On another note, it seems that the "Please select color..." option is not setup properly to be a display only, default attribute. I could be wrong.
It does seem that the option name type is correctly set and that the dynamic dropdowns options are correctly set to use the SBA simple select (dropdown) options. I say this because the quantity of available product is shown and I don't see any remnants of the Dynamic Dropdown javascript in the source code.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
Bookmarks