Dynamic Price Updater

[Chrome]

Hi and thanks Matt!

The only reason there is no plug in to the text attributes is that I haven't done it yet

It's not actually a difficult thing to do, more time-consuming, but I decided to leave it for now while I have a word with another developer about feeding the vars into the JS from the backend framework (I have some theories here)

There should, in theory, be another release of this soon... If I get bored I may well add the text attribute reader just to see if I can... As long as it's recognised that this mod is pretty much experimental and may not work for some I'll add bits and pieces to it

Feel free to mess about with the code if it's of any worth to you

Dan

[Ajeh]

Just a reminder on TEXT Attributes ...

TEXT attributes are priced by fixed price, word or letter with free XX words or XX letters not counting spaces or counting spaces ... don't forget the returns should not count when a TEXTAREA ...

Did I leave anything out?

Good news ... there is a ... umm ... unexpected feature ... on TEXTAREA to do with enters and spaces that has been fixed in the upcoming Zen Cart v1.3.8 release ...

Might want to kind of hold off on this aspect for the moment so you aren't re-writting it 27 times ...

[Chrome]

Thanks for reminding me how sneaky those attributes are lol

And I think you mean rewriting *another* 27 times

I'll wait for the upcoming release as it provides an excellent excuse to spend a load of time scratching my head wondering how this is going to work

[Ajeh]

Ain't I the helpful one?!

[Chumly]

Hi All,

Great looking code!
However, I have a little problem..
I have a service which prices the product based on a customer selectable number. ( effectively a quantity. )
I've set up a drop down list with all the modifiers to the price ( Value 0,* 12, offset 0 ) This gives me the list I'm looking for. I've set the product to be priced by attribute, and everything looks great on the product page. However, when I move on to the order page, it has added the original price to the order.
I checked the javascript, and added some debug code to display the original price beside the new price, and it was zero. So, it seems like the javascript is not finding the original price.

Thats one issue.
Another issue is that I'm unable to add multiple selections of the same type.
It looks like I can have one dropdown and one radio, but not two dropdowns.
I have tested both dropdown lists independently, and both work alone, but not on the same page.

Now, I can achieve the desired effect by manually setting each of the dropdown values, but the idea is to save massive amounts of time by setting a 'hidden' base value, and only change a few entries instead of several hundred.

Could you assist me in figuring out the best method of handling these issues?
Thanks!
Chumly

[swguy]

Nicely done. An extremely skillful application of DOM traversal. But there are a couple of outstanding issues:

- sales and specials seem to break it.
- sideboxes with radio buttons seem to break it.

I just skimmed the thread quickly and I apologize if someone else has already mentioned these items.

Scott

PS> I thought the use of innerHTML was unsafe in FF and friends, but it seems to work in my FC4/FF 1.5 and Win/FF 2, so there you are.

[Chrome]

Hi

Sorry for the lateness of my reply

First off thanks Chumly and Scott for your comments, which I'll deal with in order

Chumly: Do you have some links to pages that are failing? I know why your first problem is happening but the Updater should certainly be able to handle multiple instances of, say, a radio box

Scott

1st issue: Yeah, basically this is because the base price 'finder' is inefficient... I'm working on a way round this (there is another way but I really don't want this mod to be affecting other ZC files)

2nd issue: I have noticed this but it seems to be a bit spurious... After reading your post it occurred to me that I could probably avoid this by narrowing the scope of the traversal... Testing ahoy

As for the innerHTML issue: There is a small comment near the bottom of the script that admits that innerHTML is cheating ... Essentially I think innerHTML is a Microsoft creation... Issues arise in standards compliant browsers when the innerHTML applied contains HTML which needs to be accessed using DOM methods... IE will parse and format the contents of innerHTML and place them into the DOM tree whereas FF et al will not

Dan