Dynamic Price Updater

thx that did the trick.

I've been trying to make it multi lingual. the easiest way is to remove the defines from dpu_ajax.php , and place them in includes/languages/YOUR_LANGUAGE/YOUR_LANGUAGE.php

that worked for me :yes:

Excellent mod... I installed it in a new 1.39h cart that will be replacing our 1.38a store. It seems to work well... have not added sales yet however...

I do have a question... is there a way for the top price to remain static? We have long descriptions and the only price seen when selecting attributes is the bottom one... I suppose it does not matter much nut was trying to figure that out without any luck.

All in all... very nice thank you.

Hi,

First off, this mod rocks. Top marks to Dan for all the time and effort.

Anyway, I was looking for a solution to a niggling problem with DPU and found a 'fix' on Page 52 (October 2009) of this thread. One user (izar74) posted that he had the problem of DPU adding 1% to the product prices (as displayed on the product information page). I have the exact same problem.

Now, izar74's solution was to make a 'tiny' change which I followed and it worked for me - phew. However, according to Dan, it's not the best solution as it could have unintended consequences as the fix removes the tax.

So my question is, has this bug been looked into further but not incorporated into the latest version of the mod? I've just installed DPUv2 (from august 2009) and since I get the 1% extra on my prices, I'm assuming it hasn't been corrected in the download files. Hopefully there is a fix for it. :smile: I'm pretty certain it has to do with rounding of the decimal places of the product net price.

Cheers

Hi

Thanks for the support :smile: and sorry for not replying sooner

@spirit: The only way I can think of is to change the element the Updater looks for when it changes the price... It will definitely cause Javascript errors and to be honest I don't know if it will halt script execution... If you want to try it, find the line that says:

Code:

---

define('DPU_PRICE_ELEMENT_ID', 'productPrices'); // this is the ID of the element where your price is displayed

---

And change 'productPrices' to an element that doesn't exist... Let me know if that works because if it doesn't I do have another idea

@manxaura: Unfortunately, things keep preventing me from working on these little niggles with the Updater... I know they're important and I can only promise that as soon as I can I'll get around to fixing them... I really do hope this will be soon

Just as a matter of interest, the date of August 2009 is only when the Updater was first monitored for how many downloads it receives... It's had minor tweaks and fixes since then but it has no official versioning... I might start a system, though

Cheers

Dan

Quote:

---

Originally Posted by Chrome

Hi

I don't know if this module will be of any use to anyone but I've been asked to include it a couple of times so thought I'd release it into the wild to see if anyone can make use of it... Here's what it does:

When you have a product with attributes that alter the price this module will update the price displayed on the page instantly... This gives customers an at-a-glance price total as opposed to having to work it out themselves

The updater should (in theory) work with any amount of attributes

There is a readme included in the ZIP but installation is literally to just upload the file... It overwrites nothing, has no database hooks and is completely autonomous... if it breaks just delete the file



Currently it only works with attributes that are SELECTs... If it works for people I will update it to handle the radio boxes and checkboxes

The file can be found at http://chrome.me.uk/PriceUpdater.zip

A working version can be seen at http://www.studio5.uk.com/index.php?...&products_id=3

Let me know if it does/doesn't work or if anyone wants anything added or changed

Dan

---

Im having an issue with the cart, just added a new vendor to my cart. The issue only affects new items i recently added that have price attributes. When the quantity goes up, the price remains for 1 item. Previous items ive added with price attributes dont have this isssue. What do i have to change?

I'm still getting this error in my logs constantly:

Quote:

---

[10-Mar-2011 09:24:33] PHP Warning: reset() [<a href='function.reset'>function.reset</a>]: Passed variable is not an array or object in /****/rainestudios.net/includes/classes/dynamic_price_updater.php on line 194
[10-Mar-2011 09:24:33] PHP Warning: Variable passed to each() is not an array or object in /****/rainestudios.net/includes/classes/dynamic_price_updater.php on line 195

---

It doesn't seem to affect the functionality, everything is displaying fine in my shop, but this can't be good, right?

thanks,
amy

Hi

@mattieh1: Do you have a link for your site? I don't recall this issue being raised before but go for a hunt through the thread to see if there are any similar reports... Off the top of my head I can't think of any reason that would happen

@amy: You're quite right, that shouldn't be... I'm quite surprised it's actually still working :blink:... I'll check out your site see if I can see any weird data getting thrown about

Cheers

Dan

Hi Dan -

Just a few posts back (#737) I posted a code change I made to v1 of your DPU mod so I could get it to display the way I wanted.

I've just come across an anomaly and wondered if there was an obvious explanation. I add codes in parentheses at the beginning of each attribute. These codes make it easier to fulfill orders. I've discovered that if I have parenthesis containing LETTERS and no spaces, then the price dynamically recalculates placing the text from that code into the price display. So I guess it's interfering with the code.

So (L), (R), (LL) results in the error and but (1), (L L) don't make the error. You can see in the link below where I experimented with lots of variations to figure out the exact ingredients for the error.

http://focalpointhardware.net/index....roducts_id=234

I haven't upgraded to v2 because this was working fine for me up until now. If you tell me there is no fix for this version I may upgrade to V2 and try to recreate my display.

Thanks for your help!

-Andy

Hi

I'm afraid to say that there really isn't a cure for this... Y'see, the original Updater uses a regular expression to 'read' the page and make decisions based on certain patterns it finds... Now, this regex (called seeker) is quite complex and I doubt it would be easy to upgrade

As a workaround you could try using square brackets or even the brace {}

Cheers

Dan

Thanks for your quick reply. I think I will try Brackets instead.

Is regex is the same for V2 also?