Spree Commerce

Try It Now

Fosdick and MDS Fulfillment Integration Upgrades

Posted on December 16, 2014 by Alexander Diegel

Spree Commerce Upgrades Fosdick and MDS Fulfillment Integrations for Wombat

Spree Commerce has upgraded the Fosdick and MDS Fulfillment Integrations for its automated ecommerce integration platform, Wombat. Now, connecting with these integrations is just a matter of following a few simple steps.

Wombat connects ecommerce storefronts to a versatile range of integrations, simplifying the backend operations and increasing speed to market. By making the connection to leading fulfillment and inventory integrations like Fosdick and MDS, Wombat users can automate their shipment processes.

Specific benefits users will gain with these integrations include the ability to:

  • Increase efficiency by fulfilling shipments when online orders are placed
  • Keep inventory in sync by tracking inventory levels in real time
  • Reduce lag between order creation and order shipment; improve customer experience

“Accurate shipping and fulfillment services are a clear need for any ecommerce brand,” said Spree Commerce co-founder and CEO Sean Schofield. “When you automate this process with one of these integrations, you maximize the potential of these services from both an accuracy and efficiency standpoint. The more precise and effective your shipping and inventory is, the more customers will know they can trust your brand, and the more they’ll come back.”

Get accurate and reliable access to MDS Fulfillment and Fosdick by signing up for a free two-week integration platform trial of Wombat. For technical documentation on these integrations, visit the Wombat knowledge base.

To view this press release in its orginal format, visit Nasdaq GlobeNewswire.

Bronto and Twilio Integration Upgrades for Wombat

Posted on December 09, 2014 by Alexander Diegel

Spree Commerce and Spree Certified Partner Agile Engine upgraded the Twilio and Bronto integrations for Spree’s automated ecommerce integration platform, Wombat. Now, making these connections is just a matter of a few minutes.

Wombat connects ecommerce brands with all of their mission-critical services with the most versatile arsenal of integrations in the industry. By making the connection to leading communication and customer service integrations like Bronto and Twilio, Wombat users can automate key aspects of their messaging and marketing campaigns.

Specific benefits users will gain with these integrations include the ability to:

  • Track and verify customer information
  • Ensure superior customer service by providing order status information right at customers’ fingertips
  • Send order confirmations when orders are placed or updated

“Effective communication is a two-way street,” said Spree Commerce co-founder and CTO Brian Quinn. “In order for customers to receive what seems like a simple email or a text, everything has to run properly on the backend first. With these upgrades, we’ve made the backend process as straightforward as possible; no custom code required.”

Get accurate and reliable access to Bronto and Twilio by signing up for a free two-week integration platform trial trial of Wombat. For technical documentation on integrating Bronto and/or Twilio with Wombat, visit the Wombat knowledge base.

To view this press release in its original format, visit NASDAQ Globewire.

Spree 2.4.2 Released

Posted on December 05, 2014 by Jeff Dutil

Summary

We have just released new versions of all the currently supported Spree versions. The Spree 2.4.2, 2.3.6, 2.2.8, 2.1.11 releases are out now!

The primary focus of these releases was resolving a security flaw in the API. While no user or credit card data could be exploited with this flaw, there is the potential to commit fraud by manipulating an item’s price. It is recommended that all Spree installations running a 2.1.x, 2.2.x, 2.3.x, and 2.4.x upgrade as soon as possible.

Thanks to Leandro Julian for finding the issue, and providing a patch to resolve the issue.

You can review the Github Compare for a complete list of 2.4.x changes.
You can review the Github Compare for a complete list of 2.3.x changes.
You can review the Github Compare for a complete list of 2.2.x changes.
You can review the Github Compare for a complete list of 2.1.x changes.

Reporting Security Issues

Please do not announce potential security vulnerabilities in public. We have a dedicated email address security@spreecommerce.com. We will work quickly to determine the severity of the issue and provide a fix for the appropriate versions. We will credit you with the discovery of this patch by naming you in a blog post.

If you would like to provide a patch yourself for the security issue do not open a pull request for it. Instead, create a commit on your fork of Spree and run this command:

$ git format-patch HEAD~1..HEAD —stdout > patch.txt

This command will generate a file called `patch.txt` with your changes. Please email a description of the patch along with the patch itself to security@spreecommerce.com.

Older Versions of Spree

If you are using Spree versions 2.0.x and older you should consider upgrading as soon as possible. While this security flaw only affects versions 2.1.x+ we have already reached the end of life for official 2.0.x support. Our current Release Policy is to only maintain the latest two versions of Spree along with the current master.

Follow Spree Commerce!

The Minimalist Guide to Spree Static Content

Posted on December 03, 2014 by Carlos Muñiz

About the Author

Carlos Muñiz is a software engineer for Spree Commerce Certified Partner Crowd Interactive. He is always interested in being part of new and innovative projects, looking for new ways of interaction and combining different technologies. Crowd Interactive is a leading Ruby on Rails consultancy that specializes in creating and scaling Rails applications and building high-quality stores for customers who are passionate about the creative process.

In many Spree projects where I’ve worked previously, it had become necessary to handle static pages like “Help,” “Terms and Conditions,” “About Us,” etc. In short, all those “stock pages” and some others that come out of the box with any ecommerce website.

I always recommend my colleagues deliver a simple way to generate the pages. Although I LOVE to write all the HTML with my own hands, it’s more efficient to use Rails helpers or some other markup such as HAML.

The point is, as consultants, it’s our duty to deliver a stable, functional, installable and, somewhat recoverable product. To achieve this, the extension Spree Static Content has always worked for me because it’s simple to configure and we can easily generate a task to regenerate all the “core” static pages of our project. It’s especially useful for those cases where someone “accidentally” deletes their content.

lib/tasks/static_content.rake

As you can see, the rake task is quite simple and consists of the following steps:

1. Delete existing pages:

This is a matter of taste. It’s possible to separate the “default” static pages from any other with some scope if you’re able to find specific pages you want to delete. In my case, I’m destroying all of them.

2. Read the information on pages:

For convenience, I always create a “setup” file separately that contains the necessary information for our pages, such as Title, Slug, and the name of the View that we’ll be using as our static page’s Body.

3. Create an instance of a controller:

This has the purpose of delegating the rendering of the views to the proper object allowing us, as I said before, to use view helpers or another abstraction markup language like HAML.

4. Iterate each page:

For each entry we have in our configuration file, we’re going to generate the body of the page letting our Controller instance the renderee. From there on out we only create the Spree::Page.

Static Content Example config file:
db/fixtures/static_content.yml

Example page:
app/views/spree/staticcontent/privacy_policy.html.haml

That’s all, we just need to go to a terminal and run:

terminal

$ be rake static_content:reload

And… Voilà! we won’t have headaches trying to update, maintain or recover any “static page” we deliver and that somebody had erased “accidentally”.

To view this guide in its original format, visit the blog of Crowd Interactive.