browsercms 3.4.2 → 3.5.0.rc1

data/config/database.postgres.yml

@@ -1,25 +0,0 @@
-development:
-  adapter: postgresql
-  database: browsercms_development
-  username: postgres
-  password: 
-
-# Warning: The database defined as 'test' will be erased and
-# re-generated from your development database when you run 'rake'.
-# Do not set this db to the same as development or production.
-test:
-  adapter: postgresql
-  database: browsercms_test
-  username: postgres
-  password: 
-
-production:
-  adapter: postgresql
-  database: browsercms_production
-  username: postgres
-  password: 
-
-
-test_sqlite3:
-  adapter: sqlite3
-  database: db/test.sqlite3

data/config/database.sqlite3.yml

@@ -1,11 +0,0 @@
-# Do not edit the database.yml file directory. BrowserCMS test suites run against multiple databases, so
-# make changes to the correct 'source' db file. In this case, edit: config/database.sqlite3.yml instead.
-development:
-  adapter: sqlite3
-  database: ":memory:"
-
-
-test:
-  adapter: sqlite3
-  database: "db/test.sqlite3"
-

data/config/environment.rb

@@ -1,6 +0,0 @@
-# Load the rails application
-require File.expand_path('../application', __FILE__)
-
-# Initialize the rails application
-Browsercms::Application.initialize!
-

data/config/initializers/query_reviewer_patch.rb

@@ -1,12 +0,0 @@
-# If we are using QueryReviewer, we need to patch it to avoid the sitemap blowing up.
-if defined?(QueryReviewer)
-
-  QueryReviewer::SqlQuery.class_eval do
-    # Hack to prevent nil pointer errors from occuring on pages when queryanalyzer is on.
-    def table
-      return @subqueries.first.table unless @subqueries.empty?
-      "fake_table"
-    end
-
-  end
-end

data/config/initializers/rack_1_2_1_patch.rb

@@ -1,12 +0,0 @@
-# TODO: Can be removed after updating to rack 1.3.0
-# Avoids this issue: http://stackoverflow.com/questions/3622394/ruby-1-9-2-strange-warning-when-running-cucumber-specs
-module Rack
-  module Utils
-    def escape(s)
-      CGI.escape(s.to_s)
-    end
-    def unescape(s)
-      CGI.unescape(s)
-    end
-  end
-end

data/config/locales/en.yml

@@ -1,5 +0,0 @@
-# Sample localization file for English. Add more files in this directory for other locales.
-# See http://github.com/svenfuchs/rails-i18n/tree/master/rails%2Flocale for starting points.
-
-en:
-  hello: "Hello world"

data/features/acts_as_content_page.feature

@@ -1,62 +0,0 @@
-Feature: Acts as Content Page
-  Rails developers should be able to create standard Rails Controllers that include CMS features, including:
-  1. Handling of exceptions (i.e. routing to standard CMS error pages)
-  2. Security (protected controllers as if they were site pages.
-
-  See 'Tests::PretendController' for other scenarios to pull out.
-
-  Background:
-    Given the cms database is populated
-    And I am a guest
-
-  Scenario: Use CMS templates with Rails Controllers
-    When I visit /content-page
-    Then the response should be 200
-    And I should see a page titled "Content Page"
-    And I should see the following content:
-      | Dummy Site Template |
-
-  Scenario: Set a Page Title
-    When I visit /custom-page
-    Then I should see a page titled "My Custom Page"
-    And I should see the following content:
-    | Some Custom Content |
-
-  Scenario: Content Page
-    When I visit /tests/open
-    Then the response should be 200
-    Then I should see the following content:
-      | Open Page                     |
-      | You can see this public page. |
-
-
-  Scenario: Error Page
-    When I am at /tests/error
-    Then the response should be 500
-    And I should see a page titled "Server Error"
-    And I should see the following content:
-      | The server encountered an unexpected condition that prevented it from fulfilling the request. |
-
-  Scenario: Controller throws Missing Page Error
-    When I am at /tests/not-found
-    Then the response should be 404
-    And I should see a page titled "Not Found"
-    And I should see the following content:
-      | Page Not Found |
-
-
-  Scenario: A Controller in a 'Restricted' section
-    Given a members only section
-    When I am at /tests/restricted
-    Then the response should be 403
-    And I should see a page titled "Access Denied"
-    And I should see the following content:
-      | Access Denied |
-
-
-  Scenario: NotFound Page as a Content Editor
-    Given I am logged in as a Content Editor
-    When I visit /tests/not-found
-    Then the response should be 500
-    And I should see a page titled "Error: ActiveRecord::RecordNotFound"
-

data/features/add_content_to_pages.feature

@@ -1,45 +0,0 @@
-Feature: Add Content to Pages
-  Content Editors should be able to add content to pages.
-
-  Background:
-    Given the cms database is populated
-
-  Scenario: Selecting an existing html block
-    Given there is an Html Block with:
-      | name        | content     |
-      | Hello World | I'm content |
-    And there is a page with:
-      | path       | name      |
-      | /some-page | Some Page |
-    And I am logged in as a Content Editor
-    And I turn on edit mode for /some-page
-    When I am at /some-page
-    And I click the Select Existing Content button
-    Then I should see the following content:
-      | Hello World |
-
-  Scenario: Add Html/Text to a page
-    Given there is a page with:
-      | path       | name      |
-      | /some-page | Some Page |
-    And I am logged in as a Content Editor
-    And I turn on edit mode for /some-page
-    When I am at /some-page
-    And I add new content to the page
-    Then I should see the following content:
-      | File    |
-      | Text    |
-      | Image   |
-      | Portlet |
-    And I should see a page titled "Select Content Type"
-    When I follow "Text"
-    Then I should see a page titled "Content Library / Add New Text"
-    And I should see the following content:
-      | Name |
-      | Text |
-    When I fill in "Name" with "Hello"
-    And I fill in "Content" with "I'm some new content"
-    And I press "Save"
-    Then I should see a page titled "Some Page"
-    And I should see the following content:
-      | I'm some new content |

data/features/caching.feature

@@ -1,13 +0,0 @@
-Feature: Caching
-  In order for the site to scale there should be caching in place for pages.
-
-  Background:
-    Given the cms database is populated
-    And I am logged in as a Content Editor
-    
-  Scenario: Clear Page Cache
-    When I request /cms/cache
-    Then I should see a page titled "Page Cache Info"
-    When I click on "Clear Page Cache"
-    Then I should see a page titled "Page Cache Info"
-

data/features/ckeditor.feature

@@ -1,11 +0,0 @@
-Feature: CKEditor
-  In order to allow non-technical users to edit HTML content
-  the open source CKEditor (WYSIWYG) will be used for content that is HTML
-
-  Scenario: Editing an Html Block
-    Given the cms database is populated
-    And I am logged in as a Content Editor
-    When I request /cms/content_library
-    And I click on "add new content"
-    Then I should see a widget to select which editor to use
-    And  I should see the CKEditor

data/features/commands/confirm_aruba_works.feature

@@ -1,24 +0,0 @@
-Feature: Aruba Behavior
-  Verifies that Aruba is configured correctly and that it is testing things as I expect them to.
-
-  Background:
-
-  Scenario: Create a new Rails project
-    When I run `rails new hello_world --skip-bundle`
-    Then a rails application named "hello_world" should exist
-
-  Scenario: Previously generated projects should be cleaned up before each Scenario
-    Then the following directories should not exist:
-      | hello_world |
-
-  Scenario: Create and verify a file exists
-    Given a file named "test.txt" with:
-    """
-    hello
-    """
-    Then a file named "test.txt" should exist
-
-  Scenario: Aruba cleans up files before each Scenario
-    Then a file named "test.txt" should not exist
-
-

data/features/commands/generate_module.feature

@@ -1,54 +0,0 @@
-@cli
-Feature: Generate Module
-  A developer should be able to create a new BrowserCMS module by using a command line tool.
-
-  Background:
-
-  Scenario: Create a BrowserCMS module
-    When I create a module named "bcms_store"
-    Then a rails engine named "bcms_store" should exist
-    And BrowserCMS should be added the .gemspec file
-    And a file named "bcms_store/test/dummy/app/views/layouts/templates/default.html.erb" should exist
-
-  Scenario: Generate a module (3.4.x)
-    Given I run `bcms module bcms_widgets`
-    Then I cd to "bcms_widgets"
-    And a Gemfile should be created
-    And the engine should be created
-    And the installation script should be created
-    And the following files should exist:
-    | COPYRIGHT.txt |
-    And the project should be LGPL licensed
-    And the following files should exist:
-    | test/dummy/db/browsercms.seeds.rb|
-    And it should no longer generate a README in the public directory
-    And the file "test/dummy/config/routes.rb" should contain:
-    """
-    Rails.application.routes.draw do
-
-      mount BcmsWidgets::Engine => "/bcms_widgets"
-
-      mount_browsercms
-    """
-
-  Scenario: Can Install modules
-    Given I run `bcms module bcms_widgets`
-    And I cd to "bcms_widgets"
-    When I run `rake db:install`
-    Then it should seed the BrowserCMS database
-
-  Scenario: Packaging Modules as Gems
-    Given I run `bcms module bcms_widgets`
-    And I cd to "bcms_widgets"
-    Then the file "bcms_widgets.gemspec" should contain "s.files -= Dir['lib/tasks/module_tasks.rake']"
-    # Better tests, build the gem, check for errors
-    # Install the gem, check the contents.
-
-
-
-
-
-
-
-
-

data/features/commands/install_browsercms.feature

@@ -1,21 +0,0 @@
-@cli
-Feature: Install BrowserCMS
-  As a Rails developer who wants to add a CMS to my Rails project,
-  I should be able to run a single command to have it add BrowserCMS
-  In order to be up and running fast
-
-  Background:
-    Given a rails application named "petstore" exists
-
-  Scenario: Verify
-    Then a rails application named "petstore" should exist
-
-  Scenario: Install CMS into existing project
-    Given I cd to "petstore"
-    And I run `bcms install --skip-bundle`
-    Then BrowserCMS should be installed in the project
-
-
-
-
-

data/features/commands/new_demo_project.feature

@@ -1,30 +0,0 @@
-@cli
-Feature:
-  As a new user of BrowserCMS, I want to be able to experiment with the system by creating a demo site.
-  This demo site should have a basic look and feel, and some pages and content to play with, all of which are
-  designed to show off some of the features of the system.
-
-  Background:
-
-  Scenario: Forgot to specify a name
-    When I run `bcms demo`
-    Then the output should contain:
-    """
-    "demo" was called incorrectly. Call as "bcms demo [NAME]".
-    """
-    And the exit status should be 0
-
-  Scenario: Make a demo project
-    When I run `bcms demo petstore`
-    Then a demo project named "petstore" should be created
-    When I run `rake db:install`
-    Then it should seed the BrowserCMS database
-    And it should seed the demo data
-
-
-
-
-
-
-
-

data/features/commands/new_projects.feature

@@ -1,50 +0,0 @@
-@cli
-Feature: New Project Generator
-  Developers should be able to create new projects from the command line.
-
-  Background:
-
-  Scenario: Output the Version
-    When I run `bcms -v`
-    Then the output should contain "BrowserCMS 3.4.2"
-
-  Scenario: Create a new BrowserCMS project
-    When I create a new BrowserCMS project named "hello"
-    Then a rails application named "hello" should exist
-    And a file named "public/index.html" should not exist
-    And it should copy all the migrations into the project
-    And the file "hello/config/routes.rb" should contain "mount_browsercms"
-    And the file "hello/db/seeds.rb" should contain "require File.expand_path('../browsercms.seeds.rb', __FILE__)"
-    And a file named "hello/db/browsercms.seeds.rb" should exist
-    And a file named "hello/config/initializers/browsercms.rb" should exist
-    And a file named "hello/app/views/layouts/templates/default.html.erb" should exist
-    And the output should not contain "identical"
-    And BrowserCMS should be added the Gemfile
-    And the correct version of Rails should be added to the Gemfile
-    And the production environment should be configured with reasonable defaults
-
-  Scenario: With a specific database
-    When I run `bcms new hello_world -d mysql`
-    Then the file "hello_world/Gemfile" should contain "mysql2"
-
-  Scenario: With an application template
-      The exact template is irrelevant, so long as bcms command passes it to rails.
-
-      When I run `bcms new hello_world -m sometemplate.rb`
-      Then the output should contain "sometemplate.rb] could not be loaded"
-
-  Scenario: Creating a new CMS project without a  name
-    When I run `bcms new`
-    Then the output should contain:
-    """
-    "new" was called incorrectly. Call as "bcms new [NAME]".
-    """
-    And the exit status should be 0
-
-  Scenario: Creating a CMS module without a  name
-    When I run `bcms module`
-    Then the output should contain:
-    """
-    "module" was called incorrectly. Call as "bcms module [NAME]".
-    """
-    And the exit status should be 0

data/features/commands/upgrade_modules_to_3_4_0_from_3_1_x.feature

@@ -1,19 +0,0 @@
-@cli
-Feature: Upgrade Module from 3.1.x to 3.4.x
-
-  Background:
-    Given I am working on a BrowserCMS v3.1.x module named "bcms_widgets"
-
-  Scenario: Verify Project
-    Then a file named "script/console" should exist
-
-  Scenario: Upgrade a Module from 3.1.x to 3.4.x
-    When I run `bcms-upgrade module`
-    Then the output should contain "Upgrading to BrowserCMS 3.3.x"
-    And a Gemfile should be created
-    And the engine should be created
-    And the installation script should be created
-
-
-
-

data/features/commands/upgrade_project_to_3_4_0_from_3_3_x.feature

@@ -1,52 +0,0 @@
-@cli
-Feature:
-  Assuming there is BrowserCMS project that is currently running 3.3.x
-  the upgrade script should handle generating, and/or manipulating files to make upgrading simple
-
-  # Note: We skip running `rake rails:update` as part of these tests since it requires an interactive
-  # command as part a separate process to overwrite files, so its very hard to wait for the exact timing.
-
-  Background:
-    Given I am working on a BrowserCMS v3.3.x project named "petstore"
-
-  Scenario: Upgrade Project
-    When I run `bcms upgrade --skip-rails`
-    Then Gemfile should have the correct version of BrowserCMS
-    And it should comment out Rails in the Gemfile
-    And it should run bundle install
-    And it should copy all the migrations into the project
-    And it should add the seed data to the project
-    And it should display instructions to the user
-
-  Scenario: Projects with Content Block
-    Given the project has a "turtle" block
-    When I run `bcms upgrade --skip-rails`
-    Then I should have a migration for updating the "turtle" versions table
-
-  Scenario: Projects with Content Blocks and Models
-    Rails models (that aren't blocks) should not have a migration generated for them.
-
-    Given the project has a "turtle" block
-    And the project has a "category" model
-    When I run `bcms upgrade --skip-rails`
-    Then I should have a migration for updating the "turtle" versions table
-
-  Scenario: Updates version table
-    Given the project has a "turtle" block
-    When I run `bcms upgrade  --skip-rails`
-    When I run `rake db:migrate`
-    Then the migration should update the version table for "turtle" block
-
-  Scenario: Migrations work for new project
-    Given the project has a "turtle" block which hasn't ever been migrated
-    When I run `bcms upgrade  --skip-rails`
-    When I run `rake db:migrate`
-    Then the migration should not update the version table for "turtle" block
-
-
-
-
-
-
-
-