browsercms 3.5.7 → 4.0.0.alpha

data/db/migrate/20130327184912_browsercms400.rb

@@ -0,0 +1,90 @@
+class Browsercms400 < ActiveRecord::Migration
+
+  def up
+    apply_cms_namespace_to_all_core_tables
+
+    add_column :cms_section_nodes, :slug, :string
+    add_content_column :cms_dynamic_views, :path, :string
+    add_content_column :cms_dynamic_views, :locale, :string, default: 'en'
+    add_content_column :cms_dynamic_views, :partial, :boolean, default: false
+
+    Cms::PageTemplate.all.find_each do |pt|
+      pt.path = "layout/templates/#{pt.name}"
+      pt.locale = "en"
+      pt.save!
+    end
+
+    Cms::PagePartial.all.find_each do |pp|
+      pp.path = "partials/#{pp.name}"
+      pp.locale = "en"
+      pp.partial = true
+      pp.save!
+    end
+
+    drop_table :cms_content_type_groups
+    drop_table :cms_content_types
+
+    create_content_table :cms_forms do |t|
+      t.string :name
+      t.text :description
+      t.string :confirmation_behavior
+      t.text :confirmation_text
+      t.string :confirmation_redirect
+      t.string :notification_email
+    end
+
+    create_table :cms_form_fields do |t|
+      t.integer :form_id
+      t.string :label
+      t.string :name
+      t.string :field_type
+      t.boolean :required
+      t.integer :position
+      t.text :instructions
+      t.text :default_value
+      t.text :choices
+      t.timestamps
+    end
+
+    # Field names should be unique per form
+    add_index :cms_form_fields, [:form_id, :name], :unique => true
+
+    create_table :cms_form_entries do |t|
+      t.text :data_columns
+      t.integer :form_id
+      t.timestamps
+    end
+
+  end
+
+  private
+
+  # In 4.x, all core tables MUST start with cms_. See https://github.com/browsermedia/browsercms/issues/639
+  def apply_cms_namespace_to_all_core_tables
+    unversioned_tables.each do |table_name|
+      if (needs_namespacing(table_name))
+        rename_table table_name, cms_(table_name)
+      end
+    end
+
+    versioned_tables.each do |table_name|
+      if (needs_namespacing(table_name))
+        rename_table table_name, cms_(table_name)
+        rename_table versioned_(table_name), cms_(versioned_(table_name))
+      end
+    end
+  end
+
+  # All tables that aren't versioned. (I.e. two tables)
+  def unversioned_tables
+    [:categories, :category_types, :connectors, :content_types, :content_type_groups, :email_messages, :group_permissions, :group_sections, :group_type_permissions, :group_types, :groups, :page_route_options, :page_routes, :permissions, :portlet_attributes, :portlets, :redirects, :section_nodes, :sections, :sites, :taggings, :tags, :tasks, :user_group_memberships, :users]
+  end
+
+  def versioned_tables
+    [:attachments, :dynamic_views, :file_blocks, :html_blocks, :links, :pages]
+  end
+
+  def needs_namespacing(table_name)
+    table_exists?(table_name) && !table_exists?(cms_(table_name))
+  end
+end

data/db/migrate/20131206214021_devise_create_users.rb

@@ -0,0 +1,47 @@
+class DeviseCreateUsers < ActiveRecord::Migration
+  def change
+    change_table(:cms_users) do |t|
+      ## Database authenticatable
+      #t.string :email,              :null => false, :default => ""
+      t.string :encrypted_password, :null => false, :default => ""
+
+      ## Recoverable
+      t.rename   :reset_token, :reset_password_token
+      t.datetime :reset_password_sent_at
+
+      ## Rememberable
+      t.rename :remember_token_expires_at, :remember_created_at
+      t.remove :remember_token # Not needed by devise.
+
+      # Remove old SHA based encrypted passwords.
+      # Comment out the following line if you have a strong need to preserve old hashed passwords
+      t.remove :crypted_password
+
+      ## Trackable
+      #t.integer  :sign_in_count, :default => 0, :null => false
+      #t.datetime :current_sign_in_at
+      #t.datetime :last_sign_in_at
+      #t.string   :current_sign_in_ip
+      #t.string   :last_sign_in_ip
+
+      ## Confirmable
+      # t.string   :confirmation_token
+      # t.datetime :confirmed_at
+      # t.datetime :confirmation_sent_at
+      # t.string   :unconfirmed_email # Only if using reconfirmable
+
+      ## Lockable
+      # t.integer  :failed_attempts, :default => 0, :null => false # Only if lock strategy is :failed_attempts
+      # t.string   :unlock_token # Only if unlock strategy is :email or :both
+      # t.datetime :locked_at
+
+
+      #t.timestamps
+    end
+
+    add_index :cms_users, :email,                :unique => true
+    add_index :cms_users, :reset_password_token, :unique => true
+    # add_index :users, :confirmation_token,   :unique => true
+    # add_index :users, :unlock_token,         :unique => true
+  end
+end

data/db/migrate/20131211223908_kill_reset_password.rb

@@ -0,0 +1,5 @@
+class KillResetPassword < ActiveRecord::Migration
+  def up
+    Cms::Portlet.connection.execute("UPDATE cms_portlets SET type = 'DeprecatedPlaceholder' WHERE type = 'ResetPasswordPortlet'")
+  end
+end

data/db/migrate/20131218222005_create_cms_external_users.rb

@@ -0,0 +1,10 @@
+class CreateCmsExternalUsers < ActiveRecord::Migration
+  def change
+    change_table :cms_users do |t|
+      t.column :type, :string, default: 'Cms::User'
+      t.column :source, :string
+      t.text :external_data
+    end
+
+  end
+end

data/doc/features/design_integration.md

@@ -0,0 +1,45 @@
+# Design Integration
+
+This covers some of the remaining design issues that we need to resolve before the beta/final 4.0 release.
+
+## [Ask Kyle]
+
+* Fonts for Dashboard table headers/menus are just less bold than in design.
+* Icons for:
+    - Edit button (Pencil) for content
+    - Links
+    - Portlets - Should use 'list' icon
+    - Other Content Types (Product, Catalog, Generic Document) - Ideas: Book? Newspaper? Full page?
+    - Visual Indicator for a section/page can't be edited. (Currently just removing the buttons)
+    - Up and down sorting icons (caret is always down)
+* Need style for Checkbox groups that are labeled. See Add User.
+* Tables that are too wide (/cms/routes)
+* JQuery Date picker - Has no styling.
+* Styling for CKEditor 'selector'.
+* Need help styling 'path' element.
+* Errors - Review the placement of errors on the form.
+* Products
+    - Photo 2 is wrapping unnecessarily (Does it without photo 1)
+    - Slug path needs styling.
+
+## IA Questions
+
+* What Label for first element under Assets? (Assets? Asset library). Or just make Text first.
+* Selecting a section always toggles. Might want to select an open section to add content to it, but not close it.
+* Where should "Settings" link take user to.
+
+## Implied Features by Design
+
+Features in the original design/IA that didn't get implemented.
+
+* Make 'Assign' on Edit page work.
+* Sitemap filters
+* Sitemap Hide/Archive/Publish
+* Dashboard Activity / My and All
+* [Assets] Filter by publish/notpublished
+* [Assets] Infinite scrolling
+
+
+
+
+

data/doc/features/external_user.md

@@ -0,0 +1,7 @@
+# [#644] External User
+
+Support a built in way to authenticate external users and store their information in the database. These users could be from any system (CRM, AMS, Facebook) and they would be authenticated using credentials from those services. Each external user would be given a record in the user table and would be marked as an external user.
+
+* Permission: Groups would be dynamically assigned on login and recorded as an association with that user until they reauthentice.
+* External Data: Third Party APIs often provide extra information. Provide an easy way to store this information on the user record without needing new columns.
+* Subclasses: Projects/Engines should be able to subclass ExternalUser to provide additional behavior.

data/doc/features/form_builder.md

@@ -0,0 +1,40 @@
+# Form Builder
+
+Allow content editors to create new form via the interface.
+
+## Remain issues/features
+
+* [MINOR] Unique icon for forms (i.e. custom) for sitemap
+* [Improvement] Captcha?
+* [FEATURE] Allow sorting/reporting.
+* [BUG] Preview for dropdowns is inaccurate (doesn't change after updates). To fix, would need to refactor to have HTML returned rather than JSON.
+* [BUG] 500 errors when posting forms within CMS shows errors within double nested toolbar.
+* [Improvement] Default Forms just uses bootstrap, which is probably not a valid option. Need a way to pare it down to avoid changing styles for existing designes.
+* [BUG] After adding a field, it clears but does not correctly show the 'blank' value.
+* [BUG] Addressable content types (product, forms, etc) do not/cannot appear in menus without manually creating a link.
+
+## Documentation
+
+## Forms
+
+* Can notify staff when a form is submitted.
+* Email mailbot can be configured in application.rb
+
+### Configuration
+
+In config/application.rb, to change which CSS stylesheet is applied to Form pages, update the following:
+
+```
+ # Default is 'cms/default-forms'
+ config.cms.form_builder_css = 'my-forms' # Returns /assets/my-forms.css
+```
+
+# New Namespacing
+
+When upgrading, Content Models should be moved under application namespace. Basis steps:
+
+    Custom models should have the following added to them:
+        Create a directory in the project named app/models/cms
+        Move any Content Blocks into that directory.
+        Rename from Widget to *Cms::*Widget
+        Add self.table_name = :widgets (or migrate the table from widgets to cms_widgets)

data/doc/features/simple_form_refactor.md

@@ -0,0 +1,60 @@
+[#623] Refactor CMS forms to use SimpleForm
+
+Converted all the internal forms to use SimpleForm rather than our own custom form builder. This provides better consistency with bootstrap forms, as well as well tested API for defining new form inputs. This will primarily affect developers when they create content blocks. New content will be generated using simple_form syntax like so:
+
+<%= f.input :photo, as: :file_picker %>
+
+rather than the older syntax that looks like this:
+
+<%= f.cms_file_field :photo %>
+
+The old form_builder methods like cms_text_field and cms_file_field have been deprecated and will generate warnings when used. These methods are scheduled for removal in BrowserCMS 4.1. It's recommended that custom content blocks be upgraded to use the new syntax when feasible. The deprecation warnings should provide some guideance, but also look at simple_forms documentation http://simple-form.plataformatec.com.br for help.
+
+## Available Input Types
+
+All of the existing simple_form input mappings are available. See http://simple-form.plataformatec.com.br/#mappings-inputs-available for the reference. BrowserCMS adds some additional input types for specific CMS features.
+
+|# Mapping | Input | Purpose/column type #|
+| file_picker | File Upload | A single attachment with section/path selectors |
+| cms_text_area | text area | Like :text but with a :default |
+| cms_text_field | text field | Like :string with optional path generator (for addressable content types)|
+| date_picker | jquery date select | date   |
+| path | text field | A slug/path for addressable content (works with cms_text_field to automatically generate names)   |
+| template_editor | text area | For editing templates via ERB or other permitted template languages. |
+| text_editor | WYSIWYG editor | For editing HTML content (has toggle to use a text area |
+| attachments | Multiple File Uploads | Unlimited # of attachments. |
+| tag_list| text field | has_many with :tags |
+
+### Usage
+
+Here are some examples showing how to use the CMS specific inputs.
+
+```
+<%= f.input :name, as: :cms_text_field, default: "Some Value" %>
+```
+
+Generates the 'name' field, and a :path input if the content block is addressable. Can supply a default value that will be used when creating a new record.
+
+```
+<%= f.input :expires_on, as: :date_picker %>
+```
+
+Renders a text_field that can be left blank or have a date entered into it as text. Clicking on it will bring up a JQuery Date Picker to select the date.
+
+```
+<%= f.input :template, as: :template_editor %>
+```
+
+Renders a template editor (if the content block has enabled template editing). The default template body for the model will be used when creating a new record.
+
+
+### Usage Exceptions
+
+Several of the input types above are not used directly, but rather via methods like this that hide some of their complexity:
+
+```
+<%= f.cms_attachment_manager %>
+<%= f.cms_tag_list %>
+```
+
+

data/doc/release_notes.md

@@ -1,17 +1,231 @@
-v3.5.5
+# v4.0
+
+
+## Major Features
+
+This release includes the following major features:
+
+* User Interface Redesign - User interface has been complete redesigned from the ground up. The new UI is based on Twitter Bootstrap, has usability enhancements as well as an improved design.
+* True In Context Editing [#566] - Editors can directly edit Html content and page titles using CKEditor's inline capability.
+* Rails 4 Upgrade [#617] - BrowserCMS is now designed to work with Rail 4.0.
+* Ruby 2.0 [#651] - BrowserCMS is now designed to work with Ruby 2, matching the recommended specs for Rails 4. Ruby 1.9.3 and 1.9.2 may still work.
+* Form Builder [#124] - Allow editors to create form pages that can be used to collect information from visitors
+* Addressable Content [#588] - Custom content blocks (i.e. Product, Event, News Articles) can be created directly as pages in the sitemap.
+* Improved Template Storage [#608] - Database managed templates are no longer written out to the file system. Sites should have less permission related issued during deployments. Using Heroku to host sites should be easier as well.
+* Devise Integration [#641] - Devise is now used as standard authentication tool. Upgrading projects will have passwords reset (See upgrade notes for more details).
+* External Users [#644] - Better support for authenticating/authorizing users from external data sources rather than using additional solutions like CAS.
+
+## Other Features/Improvements
+
+In addition to the other major features above, here are some improvements/features of note.
+
+* Portlet Descriptions [#619] - Portlets can now have a description that will be used to provide additional context when users are building/placing them.
+* No need to register Content Types [#621] - Content Blocks will automatically appear in the menus without needing to add them to the database.
+* Using SimpleForm [#623] Reworked all forms to use simple_form (https://github.com/plataformatec/simple_form).
+* Migration Cleanup [#594] Migrations for previous versions have been compressed. This has implications for upgrading, but should make new project cleaner.
+* Consistent table prefixes [#639] All core cms tables will now start with cms_ rather than being configurable.
+* Content Blacklisting - Portlets can be blacklisted via configuration so that they can't be created. Several previously stock types are blacklisted.
+* Refined Content API [#256] [#582][#584] - Make content blocks closer in behavior to ActiveRecord.
+
+## UI Redesign
+
+The entire UI has been reworked to be more streamlined and lightweight. It is now built using Twitter Bootstrap, and makes better use of global menus and toolbars. Here are the notable changes.
+
+1. Global Menu - Many commons functions can now be invoked directly from the main menu, including adding new content or users.
+1. Smart 'New' button - Users can add content from any page in the CMS. The "New" button is a split button that can either add a specific type of content, or will 'guess' based on where a user is in the site.
+1. Sitemap - Each row now has hover buttons to edit/remove content rather than needing to select a row then click a button menu.
+1. Assets/Asset Library - The content library has been renamed to be called assets.
+
+## In Context Editing
+
+Users can now edit most HTML content directly in the page. Icons indicate the area of the pages that are editable. Here are some of the highlights:
+
+1. No need to toggle the editor on/off. Just click the area of the page you want to edit.
+1. Full Edit - Click to edit in full text editor. Any changes made will be saved before going to the full editor. There is also a edit button on each block in the upper right hand corner.
+1. Remove blocks from page - Editors can select a block then remove it from the page via a button on the editor. Users will be prompted before its removed.
+1. Reorder content - Can move content blocks up or down within a page. Page will refresh after moving.
+1. Editable Page titles - Page title can be edited directly from the header.
+1. Preview Page - Editors can now preview the page without a toolbar or editing controls.
+1. Non-incontext Content - Not all content makes sense to be inline editable (for example portlets). For these content types, the previous move/remove/edit links now float in the upper right hand corner of the content block.
+
+## Addressable Content Blocks
+
+Content blocks can created with as their own pages. To make a block addressable, a developer must do the following:
+
+1. Add is_addressable to the model. This will automatically generate a :slug form field when creating/editing instances.
+2. Set the Page Template that should be used (defaults to 'default').
+
+```
+class Product < ActiveRecord::Base
+  is_addressable path: "/products", template: "product"
+end
+```
+
+3. Add the following field to the _form.html.erb.
+
+```
+<%= f.input :slug, as: :path %>
+```
+
+## Form Builder
+
+Allow editors to create form pages that can be used to collect information from visitors (i.e. Contact Us, Support requests, etc). Basically, any quick collect a few fields using a consistent form styling.
+
+### Features include:
+
+1. Forms can have multiple fields which can be text fields, textareas or multiple choice dropdowns. Field management is done via AJAX and fields can be added/reordered/removed without leaving the page.
+2. Fields can be required, have instructions and default values. Choices are added as lines of text for each dropdown field. Dropdowns use the first value as the default.
+3. Entries are stored in the database and can optionally notify someone via email when new submissions are created.
+4. Editors can manage entries via the admin (CRUD)
+5. Visitors can be redirected to another URL after submitting their entry or display a customizable 'success' message.
+6. Forms generate the HTML display using bootstrap's CSS by default. Projects can customize this in the application.rb with config.cms.form_builder_css
+
+## Refined Content API
+
+1. .save now works identically between ActiveRecord and Content Blocks
+
+Previously, calling .save on a block would save a draft copy, rather then updating the record in place. This has been changed. To save a draft, you can do either:
+
+    @block.publish_on_save
+    @block.save
+    # or
+    @block.save_draft
+
+
+## Registering Content Types
+
+Content blocks no longer need to have a separate registration in the database to appear in menus.
+
+Defining a new content model should be sufficient to have it appear in the content library. To specify which module it should appear in, you can configure it like so:
+
+class Widget < ActiveRecord::Base
+  acts_as_content_block
+  content_module :acme
+end
+
+The content_types and content_type_groups tables have been removed as they are no longer necessary. If you don't want a block to appear in the menus, you can specify this via:
+
+class Widget < ActiveRecord::Base
+  acts_as_content_block content_module: false
+end
+
+## Refactor to use SimpleForm
+
+Converted all the internal forms to use SimpleForm rather than our own custom form builder. This provides better consistency with bootstrap forms, as well as well tested API for defining new form inputs. This will primarily affect developers when they create content blocks. New content will be generated using simple_form syntax like so:
+
+```
+<%= f.input :photo, as: :file_picker %>
+```
+
+rather than the older syntax that looks like this:
+
+```
+<%= f.cms_file_field :photo %>
+```
+
+The old form_builder methods like cms_text_field and cms_file_field have been deprecated and will generate warnings when used. These methods are scheduled for removal in BrowserCMS 4.1. It's recommended that custom content blocks be upgraded to use the new syntax when feasible. The deprecation warnings should provide some guideance, but also look at simple_forms documentation http://simple-form.plataformatec.com.br for help.
+
+## Portlet Blacklists
+
+Portlets can be blacklisted so that new instances cannot be created. This can be used to turn off some portlets for security, convience or otherwise. By default, the following portlet types are blacklisted (as 'deprecated').
+
+* LoginPortlet (:login_portlet)
+* DynamicPortlet (:dynamic_portlet)
+* ForgotPasswordPortlet (:forgot_password_portlet)
+
+### Modifying the blacklist
+
+```
+# Prevention creation
+config.cms.content_types.blacklist += [:email_page_portlet]
+
+# Allowing creation
+config.cms.content_types.blacklist -= [:login_portlet]
+```
+
+## Devise Integration
+
+Devise is now the standard authentication mechanism for BrowserCMS. This adds some new (and improved) authentication features including:
+
+* Reset Password - Admin users have a link to reset passwords.
+* Strong Password storage - Passwords are now encrypted using bcrypt which is a safer method (http://codahale.com/how-to-safely-store-a-password/)
+* Remember Me - Allows users to stay logged in for up to two weeks.
+* Devise/Warden APIs - Developers can use Devise and/or Warden's APIs to customize how authenication works. The previous RESTful Authentication based solution was not really pluggable.
+
+### [Warning] Upgrading/Password Reset
+
+Upgrading to 4.0 means all user passwords will need to be reset. This doesn't apply where external user databases are used (i.e. CAS) for authentication. Just user accounts stored in the CMS itself.
+
+This reset is a side effect of using a more secure password encryption algorithm (bcrypt). When users try to log in, they will have to request a password reset. This feature is provided on /cms/login as a standard feature. Users will need to provide an email, and a link for reseting their password will be sent to them. Alternatively, developers may choose to change passwords via the admin interface (or rails console) before turning over sites to the site maintainers.
+
+### Avoiding a reset
+
+For most sites, the number of admin users is likely limited and part of a cohesive team. So forcing a reset shouldn't be an issue. In the case of sites that have large user databases, a migration strategy to mass update or possibly creating a new Warden/Devise strategy based on the 3.5.x encryption strategy. These two are coding exercises left to the developers working on the project.
+
+For sites that need to keep a record of the old encrypted passwords, remove/comment out the following line from the browsercms400 migration which will preserve the old encrypted passwords.
+
+```
+t.remove :crypted_password
+```
+
+Note that preserving the old password data is just the first step. The new encryption strategy will still be used unless modifications are made to the project.
+
+### Forgot Password
+
+Users can reset their password via the admin UI. On /cms/login, a link to 'Forgot Password' is available. Users can enter an email and have the reset link mailed to them.
+
+Configuration: For Forgot Password to work, need to ensure the following is present for mailer in BrowserCMS setups.
+    * config.action_mailer.default_url_options = { :host => "yourhost" }
+
+The core 'ForgotPassword' portlet has been reworked and is probably 100% unnecessary on most sites. It is now blacklisted by default. The portlet now just renders the stock /forgot-password view and isn't editable. Use /forgot-password instead.
+
+## External User API [#644]
+
+There is now a core API for handling users that are authenticated/authorized against external data sources. There is a new class (Cms::ExternalUser) which represents a user which has been authenticated using some source other than the Core CMS. This user can have extra information retained as attribute and can be authorized to be part of a specific group(s).
+
+A sample implementation of an authentication strategy can be found in lib/cms/authentication/test_password_strategy. Strategies are implemented as Devise Strategies and should either login or pass to the next strategy.
+
+This implementation is intended to replace CAS based strategies used in BrowserCMS 3.x. It provides the ability to style the login page directly, and avoid having an external CAS server software.
+
+## Upgrading
+
+1. Editable Page Titles: In order to take advantage of the editable pages titles, templates need to use the new Template API Method: page_header(). Used rather that <%= page_title %> within h1/h2 etc, this will output an editable page title element for logging in users.
+2. match -> get: Update your config/routes.rb to change any use of 'match' to get or post for your controller.
+3. Install the deprecated finders and other gems to help with upgrade. Once you get rid of the deprecation warnings you can remove the gem.
+4. Content Types - If you have defined content blocks in custom group names, you should edit them to specify the module name. See 'Registering Content Types' above for details. You can delete any seeds that create content types. There will be a deprecation warning if you call save! or create! on ContentTypes.
+5. Forms - Rework existing form fields in content blocks to use SimpleForm.
+6. Table Prefixing - In config/initializers/browsercms.rb remove the `Cms.table_prefix = 'cms_' line, which generated deprecation warnings.
+7. Password Reset - Users will need to reset their password after the upgrade. See Devise Integration/Avoiding a reset if this is concern.
+8. Forgot Password - Consider removing any existing ForgotPassword portlets and just use /forgot-password controller.  Creation is disabled by default.
+9. Reset Password Portlet - These have been removed as they were no longer necessary. Any remaining instances have been converted to 'DeprecatedPlaceholders'. Find and remove these portlets (and the page they were on) from your site.
+10. Login Portlet - Consider removing these and using the built in /login route. Creation is disabled by default.
+
+### Migration Cleanup
+
+Projects using versions older than 3.5.4 must first upgrade to the latest 3.5.x version. This is because we have compressed the migrations from 3.0.0 up to 4.0.0 into a single migration (browsercms300). Migrations, especially those that alter data get hard to maintain over time. And new projects don't care when they start with fresh data.
+
+After migrating your production environment to 3.5.7 do the following:
+
+1. Record the timestamp for the existing 3_0_0 migration (i.e. 20080815014337).
+2. Delete all the BrowserCMS migrations (3_0_0, 314, etc) from the project.
+3. Add the migrations for 4.0.0.
+4. Change the name of the new browsercms300 migration so it matches the old timestamp of browsercms3_0_0. This will prevent the new migration from running.
+
+
+## Deprecations
+
+* page_title("Some Name") is deprecated in favor of use_page_title("Some Name") for overriding a page title. This will be remove in 4.1. This probably will probably only effect changes make in modules or customizations to the core.
+
+v3.5.6
 ======
 
-Community contributed bug fixes, including making it easier to start contributing to the project.
+* [#591] Error pages do not render mobile templates
+
+v3.5.5
+======
 
-* [#561] Fix invalid code in generated production.rb file (Thanks RoopeHakulinen)
-* [#557] Fix extra column on blocks index page (Thanks metalon)
-* [#543] Allow cms_file_field to use default label (Thanks josiahivey)
-* [#563] Continuous Integration - Get Travis CI up and working for the project.
-* [#539] Fix missing assets on CMS Login page (Thanks korin)
-* [#537] Better support core contributions by removing database.yml from checkin. Run `rake project:setup[mysql]` to create a database.yml for your local database. (Thanks josiahivey)
-* [#564] Update to Rails 3.2.12 - Ensure tests to pass (there appeared to be some changes in inflection and html_safe between 3.2.5 and 3.2.8)
+* Update to Rails 3.2.8 - Ensure tests to pass (there appeared to be some changes in inflection and html_safe between 3.2.5 and 3.2.8)
 
-See https://github.com/browsermedia/browsercms/issues?milestone=18&page=1&state=closed for more details.
 
 v3.5.4
 ======