Dynamic Price Updater

[mc12345678]

Can anyone provide a reason why this code should claim all onchange, onkeyup, and onselect javascript actions for applicable attribute types rather than sharing those actions with other javascript code or be required to be in some way loaded after the other javascript code?

[Design75]

Can anyone provide a reason why this code should claim all onchange, onkeyup, and onselect javascript actions for applicable attribute types rather than sharing those actions with other javascript code or be required to be in some way loaded after the other javascript code?

Nope,

The code is ancient, and in the past there probaly was a reason, or the original coder did not now or had no better reason to do it another way. I have been planing on updating the codebase for a long tome, but am lacking the time. If you want to update this mod be my guest

[mc12345678]

Nope,

The code is ancient, and in the past there probaly was a reason, or the original coder did not now or had no better reason to do it another way. I have been planing on updating the codebase for a long tome, but am lacking the time. If you want to update this mod be my guest

In a very small part that was something I was considering, but I'm truly just stepping into this game. Recalled maybe 2 years ago installing it somewhere and having to make a change so that the actions of this plugin and another would fire, but didn't remember that this last weekend when I was again trying to get it to play nice with another javascript action. Do you happen to have your code on github or otherwise available?

[mc12345678]

Forgot to add that I wasn't sure if there was some sort of "security" concern or other tidbit that I wasn't aware of. I've got a post prepared at least to address that issue which may help others like the tidbits that I found in this forum to address errors encountered.

FWIW, generally speaking with addressing the few issues encountered, this code does/can be used with Stock By Attributes (specifically when using multiple attributes and dynamic dropdowns as implemented in the github version). I haven't worked through the initial display of a 0 price instead of starting at, but I think while reviewing the thread that it is addressed.

[Design75]

Forgot to add that I wasn't sure if there was some sort of "security" concern or other tidbit that I wasn't aware of. I've got a post prepared at least to address that issue which may help others like the tidbits that I found in this forum to address errors encountered.

FWIW, generally speaking with addressing the few issues encountered, this code does/can be used with Stock By Attributes (specifically when using multiple attributes and dynamic dropdowns as implemented in the github version). I haven't worked through the initial display of a 0 price instead of starting at, but I think while reviewing the thread that it is addressed.

It would be nice if this mod could be rebuild to work nice with SBA. I always cheated 0 price issue with setting the base price to 0.0001. Not a good solution (I know), but it worked).
I the new mod is written properly it may make a chance to get incorporated into the core code

[Kcin]

So what is the final consensus? Is that officially broken on 1.55a? Are there any alternatives? I'd rather have an updated price on the fly so I can get rid of hte (+3.00) in the attributes drop down.

[mc12345678]

So what is the final consensus? Is that officially broken on 1.55a? Are there any alternatives? I'd rather have an updated price on the fly so I can get rid of hte (+3.00) in the attributes drop down.

Functional with minor modification as either described in this thread or as identified through troubleshooting with browser's tools (F12).

There are some github forks with a few already included modifications to address some of the items/issues. But it does or relatively can work with ZC 1.5.5a.

[mc12345678]

So what is the final consensus? Is that officially broken on 1.55a? Are there any alternatives? I'd rather have an updated price on the fly so I can get rid of hte (+3.00) in the attributes drop down.

As to the (+3.00), I don't know why you wouldn't want to indicate to the customer that the option being chosen affects the price in some way rather than the possibility that if they 1) have javascript disabled or 2) fail to see the change in price upon selection for some other reason and then not realize how the prices play out.