The Solidus Blog

We just released Solidus v2.10! Thanks to all contributors, testers, and users who made this release possible. This version's support will end in 18 months: 2021-07-15. - [2.10.0 on GitHub](https://github.com/solidusio/solidus/releases/tag/v2.10.0) - [2.10.0 on RubyGems](https://rubygems.org/gems/solidus/versions/2.10.0) ### What's changed? The full CHANGELOG can be found on our [GitHub repository](https://github.com/solidusio/solidus/blob/main/CHANGELOG.md) but here's a list of all major changes: #### Added support for Rails 6 Solidus core now fully supports Rails 6! After upgrading to the 2.10 version you can follow the official [Rails Upgrading Guide](https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-5-2-to-rails-6-0). Please note that Rails 6 requires Ruby 2.5.0 or newer. - Add support for Rails 6 [#3236](https://github.com/solidusio/solidus/pull/3236) ([aldesantis](https://github.com/aldesantis)) - Fix dummy app generator to skip Bootsnap and Webpack in Rails 6 [#3327](https://github.com/solidusio/solidus/pull/3327) ([aldesantis](https://github.com/aldesantis)) - Handle deprecation for Rails 6 in DummyApp [#3352](https://github.com/solidusio/solidus/pull/3352) ([cedum](https://github.com/cedum)) #### Deprecated support for Rails 5.1 Rails 5.1 is deprecated and we'll remove support for 5.1 on the next version. If you are still using it, a deprecation warning will be printed in your logs when the application boots. - Deprecate Rails 5.1 [#3333](https://github.com/solidusio/solidus/pull/3333) ([kennyadsl](https://github.com/kennyadsl)) #### Changed default images sizes We update the images used by Solidus demo in the `sample` gem. To update those images we needed to change the default sizes of Spree::Image. They changed from: ``` mini: '48x48>', small: '100x100>', product: '240x240>', large: '600x600>' ``` to ``` mini: '48x48>', small: '400x400>', product: '680x680>', large: '1200x1200>' ``` If your store relies on these sizes, you should change them back following the guide [here](https://legacy-guides.solidus.io/developers/products-and-variants/product-images.html#paperclip-settings). - Upload new sample images [#3270](https://github.com/solidusio/solidus/pull/3270) ([mfrecchiami](https://github.com/mfrecchiami)) - Remove unused sample images [#3397](https://github.com/solidusio/solidus/pull/3397) ([JDutil](https://github.com/JDutil)) - Update sample imgs with wrong file extension [#3343](https://github.com/solidusio/solidus/pull/3343) ([mfrecchiami](https://github.com/mfrecchiami)) #### State machines extracted into their own replaceable modules This allows stores to replace the state machine completely with their own implementation, even with different gems or using custom code without any state machine gem. All the customizations previously made to the state machine should work smoothly, but it could be a good idea to check twice. You can read more about the suggested way to customize the state machine [here](https://legacy-guides.solidus.io/developers/customizations/state-machines.html#state-machines). - Extract the state machines into replaceable modules [#3356](https://github.com/solidusio/solidus/pull/3356) ([cedum](https://github.com/cedum)) #### Display error if editing non-current order In Solidus frontend users were able to input any `order_id` in the `/orders/:order_id/edit` route and they were simply seeing the cart (showing the current order and not the requested one) without any notice. With this Solidus version we print an flash message and redirect users to their cart. - Display error if editing non-current order [#3391](https://github.com/solidusio/solidus/pull/3391) ([JDutil](https://github.com/JDutil)) #### Solidus now requires Ruby 2.4 or newer Ruby 2.2 and 2.3 support has ended, Rubocop support for 2.2 ended and they are also about to drop 2.3. Also, we already introduced code that is not compliant with 2.2 anymore. - Bump required ruby version to 2.4 [#3337](https://github.com/solidusio/solidus/pull/3337) ([kennyadsl](https://github.com/kennyadsl))

Hey there! We just wanted to update you about the current state of Design in the Solidus ecosystem and give you a little preview about its future. ## Rebranded Admin  As you may have already noticed, in version [2.9](/blog/solidus-v2-9) we finally updated the color palette of the Admin UI to a brand new one, which has already been in use on the solidus.io website for a while. This change comes from the aim to consolidate the Solidus brand and stand out from the competition. Another great new change is using Inter as default typeface on the admin. [Inter](https://rsms.me/inter/) is an Open Font similar to Roboto and Apple’s San Francisco, which was designed for user interfaces with focus on high legibility. ## Collapsing Sidebar  This long-overdue feature changed hands in its implementation over these years. Finally, thanks to the work of more than one contributor ([#3322](https://github.com/solidusio/solidus/pull/3322), [#2961](https://github.com/solidusio/solidus/issues/2961), [#666](https://github.com/solidusio/solidus/issues/666), [#2957](https://github.com/solidusio/solidus/pull/2957), [#1718](https://github.com/solidusio/solidus/pull/1718)), we can easily minimize the admin sidebar navigation and recover some lost screen real estate. This is the first step in achieving a more responsive and modern UI in Solidus. ## Solidus Brand We released a [public repository](https://github.com/solidusio/brand) with all the Solidus brand assets, so if you need to use the Solidus logo, please use those official resources. We plan to publish those brand assets, along with a revamped style guide, also on the official project website. Stay tuned! ## What's next? The next step is to follow the upcoming official roadmap, making design decisions based on a shared purpose and qualitative and quantitative data.

As with all open source projects, the heart and soul of Solidus lie in its community. Over the years, hundreds of people have contributed to Solidus to turn it into the best eCommerce platform for custom stores, and we are honored for having the opportunity to work with such outstanding professionals every day. It is our responsibility to ensure Solidus continues to be an amazing and collaborative space for developers and eCommerce experts from all over the world, which is why we are proud to present the first version of our [Community Guidelines](https://guides.solidus.io/). We want everybody to feel welcome and free to contribute to Solidus and participate in its community, no matter their identity or beliefs, and we can only do that by having the proper tools and processes in place. At this time, the Community Committee, responsible for enforcing the Guidelines, is made up by Jacob Herrington, Peter Berkenbosch and Alessandro Desantis. Feel free to reach out to them on Slack if you have any questions or feedback! We hope that the Guidelines will encourage even more people to contribute to Solidus and be a part of our community. We look forward to seeing you!

We’re proud to announce that YOU could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Ryan Cromwell could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Thomas Sample could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Branden Douglas could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Peter Berkenbosh could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Joel Saupe could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Taylor Scott could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Ernesto Tagwerker could be joining us as a speaker for SolidusConf 2019.

We’re proud to announce that Sean Denny will be joining us as a speaker for SolidusConf 2019.