Sharetribe versions 5.12.0 is now available!

Announcements
1

[5.12.0] - 2016-09-27

Added

  • Added date picker for “per night” listing unit type #2481
  • SEO: Added rel=next and rel=prev links to give a hint to crawlers about the paginated content #2505
  • Added New layout admin page where marketplace admins can enable new layout designs for the whole marketplace or just for themselves to try out #2338 and #2469
  • Added functionality to edit Post a new listing button text #2448
  • Sitemap #2492, thanks Dan Moore (@mooreds) for helping!
  • Mocha test setup for new frontend architecture #2550

Deprecated

  • Deprecated use of MySQL server version 5.6.x 2566

Removed

  • Removed configuration for TravisCI (CircleCI now fully in use) #2489

Changed

  • Updated React on Rails to 6.0.5 #2428 and #2472
  • Updated React Storybook to version 2.13.0 #2528
  • Changed ActiveRecord schema format to :sql #2531
  • Upgraded Paperclip and Delayed::Paperclip, dropped deprecated AWS SDK v1 #2522
  • Upgraded mysql2 dependency #2565

Fixed

  • Correctly add https or http to links generated in community.rb #2459
  • Transactions in initiated state showed wrong total price in the transaction page if the item quantity was more than one #2452
  • Fix bug in infinite scroll: The current page was not taken into account #2532
  • Fix bug: Testimonial reminders were sent even if user had disabled them #2557
  • Fix regression: Add quantity pickers to non-payment transactions #2568

Upgrade from 5.11.0 to 5.12.0

IMPORTANT: This release deprecates use of MySQL server version 5.6.x. Please, consider upgrading to MySQL 5.7. Support for MySQL 5.6 will be dropped with the next release of Sharetribe. From this point onward, versions other than 5.7 might work, but are not guaranteed to work with Sharetribe. Make sure to back up your database before upgrading MySQL server. For general upgrade instructions, see the official MySQL upgrade instructions.

If you are using S3 and are using an AWS region other than us-east-1, you need to update your config.yml file and set the s3_region configuration option to the AWS region you are using. As with all configuration options, you can also pass it as an environment variable.

1 Like