bcms_event 1.0.0

data/LICENSE.txt

@@ -0,0 +1,165 @@
+		   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions. 
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version. 
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

data/README

@@ -0,0 +1,243 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create 
+database-backed web applications according to the Model-View-Control pattern. 
+
+This pattern splits the view (also called the presentation) into "dumb" templates
+that are primarily responsible for inserting pre-built data in between HTML tags.
+The model contains the "smart" domain objects (such as Account, Product, Person,
+Post) that holds all the business logic and knows how to persist themselves to
+a database. The controller handles the incoming requests (such as Save New Account,
+Update Product, Show Post) by manipulating the model and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails.  You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
+   and your application name. Ex: rails myapp
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
+4. Follow the guidelines to start developing your application
+
+
+== Web Servers
+
+By default, Rails will try to use Mongrel if it's are installed when started with script/server, otherwise Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails
+with a variety of other web servers.
+
+Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+
+Say other Ruby web servers like Thin and Ebb or regular web servers like Apache or LiteSpeed or
+Lighttpd or IIS. The Ruby web servers are run through Rack and the latter can either be setup to use
+FCGI or proxy to a pack of Mongrels/Thin/Ebb servers.
+
+== Apache .htaccess example for FCGI/CGI
+
+# General Apache options
+AddHandler fastcgi-script .fcgi
+AddHandler cgi-script .cgi
+Options +FollowSymLinks +ExecCGI
+
+# If you don't want Rails to look in certain directories,
+# use the following rewrite rules so that Apache won't rewrite certain requests
+# 
+# Example:
+#   RewriteCond %{REQUEST_URI} ^/notrails.*
+#   RewriteRule .* - [L]
+
+# Redirect all requests not available on the filesystem to Rails
+# By default the cgi dispatcher is used which is very slow
+# 
+# For better performance replace the dispatcher with the fastcgi one
+#
+# Example:
+#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
+RewriteEngine On
+
+# If your Rails application is accessed via an Alias directive,
+# then you MUST also set the RewriteBase in this htaccess file.
+#
+# Example:
+#   Alias /myrailsapp /path/to/myrailsapp/public
+#   RewriteBase /myrailsapp
+
+RewriteRule ^$ index.html [QSA]
+RewriteRule ^([^.]+)$ $1.html [QSA]
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
+
+# In case Rails experiences terminal errors
+# Instead of displaying this message you can supply a file here which will be rendered instead
+# 
+# Example:
+#   ErrorDocument 500 /500.html
+
+ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong.  Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files.  Have "tail -f" commands running
+on the server.log and development.log. Rails will automatically display debugging
+and runtime information to these files. Debugging info will also be shown in the
+browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code using
+the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
+
+* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
+* Learn to Program: http://pine.fm/LearnToProgram/  (a beginners guide)
+
+These two online (and free) books will bring you up to speed on the Ruby language
+and also on programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your Mongrel or
+Webrick server with --debugger. This means that you can break out of execution at any point
+in the code, investigate and change the model, AND then resume execution! 
+You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
+Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better is that you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you enter "cont"
+
+
+== Console
+
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+Here you'll have all parts of the application configured, just like it is when the
+application is running. You can inspect domain models, change values, and save to the
+database. Starting the script without arguments will launch it in the development environment.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
+You would be connected to the database with the credentials defined in database.yml.
+Starting the script without arguments will connect you to the development database. Passing an
+argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
+Currently works for mysql, postgresql and sqlite.
+
+== Description of Contents
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from ApplicationController
+  which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
+  syntax.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the common
+  header/footer method of wrapping views. In your views, define a layout using the
+  <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
+  call <% yield %> to render the view using this layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are generated
+  for you automatically when using script/generate for controllers. Helpers can be used to
+  wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+
+db
+  Contains the database schema in schema.rb.  db/migrate contains all
+  the sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when generated
+  using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that doesn't
+  belong under controllers, models, or helpers. This directory is in the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files. This should be
+  set as the DOCUMENT_ROOT of your web server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the script/generate scripts, template
+  test files will be generated for you and placed in this directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  If the app has frozen rails, those gems also go here, under vendor/rails/.
+  This directory is in the load path.

data/app/controllers/cms/events_controller.rb

@@ -0,0 +1,2 @@
+class Cms::EventsController < Cms::ContentBlockController
+end

data/app/models/event.rb

@@ -0,0 +1,53 @@
+class Event < ActiveRecord::Base
+  acts_as_content_block :taggable => true
+  belongs_to_category
+  
+  before_validation :set_slug
+  validates_presence_of :name, :slug, :starts_on
+
+  named_scope :starts_on, lambda {|date|
+    d = if date.kind_of?(Hash)
+      Date.new(date[:year].to_i, date[:month].to_i, date[:day].to_i)
+    else
+      date
+    end
+    
+    {:conditions => ["events.starts_on = ?", d]}
+  }
+      
+  named_scope :with_slug, lambda{|slug| {:conditions => ["events.slug = ?",slug]}}  
+
+  def self.default_order
+    "starts_on desc"
+  end
+  
+  def self.columns_for_index
+    [ {:label => "Name", :method => :name, :order => "name" },
+      {:label => "Starts On", :method => :starts_on_label, :order => "starts_on" } ]
+  end  
+  
+  def starts_on_label
+    starts_on ? starts_on.to_s(:long) : nil
+  end
+  
+  def set_slug
+    self.slug = name.to_slug
+  end
+  
+  def route_params
+    {:year => year, :month => month, :day => day, :slug => slug}
+  end  
+  
+  def year
+    starts_on.strftime("%Y")
+  end
+  
+  def month
+    starts_on.strftime("%m")
+  end
+  
+  def day
+    starts_on.strftime("%d")
+  end
+
+end

data/app/portlets/event_portlet.rb

@@ -0,0 +1,10 @@
+class EventPortlet < Portlet
+    
+  def render
+    # @event should already be set by the page route
+    if !@event && params[:event_id]
+      @event = Event.published.find(params[:event_id])
+    end
+  end
+    
+end

data/app/portlets/events_portlet.rb

@@ -0,0 +1,11 @@
+class EventsPortlet < Portlet
+    
+  def render
+    if self.category_id.blank?
+      @events = Event.published.all
+    else
+      @events = Event.published.all(:conditions => {:category_id => self.category_id})
+    end
+  end
+    
+end

data/app/views/cms/events/_form.html.erb

@@ -0,0 +1,11 @@
+<%= f.cms_text_field :name %>
+<%= f.cms_date_picker :starts_on %>
+<%= f.cms_date_picker :ends_on %>
+<%= f.cms_text_field :location %>
+<%= f.cms_text_field :contact_email %>
+<%= f.cms_text_area :description %>
+<%= f.cms_text_field :more_info_url %>
+<%= f.cms_text_field :registration_url %>
+<%= f.cms_drop_down :category_id, categories_for('Event').map{|c| [c.path, c.id]}, :include_blank => true %>
+<%= f.cms_tag_list %>
+<%= f.cms_text_editor :body %>

data/app/views/cms/events/render.html.erb

@@ -0,0 +1,10 @@
+<p><b>Name:</b> <%= @content_block.name %></p>
+<p><b>Starts On:</b> <%= @content_block.starts_on %></p>
+<p><b>Ends On:</b> <%= @content_block.ends_on %></p>
+<p><b>Location:</b> <%= @content_block.location %></p>
+<p><b>Contact Email:</b> <%= @content_block.contact_email %></p>
+<p><b>Description:</b> <%= simple_format h(@content_block.description) %></p>
+<p><b>More Info Url:</b> <%= @content_block.more_info_url %></p>
+<p><b>Registration Url:</b> <%= @content_block.registration_url %></p>
+<p><b>Category:</b> <%= @content_block.category_name %></p>
+<p><b>Body:</b> <%= @content_block.body %></p>

data/app/views/portlets/event/_form.html.erb

@@ -0,0 +1,2 @@
+<%= f.cms_text_field :name %>
+<%= f.cms_text_area :template, :default_value => @block.class.default_template %>

data/app/views/portlets/event/render.html.erb

@@ -0,0 +1,10 @@
+<p><b>Name:</b> <%= @event.name %></p>
+<p><b>Starts On:</b> <%= @event.starts_on %></p>
+<p><b>Ends On:</b> <%= @event.ends_on %></p>
+<p><b>Location:</b> <%= @event.location %></p>
+<p><b>Contact Email:</b> <%= @event.contact_email %></p>
+<p><b>Description:</b> <%= simple_format h(@event.description) %></p>
+<p><b>More Info Url:</b> <%= @event.more_info_url %></p>
+<p><b>Registration Url:</b> <%= @event.registration_url %></p>
+<p><b>Category:</b> <%= @event.category_name %></p>
+<p><b>Body:</b> <%= @event.body %></p>

data/app/views/portlets/events/_form.html.erb

@@ -0,0 +1,3 @@
+<%= f.cms_text_field :name %>
+<%= f.cms_drop_down :category_id, categories_for('Event').map{|c| [c.path, c.id]}, :include_blank => true %>
+<%= f.cms_text_area :template, :default_value => @block.class.default_template %>

data/app/views/portlets/events/render.html.erb

@@ -0,0 +1,18 @@
+<div>
+  <% @events.group_by{|e| e.starts_on.year}.sort_by(&:first).reverse.each do |year, events_grouped_by_year| %>
+    <!-- <%= year %> -->
+    <% events_grouped_by_year.group_by{|e| e.starts_on.month}.sort_by(&:first).reverse.each do |month, events_grouped_by_month| %>
+      <b class="month"><%= Date::MONTHNAMES[month] %></b>
+      <% for event in events_grouped_by_month.sort_by(&:starts_on).reverse %>
+        <div id="event_<%= event.id %>" class="event">
+          <span class="event_starts_on"><b><%= event.starts_on.to_s(:long) %></b></span>
+          <br/>
+          <%= link_to "<b>#{h(event.name)}</b>", event_path(event.route_params) %><br/>
+          <% unless event.description.blank? -%>
+            <p><%= simple_format h(event.description) %></p>
+          <% end %>
+        </div>
+      <% end %>
+    <% end %>
+  <% end %>
+</div>

data/db/migrate/20090504174621_create_events.rb

@@ -0,0 +1,60 @@
+class CreateEvents < ActiveRecord::Migration
+  def self.up
+    create_versioned_table :events do |t|
+      t.string :name 
+      t.string :slug
+      t.date :starts_on 
+      t.date :ends_on 
+      t.string :location 
+      t.string :contact_email 
+      t.text :description 
+      t.string :more_info_url 
+      t.string :registration_url 
+      t.belongs_to :category 
+      t.text :body, :size => (64.kilobytes + 1) 
+    end
+    unless CategoryType.named('Event').exists?
+      CategoryType.create!(:name => "Event")
+    end
+    
+    ContentType.create!(:name => "Event", :group_name => "Event")
+    
+    event_page = Page.create!(
+      :name => "Event", 
+      :path => "/event", 
+      :section => Section.root.first,
+      :template_file_name => "default.html.erb")
+      
+    EventPortlet.create!(
+      :name => "Event Details",
+      :template => EventPortlet.default_template,
+      :connect_to_page_id => event_page.id,
+      :connect_to_container => "main",
+      :publish_on_save => true)
+      
+    EventsPortlet.create!(
+      :name => "Event List",
+      :template => EventsPortlet.default_template,
+      :connect_to_page_id => event_page.id,
+      :connect_to_container => "main",
+      :publish_on_save => true)      
+      
+    route = event_page.page_routes.build(
+      :name => "Event",
+      :pattern => "/events/:year/:month/:day/:slug",
+      :code => "@event = Event.published.starts_on(params).with_slug(params[:slug]).first")
+    route.add_condition(:method, "get")
+    route.add_requirement(:year, '\d{4,}')
+    route.add_requirement(:month, '\d{2,}')
+    route.add_requirement(:day, '\d{2,}')
+    route.save!    
+    
+  end
+
+  def self.down
+    ContentType.delete_all(['name = ?', 'Event'])
+    CategoryType.all(:conditions => ['name = ?', 'Event']).each(&:destroy)
+    drop_table :event_versions
+    drop_table :events
+  end
+end

data/lib/bcms_event/routes.rb

@@ -0,0 +1,7 @@
+module Cms::Routes
+  def routes_for_bcms_event
+    namespace(:cms) do |cms|
+      cms.content_blocks :events
+    end  
+  end
+end

data/lib/bcms_event.rb

@@ -0,0 +1 @@
+require 'bcms_event/routes'

data/rails/init.rb

@@ -0,0 +1,3 @@
+gem_root = File.expand_path(File.join(File.dirname(__FILE__), ".."))
+Cms.add_to_rails_paths gem_root
+Cms.add_generator_paths gem_root, "db/migrate/[0-9]*_*.rb"

data/test/functional/events_portlet_test.rb

@@ -0,0 +1,31 @@
+require File.dirname(__FILE__) + '/../test_helper'
+
+class EventsPortletTest < ActionController::TestCase
+  tests Cms::ContentController
+  
+  def setup
+    create_baseline_data!
+    create_sample_data!
+    @events_portlet = EventsPortlet.create!(:name => "Events Portlet",
+      :template => EventsPortlet.default_template,
+      :connect_to_page_id => @events_page.id,
+      :connect_to_container => "main",
+      :publish_on_save => true)
+  end
+  
+  def test_show_post
+    get :show, :path => ["events"]
+    log @response.body
+    assert_response :success
+    assert_select "title", "Events"
+    
+    assert_select ".event" do
+      assert_select ".event_starts_on", "January 19, 2009"
+      assert_select "a b", "Martin Luther King Day"
+    end
+    
+    assert_select ".event a b", {:text => "Unpublished", :count => 0}
+    
+  end
+  
+end

data/test/performance/browsing_test.rb

@@ -0,0 +1,9 @@
+require 'test_helper'
+require 'performance_test_help'
+
+# Profiling results for each test method are written to tmp/performance.
+class BrowsingTest < ActionController::PerformanceTest
+  def test_homepage
+    get '/'
+  end
+end

data/test/test_helper.rb

@@ -0,0 +1,73 @@
+ENV["RAILS_ENV"] = "test"
+require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
+require 'test_help'
+
+class ActiveSupport::TestCase
+  require File.dirname(__FILE__) + '/test_logging'
+  include TestLogging
+  include SampleData
+  # Transactional fixtures accelerate your tests by wrapping each test method
+  # in a transaction that's rolled back on completion.  This ensures that the
+  # test database remains unchanged so your fixtures don't have to be reloaded
+  # between every test method.  Fewer database queries means faster tests.
+  #
+  # Read Mike Clark's excellent walkthrough at
+  #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
+  #
+  # Every Active Record database supports transactions except MyISAM tables
+  # in MySQL.  Turn off transactional fixtures in this case; however, if you
+  # don't care one way or the other, switching from MyISAM to InnoDB tables
+  # is recommended.
+  #
+  # The only drawback to using transactional fixtures is when you actually 
+  # need to test transactions.  Since your test is bracketed by a transaction,
+  # any transactions started in your code will be automatically rolled back.
+  self.use_transactional_fixtures = true
+
+  # Instantiated fixtures are slow, but give you @david where otherwise you
+  # would need people(:david).  If you don't want to migrate your existing
+  # test cases which use the @david style and don't mind the speed hit (each
+  # instantiated fixtures translates to a database query per test method),
+  # then set this back to true.
+  self.use_instantiated_fixtures  = false
+
+  # Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
+  #
+  # Note: You'll currently still have to declare fixtures explicitly in integration tests
+  # -- they do not yet inherit this setting
+  fixtures :all
+
+  # Add more helper methods to be used by all tests here...
+  def create_baseline_data!
+    @section = Section.create!(:name => "My Site", :path => "/")
+    Group.create!(:name => "Guest", :code => "guest", :sections => [@section])
+    @page_template = PageTemplate.create!(:name => "test", :format => "html", :handler => "erb", :body => %q{<html>
+      <head>
+        <title>
+          <%= page_title %>
+        </title>
+        <%= yield :html_head %>
+      </head>
+      <body>
+        <%= cms_toolbar %>
+        <%= container :main %>
+      </body>
+    </html>})
+
+    @events_page = Page.create!(:name => "Events", :section => @section, :path => "/events", :template_file_name => "test.html.erb")
+    @event_page = Page.create!(:name => "Event", :section => @section, :path => "/event", :template_file_name => "test.html.erb")
+
+    @event_route = @event_page.page_routes.build(
+      :name => "Event",
+      :pattern => "/events/:year/:month/:day/:slug",
+      :code => "@event = Event.published.starts_on(params).with_slug(params[:slug]).first")
+    @event_route.add_condition(:method, "get")
+    @event_route.add_requirement(:year, '\d{4,}')
+    @event_route.add_requirement(:month, '\d{2,}')
+    @event_route.add_requirement(:day, '\d{2,}')
+    @event_route.save!    
+
+    @events_page.publish!
+    @event_page.publish!
+  end  
+end

data/test/test_logging.rb

@@ -0,0 +1,64 @@
+module TestLogging
+  def log(msg)
+    Rails.logger.info(msg)
+  end
+  
+  def log_array(obj, *columns)
+    lengths = columns.map{|m| m.to_s.length }
+
+    obj.each do |r|
+      columns.each_with_index do |m, i|
+        v = r.send(m)
+        if v.to_s.length > lengths[i]
+          lengths[i] = v.to_s.length
+        end
+      end
+    end
+
+    str = "  "
+    columns.each_with_index do |m, i|
+      str << "%#{lengths[i]}s" % m
+      str << "  "
+    end
+    str << "\n  "
+
+    columns.each_with_index do |m, i|
+      str << ("-"*lengths[i])
+      str << "  "
+    end
+    str << "\n  "
+
+    obj.each do |r|
+      columns.each_with_index do |m, i|
+        str << "%#{lengths[i]}s" % r.send(m)
+        str << "  "
+      end
+      str << "\n  "      
+    end
+
+    log str    
+  end  
+  
+  def log_table(cls, options={})
+    if options[:include_columns]
+      columns = options[:include_columns]
+    elsif options[:exclude_columns]
+      columns = cls.column_names - options[:exclude_columns].map(&:to_s)
+    else
+      columns = cls.column_names      
+    end
+    log_array (cls.uses_soft_delete? ? cls.find_with_deleted(:all) : cls.all), *columns
+  end
+  
+  def log_table_with(cls, *columns)
+    log_table(cls, :include_columns => columns)
+  end
+  
+  def log_table_without(cls, *columns)
+    log_table(cls, :exclude_columns => columns)
+  end
+
+  def log_table_without_stamps(cls, *columns)
+    log_table(cls, :exclude_columns => %w[created_at updated_at created_by_id updated_by_id] + columns)
+  end    
+end

metadata

@@ -0,0 +1,72 @@
+--- !ruby/object:Gem::Specification 
+name: bcms_event
+version: !ruby/object:Gem::Version 
+  version: 1.0.0
+platform: ruby
+authors: 
+- BrowserMedia
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2009-07-02 00:00:00 -04:00
+default_executable: 
+dependencies: []
+
+description: The Event Module for BrowserCMS
+email: github@browsermedia.com
+executables: []
+
+extensions: []
+
+extra_rdoc_files: 
+- LICENSE.txt
+- README
+files: 
+- app/controllers/cms/events_controller.rb
+- app/models/event.rb
+- app/portlets/event_portlet.rb
+- app/portlets/events_portlet.rb
+- app/views/cms/events/_form.html.erb
+- app/views/cms/events/render.html.erb
+- app/views/portlets/event/_form.html.erb
+- app/views/portlets/event/render.html.erb
+- app/views/portlets/events/_form.html.erb
+- app/views/portlets/events/render.html.erb
+- db/migrate/20090504174621_create_events.rb
+- lib/bcms_event.rb
+- lib/bcms_event/routes.rb
+- rails/init.rb
+- LICENSE.txt
+- README
+has_rdoc: true
+homepage: http://browsercms.org
+post_install_message: 
+rdoc_options: 
+- --charset=UTF-8
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
+  version: 
+requirements: []
+
+rubyforge_project: browsercms
+rubygems_version: 1.3.1
+signing_key: 
+specification_version: 2
+summary: The Event Module for BrowserCMS
+test_files: 
+- test/functional/events_portlet_test.rb
+- test/performance/browsing_test.rb
+- test/test_helper.rb
+- test/test_logging.rb