Problems with product info page

Hi,

Please see http://www.theengravingshop.co.uk/bench-memorial-plaques/bench-memorial-plaque, using version 1.5.1. When you complete the details for the plaque, i.e. text required, corners, etc, but leave the size of the plaque at option "Please select", when you click add to cart, it correctly shows the error message of what you have failed to select, but then it removes the text box for Text Required, so you cannot add it again, and messes up the layout. How can I fix this so when customers forget to select options, that they can go back and still amend all options?

There are 2 ways to do, I think:

1. Use javascript/jquery validation.
2. Set session for options after submit.

I suggest #1.

Thanks for the reply. Can you please tell me what to do? How do I use use javascript/jquery validation?

Here you are
http://jquery.bassistance.de/validate/demo/radio-checkbox-select-demo.html

cvhainb:

Here you are
http://jquery.bassistance.de/validate/demo/radio-checkbox-select-demo.html

What about if visitor has java disabled or not a feature of their device? Still works?

No, of course if the visitor has javascript disabled the validator wouldn't work.

I presume your question was rhetorical:)

To the OP - does it do the same thing if you switch temporarily to the Classic template ?

Hi stevesh,

Sorry for late reply, seem I have been excluded from part of the conversation! Yes, I have just switched to classic template, didn't complete any details but just selected add to cart. All the relevant error messages came up, and again the text boxes were missing (for the text and special instructions). The radio selectors and drop downs still show.

Fresh page before submission

<input type="text" value="400" maxlength="3" size="3" name="remainingTEXT_PREFIX31" disabled="disabled"></input>

After submission with error

  <input disabled="disabled" type="text" name="remainingTEXT_PREFIX31" size="3" maxlength="3" value="400" />  maximum characters allowed<br /><textarea class="attribsTextarea" name="id[TEXT_PREFIX31]" rows="10" cols="50" onkeydown="characterCount(this.form['id[TEXT_PREFIX31]'],this.form.remainingTEXT_PREFIX31,400);" onkeyup="characterCount(this.form['id[TEXT_PREFIX31]'],this.form.remainingTEXT_PREFIX31,400);" id="attrib-31-0" ></textarea>

http://www.w3schools.com/tags/att_input_disabled.asp

I have never seen disabled="disabled" used before and dont know why you have included it.

Have you tested your form without the disabled part.

gjh42:

No, of course if the visitor has javascript disabled the validator wouldn't work.

I presume your question was rhetorical:)

Relatively rhetorical. Hoping to insight a solution that would maximize functionality without excluding a potentially large group of visitors/purchasers. Or if it will exclude, then to ensure that the implementer considers identifying to the user(s) why something would not work or or advises of minimum requirements to ensure functionality. :)

(So, yeah, I knew it wouldn't work if turned off. :))

Hey dw08gm,

This is part of the standard v 1.5.1 files, in includes/modules/attributes.php, this is not something I have added. Any other ideas?

barendfaber:

Hey dw08gm,

This is part of the standard v 1.5.1 files, in includes/modules/attributes.php, this is not something I have added. Any other ideas?

I agree that the disabled="disabled" statement is in the attributes filei can't swear that some other mod I have added did not put it in there, but I found it in there by search using the Developers Tool Kit. I am curious about when that "line" is applied. May want to remove that portion from one of the statements (or more) and see if it resolves. Or to search the forum more.

barendfaber:

Hey dw08gm,

This is part of the standard v 1.5.1 files, in includes/modules/attributes.php, this is not something I have added. Any other ideas?

I agree that the disabled="disabled" statement is in the attributes filei can't swear that some other mod I have added did not put it in there, but I found it in there by search using the Developers Tool Kit. I am curious about when that "line" is applied. May want to remove that portion from one of the statements (or more) and see if it resolves. Or to search the forum more.

barendfaber:

Hey dw08gm,

This is part of the standard v 1.5.1 files, in includes/modules/attributes.php, this is not something I have added. Any other ideas?

Indeed, it is standard and has been there for years. I have never had a problem with text attributes, so have not needed to look closely into it. Stumped.