mc12345678
commented
9 years ago Past experience with other SBA related code has been that in the situation of multiple attributes, that the Dynamic Filter plugin (or equivalent) is needed to correctly display the available options if subsequent attributes are "pickable" ie. typical example: shoes of a size and color. The caveat though has been that in a previous implementation the direction had been that the Dynamic Filter would be applied to all products and in a sense required every product to have an attribute. Now, I realize a lot has changed since that including for example my own knowledge on how to temper the application of the Dynamic Filter to a particular page/product based on the presence of attributes with that product, so that "requirement" may just not have been effectively incorporated into the instruction/code.
The concern I have in implementations that require such a plugin (javascript like code) is that the guest has the ability to turn that off, and in some cases for it not to be supported on the device accessing the location and therefore, the recommendation is to have a functional display that is relatively understandable that doesn't require the plugin, but when the plugin "works" that the performance is improved.
In part to meet that characteristic and based on some of the comments seen already it appears that to support the site not using the dynamic filter that an additional file needs to be included in the includes/extra_cart_actions to capture the SBA selections made and not allow adding the product(s) to the cart if the desired condition(s) are not met. Effectively, without the Dynamic Filter functionality this would redirect the customer back to the product page (before adding to the cart) and with the Dynamic Filter would not be "activated" as an out-of-range choice should not be possible.
Determine what if anything needs to be done to work properly with the Dynamic Filter plugin.