Attribute Required for Text flag not working

ZC v1.3.9h
Database Patch Level: 1.3.9h
PHP v5.2.14
Contributions: CKEditor v3.4, Easy Populate v1.2.5.5, IH2 v2.0 Rev 8c, Order Steps Tableless v2.3.2, Quick Updates v2.04, SitemapXML v2.1.0
Originally built with 1.3.8a and upgraded to 1.3.9h a couple of months ago.


I recently needed to lock down some attribute text boxes to require input prior to adding to shopping cart. I have never done this before, so no idea if it ever would have worked.

I modified each TEXT option name to enable the "Attribute Required for Text" attribute flag.

In testing, the product is added to the shopping cart without forcing me to fill in the required text fields. Essentially, the required attribute flag does nothing.

I found some forum threads from 2007 regarding this issue, but I am somewhat confused as I can't duplicate problem in brand new install. Someone pointed to the "Google Sitemaps" SQL install patch as the culprit as it overwrote items in the configuration table. I have never installed the old Google Sitemaps contribution. I did however install SitemapXML (back when I was on v1.3.8a) which was the new replacement for Google Sitemaps.


As a test, I installed a fresh 1.3.9h in a test directory, brand new database, no contributions. The Attribute Required flag works perfectly.
I then installed SitemapXML. The Attribute Required flag still works perfectly. :huh:


I then searched through a SQL dump of production database looking for the referenced Configuration values in this post. I could not find the following values in my production database (no clue why they are missing as I never installed Google Sitemaps):

Code:

---

INSERT INTO `configuration` VALUES ('', 'Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, '2007-03-19 17:57:39', '2007-03-19 17:57:39', NULL, NULL);
INSERT INTO `configuration` VALUES ('', 'Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, '2007-03-19 17:57:39', '2007-03-19 17:57:39', NULL, NULL);
INSERT INTO `configuration` VALUES ('', 'Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, '2007-03-19 17:57:39', '2007-03-19 17:57:39', NULL, NULL);

---

As a test, I inserted the following via Install SQL Patches into a test copy of my production database (from the 2007 forum post):

Code:

---

INSERT INTO `configuration` VALUES ('', 'Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, '2010-12-17 23:00:00', '2010-12-17 23:00:00', NULL, NULL);
INSERT INTO `configuration` VALUES ('', 'Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, '2010-12-17 23:00:00', '2010-12-17 23:00:00', NULL, NULL);
INSERT INTO `configuration` VALUES ('', 'Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, '2010-12-17 23:00:00', '2010-12-17 23:00:00', NULL, NULL);

---

This appears to have fixed the Attribute required flag as it is now functioning in my test copy of site.

Question, are the statements that I inserted above correct for Zen Cart 1.3.9h?

You can always check the default settings in the file:
/zc_install/sql/mysql_zencart.sql

The statements are different in the mysql_zencart.sql - the following is added to each statement:

(configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function)

and the dates are specified as now().

Should I be inserting the sql exactly as what is in the install file?

Code:

---

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, now(), now(), NULL, NULL);

---

now() just grabs the current date, specifying a date is fine ...

ok, I inserted the same exact statements as contained in the mysql_zencart.sql:

Code:

---

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, now(), now(), NULL, NULL);

---

This has resolved the Attribute Required for Text issue.

FYI I just saw this on a fresh install of 1.3.9F that was done a couple of months back.

I wonder if the root cause of this is that for the text flag prefix (and 2 other values upload prefix and product option type select), the sort order is 0, and something is stomping on this? What if these were changed to 6 like the values around them?

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 6, NULL, now(), now(), NULL, NULL);

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 6, NULL, now(), now(), NULL, NULL);

INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 6, NULL, now(), now(), NULL, NULL);

(obviously the existing keys TEXT_PREFIX, UPLOAD_PREFIX and PRODUCTS_OPTIONS_TYPE_SELECT would need to be deleted before doing this.)

Related thread: http://www.zen-cart.com/forum/showthread.php?t=57828

Here's the root cause. Some mods which have SQL scripts that create new configuration groups will do an initial cleanup like this: (this example is taken from Printable Price List)

SELECT @pricelistid:=configuration_group_id
FROM configuration_group WHERE configuration_group_title="Printable Price-list";

DELETE FROM configuration WHERE configuration_group_id=@pricelistid;
DELETE FROM configuration_group WHERE configuration_group_id=@pricelistid;

This works and does not cause problems. However, other mods set an initial value for the variable. This causes the problem. The example below is taken from Fual Slimbox:

SET @t4=0;
SELECT (@t4:=configuration_group_id) as t4
FROM configuration_group
WHERE configuration_group_title= 'Fual Slimbox';
DELETE FROM configuration WHERE configuration_group_id = @t4;
DELETE FROM configuration_group WHERE configuration_group_id = @t4;

If you run this sql, and you have not previously installed Fual Slimbox, you will delete the 2 prefix and product options type select values which are in group 0.

Again, I believe the proper way to resolve this is to change the Zen Cart sql to put these items in a non-zero group.

I did a quick check of some mods I have downloaded (not an exhaustive list), and the following mods have this bug:

FAQ Manager
Google Analytics
SimpleSEOURL
Fual Slimbox
Super Orders
Integrated COWOA
Google Sitemap Admin
Autoresponder+
Return Authorization
Recover Cart Sales
CaptchaTTF and Hide Phone
Amazon Exporter
Fast and Easy Checkout
Testimonial Manager
Ty Package Tracker

Following up to summarize some of this:

Q: Required text attributes aren't working. How do you know if I have the problem mentioned in this thread?
A: Run the SQL command

SELECT * FROM configuration WHERE configuration_group_id =0

If you don't get 3 rows returned, you have this problem.

Q: How do I fix it if I have this problem?
A: Use the fix from this post:

http://www.zen-cart.com/forum/showpo...17&postcount=3

Having the same problem, tried the fix, got these errors:
Failed: 3
ERROR: Cannot insert configuration_key "PRODUCTS_OPTIONS_TYPE_SELECT" because it already exists
ERROR: Cannot insert configuration_key "UPLOAD_PREFIX" because it already exists
ERROR: Cannot insert configuration_key "TEXT_PREFIX" because it already exists

ZC v1.3.9.
IH3

Still doesn't work, help!

I am running 1.5.0 and am having the same issues. I tried the fix located earlier in this thread and received:

Error Failed: 3
Error ERROR: Cannot insert configuration_key "PRODUCTS_OPTIONS_TYPE_SELECT" because it already exists
Error ERROR: Cannot insert configuration_key "UPLOAD_PREFIX" because it already exists
Error ERROR: Cannot insert configuration_key "TEXT_PREFIX" because it already exists
Warning Note: 3 statements ignored. See "upgrade_exceptions" table for additional details.

I am still allowed to add products of a particular attribute name with "not required" selected. Are my attributes setup wrong? For example I have a product that comes in two colors; black and white. I have an attribute value black and white (both are marked as required) and a third, default, attribute value of "-----------" not marked as required. I am looking to have Zen Cart prohibit the "----------" value from being added into the cart to make sure that the user selects a specific color.

I would appreciate any help on this, thanks.

Todd

Set the Black and White to Not Required ...

Set the --------- to Required and Display Only

Now the customer has to pick Black or White or they cannot add it to the cart ...

Quote:

---

Originally Posted by Ajeh

Set the Black and White to Not Required ...

Set the --------- to Required and Display Only

Now the customer has to pick Black or White or they cannot add it to the cart ...

---

Typical, I was doing it wrong the whole time. Thank you, thank you, thank you. Works perfectly.

Todd

Following up on the original post with fix suggestions:

a) Have a separate "uninstall" utility.

b) If you want to use the code shown above to cleanup before your install SQL, just qualify it by doing the deletes "where configuration_id != 0", e.g.

Code:

---

SET @t4=0;
SELECT (@t4:=configuration_group_id) as t4
FROM configuration_group
WHERE configuration_group_title= 'Fual Slimbox';
DELETE FROM configuration WHERE configuration_group_id = @t4 AND configuration_group_id != 0;
DELETE FROM configuration_group WHERE configuration_group_id = @t4 AND configuration_group_id != 0;

---

Scott,

I am at a loss. I tested with

SELECT * FROM configuration WHERE configuration_group_id =0

and received Failed!: notification. I then inserted the recommended fix


INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, now(), now(), NULL, NULL);

and got three statements processed.

I retested with the first test code and still got failed notification.

I have 1.5.1 and have google analytics, TyTracker and Super Orders, Autoresponder+, Return Authorization, and Ty Package Tracker installed. The database seems to function flawlessly, to an amateur eye. I was recommended to this thread and told I probably had this problem. I have had trouble editing attributes in an order as the last attribute won't select, it is a fixed field in the edit orders window.

Marc

Any recommendations to test if I am ok? Sorry for my imperfect understanding.

Quote:

---

Originally Posted by Trademagic

Scott,

I am at a loss. I tested with

SELECT * FROM configuration WHERE configuration_group_id =0

and received Failed!: notification. I then inserted the recommended fix


INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Product option type Select', 'PRODUCTS_OPTIONS_TYPE_SELECT', '0', 'The number representing the Select type of product option.', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Upload prefix', 'UPLOAD_PREFIX', 'upload_', 'Prefix used to differentiate between upload options and other options', 0, NULL, now(), now(), NULL, NULL);
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Text prefix', 'TEXT_PREFIX', 'txt_', 'Prefix used to differentiate between text option values and other option values', 0, NULL, now(), now(), NULL, NULL);

and got three statements processed.

I retested with the first test code and still got failed notification.

I have 1.5.1 and have google analytics, TyTracker and Super Orders, Autoresponder+, Return Authorization, and Ty Package Tracker installed. The database seems to function flawlessly, to an amateur eye. I was recommended to this thread and told I probably had this problem. I have had trouble editing attributes in an order as the last attribute won't select, it is a fixed field in the edit orders window.

Marc

Any recommendations to test if I am ok? Sorry for my imperfect understanding.

---

After doing all this, have you gone back to see if the original problem has been resolved?
It would seem, that whether this issue was the source of your problem or not, the fact that the three statements processed successfully indicates that they were in fact missing from your cart database. The failed message appears to be a result of trying to run the select sql query from the admin panel's install SQL patch utility. Select statements for the specific purpose of displaying information generally do not work in that area, but will handle variable assignments such as discussed at the beginning of this thread.

Btw, my suggestion, if this issue you are having continues it should probably taken to a thread other than this one. Again, it looks like your cart had the problem related to this thread and it is now fixed. (Could verify by running the three sql statements again to see if an error message is now generated or use mySQLadmin to run the select query being sure to substitute any table prefix as applicable.)

Hey MC,

You get around sailor! Thanks for your response. I tried to reenter the three statements,

Error Failed: 3
Error ERROR: Cannot insert configuration_key "PRODUCTS_OPTIONS_TYPE_SELECT" because it already exists
Error ERROR: Cannot insert configuration_key "UPLOAD_PREFIX" because it already exists
Error ERROR: Cannot insert configuration_key "TEXT_PREFIX" because it already exists
Warning Note: 3 statements ignored. See "upgrade_exceptions" table for additional details.

then checked the edit orders failure of before and it is fixed. It is due to all of you being so brilliant that I am surviving this endeavor. My deep thanks, and hopes that this beast of a site will take some orders soon.

I owe a couple of donations.

Marc

Quote:

---

Originally Posted by Trademagic

Hey MC,

You get around sailor! Thanks for your response.

---

I'm sure you mean that in an appropriate way. :)

Very welcome and happy holidays.

Quick update: I saw a system (1.5.1) just today that still had this problem. So don't assume you don't have it unless you have checked

http://YOUR-SITE/your-admin-page/con...tion.php?gID=0

and verified that you have the expected three entries.

Note that this issue was fixed by the Zen Cart 1.5.3 upgrade script, which migrated these three values to configuration_group_id 6.

I am having an issue with this on my 1.5.5f installation, I have the following addons installed:
Advanced Shipper
Fast and Easy Checkout
Ceon Url Mapper
Css/JS Loader

I checked the database and these 3 configuration setting in group 6, but it still not working.
I had to set a default option just so one was selected on checkout, but i know this wont last for long.

Here is the link to a product, keep in mind i set a default.
https://theaquablock.com/aquablocks/...nd/aquadiamond
Any other places i can look into to see whats going on?

Jeff

Quote:

---

Originally Posted by jeffiec

I am having an issue with this on my 1.5.5f installation, I have the following addons installed:
Advanced Shipper
Fast and Easy Checkout
Ceon Url Mapper
Css/JS Loader

I checked the database and these 3 configuration setting in group 6, but it still not working.
I had to set a default option just so one was selected on checkout, but i know this wont last for long.

Here is the link to a product, keep in mind i set a default.
https://theaquablock.com/aquablocks/...nd/aquadiamond
Any other places i can look into to see whats going on?

Jeff

---

What do you mean by "it still not working"?

What is happening, what is desired to happen (differently)?

A product that has attributes, but does not in some way force the attribute to remain as a selection can be added to the cart without the applicable attribute selected. Zen Cart attributes have a "required" flag that is described as applying only to text type attributes (Text provided by the customer or the text associated with uploading a file). Any other attribute type does not have a "requirement" to be present in a default installation. What I saw of the various radio buttons, is that a default has been set to them allowing the customer to simply select add-to-cart and go through the shopping process without ever really understanding that there are options among each of those attributes... Ie. you may find that you are going to sell a lot of this item that is black, without aqua light, no Betta Fish, No thermomenter, no AquaBrush, no AquaBlock Fish Food, and without a carrying case... You may also find that you may end up with a lot of returns/exchanges of the same thing.....

The recommendation is that there be an option in each of the attributes that suggests to the customer that they should choose one of the available options and that by not choosing one of the options, when they add the product to the cart the cart alerts that such a selection should be made... Yes, this "text" can be hidden, but the whole thing is that the CUSTOMER makes the selection not someone else in setting up the store...

So... For each of the option names used on this product (and other similar), one would add an option value within the option values manager. That option value should have a sort order of 0. Recommended text may be: "Please select an AquaDiamond..." for the first option name.

Then once all of those option names have that additional option value, within the attributes controller, that option value is added and is to be marked "Default" and "Display Only" and still have a sort order of 0. This is done for each option name.

Now, on the product page, there will be a radio button that is selected upon page display and if the product at that point is attempted to be added to the cart, there will be a message associated with the option name(s) that are still selected at being the default of "Please select xxxx..." and the product will not be added to the cart...

The need of an attribute to be associated with a product is determined by the store owner. It is possible that a product/attribute does not need to consider the attribute being associated... Therefore not EVERY product requires a default attribute to support purchase... But, if an attribute is required to be selected in order to support selecting the correct "product" then a default is a good idea such that the default is *not* something that can be added to the cart...

But, my question still stands. :) What is still not working?

Further, I don't see any text field that relates to this thread?