This thread will serve as a running to-do list of things that must or should happen during the beta phase of Ubercart 1.0. It is flexible, but we aren't going to overdue it with new features. We're continuing to press ahead to 1.0 as fast as possible and are pleased with the pace and development going on in the beta phase so far. Many thanks to those reporting and helping fix bugs!
This list originated in the beta 1 release thread, but I've left off the items that were already completed in the beta 2 release. Feel free to discuss items on this list or necessary additions in this thread.
Things to keep an eye on: (not necessarily bugs, but might be)
- Installation process
Shipping quotesWorkflow-ng conditions and default configurationsAnonymous checkout and user account creationPostgreSQL support- Make sure reports are being generated correctly
Known bugs to iron out:
Get Tango icons out of the core on d.o for licensing reasons.Caching bugs for anonymous users
(refer to this issue if you have a caching bug to report... I couldn't find any.
)
Add logic to support the copy address box when shipping/billing panes are reversed.Remove admin check box for payment methods, as all should be available.
Features still in the works:
Recurring fee support(check it out)Review and include more Views integrationAdding encryption to CC numbers in the databaseTest it!TAPIr/uBrowser review and update(While I feel these could use some love, I do not see this as something that should hold up Ubercart development.)Move default payment methods out of the payment module into their own modules.(Put code in new core module Payment Method Pack.)
Items in need of some contributed love: (best served up as modules or patches for review as we can't seem to find the time to get to these)
Support for $0 order total checkoutGet the contrib.- Address/profile integration
Support for non-JS users (I like that idea about instructing users how to turn on JS for a contrib module)Test out greenSkin's solution!- Attribute enhancements - images per attribute, dependent attributes,
required attributes and different form element types - Product kit enhancements
As stated before, the Drupal.org issue tracker for Ubercart is open to bug reports, but we will not address feature or support requests there. It is not necessary to use the tracker there, it's just another option that we may take advantage of more internally to nail down any remaining issues prior to the 1.0 release.









Joined: 08/07/2007