browsercms 3.3.4 → 3.4.0.rc1

data/doc/test_procedure.txt

@@ -0,0 +1,141 @@
+Here is a series of tasks to test the basic interface functionality of the CMS.
+
+Note: It is best to build the cms gem and install it, then test the functionality in a rails app that has been configured to use the new gem.
+
+Sitemap:
+  Add Section
+  Add Page
+  Test Edit Page Link
+  Add Link
+  Edit Section Properties
+  Edit Page Properties
+  Edit Link Properties
+  Publish Link
+  Move Link
+  Move Page
+  Move Section
+  Delete Link
+  Delete Page
+  Delete Section
+
+Content Library:
+  Add Image
+  Edit Image Metadata
+  Edit Image File
+  Revert Image to different metadata
+  Revert Image to different file
+  Search Image
+  Add Text
+  Edit Text
+  Add Link to Text
+  Add Image to Text
+  Revert Text
+  Bulk add Text
+  Paginated Search links
+  Delete Text
+  Delete Image
+  Add Portlet
+  Edit Portlet
+  Search Portlet
+  Delete Portlet
+  Add File
+  Edit File Metadata
+  Edit File File
+  Revert File to metadata
+  Revert File to different file
+  Search File
+  Delete File
+  Add Category Type
+  Edit Category Type
+  Search Category Type
+  Add Category
+  Edit Category
+  Search Category
+  Delete Category
+  Delete Category Type
+  Add Tag
+  Edit Tag
+  Search Tag
+  Delete Tag
+
+Administration:
+  Add Public User Group
+  Add Admin Group
+  Edit Public User Group
+  Edit Admin Group
+  Add User
+  Edit User
+  Search User
+  Disable User
+  Search inactive User
+  Enable User
+  Login as User
+  Change User Password
+  Login as User
+  Add Page Partial
+  Edit Page Partial
+  Add Page Partial
+  Delete Page Partial
+  Add Page Template
+  Edit Page Template
+  Add Page Template
+  Delete Page Template
+  Add Page Route
+  Test Page Route
+  Edit Page Route
+  Test old Page Route
+  Test new Page Route
+  Delete Page Route
+  Test old Page Route
+  Test new Page Route
+  Test Rails Route
+  Clear Page Cache
+  Add Redirect
+  Test Redirect
+  Edit Redirect
+  Test old Redirect
+  Test new Redirect
+  Delete Redirect
+  Test old Redirect
+  Test new Redirect
+
+Page:
+  Toggle Visual Editor On
+  Toggle Visual Editor Off
+  Toggle Visual Editor On
+  Add New Text to Container
+  Add Existing Text to Container
+  Move Text Up
+  Move Text Down
+  Edit Text
+  Remove Text
+  Publish
+  List Versions
+  Revert
+  Assign
+  Complete Task
+  Edit Properties
+  Add New Portlet to Container
+  Add Existing Portlet to Container
+  Move Portlet Up
+  Move Portlet Down
+  Edit Portlet
+  Remove Portlet
+  Add New File to Container
+  Add Existing File to Container
+  Move File Up
+  Move File Down
+  Edit File
+  Remove File
+  Add New Image to Container
+  Add Existing Image to Container
+  Move Image Up
+  Move Image Down
+  Edit Image
+  Remove Image
+  Delete Page
+
+Dashboard:
+  Publish page
+  Publish pages
+  Remove task

data/doc/upgrading_to_3_3.txt

@@ -0,0 +1,90 @@
+This file is out of date. Can be deleted since: https://github.com/browsermedia/browsercms/wiki/Upgrading-modules-to-3.3 exists
+
+# Upgrading a Module to use BrowserCMS 3.3. (and Rails3)
+
+* Update the lib/bcms_name_of_module/routes.rb to use the Rails 3 routing syntax. This means routes like:
+
+## Rails 2 style
+namespace(:cms) do |cms|
+    cms.content_blocks :news_articles
+end
+
+should be written as:
+
+## Rails 3 style
+namespace(:cms) do
+    content_blocks :news_articles
+end
+
+Other individual routes may need to be rewritten as well, for example:
+
+## Rails 2 style
+news_articles '/news/articles.rss', :controller => "news_articles", :conditions => {:method => :get}, :format => "rss"
+## Becomes Rails 3 style
+match '/news/articles.rss', :to=>"news_articles#index", :as=>'news_articles', :method=>:get, :defaults => { :format => 'rss' }
+
+Writing a generator to handle upgrading bcms_modules from Rails 2 to Rails 3.
+=======
+
+Assumed
+======
+* Make sure the module is in source control. These instructions rely on being able to revert. merge and check in files.
+
+Steps:
+======
+* Do script/plugin install git://github.com/rails/rails_upgrade.git . This installs the rails 3 upgrade plugin.
+* Run rake rails:update:check
+* Run rake rails:update:gems ; Create a Gemfile with that code in it.
+* Run rake rails:update:routes ; Create a file config/routes.rails3.rb with that code in it. This will be used to merge the routes later.
+
+* [D] Create a file called lib/tasks/build_gem.rake. Copy all Jeweler code from Rakefile to this file. Test and check this in.
+* [D] From inside the project, run rails new . This will generate a new Rails3 project on top of the existing module. Enter a to overwrite all files.
+
+Files to Delete (after rails new)
+=====
+* [D] Remove the rails/init.rb (No longer needed. Uses Engine instead)
+* [D] Remove the db/migrate/browsercms_3_0_0.rb from the project
+* [D] Remove the db/migrate/browsercms_3_0_5.rb from the project
+* [D] Remove the db/migrate/load_seed_data.rb from the project
+* [D] Remove public/index.html
+* [D] Remove the app/views/layouts/application.html.erb (Use core CMS layouts)
+
+Files to rollback
+====
+* [D] doc/README_FOR_APP
+* [D] README (either delete or rollback depending on if you have a README.md or not)
+* [D].gitignore
+* [D] database.yml - Unlikely you want this to change
+
+File to merge (diff new vs old)
+===
+* [D] test/test_helper (If you added anything custom)
+* [D] Rakefile (compare, especially if you used Jeweler. If Jeweler, make sure you moved those tasks to lib/tasks/build_gem.rake)
+
+More Steps:
+==========
+* [D] Edit config/routes.rb file. Make sure you have these routes:
+
+BcmsNameOfModule::Application.routes.draw do
+  routes_for_bcms_name_of_module
+  routes_for_browser_cms
+end
+
+* [D] Add Jeweler to the Gemfile (if you use it)
+
+group :development do
+  gem "jeweler"
+end
+
+* [D] Add mysql to the Gemfile (if you use it)
+
+gem "mysql"
+
+* [D] Create an Engine for the module
+* [D] Create a generator that will handle installing any migrations from your gem.
+* [D] Remove all public CMS files
+* [D] Run 'rails g browser_cms:cms' to write the migrations out from the core CMS gem.
+* Run 'rake db:drop db:create db:migrate db:seed' to rebuild the database.
+* Run tests (may have to update require 'test_helper' in _test.rbs)
+
+* Run rake rails:upgrade:check to get other warnings about your code (i.e. deprecation warnings about named_scope)

data/doc/upgrading_to_3_4.md

@@ -0,0 +1,19 @@
+Update bcms-upgrade so it can detect the differences between:
+
+3.1
+3.3 (Already does this pretty well)
+* If there are no errors, say 'its ready to go' rather than just warning in RED that its does now.
+* Need to update the dependency on browsercms before running rails generators
+	(Insert s.add_dependency(%q<browsercms>, ["~> 3.3.0"]) into .gemspec
+* I can generate a basic gemspec that will probably work for 95% of cms modules.
+* Doesn't use mysql2 '0.2.18'
+* Make sure cms:install works
+3.4 (Needs to do this)
+* Might still want to have a custom installer for each module for generating files in the project (i.e. Fckeditor would need this)
+
+# Upgrading a project to bcms-3.4
+
+* Ensure there is no table prefix set (i.e. tables will in versions prior to 3.4 were not prefixed with cms_
+
+
+

data/features/acts_as_content_page.feature

@@ -0,0 +1,48 @@
+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: 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

@@ -0,0 +1,46 @@
+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 |
+#  I want to test selecting content, but that requires javascript drivers
+
+  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

@@ -0,0 +1,13 @@
+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

@@ -0,0 +1,11 @@
+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

@@ -0,0 +1,24 @@
+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

@@ -0,0 +1,54 @@
+@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.
+
+
+
+
+
+
+
+
+