account against built cart carts changes check checked code computer course direct elsewhere fact fix fraud free happening important months notification order placed price prices problem processing service sites testing totally variable version website

are the carts doubling the prices somehow right now?

i seeing this using different ejunkie accounts on different website sites but im using a totally different computer then i ever have before elsewhere.

anybody see this in their carts too?

I am seeing this in my cart as well.

Same here. I emailed them but no answer as of yet. Thought I done something lol

Well if 3 of us see this them it must just be us 3 only.

You guys go reduce your prices by half and problem solved.

Nice one. Nothing like making changes without proper testing. What a nightmare.

But then again, dinner is far more important so glad to see everyone got home in time.

lol

The more I think about it the more this scares me.

What would have happened if prices got cut in half instead?

I think ejunkie needs to put controls in place to keep this from ever happening again.

In fact, this is so bad that I HOPE it is just me and a problem I have and not ejunkie at all.

Need to think about having the cart software *check again* the value in the cart variable against the actual price in the account - or something to that effect, so that there is a built in double checker against code change errors.

Soon as I change the price by 1/2 they will fix it lol

Mike

Looks like they may have fixed it. I just checked mine and they are coming up the right price.

Mike

Really sorry about this folks .. we've posted about this at http://www.e-junkie.com/bb/topic/2871

lemonbar
What would have happened if prices got cut in half instead?

That will cause the price validation step in order notification processing to fail and you'll get a "suspected fraud" e-mail from us.

Like mentioned above...

Why not ad a step at the end that check the price that will be placed in in the cart against the price in the account. That step/code section should never get modified and is a fail safe. And of course you wouldnt use the same varible as you did in the prior steps. That section of code is clean safe and does a direct check.

This way even if you guys *choose* not to test something that is so important before you install a new version then the price thing will never happen.

Also, that way you could have all the newbies you want to develop your code at 1/10th hourly rates, promises of free e-junkie service for 6 months and e-junkie t-shirts, yet still never have this problem.

By the way, e-junkie t-shirts are "Chick Magnets" for sure. Why not ad e-junkie bright orange thongs?

Hey! lemonbarobama ... your new identity is more fun for sure .. we'll add the check you have suggested.

That would be Baramolemonacka actually.