Hey paul, you probably want to go into the admin>options>inventory and check the disable inventory button. Also, go to admin>options>workflows and go to the Process New Order workflow and remove the "Run Payment Complete Workflow If Paid" workflow item.

The first issue is most likely an inventory issues, but the second issue is a bug which we will address as soon as possible.

FYI to BV:



Check your store's code: http://www.bvsoftware.com/store



It looks bad in IE7.



See attachment for a screenshot.



Plus, where's the demo guys?

Yes, but there are many using it. Plus, every web developer should at least install it to check their sites out. REASON: Microsoft is going to automatically install IE7 through "Automatic Updates" to every computer in the world that is accepting Automatic Updates.

You don't want your site looking bad to the millions of people who don't understand why your site looks bad ... do you?

Hmmm... I've been able to make my sites look good for all. (NOT implying anything at all with that statement.)

Are you using strict or transitional?

Maybe they should hire you.

I disagree. We should take it seriously since ... soon ... 80% of Internet users will be using it.

I'm not trying to bloat this issue and turn it into a Firefox vs. IE discussion (Firefox is over-rated by the way). The browser war has benefits for each developing company. Benefit to help IE make a better product. Benefit to FF to spread their gospel. Benefit to Opera to inspire them to create the awesome (more-secure-than-Firefox) browser.

I believe we should take it seriously and make our sites conform to all the browsers and if that means sacrificing a little Form over Function (until the browser's catch up to what designers want to create), then sacrifice.

And ... for professional software developement companies creating software running on MICROSOFT solutions *ASP.NET 2.0*, they had better look good to be taken seriously.

It's all good. Good discussion. The overall driving factor of my post is this:

Hey, it looks funny in IE7.

That's it. Just being nice.

I don't think I phrased my post quite like I intended (jet lagged a bit). :) Noah is spot on in my intentions.

My response was mostly in agreement, and in general, that it is very important to test on IE7, but not to take it too far yet. What we see in the current testing version and the final product could be very different, so don't kill yourself trying to gain compatibility. It should be easy for the most part to get the same result on all modern browsers, such as in the BV Store floating solution, but if there is something you just can't get right, it's usually best to hold off on it until final release - or investigate whether you can confirm a bug.

Firefox is usually the preferred browser on Windows for standards compatibility testing, in part due to the great add-ons; they all have their quirks and issues (Opera has some odd ones) and should all be used throughout the design implementation phase.

All in good humor, I came across this article from Slashdot and have decided to post it - well knowing that this is so off topic it's pathetic :)

---

"A new Symantec study on browser vulnerabilities covering the first half of 2006 has some surprising conclusions. It turns out that Firefox leads the pack with 47 vulnerabilities, compared to 38 for Internet Explorer. From Ars Technica's coverage: 'In addition to leading the pack in sheer number of vulnerabilities, Firefox also showed the greatest increase in number, as the popular open-source browser had only logged 17 during the previous reporting period. IE saw an increase of just over 50 percent, from 25; Safari doubled its previous six; and Opera was the only one of the four browsers monitored that actually saw a decrease in vulnerabilities, from nine to seven.' Firefox still leads the pack when it comes to patching though, with only a one-day window of vulnerability." (one-day vulnerability from the moment they "discover" it, that is. -jc)

---

Where's the demo? :) Broken record, eh?

One thing that gets me about Firefox is the memory issue. It can get really frustrating, especially if you have a bunch of tabs running over a time with a couple ajaxy sites like Netvibes and Gmail. Sometimes I look at the processes and Firefox is burning up 300 megs, which is just insane.

I'm really hoping that IE7 will work on the very basic remaining compliance issues - such as floats and :after - for the official release. It's amazing to me that they have all of the resources in the world, and still fall far behind in the most basic CSS rules, regarding layout of all things. It really sucks to run into these IE7 bugs on a regular basis and wonder if you'll have to un-hack your hack when the browser is available to the mass public.