NEW
Notice something different? Meet the new Solidus brand!

Version 1.2.0

JH

John Hawthorn

26 Jan 2016 - 3 mins read

Cover image of Version 1.2.0 post

github rubygems

Submitted for your consideration, Solidus 1.2.0

This is a minor release of Solidus, the most major change is the location of the admin navigation, which is now on the left. It also contains many bug fixes and improvements.

  • Admin menu has been moved from top of the page to the left side.

  • Submenu items are accessible from any page. See the wiki for more information and instructions on upgrading.

  • Solidus_auth_devise should be updated to '~> 1.3' to support the new menu.

  • Added optional styles to the admin area to advance admin rebrand. To use the new colors, add @import 'spree/backend/themes/blue_steel/globals/_variables_override'; to your spree/backend/globals/variables_override.

  • Added a style guide for html and css in the admin. Can be found at /admin/style_guide #602

  • Removed deface requirement from core

    Projects and extensions which rely on deface will need to add it explicitly to their dependencies.

  • testing_support/capybara_ext.rb no longer changes capybara's matching mode to :prefer_exact, and instead uses capybara's default, :smart.

    You can restore the old behaviour (not recommended) by adding Capybara.match = :prefer_exact to your spec_helper.rb.

    More information can be found in capybara's README

  • Fixed a bug where sorting in the admin would not save positions correctly. #632

  • Included (VAT-style) taxes, will be considered applicable if they are inside the default tax zone, rather than just when they are the defaut tax zone. #657

  • Update jQuery.payment to v1.3.2 (from 1.0) #608

  • Removed Order::CurrencyUpdater. #635

  • Removed Product#set_master_variant_defaults, which was unnecessary since master is build with is_master already true.

  • Improved performance of stock packaging #550 #565 #574

  • Replaced admin taxon management interface #569

  • Fix logic around raising InsufficientStock when creating shipments. #566

    Previously, InsufficientStock was raised if any StockLocations were fully out of inventory. This was incorrect because it was possible other stock locations could have fulfilled the inventory. This was also incorrect because the stock location could have some, but insufficient inventory, and not raise the exception (an incomplete package would be returned). Now the coordinator checks that the package is complete and raises InsufficientStock if it is incomplete for any reason.

  • Support sprockets-rails 3.0 and greater

Full list of changes