query to determine products with attributes with no default option value

[torvista]

I want a warning if someone has forgotten to set a default option value on an attribute.
I'm sure I can do it all in a single query to retrieve that product's id...but brain is refusing to cooperate.

So, can someone rewrite this to do what I want?

SELECT pa.products_attributes_id, pa.products_id, pa.options_id, pa.options_values_id, pa.attributes_default
FROM " . TABLE_PRODUCTS_ATTRIBUTES . " pa"

THANKS!

[lat9]

Sure, you might want a refinement since this is going to kick out all TEXT attributes, too:

SELECT DISTINCT pa.products_id, pa.options_id
FROM products_attributes pa
GROUP BY pa.products_id, pa.options_id
HAVING SUM(pa.attributes_default) = 0;

[DrByte]

Additional variations:

#all attribs without a default set
SELECT pa.products_id, pa.options_id
FROM products_attributes pa
LEFT JOIN products_options po ON pa.options_id = po.products_options_id
WHERE products_options_type != 1 AND products_options_type != 4
GROUP BY pa.products_id, pa.options_id 
HAVING SUM(pa.attributes_default) = 0
ORDER BY pa.products_id, pa.options_id, pa.options_values_id;

#all attribs without a default set, AND skip those for which only one option exists (since it is likely auto-set as default anyway)
SELECT pa.products_id, pa.options_id
FROM products_attributes pa
LEFT JOIN products_options po ON pa.options_id = po.products_options_id
WHERE products_options_type != 1 AND products_options_type != 4
GROUP BY pa.products_id, pa.options_id 
HAVING SUM(pa.attributes_default) = 0
 AND COUNT(pa.options_id) > 1
ORDER BY pa.products_id, pa.options_id, pa.options_values_id;

# all data, for visual inspection
SELECT pa.products_attributes_id, pa.products_id, p.products_model, pa.options_id, po.products_options_name, pa.options_values_id, pv.products_options_values_name, pa.attributes_default
FROM products_attributes pa
LEFT JOIN products_options po ON pa.options_id = po.products_options_id
LEFT JOIN products_options_values pv ON pa.options_values_id = pv.products_options_values_id
LEFT JOIN products p ON pa.products_id = p.products_id
WHERE products_options_type != 1 AND products_options_type != 4
ORDER BY pa.products_id, pa.options_id, pa.options_values_id;

Notes: products_options_type 1 is TEXT and 4 is FILE hence the exclusions

[torvista]

Excellent!

The background here is that the Dynamic Price Updater does not show any price if the attribute does not have an option preselected/default.

[mc12345678]

Excellent!

The background here is that the Dynamic Price Updater does not show any price if the attribute does not have an option preselected/default.

Is there an example of this condition in the default ZC install with the sample product? I thought the logic included a review of all selected and unselected options to identify a possible minimum price based on the options available from which to select...

[mc12345678]

Excellent!

The background here is that the Dynamic Price Updater does not show any price if the attribute does not have an option preselected/default.

Is there an example of this condition in the default ZC install with the sample product? I thought the logic included a review of all selected and unselected options to identify a possible minimum price based on the options available from which to select...

I'm curious because I just even tried index.php?main_page=product_info&cPath=54_57&products_id=131 and index.php?main_page=product_info&cPath=54_57&products_id=134

After removing the color option name (which has a dropdown set of attributes that each have a base price) of course this makes the base price of the product 0, but even after I entered a price for the product on the product edit page, no text entered into any of the text fields and the product's base price appeared upon display and then as I entered text, it updated based on the text's pricing scheme. (per letter or per word including total consideration of free letters/words).

I then also searched for a method that uses radio buttons: index.php?main_page=product_info&cPath=21&products_id=47

And it has no radio buttons defaulted and does not force any attribute to be selected which allows the product to be added to the cart in that manner. At that point the price of the product is 0 and carries through as 0 until at least a radio button has been selected...

What I'm also getting at is that not providing a price is similar to saying that the product when placed in the cart does not have a price... So personally I'm trying to better understand so that can possibly address the issue in a solvable manner.

And to that trying to understand what has been changed from the recent version of DPU to cause this issue where such an additional search/assignment does not appear necessary? I realize its a strong question in absence of response to the earlier question... :)

[torvista]

>Is there an example of this condition in the default ZC install with the sample product

Which version of DPU (plugins, your repository/beta, Zen4All...?)....in which Zen Cart...and where should this conversation be continued: Plugin thread or someones Github...:

Every time I open DPU code it's a Pandora's box so since I understand the various forks of DPU are being mashed into one version to rule them all, I'd prefer to wait to test that, in ZC157, in the relevant repository..
Thanks.

[swguy]

Note also that Zen Cart 1.5.7 has the new function zen_requires_attribute_selection($products_id). The inverse of this would be what you want.

[torvista]

>Zen Cart 1.5.7 has the new function zen_requires_attribute_selection

Thanks, I didn't know that.

[swguy]

This was done so that items with single valued attributes (such as most downloads) can be added from the listing page.