parndt · December 19, 2015 18:28 · Jul 15, 2013 · Jul 15, 2013 · Jul 15, 2013 · Jul 15, 2013
diff --git a/gistfile1.textile b/gistfile1.textile
@@ -4,7 +4,7 @@ This guide will guide you through the upgrade process from version 2.0.10 to ver
 
 endprologue.
 
-WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend for you to upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.
+WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend that you upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.
 
 WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.
 
@@ -18,11 +18,11 @@ After you complete the steps above your Gemfile should look like this:
 gem "refinerycms", "~> 2.1.0"
 </ruby>
 
-Now run +bundle install+ and let it install new gems.
+Now run +bundle update+ and let it install new gems.
 
 h3. Running Refinery's CMS generator
 
-WARNING: If the application you will be upgrading is using SQLite database then you need to read +Refinery's CMS generator and SQLite database+.
+WARNING: If the application you will be upgrading is using a SQLite database then you need to read +Refinery's CMS generator and SQLite database+.
 
 Go to the terminal and run following command:
 
@@ -32,35 +32,34 @@ rails generate refinery:cms
 
 This command will do a couple of things:
 
-* Add two css requires in +application.css+
-* Update +app/views/sitemap/index.xml.builder+ template
-* Wrap  +config.action_mailer+ config in +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+
-
-* Copy new migrations
-* Run +rake db:migrate+ and +rake db:seed+ commands
+* Add two css requires in +application.css+.
+* Update +app/views/sitemap/index.xml.builder+ template.
+* Wrap  +config.action_mailer+ config entry in a conditional +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+.
+* Copy new migrations.
+* Run +rake db:migrate+ and +rake db:seed+ commands.
 
 NOTE: If you don't want the generator to run +rake db:migrate+ and +rake db:seed+ commands pass the +--skip_db+ option when invoking the generator:
 
 <shell>
 rails generate refinery:cms --skip_db
 </shell>
 
-h3. Refinery's CMS generator and SQLite database
+h3. Refinery's CMS generator with a SQLite database
 
 INFO. Because SQLite can only handle index names that are no longer than 64 characters you will have to edit one of the migrations that will be generated when you run the following command in the terminal:
 
 <shell>
 rails generate refinery:cms --skip_db
 </shell>
 
-Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "this gist":https://gist.github.com/ugisozols/5998256
+Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "Uģis' gist":https://gist.github.com/ugisozols/5998256.
 
-It will check if +seo_meta+ tables has and index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:
+What this will do is check if the +seo_meta+ table has an index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:
 
-* Remove current index named +seo_meta_id_and_seo_meta_type+
-* Remove +meta_keywords+ column
-* Add original index but with a shorter name
+* Remove the current index named +seo_meta_id_and_seo_meta_type+.
+* Remove the +meta_keywords+ column.
+* Add back the original index but with a shorter name.
 
 Now run +rake db:migrate+.
 
-h3. Profit!
+h3. Profit!
diff --git a/gistfile1.textile b/gistfile1.textile
@@ -4,7 +4,6 @@ This guide will guide you through the upgrade process from version 2.0.10 to ver
 
 endprologue.
 
-
 WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend for you to upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.
 
 WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.
@@ -23,6 +22,8 @@ Now run +bundle install+ and let it install new gems.
 
 h3. Running Refinery's CMS generator
 
+WARNING: If the application you will be upgrading is using SQLite database then you need to read +Refinery's CMS generator and SQLite database+.
+
 Go to the terminal and run following command:
 
 <shell>
@@ -44,4 +45,22 @@ NOTE: If you don't want the generator to run +rake db:migrate+ and +rake db:seed
 rails generate refinery:cms --skip_db
 </shell>
 
-h3. Profit!
+h3. Refinery's CMS generator and SQLite database
+
+INFO. Because SQLite can only handle index names that are no longer than 64 characters you will have to edit one of the migrations that will be generated when you run the following command in the terminal:
+
+<shell>
+rails generate refinery:cms --skip_db
+</shell>
+
+Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "this gist":https://gist.github.com/ugisozols/5998256
+
+It will check if +seo_meta+ tables has and index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:
+
+* Remove current index named +seo_meta_id_and_seo_meta_type+
+* Remove +meta_keywords+ column
+* Add original index but with a shorter name
+
+Now run +rake db:migrate+.
+
+h3. Profit!
diff --git a/gistfile1.textile b/gistfile1.textile
@@ -11,20 +11,17 @@ WARNING. Before continuing make sure you have a backup copy of your application
 
 h3. Updating gems
 
-Open up Gemfile and change version of +refinerycms+ gem entry from +2.0.10+ to +2.1.0+. Do the same thing for +refinerycms-i18n+ gem entry.
-
-NOTE: If you don't have a +refinerycms-i18n+ gem entry in your Gemfile then you need to add it because in Refinery CMS 2.1.0 we made it a hard dependency for +refinerycms-core+ gem (which is a part of +refinerycms+ gem itself).
+Open up your application's Gemfile and change the version of the +refinerycms+ gem entry from +2.0.10+ to +2.1.0+.
 
 After you complete the steps above your Gemfile should look like this:
 
 <ruby>
-gem "refinerycms", "2.1.0"
-gem "refinerycms-i18n", "2.1.0"
+gem "refinerycms", "~> 2.1.0"
 </ruby>
 
 Now run +bundle install+ and let it install new gems.
 
-h3. Running refinery:cms generator
+h3. Running Refinery's CMS generator
 
 Go to the terminal and run following command:
 
@@ -34,14 +31,14 @@ rails generate refinery:cms
 
 This command will do a couple of things:
 
-* add two css requires in +application.css+
-* update +app/views/sitemap/index.xml.builder+ template
-* wrap  +config.action_mailer+ config in +if config.respond_to?(:action_mailer)+ clause for each environment files located in +app/config/environments+
+* Add two css requires in +application.css+
+* Update +app/views/sitemap/index.xml.builder+ template
+* Wrap  +config.action_mailer+ config in +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+
 
-* copy new migrations
-* run +rake db:migrate+ and +rake db:seed+ commands
+* Copy new migrations
+* Run +rake db:migrate+ and +rake db:seed+ commands
 
-NOTE: If you don't want for this generator to run +rake db:migrate+ and +rake db:seed+ commands pass +--skip_db+ option when running generator command:
+NOTE: If you don't want the generator to run +rake db:migrate+ and +rake db:seed+ commands pass the +--skip_db+ option when invoking the generator:
 
 <shell>
 rails generate refinery:cms --skip_db

diff --git a/gistfile1.textile b/gistfile1.textile
@@ -0,0 +1,50 @@
+h2. Upgrading from version 2.0.10 to version 2.1.x
+
+This guide will guide you through the upgrade process from version 2.0.10 to version 2.1.x.
+
+endprologue.
+
+
+WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend for you to upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.
+
+WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.
+
+h3. Updating gems
+
+Open up Gemfile and change version of +refinerycms+ gem entry from +2.0.10+ to +2.1.0+. Do the same thing for +refinerycms-i18n+ gem entry.
+
+NOTE: If you don't have a +refinerycms-i18n+ gem entry in your Gemfile then you need to add it because in Refinery CMS 2.1.0 we made it a hard dependency for +refinerycms-core+ gem (which is a part of +refinerycms+ gem itself).
+
+After you complete the steps above your Gemfile should look like this:
+
+<ruby>
+gem "refinerycms", "2.1.0"
+gem "refinerycms-i18n", "2.1.0"
+</ruby>
+
+Now run +bundle install+ and let it install new gems.
+
+h3. Running refinery:cms generator
+
+Go to the terminal and run following command:
+
+<shell>
+rails generate refinery:cms
+</shell>
+
+This command will do a couple of things:
+
+* add two css requires in +application.css+
+* update +app/views/sitemap/index.xml.builder+ template
+* wrap  +config.action_mailer+ config in +if config.respond_to?(:action_mailer)+ clause for each environment files located in +app/config/environments+
+
+* copy new migrations
+* run +rake db:migrate+ and +rake db:seed+ commands
+
+NOTE: If you don't want for this generator to run +rake db:migrate+ and +rake db:seed+ commands pass +--skip_db+ option when running generator command:
+
+<shell>
+rails generate refinery:cms --skip_db
+</shell>
+
+h3. Profit!