It really depends on what you need to do with taxes and shipping quotes. Those will be the two final things to come in as we finalize the UI for them. Everything else should be fine, and we'd welcome another set of eyes testing the code.

fwiw, UC 1.0 has been in use since its alpha releases. We try to make sure all our releases are stable, so ideally even our first beta for D6 will work fine for you. I won't make any promises of course, but chances are good we'll have a 2.0 before November.

Hi Ryan,

Thanks for the straight answer. I definitely have no problem that there might still be some bugs to work out. Hopefully I can even help with that some. It's just awesome that you guys have put so much work into it in the first place, and if there's anything I can do to help get it completely ready then I'm all in. The thought of trying to do all of this from scratch.. well.. actually I just won't think about that at all right now.

Taxes won't be a complex issue for us, but down the road I may have some contributions to make in the shipping area.

The store I'm working on sells vintage furniture of all different sizes, which makes shipping a large enough issue that we basically won't try to do it directly through the web site at this point. All the shipping arrangements will be made post sale to start out with, but I will likely be working on some freight shipping integration and we also do a lot with moving companies.. there may be some type of module that comes out of both of those.

For now it will just be the products that are sold on the site and then the shipping worked out later though. More to come later on.

Thanks again!

Dave

humm, ya, I wonder how they separate out the documentation on Drupal.org... oh they don't really do they (well, only for the API docs). I guess you'd be forced to have each as a separate book or you could write some module which managed multipule copied of the same doc in parllel, sort of like the content translation module in D6 but not based on langauge. It think it a problem that the Drupal hasn't figured out how to tackle yet (judging from the anarchy of the documentation on drupal.org).

As for community development, have you opened up a community CVS or bzr repository? I'll have a look at the community site and see whats what

I'm playing with the D6 version of the module and having a heck of a time with it. The whole "conditional actions" part of things seems to be pretty buggy, and I'm not sure where to start with debugging it since there's little documentation and I'm not sure what the correct behavior is supposed to be. So this means no auto-decrementing of stock levels…

I'll set that aside for now and focus on trying to code an auction product module. Please keep us up to date, Übercart crew - it's reassuring to hear about progress being made on this.

I'm curious about the progress, too. I'm starting a new site and it feels like I'm right between D5 and D6 as far as Ubercart goes. I'd prefer to use D6 since it seems like Ubercart is just about there. It sounds like conditional actions is the main problem at this point? Is there anything else in the way?

Any idea on when we will get a 100% usable (not necessarily 1.0, though) Ubercart 6?

How do you deal with "This version is incompatible with the 6.x..." in some modules?

That sounds like you're using PHP4, but we're not going to support it any more for UC 2.0. We haven't put that requirement in the info files yet, but it will be there soon.

2 more problems found in the status report...

user warning: Table 'mubiecom_ssdrp07.uc_payment_credit' doesn't exist query: DELETE upc.* FROM uc_orders AS uo LEFT JOIN uc_payment_credit AS upc ON uo.order_id = upc.order_id WHERE uo.modified <= 1222173965 AND uo.order_status = 'in_checkout' in /home/mubiecom/public_html/IFDMdev/modules/ubercart/payment/uc_credit/uc_credit.module on line 130.

user warning: Table 'mubiecom_ssdrp07.uc_payment_credit' doesn't exist query: DELETE upc.* FROM uc_orders AS uo LEFT JOIN uc_payment_credit AS upc ON uo.order_id = upc.order_id WHERE uo.modified <= 1190565965 AND uo.order_status = 'completed' in /home/mubiecom/public_html/IFDMdev/modules/ubercart/payment/uc_credit/uc_credit.module on line 143.

Well, we're going to keep requiring PHP 5, but I've reworked that code in uc_payment.module. It should be valid code in PHP 5, though. Maybe it's something specific to the CGI version? I dunno.

I doubt my change has been pushed to CVS... it was a quick, small change. It would be in the Bazaar repo.

My logs are filling up with thesePHP errors:
file_get_contents(sites/all/modules/ubercart/uc_cart/uc_cart_block.js?81749) [<a href='function.file-get-contents'>function.file-get-contents</a>]: failed to open stream: No such file or directory in /home/mambear/www/includes/common.inc on line 2261.

And these 404 messages, in various incarnations:
http://www.mamabearproductions.com/sites/default/files/js/)))1e(-d.2e,-d.2c);G(42&&1g(d,

This has all begun after upgrading to the latest 6-dev version. I seemed to get rid of the second error by dumping everything in my cart, therefore my cart block is not showing.

I updated a few other modules, but I'm pretty sure CCK and Views aren't doing this.

Hmm... I'm not entirely sure if a recent commit by Lyle will fix this or not, but we had to revert our usage of uc_add_js() to drupal_add_js(). They've added a new method for caching .js files based on the query string (the data after the ? in the URL), and our previous solution was conflicting with it.