PRODUCTS - individual products

[rachelfwells]

Hi Sam,

• Can you please add a heading for the contact form on the individual product pages - 'Enquire About This Product' (Same styling as Plate/Power/Material etc) http://rachelwells.com.au/moodiedev/?product=single-cabinet-bbq-queensize

• Can you please hide the social media icons at this stage.

• On this page is there the ability to upload a pdf? See attached jpg for reference.

[rachelfwells]

Also can the contact form automatically populate with SKU and product name/details selected etc?

[samadd]

SKU & details are appended to hidden fields and contained within the submission.

I've styled the pdf and Enquire buttons to match here, but please check the hover states are right!

Thanks.

[samadd]

PDFs - to include a pdf, just attach a pdf to the body of the product description. Doesn't matter where, or what link text is set - I've coded something to sniff out a pdf link and move it on to the form as a button.

[rachelfwells]

Hi Sam - I don't think this page is very clear to the user now... and a few functional things have been changed that were really great.

The SKU doesn't change as it did before when you changed the menus under plate, power and or material. Also the images don't change anymore. This functionality would be a shame to loose. We either need the enquire button to take the user to the contact page or for hidden contact form fields to appear once this is clicked on. My issue is I'm just not sure what's possible? Any suggestions?

'Enquire' roll over button seems to be a bolder font weight than the rollover for 'pdf download' and this button should not sit right next to the enquire button if that is now the 'submit'... it's a bit confusing....

I'll think on it some more and send a jpg of possible layout... if you can give me your thoughts first that may be helpful.

[rachelfwells]

I've given this one a bit more thought. Can you return the page to the way it was and make can we have a new page for the enquires. Asos do this for their 'email a friend' option except in this case it would still be

Enquire button would take you to a simple page with moodie header and footer and contact form as below

Enquire about the DEFAULT PRODUCT NAME

Your Name Your Email Your Enquiry*

Submit

(Next page)

Thank you for your enquiry we will get back to you as soon as possible.

Go back to the product page.

[samadd]

Try this out for size: http://rachelwells.com.au/moodiedev/?product=single-cabinet-bbq-queensize

[rachelfwells]

This is great Sam - perfect - Can you add a go back button or simply text on this page? So people can go back to where they were.

Also will it still be possible for Clint to add the options he had in there before which were in the contact form but are now missing?

Thanks

[samadd]

Back button added. (Resisted the urge to add an arrow pointing to the top left of the browser window!)

The problem with the drop-downs is that they are part of the Add to Cart form. The proper way of replacing the add to cart with an enquire form, which I have done now, simply replaces the Add to Cart from with whatever static form, link or button you want. This won't be bound to the specifics of the product.

What I'd done before was a slightly lunatic hack that involved injecting the custom enquiry form in to every page and hiding it, then detecting if we were on a product page using javascript, extracting the enquiry form from its secret location, and then extracting the options drop-downs from the form, injecting that into the magic enquiry form, then wiping the Add to Cart form and injecting the doctored Enquiry form into its place for the user to see. On top of that, there was some code listening for drop down-selections and binding those values to the hidden fields on the Enquire form, as the snuck-in drop-downs themselves would not be recognised by the server-side code.

All of which was probably the reason that some of the functionality there before was lost like you mentioned, and on top of that, all of that jiggery-pokery would be pretty sensitive to any variations in the format of the product pages that I might not have anticipated. So on reflection I'd be reluctant to re-attempt that, unless it's really crucial to have these fields in the enquiry form.

[rachelfwells]

They aren't crucial in the enquiry form. Just want them back as a part of the page functionality. Doable?

Thanks

Sent from my iPhone

On 30/01/2014, at 8:12 AM, samadd notifications@github.com wrote:

Back button added. (Resisted the urge to add an arrow pointing to the top left of the browser window!)

The problem with the drop-downs is that they are part of the Add to Cart form. The proper way of replacing the add to cart with an enquire form, which I have done now, simply replaces the Add to Cart from with whatever static form, link or button you want. This won't be bound to the specifics of the product.

What I'd done before was a slightly lunatic hack that involved injecting the custom enquiry form in to every page and hiding it, then detecting if we were on a product page using javascript, extracting the enquiry form from its secret location, and then extracting the options drop-downs from the form, injecting that into the magic enquiry form, then wiping the Add to Cart form and injecting the doctored Enquiry form into its place for the user to see. On top of that, there was some code listening for drop down-selections and binding those values to the hidden fields on the Enquire form, as the snuck-in drop-downs themselves would not be recognised by the server-side code.

All of which was probably the reason that some of the functionality there before was lost like you mentioned, and on top of that, all of that jiggery-pokery would be pretty sensitive to any variations in the format of the product pages that I might not have anticipated. So on reflection I'd be reluctant to re-attempt that, unless it's really crucial to have these fields in the enquiry form.

— Reply to this email directly or view it on GitHub.

[samadd]

It could be possible to hack it to do this, but given the variations between products, the potential for error is high once you try to generalise it.

Further, if the 'product enquiry' is the main way of enquiring about a product (range), then it's not clear what the drop-downs are supposed to do, if they don't have any role in the submitted form content?

[rachelfwells]

Hey Sam

Having the variation functionality on the page is what Clint wants - it doesn't need to populate the form at this stage. Top line 'range' enquiry is fine for the enquiry form. He will enter some text that indicates what the drop downs are supposed to do.

Thanks

On 31/01/2014, at 9:00 AM, samadd wrote:

It could be possible to hack it to do this, but given the variations between products, the potential for error is high once you try to generalise it.

Further, if the 'product enquiry' is the main way of enquiring about a product (range), then it's not clear what the drop-downs are supposed to do, if they don't have any role in the submitted form content?

— Reply to this email directly or view it on GitHub.

[samadd]

Hi Rachel,

Okay - we'll go with that then. Can you confirm what the drop downs are intended to do, exactly? Just so we're definitely on the same page! cheers -Sam