Spree Commerce

Try It Now

Spree Makes it into Github's Top Ten

Posted on October 12, 2009 by Sean Schofield

Github recently revamped its user interface and they’re now showing some
cool reports. If you look at the Popular
report you will see a familiar
open source e-commerce project listed there. At the time this post was
written, Spree is coming in at #9 with 212 forks. We’re honored to be
ranked right up there with some very significant projects. Currently
Spree is ranked between restful_authentication and webrat. This is a testament to all of the great work we’ve been doing as a community. Keep forking!

Spree Now 100% jQuery

Posted on October 05, 2009 by Sean Schofield

A small but vocal group of people have been asking to get rid of Prototype ever since the first version of Spree was released. We told these critics that we would be happy to make Spree 100% jQuery if only one of them would stop complaining and actually write some code. Fortunately for all of you Prototype haters, that day has arrived. Thanks to Roman Smirnov, you can now enjoy pure 100% jQuery in the latest edge version of Spree.

This work was actually completed several weeks ago but we delayed moving it into core until after the 0.9.0 release. Please report any bugs you find in our issue tracker. Roman has actually been contributing a lot of great patches lately and we have several more of them in the pipeline that we need to get around to. The Spree community is still going strong. Keep those awesome contributions coming!

Spree 0.9.0 Released

Posted on September 22, 2009 by Sean Schofield

Spree 0.9.0 has been officially released. This is a major release with several new features and improvements. The most anticipated new feature is coupon and discount support. The Spree core now ships with a minimal set of coupon calculators and provides the framework for building much more powerful custom logic. Speaking of calculators, Spree is now sporting a significantly improved system of calculators.

The new release is also compatible with Rails 2.3.4 which contains some crucial security fixes. This release also contains some signficiant improvements to product variants. It is now possible to configure different product images for each variant and to display the specific variant image in the shopping cart. Please also see the very detailed release notes for more information on the release and how to upgrade an existing version of Spree.

Spree continues to improve its i18n support and is proud to announce the addition of the following localizations:

  • Thai
  • Hebrew
  • Dutch
  • Finnish
  • Mexican Spanish

If you have a new localization to add or wish to make improvements to an existing one, please see our contribution guidelines for information on how you can contribute.

We are already hard at work on the next major release. The massive growth in real world deployments of Spree has provided us with valuable insight into possible new features and improvements. We’ll be doing a major push to add core features as well as new extensions. There will also be a concerted effort to document and update the existing extensions. Stay tuned!

New Update Procedure

Posted on September 21, 2009 by Sean Schofield

The rake spree:upgrade task has been eliminated. It turns out there were some crucial flaws that caused issues when the older version of Spree used a different version of Rails or a different version of upgrade.task than the newer version of Spree. The rake task has been replaced by a new gem command:

spree —update

You can also use the abbreviated form:

spree —u

After installing a new version of the Spree gem, simply run either one of these commands from inside RAILS_ROOT (your application directory) and your application will be upgraded.

The update process is also now less "destructive" than in previous versions of Spree. Instead of silently replacing crucial files in your application, Spree now checks the content of files it needs to replace, and if the old version differs, it will be saved with a ~ suffix.

This makes it easier to see when and how some file has changed – which is often useful if you need to update a customized version. The update command will also no longer copy the @rou