Notice something different? Meet the new Solidus brand!

Use Cases

Use cases

Product

Developers

Resources

Big player with big needs? See what Solidus can do for you.

Enterprise

Solutions

The foundation to stand up. The flexibility to stand out.

Features

Don’t reinvent the wheel—use our built-in integrations.

Integrations

Pricing plans designed to accommodate your growth.

Pricing

Documentation

Policies

Insights and announcements from the Solidus team.

Blog

Need a bit of help? Engage our trusted partners!

Partners

Join us if you want to chat—we're a friendly bunch!

Community

We've released Solidus [3.1.4](https://github.com/solidusio/solidus/releases/tag/v3.1.4), [3.0.4](https://github.com/solidusio/solidus/releases/tag/v3.0.4) and [2.11.13](https://github.com/solidusio/solidus/releases/tag/v2.11.13) to address a security vulnerability ([GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus/security/advisories/GHSA-qxmr-qxh6-2cc9)) affecting all versions of Solidus.

You can read about GHSA-qxmr-qxh6-2cc9 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [http://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-qxmr-qxh6-2cc9. Please, update your store soon.

New Solidus releases to address a security vulnerability

It's official! [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) will be on January 27th, 2022 with a bonus community day on January 28th. The conference will be entirely remote, held on Gather.town, and we couldn't be more excited to hear from the experts and spend time with the community.

The past few years have been arduous for so many people, with new obstacles arising every day. It's been difficult to not be able to get together in person and have the conferences we've gotten used to over the past five years. We were very grateful to Sean Denny and [Nebulab](https://nebulab.com/) for planning Solidus Conf 2020 last year. When some people thought we wouldn't be able to have a conference at all during the pandemic, he kept the momentum going and led the organization of a great remote event. (And he even jump-started the organization effort for this year's conference too! Thanks again Sean!)

While it would have been great to be able to return to being in-person for this upcoming conference, we're confident that hosting it on Gather.town will ensure a unique and positive experience that everyone can enjoy - regardless of location! You can visit [Gather.town](https://gather.town/app) to explore the app ahead of time, and learn more about what to expect.

At Solidus Conf, the speakers never disappoint, and this year is setting up to be no different. Jared Norman (Core Solidus Team Member), and Chris Todorov, both from [Super Good Software](https://supergood.software/)will be speaking, along with Marc Busqué (Core Solidus Team Member) from [Nebulab](https://nebulab.com/), Peter Berkenbosch, Thomas Sample from [Karma Creative](https://karmacreative.io/), and Daniel Pritchett from [Rebellion Defense](https://rebelliondefense.com/). We can't wait to hear from all of these extraordinary Solidus developers, along with those who have yet to confirm. Stay Tuned as we release the rest of the speaker list over the next coming weeks. You can find an up-to-date list of speakers and their details on the [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) website. If you, or someone you know has an idea for a great talk, please reach out and let us know - we would love to hear from you!

With everything that's been happening, we feel extremely fortunate to have the Solidus community to help provide support and comradery. The Solidus Stakeholders have been meeting at least every other week since 2018, and are passionate about keeping the platform moving forward. As an open source community, it's vital to keep the communication lines open, and the conference is the perfect place to make sure everyone is up to speed. We encourage each and every attendee to join the Solidus Slack Channel, and consider becoming a stakeholder themselves, because it really is all of us that make Solidus what it is, and can keep the platform progressing and thriving.

This year Thomas Sample and Karma Creative led the charge so far in organizing the conference, with expert design and development help from Michela Frecchiami and Nebulab. But with two months to go, we still are in need of additional hands and minds! Speaking of which, shout out to Chris Todorov from Super Good Software who is joining the organization team. Thanks Chris! -- If you are interested in helping with the organization, graphic design, web development, marketing, or day-of responsibilities at Solidus Conf 7, please reach out and let us know. In recognition, everyone involved will be listed as a contributor at the bottom of the conference website and receive some special organizer swag.

You can find additional information, and buy your tickets on the [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) website - we can't wait to see you again, learn, and have some fun together!

And have you thought about Sponsoring? You'll get $1 tickets and a bunch of other awesome benefits. And best of all, if you're already an Open Collective monthly Sponsor, you're also already a Solidus Conf 7 Sponsor! -- Open Collective Sponsors this year will automatically receive a corresponding sponsorship matching the level of their monthly donation!!

It's official! Solidus Conf 7 will be on January 27th, 2022 with a bonus community day on January 28th. The conference will be entirely remote, held on Gather.town  


Announcing Solidus Conf 7

We've released `solidus_auth_devise` [2.5.4](https://github.com/solidusio/solidus_auth_devise/releases/tag/v2.5.4) to address a security vulnerability (GHSA-xm34-v85h-9pg2) affecting all versions of `solidus_auth_devise`.

We've also released Solidus [3.1.3](https://github.com/solidusio/solidus/releases/tag/v3.1.3), [3.0.3](https://github.com/solidusio/solidus/releases/tag/v3.0.3) and [2.11.12](https://github.com/solidusio/solidus/releases/tag/v2.11.12). They just contain a patch in case you're unable to update `solidus_auth_devise`.

You can read about GHSA-xm34-v85h-9pg2 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [https://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-xm34-v85h-9pg2. Please, update your store soon.

New solidus_auth_devise & Solidus releases to address a severe security vulnerability

- [3.1.0 on GitHub](https://github.com/solidusio/solidus/releases/tag/v3.1.0)
- [3.1.0 on RubyGems](https://rubygems.org/gems/solidus/versions/3.1.0)

We've just released Solidus `v3.1.0`!

Thanks to all contributors, testers, and users who made this release possible.

This version's support will end in 18 months: 2023-03-10.

## What's next?

For the next minor release (3.2.0), we plan to make huge changes to the Event Bus, in order to provide
a solid architecture with a set of tools that will help developers use this feature. We are planning
to release a new adapter along with the current one, to allow Solidus' users some time to switch, which
could require some code change in the host applications.

The main features of the new Event Bus Adapter are:

- Isolation from `ActiveSupport::Notification`.
- Better observability for event-generated flows.
- Better testability.
- More robust events registration.

## What changed on Solidus 3.1

Here's what changed in the last released version. If you have any trouble updating or you want to leave
some feedback, please use [this GitHub Discussion](https://github.com/solidusio/solidus/discussions/4161).

### Major changes

**`Spree.load_defaults`: preference defaults depending on the Solidus version**

Solidus 3.1 brings a new feature where preference defaults can take different
values depending on a specified Solidus version. It makes it possible to stop
deprecating old defaults every time we introduce a change in the recommended
value for a setting. After all, they're just that; recommendations. Instead,
now users can explicitly ask for a given Solidus version defaults and, as
before, override the preferences they want.

When upgrading to 3.1, you have to take action to adopt the new behavior.
You'll need to add `Spree.load_defaults('3.1')` on the very top of your
`spree.rb` initializer. As we're not changing any preference default on this
release, nothing will break. A warning will be emitted on boot-up until you do
it!

However, bumping the version given to `load_defaults` straight away for future
upgrades will not be a safe option. Instead, you'll have to go through the new
update process detailed below.

Take a look at [#4064](https://github.com/solidusio/solidus/pull/4064) for more information.

**New update process**

As aforementioned, preference defaults can change after a Solidus release. Once
you have your defaults locked to the current Solidus version, a new upgrade
won't break your application because of them. However, it's a good idea to
adapt your application to the updated recommended settings. To help with this
process, Solidus comes with a generator that you can execute like this:

```bash
bin/rails g solidus:update
```

That generator will create a new initializer called `new_solidus_defaults.rb`,
which will preview all the defaults that have changed between versions, each on
a commented line. From that point, you can activate the new defaults one by one
and adapt your application incrementally. Once you're done with all of them,
you can bump the version given to `Spree.load_defaults` in the `spree.rb`
initializer and remove the `new_solidus_defaults.rb` initializer altogether.

You can read in more detail about [this process on our
guides](https://guides.solidus.io/getting-started/upgrading-solidus#updating-preferences).

On [#4087](https://github.com/solidusio/solidus/pull/4087) you can find more.

**Other important changes**

`Spree::Price#amount` field can no longer be `nil`. Besides adding the
validation at the model layer, we ship with a task that will remove records
where the amount is `NULL` in the database. You should run the task before
executing the new migrations:

```ruby
bin/rails solidus:delete_prices_with_nil_amount
bin/rails railties:install:migrations
bin/rails db:migrate
```

If you're running migrations automatically on deploy, you should run the task
before rolling out the new code. In that case, you first should make sure that
you have affected records:

```ruby
Spree::Price.where(amount: nil).any?
```

If the above code returns `false`, you don't need to do anything else.
Otherwise, copy [the
task](https://github.com/solidusio/solidus/blob/master/core/lib/tasks/solidus/delete_prices_with_nil_amount.rake)
into your code, and deploy & execute it. Another option is to execute it
manually in your console in production. However, be extremely careful when
doing that!! :warning: :warning: :warning:

```ruby
Spree::Price.where(amount: nil).delete_all
```

Take a look at PR [#3987](https://github.com/solidusio/solidus/pull/3987) for more details.

### Other Changes

But there's also a lot of other stuff in this release! If you want to see the full list of the
changes made, plase take a look at the project's [CHANGELOG on GitHub](https://github.com/solidusio/solidus/blob/master/CHANGELOG.md).


We've just released Solidus v3.1.0! Thanks to all contributors, testers, and users who made this release possible. This version's support will end in 18 months: 2023-03-10.

Solidus v3.1

Hello everyone, and welcome to This Month in Solidus: May 2021 edition!

### Solidus <-> ShipStation 1.0.0 Is Out!

After extensive production testing, we're finally happy to release the first stable version of
[solidus_shipstation](https://github.com/solidusio-contrib/solidus_shipstation)!

Our ShipStation integration supports both the legacy XML integration as well as the new, more
powerful ShipStation API. It uses a smart batch-syncing mechanism to work around ShipStation's low
rate limits, which allows it to sync up to 4000 orders/minute via the API, and it supports webhooks
to sync tracking information back to Solidus.

We've been using the extension in production in a few different stores with great success, so feel
free to go ahead and give it a try!

_Pro-tip: Combine solidus_shipstation with [solidus_easypost](https://github.com/solidusio-contrib/solidus_easypost)
to gain complete ownership of your post-purchase experience and fulfillment process!_

### Solidus Now Supports Ruby 3

We have recently introduced [Ruby 3 support!](https://github.com/solidusio/solidus/pull/4072)

While this was a pretty low-lift initiative on our side, it enables all Solidus users to benefit
from all the latest improvements to the language, and paves the way for a more modern Solidus
ecosystem!

### A Goodie for Docker Fans...

If you like developing with Docker and missed Docker support in Solidus, cry no more! You can now
boot up the codebase with as little as `docker-compose up`, thanks to our new 
[Docker Compose support](https://github.com/solidusio/solidus/pull/3947).

We hope this will make it even easier to contribute to Solidus for new and experienced users alike!

### ...And a Few More for Everyone Else!

The community has also been hard at work on a few improvements and bugfixes:

- Stock location sorting had been inadvertently broken in a previous change, but Ikraam Ghoor from
  Nebulab was kind enough to [fix it!](https://github.com/solidusio/solidus/pull/3954) Thanks, Ikraam!
- The [ItemTotal](https://github.com/solidusio/solidus/pull/3431) promo rule is now easier to extend
  and customize, thanks to Elia Schito from Nebulab!
- API attributes have been [moved to a configuration option](https://github.com/solidusio/solidus/pull/4039),
  which makes it easier to customize them without running into any autoloading issues. Thanks to
  Stefano Nada from Nebulab!
- In rare cases, it was possible for two store credit instances to have the same authorization code,
  if they were generated at very close moments in time. This was [fixed](https://github.com/solidusio/solidus/pull/4060)
  by Andrea Longhi from Nebulab!
- A validation on customer returns would break when the return did not have any items. [This isn't the
  case anymore](https://github.com/solidusio/solidus/pull/4068), thanks to Willian Veiga!
- A bug was preventing admins from setting the reason for return items. The issue was found and 
  [fixed](https://github.com/solidusio/solidus/pull/4080) by Andrea Longhi from Nebulab!

That's it for this month! We'll see you in 30 day, stronger, faster and with more updates!

_Spend an awesome Tuesday! 👋️_

Dive in and see everything that happened in the Solidus world in May 2021!

This Month in Solidus: May 2021

Here's your monthly dose of This Month in Solidus! Keep reading to learn everything that happened in
the Solidus world this April.

### Solidus 3.0.0 Has Been Released!

That's right — [Solidus 3.0.0 is finally out!](https://solidus.io/blog/2021/04/20/solidus-v3-0.html)

This release has been months in the making, and it  removes all the code that was deprecated in the
2.x series.

A big thanks to everyone who worked on it and to those who helped us get it across the finish line
by giving us feedback and testing the release candidate and the upgrade process on their store. It
was a long process, but we can now start with a clean slate to continue iterating on the framework.

In fact, we're already hard at work on features for the next releases, so stay tuned!

### Subscriptions Is Now Officially Stable!

After months of testing it on different production apps, we were finally comfortable enough to
release [solidus_subscriptions 1.0.0](https://github.com/solidusio-contrib/solidus_subscriptions) —
so we did just that.

If you have used or are using the previous version of the extension, this new release will feel like
a completely new piece of software, and for very good reasons! We removed and simplified tons of
code, while also adding even more features and extension points for aspects that developers often
want to customize.

Today, we can pride ourselves with having one of the most powerful and flexible subscriptions
engines available. If you're building a subscription-based business, it would be crazy not to
give it a try.

### Upcoming DX Improvements: Better Events, Smoother Upgrades, and More!

As I said, we're already hard at work for Solidus 3.1 and beyond.

Our focus for the 3.x series is two-fold:

- On one hand, we want to continue improving the Developer Experience of adopting, integrating and
  maintaining Solidus. By giving you sensible defaults, battle-tested best practices and powerful
  development tools, using Solidus should be a no-brainer.
- On the other, we also want to continue investing in solving big eCommerce challenges, so we'll
  continue to work on subscriptions, and... something else, but we're not quite ready to share that
  with you just yet. We'll keep you posted!
  
You can see some of this work on GitHub already, and we'll continue to share it with you in the
upcoming weeks and months [in our Slack](https://solidus.slack.io), [on our blog](/blog) and through our newsletter.
  
In the meantime, let us know if you have any feedback or ideas to share with us, and we'll see you
all again very soon!

_Have a great week! 👋️_

Dive in and see everything that happened in the Solidus world in April 2021!

This Month in Solidus: April 2021

Solidus is looking for a Developer Relations Engineer!

### About the project

Solidus is the free, open-source platform for eCommerce trailblazers. Built on Ruby on Rails, Solidus is designed to
be incredibly flexible: you start from a strong foundation, but you have the freedom to customize every single aspect
of your store. Today, Solidus is used in production by a multitude of popular stores such as Maisonette, MeUndies,
On and Ace & Tate, just to name a few.

We want to produce amazing content for developers using Solidus. Our documentation will define the best practices to
build reliable custom eCommerce websites using Ruby and Rails.

### About the role

We are looking for a Developer Relations Engineer for Solidus. You would work along the Core Team and the rest of the
Solidus community to maintain and evolve the platform over the years.

#### What you will be doing:

- Scoping and building samples, docs, and developer content with minimal guidance.
- Producing code and documentation that is accessibly written for a well-defined audience.
- Providing support to community members in the platform's Slack channel, on StackOverflow and in GitHub Discussions.
- Contributing with ideas and thoughts to shape the future of the platform.
- Improving developer experience including writing web-based tools to make developers' jobs easier.

#### Requirements and nice-to-haves

You may be the right person if you have the following:

- Experience in developer relations, or other customer-facing roles.
- Experience participating in online and offline developer communities and ecosystems (e.g., open-source platforms, blogs, YouTube video series,
  tech conferences, hackathons, meet ups, technical teaching, and training).
- Experience developing platforms, SDKs, or developer tools.
- Experience with Ruby and Rails, to make small contributions to the platform and embed ecosystem's best practices within developers content.
- Excellent oral and written English and strong communication skills.
- Ability to interact effectively with both business and engineering.

Furthermore, you are most likely the right person if you also have some or all of the following:

- Track record of open-source contributions and community involvement a plus.
- Experience maintaining and evolving large documentation projects over long periods of time.
- Experience in the eCommerce domain.

#### Timezone and location

This is a fully asynchronous position open to candidates from all over the globe.With that said, you will need to attend a few meetings every
now and then, so make sure you have at least a few hours of overlap with CET and ET.

### About the employer

Because Solidus is a community-sponsored project, you'll be paid by the community through [our Open Collective funds](https://opencollective.com/solidus),
which are collected and spent in complete transparency. You will report directly to the
[Solidus stakeholders](https://github.com/solidusio/solidus/blob/master/GOVERNANCE.md#stakeholders).

Note that this is a contractor position with no further benefits. You will be expected to manage your time, submit invoices and pay your own taxes.

#### Hiring process

These are the hiring process' steps:

1. Fill [this form](https://solidusio.typeform.com/to/GfMoUbiK) with your information.
2. You'll get in touch with one member of the Stakeholders Group for scheduling an informal video meeting. We'll be discussing your
   past experiences and why you fit the role.
3. If we are a good match, you'll be invited to another video meeting with a representative of the Stakeholders Group for the final decision.

We are looking forward to knowing you!

Solidus is looking for a Developer Relations Engineer!

Solidus is hiring a Dev Rel Engineer

- [3.0.0 on GitHub](https://github.com/solidusio/solidus/releases/tag/v3.0.0)
- [3.0.0 on RubyGems](https://rubygems.org/gems/solidus/versions/3.0.0)

We've just released Solidus `v3.0.0`!

One of the primary goals that drives the development of Solidus is allowing easy upgrades.

Easy upgrades allow teams that use Solidus to take advantage of the latest platform improvements, but it's equally crucial
for faciliating community contribution: using a recent version of Solidus lets teams easily contribute to the platform.
Due to this exchange, Solidus mirrors what's really needed by its users as closely as possible and the whole
community benefits from new features and fixes.

Solidus `v3.0` is a release that respects this mindset. In fact, Solidus `v3.0` is nearly identical to the last `v2.11.x` version,
with the only difference that the new one doesn't have the code that we deprecated during the `v2.x` lifecycle: if
you don't see deprecation messages in your application logs, you should be good to upgrade your store with minimal effort.

Despite the easy upgrade path, there are some relevant things to consider when upgrading:

### We do not require all of Rails by default anymore

By requiring `rails/all`, Solidus was loading a bunch of unnecessary code that was probably consuming more memory than necessary.
This change only loads what's strictly needed and allows stores that want to cherry-pick certain parts of Rails to benefit from the more
attentive choice.

### Active Storage by Default

Both Solidus `v2.11` and Solidus `v3.0` come with full support for Rails `6.1`, `6.0` and `5.2`. With Solidus `v3.0` as default on new stores,
we ship fully working `Active Storage` support. In future versions, we will remove the `Paperclip` dependency because `Active Storage` is
becoming the new standard for Rails developers.

This change won't impact your existing store as long as you keep using `Paperclip` as the attachment module with:

```ruby
Spree::Config.image_attachment_module = 'Spree::Image::PaperclipAttachment'
Spree::Config.taxon_attachment_module = 'Spree::Taxon::PaperclipAttachment'
```

### Discarded Paranoia

We finally completed the heroic work started by [John Hawthorn](https://github.com/jhawthorn) to remove `paranoia` and introduce a new gem for
soft-deleting records. This gem is called [discard](https://github.com/jhawthorn/discard) and provides a more explicit interface when dealing
with record deletion. After a deprecation cycle, this is now the only supported way to soft-delete records in the codebase. No more surprises when deleting or destroying records!

### Unified Name in Address

We removed all usage of split `firstname` and `lastname` for addresses since
[this concept is not valid in all cultures around the world](https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/).
Now we have a single field in the system called `name`.

In the last version of Solidus in the `v2.x` series, we added the `name` attribute to the database and started to populate it with the
combination of `firstname` and `lastname`. We also provided a rake task to populate the `name` field for existing records, in order to
make the database consistent, and ready to switch `Spree::Config.use_combined_first_and_last_name_in_address` to `true`, which will be
the only supported value in Solidus `v3.0`.

We suggest migrating to this new schema before the upgrade to `v3.0`. You can follow this approach:

1. Upgrade to the latest `v2.11.x` version
2. Run  `bin/rails railties:install:migrations` and `bin/rails db:migrate`
3. Run the dedicated rake task [`bin/rails solidus:upgrade:two_point_eleven`](https://github.com/solidusio/solidus/blob/09c53ee00ee25450e76b474d713934b087af2bed/core/lib/tasks/upgrade.rake) that will migrate the address fields
4. Switch the `Spree::Config.use_combined_first_and_last_name_in_address` preference to `true`

This process will make your application behave exactly as it will with `v3.0`, which only removes the support for that preference being `false`.

### Removed preferences

We removed some preferences that were controlling deprecated behaviors. You probably already changed their value to remove the deprecations from your logs but when upgrading, be sure they are not used in your codebase since they do not exist anymore. They are:

- `Spree::Config.raise_with_invalid_currency`
- `Spree::Config.redirect_back_on_unauthorized`
- `Spree::Config.run_order_validations_on_order_updater`
- `Spree::Config.use_legacy_order_state_machine`
- `Spree::Config.use_legacy_store_credit_reimbursement_category_name`
- `Spree::Config.consider_actionless_promotion_active`
- `Spree::Config.use_legacy_address_state_validator`
- `Spree::Config.use_combined_first_and_last_name_in_address`

Please take a look at the [CHANGELOG](https://github.com/solidusio/solidus/blob/master/CHANGELOG.md) for a detailed list of changes.

## Troubles upgrading?

If you have any issue when upgrading, you can find support on
[this thread on GitHub Discussion](https://github.com/solidusio/solidus/discussions/4030) or in the `#support` channel of our
[Slack Workspace](https://slack.solidus.io/).

## Thanks!

Thanks to all code contributors that made Pull Requests during the 2.x lifecycle, especially to [John Hawthorn](https://github.com/jhawthorn)
and the rest of what was the Stembolt team.

Thanks to all financial contributors that help the ecosystem supporting the development of Solidus and its community via our [Open Collective page](https://opencollective.com/solidus).

This release couldn't be possible without you all!

We've just released Solidus v3.0.0! One of the primary goals that drives the development of Solidus is allowing easy upgrades.

Solidus v3.0

Hey there, and welcome to your usual This Month in Solidus! Let's dive in and see everything that
happened in the Solidus world this March.

### (Yet Another) Full-Time Maintainer 👷‍♂️

Last month, we announced that Marc Busqué had joined the Nebulab team as a full-time Solidus
maintainer. We were pretty excited about the experience Marc brought to the table, being a
contributor to the popular [dry-rb](https://dry-rb.org) framework and maintaining OSS projects
of his own. In fact, Marc has already started tackling some pretty huge architectural challenges,
with the goal of making Solidus easier to extend, customize and maintain.

This month, we're doubling the excitement, because [Connor Ferguson](https://github.com/cpfergus1)
just joined Marc as our second full-time Solidus maintainer. Connor will help Marc with day-to-day
maintenance tasks as well as more future-looking initiatives, and he has already started
contributing  to finalizing the Solidus 3.0 release.

Which brings us to the next point...

### Solidus 3.0.0.rc2 Is Ready for Testing! 🛠

We released Solidus 3.0.0.rc2 on March 10. This is a release candidate, meaning that it's stable
and extremely close to what the final release will look like.

We need feedback from the entire community on the upgrade path from 2.x to 3.x, so we encourage you
to try the upgrade on your  stores and leave any feedback in [Slack](http://slack.solidus.io) or on
[GitHub Discussions](https://github.com/solidusio/solidus/discussions).

Just a little reminder: Solidus 3.0 does NOT include any new functionality, but rather it removes
all of the deprecations that were introduced during the 2.x releases, so that we can clean up the
codebase and start form a clean slate.

With that said, our goal is to build an ever more stable and extensible Solidus, and we do have tons
of stuff on the roadmap for the 3.x series. We can't wait to share it with you!

### Subscriptions 1.0.0.rc1 ♻️

We do like our release candidates, so much so that we also released
[solidus_subscriptions](https://github.com/solidusio-contrib/solidus_subscriptions) 1.0.0.rc1 this
month. It would be hard to overstate how much work went into this particular release: our goal was
to build *the* ultimate solution for managing a subscriptions-based eCommerce business, and we feel
like this release candidate is a giant leap in that direction.

The extension as a whole is now more powerful, more flexible, more performant and easier to
understand at the same time. Here's a non-comprehensive list of features and improvements:

- We've added built-in support for the most common subscription use cases and scenarios, such as the 
  ability to cancel failed installments when a new one is generated.
- We've implemented a brand new admin UI that allows you to manage all aspects of a subscription.
- We've added support for subscription events, to make it easy to run analytics and provide customer
  support. These also integrate with the Solidus event bus natively.
- We have parallelized subscription processing, which is now more resilient and allows you to take
  full advantage of your background processing library of choice!
- We have rewritten pretty much the entire codebase from scratch, to focus on simplicity and 
  linearity. We want the codebase to be easy for everyone to understand and extend.

And there's much, much more to it! Just take a look at the [closed PRs](https://github.com/solidusio-contrib/solidus_subscriptions/issues?q=is%3Aissue+is%3Aclosed)
and you'll get a sense of the amount of improvements in this release candidate. If you're already
using solidus_subscriptions, now is the time to consider upgrading to benefit from all the goodies!

With that said, there's much more that we want to do, so make sure you don't miss any of our
updates, and join [Slack](https://slack.solidus.io) and [GitHub Discussions](https://github.com/solidusio/solidus/discussions)
to become a part of the conversation.

_Once more, that's it. See you around! 👋️_

Dive in and see everything that happened in the Solidus world in March 2021!

This Month in Solidus: March 2021

Hey there, and welcome to your usual This Month in Solidus! Let's dive in and see everything that
happened in the Solidus world this February.

### New Full-Time Maintainer 👷‍♂️

Yes, you read that right! So far, Solidus has progressed thanks to the generous contributions of its
community, but we felt it was time we gave it a proper full-time maintainer, and
[Nebulab](https://nebulab.it) stepped in to fill the gap.

[Marc Busqué](https://github.com/waiting-for-dev) is a senior Ruby developer based in beautiful
[Cambrils, Spain](https://en.wikipedia.org/wiki/Cambrils). He has an impressive track record of
contributing to OSS, having worked on the renowned [dry-rb](https://github.com/dry-rb) ecosystem.

Marc recently joined the Nebulab team, where he will work with the Core Team on the maintenance and
evolution  of Solidus, splitting his time between keeping the platform in good shape and pushing it
forward with his technical expertise.

Welcome aboard Marc, and best of luck!

P.S. Pretty soon, Marc should be in good company... Stay tuned!

### Solidus 3 is getting closer 🚀

We are working hard to cross the ts and dot the is for the release of Solidus 3.0.

Last month, we organized a Hackathon to get the extensions ready for the next major bump, and
the results were amazing: we got 23 extensions ready _in a single day._ Thanks to everyone who
participated: your dedication to the project is truly inspiring!

With that said, there are still some extensions that could use some love! If you want to help,
just follow the instructions in [this GitHub Discussion](https://github.com/solidusio/solidus/discussions/3911),
and ping us on Slack if you have any questions!

### Backend UX Audit 🎨

Last Thursday, the stakeholders have approved a vote to engage [Baymard](https://baymard.com/) for
a UX audit of the Solidus backend.

We are _extremely_ excited about this: Baymard is a world-class UX institute that has worked with
some of the best players in the industry, and we're looking forward to using their expertise to
improve the Solidus backend experience.

Furthermore, this is a major initiative that is being entirely financed by our
[Open Collective funds](https://opencollective.com/solidus) — we couldn't be more grateful to our
contributors for their generosity. If you're a brand or an agency benefiting from Solidus and want
to show your appreciation, joining Open Collective ie an amazing way to do it! 

Baymard can use all the help they can get, so if you have any feedback to share about the Solidus
backend that you think would be beneficial for this audit, don't be shy about stepping forward! You
can reach out to any Core Team member on Slack, who will direct you to the proper channels.

### ShipStation API Integration 📦

[`solidus_shipstation`](https://github.com/solidusio-contrib/solidus_shipstation) was recently
overhauled to allow users to benefit from the new [ShipStation API](https://www.shipstation.com/docs/api/),
which will eventually supersede the legacy [XML integration](https://help.shipstation.com/hc/en-us/articles/360025856192-Custom-Store-Development-Guide).

The new API integration provides several advantages over the previous one: it is much more flexible,
providing you with greater granularity of how you import and handle your orders in ShipStation, and
much more performant, allowing you to sync up to 4000 orders/minute from your Solidus store.

Most importantly, we built the new integration so that switching from the legacy XML format is
completely painless, so go ahead and check it out right now!

### In The Works: Certified TaxJar Integration 💸

[SuperGood's TaxJar integration](https://github.com/SuperGoodSoft/solidus_taxjar) has always been
amazing, but it's about to get _so much better!_

The SuperGood team is working towards getting the extension [fully certified](https://developers.taxjar.com/integrations/certification-guidelines/),
which means they will add a ton of new features in the process.

They could definitely use some help, so if you have worked with TaxJar in the past and want to
contribute, hop on GitHub!

_Aaaand that's it for now. See you next month! ❤️_

Dive in and see everything that happened in the Solidus world in February 2021!


This Month in Solidus: February 2021

Hey there, and welcome to This Month in Solidus: 2020 EOY Edition! This update covers everything
that happened in the Solidus world in December 2020 and January 2021.

### Solidus 2.11.4 Is Out, with Rails 6.1 Support

Solidus 2.11.4 was released on January 19, and includes full support for Rails 6.1 as well as a few
other minor improvements and bugfixes.

If you are were planning to upgrade to Rails 6.1, now is a good time to do it!

Thanks to Filippo Liverani from Nebulab for [taking the lead](https://github.com/solidusio/solidus/pull/3862)
on this!

### Solidus 3.0: A Clean Start, Coming Soon!

In the past few months, most of the work has gone towards [removing all the code that was deprecated
in Solidus 2.x](https://github.com/solidusio/solidus/pull/3818), in preparation for Solidus 3.

This was a *huge* lift that required the effort of many contributors across several months, and the
end result is pretty amazing: we have removed almost _6,000_ lines of legacy code, which included
deprecated classes, methods, preferences and supporting utilities.

Solidus 3 represents a clean start for the framework and allows us to continue iterating and stay on
top of industry trends, while also providing the same stability and the same guarantees as its
predecessors.

A huge thanks to everyone that was involved in this, and especially to Filippo Liverani, Dumitru
Ceban, Daniele Palombo and Alberto Vena from Nebulab!

### Extensions Updates: solidus_feeds and solidus_subscriptions

In the extensions ecosystem, most of the effort has went into two major initiatives that should make
it even easier to jumpstart a modern Solidus store.

[solidus_feeds](https://github.com/solidusio-contrib/solidus_feeds) was just released, with built-in
support for the Google Merchant XML format and full decoupling of feed generation and publishing. In
other words, you can easily implement your custom feed formats and take advantage of one of the
existing publishers, or publish one of the existing feed formats to some custom location, all
through a fully configurable API. Thanks to Elia Schito, Nicolò Rebughini and Flavio Auciello from
Nebulab for their hard work on this.

[solidus_subscriptions](https://github.com/solidusio-contrib/solidus_subscriptions), an old and
beloved extension, has also seen a lot of improvements recently. Most of the work has gone towards
improving the admin UI around subscriptions and streamlining the processing logic to make it more
flexible and resilient than ever. Some goodies were also thrown in for good measure, such as
built-in [ChurnBuster](https://churnbuster.com) support and more choices around failed payment
processing. Thanks to Igor Barbosa, Nicolò Rebughini and Alessandro Desantis from Nebulab!

### GitHub Discussions Is the Place to Be

Up until now, all of the community interactions have happened mostly in our [Slack workspace](https://slack.solidus.io)
(which, by the way, is still worth joining if you're not there yet!). While Slack is great for quick
chit-chat and casual interactions, it's less than ideal for support requests: it's not indexed and
hard to search. As a result, great answers were getting lost, and great questions were being asked
over and over again.

When [GitHub Discussions](https://github.com/solidusio/solidus/discussions) became available, it
just felt like the perfect solution to our problems, and we decided to give it a try. You can access
our discussions board by clicking the "Discussions" tab in the main Solidus repository. Some quality
conversation is already happening there, so make sure to swing by and say hello!

### New Roadmap in The Works

With the new year, we immediately started to work on a new **roadmap** for
Solidus! The new roadmap will include a mix of initiatives that we still believe in and didn't get to just yet, and new projects that we believe will set Solidus on the path for success.

If you have any feedback for us, don't be a stranger to jump on [Slack](https://slack.solidus.io) or
[GitHub Discussions](https://github.com/solidusio/solidus/discussions)!

_Until next time! 👋_

Dive in and see everything that happened in the Solidus world in December 2020 and January 2021!


This Month in Solidus: Holidays 2020 Edition

Hey there, and welcome to This Month in Solidus: November 2020! The year is (finally) coming to a close soon, and the time has come to look back at some of the updates we've made in the last month. Let's dive in.

### Extension updates for November

- [**Solidus Dev Support**](https://github.com/solidusio/solidus_dev_support) continues to see a number of improvements thanks to the effort of Elia Schito. Mostly, the changes revolve around setting sensible defaults for new applications - try it out the next time you need to create a Solidus extension!

- [**Solidus Shipstation**](https://github.com/solidusio-contrib/solidus_shipstation) has seen a few small changes - most notably, there's now an option to export cancelled shipments to Shipstation, and a bug was fixed that was affecting tracking numbers on cartons.

- [**Solidus Tracking**](https://github.com/solidusio-contrib/solidus_tracking) saw an update that allows you to selectively disable automatic tracking of certain events.

- [**Solidus Importer**](https://github.com/solidusio-contrib/solidus_importer) now has some QOL improvements that prevent duplicate records or failing commands in certain situations.

- [**Solidus Subscriptions**](https://github.com/solidusio-contrib/solidus_subscriptions) had a number of updates. A bug on admin form submission was fixed, a config option was provided to allow you to specify whether you want to retry failed payments on the next billing cycle, and a handful of smaller bug fixes were bundled in as well.

### Core updates this November

This month, you might have noticed that not much in the way of new features was added to Solidus. That's intended! We're preparing for the release of Solidus 3.0, and most of the work involves removing deprecated code and small bugfixes. Here are some of the more tangible changes that happened in November:

- [Solidus now requires only the modules it specifically needs from Rails.](https://github.com/solidusio/solidus/pull/3478) Previously, Solidus required `rails/all`, but didn't _use_ all of what it required. This updates that, and ensures that we're only requiring the necessary modules - which should be a boost to speed and memory usage! Thanks to Elia Schito for this update.

- [Fixed variant-to-variant image assignment.](https://github.com/solidusio/solidus/pull/3810) This fixes a bug where a variants image could not be assigned to another variant. Thanks, Felix Holmgren!

- [Fixed a payment refund bug.](https://github.com/solidusio/solidus/pull/3831) A bug was introduced previously where if a payment refund failed, any subsequent attempt to refund the payment would also fail. Alberto Vena introduced a fix with this PR. 

- [Fixed a permission set issue that allowed regular users to see tabs on admin.](https://github.com/solidusio/solidus/pull/3840) When choosing what tabs to display on admin, some tabs checked for `show` ability instead of `admin` - which allowed some tabs like "Zones" to display to anyone with the ability to see "Zones" - including regular users. This only affected tab visibility and not the admin pages themselves, but still - big thanks to Alberto Vena for pointing this out and providing a fix!

### Solidus Governance

With [This PR](https://github.com/solidusio/solidus/pull/3836), Alberto Vena released the new version of the governance model (written by Alessandro Desantis). This document goes into detail about how Solidus is run - and what you can do to help the project, or even join the Stakeholders group. If you're interested in seeing the inner workings of a large, community-managed open source project, take a look!

### Solidus Meetups for 2020 conclude

We started this off as "Community Day" for Solidus - an hour-long event where we could get the community together, share our ideas, and hear about the cool stuff happening in the world of Solidus. We liked it so much, we decided to keep it going on a monthly basis! One of the greatest things about Solidus is the community that surrounds it, and it's been an awesome experience being able to see old friends, meet new faces, and hear from talented people at these events. I'm looking forward to putting more together for 2021 - stay tuned!

Be sure to check out our [youtube channel](https://www.youtube.com/channel/UCiFcxyt11T6QIIDPk2w0Jjw) for some our previous meetup and conference presentations. And make sure to subscribe if you want notifications on new videos!

### Solidus Roadmap Survey

Here's your last chance to help Solidus grow! We're working hard on next year's roadmap, and part of that process is the yearly [**Solidus Roadmap Survey**](https://forms.gle/hD1S1YM78JmfZXhe6). The survey is your chance to let us know what direction you want Solidus to go in. Please feel free to share it with your colleagues and clients so they can also chime in with their thoughts. More responses means a more robust roadmap, so we want to get as many responses as possible!

Dive in and see everything that happened in the Solidus world in November 2020


The Solidus Blog