refinerycms 0.9.6.34 → 0.9.7

data/vendor/plugins/rails_indexes/test/rails_indexes_test.rb

@@ -1,83 +0,0 @@
-require 'test_helper'
-
-class RailsIndexesTest < ActiveSupport::TestCase
-
-  test "relationship indexes are found" do
-    @relationship_indexes = Indexer.check_for_indexes
-
-    assert @relationship_indexes.size > 0
-
-    assert @relationship_indexes.has_key?("companies")
-    assert @relationship_indexes.has_key?("companies_freelancers")
-    assert @relationship_indexes.has_key?("addresses")
-    assert @relationship_indexes.has_key?("purchases")
-  end
-
-  # should add 2 composite indexes or each pair
-  test "has_and_belongs_to_many" do
-    @relationship_indexes = Indexer.check_for_indexes(true)
-
-    assert @relationship_indexes["companies_freelancers"].include?(["company_id", "freelancer_id"])
-    assert @relationship_indexes["companies_freelancers"].include?(["freelancer_id", "company_id"])
-  end
-
-  test "has_and_belongs_to_many with custom columns" do
-    @relationship_indexes = Indexer.check_for_indexes(true)
-
-    assert @relationship_indexes["purchases"].include?(["present_id", "buyer_id"])
-    assert @relationship_indexes["purchases"].include?(["buyer_id", "present_id"])
-  end
-
-  test "belongs_to" do
-    @relationship_indexes = Indexer.check_for_indexes(true)
-    assert @relationship_indexes["addresses"].include?("country_id")
-  end
-
-  test "belongs_to with a custom foreign key" do
-    @relationship_indexes = Indexer.check_for_indexes(true)
-    assert @relationship_indexes["companies"].include?("owner_id")
-  end
-
-  test "should not add an already existing index" do
-    @relationship_indexes = Indexer.check_for_indexes(true)
-    assert !(@relationship_indexes["companies"].include?("country_id"))
-  end
-
-  test "default find_by indexes for primary keys" do
-    @find_by_indexes = Indexer.ar_find_indexes(false)
-
-    # Default added the primary key for each table
-    assert @find_by_indexes.has_key?("users")
-    assert @find_by_indexes.has_key?("companies")
-    assert @find_by_indexes.has_key?("gifts")
-    assert @find_by_indexes.has_key?("freelancers")
-    assert @find_by_indexes.has_key?("countries")
-  end
-
-  test "default find_by indexes for custom primary keys" do
-    @find_by_indexes = Indexer.ar_find_indexes(false)
-
-    assert @find_by_indexes["gifts"].include?("custom_primary_key")
-  end
-
-  test "find_by indexes for self.find_by_email_and_name" do
-    @find_by_indexes = Indexer.ar_find_indexes(false)
-
-    assert @find_by_indexes["users"].include?(["name", "email"])
-    assert @find_by_indexes["users"].include?(["email", "name"])
-  end
-
-  test "find_by indexes for Gift.find_all_by_name_and_price" do
-    @find_by_indexes = Indexer.ar_find_indexes(false)
-
-    assert @find_by_indexes["gifts"].include?(["name", "price"])
-    assert @find_by_indexes["gifts"].include?(["price", "name"])
-  end
-
-  test "find_by indexes from UsersController" do
-    @find_by_indexes = Indexer.ar_find_indexes(false)
-
-    assert @find_by_indexes["freelancers"].include?("name")
-
-  end
-end

data/vendor/plugins/rails_indexes/test/test_helper.rb

@@ -1,30 +0,0 @@
-require 'rubygems'
-
-require 'test/unit'
-
-require 'active_record'
-require 'active_record/fixtures'
-require 'active_support'
-require 'active_support/test_case'
-require 'action_controller'
-
-require 'indexer'
-
-ActiveRecord::Base.establish_connection(
-  :adapter  => "sqlite3",
-  :database => ":memory:"
-)
-
-class Rails
-  def self.root
-    "test/fixtures/"
-  end
-end
-
-load 'test/fixtures/schema.rb'
-
-# Load models
-Dir['test/fixtures/app/models/**/*.rb'].each { |f| require f }
-
-# load controllers
-Dir['test/fixtures/app/controllers/**/*.rb'].each { |f| require f }

data/vendor/plugins/refinery/app/views/admin/_footer.html.erb

@@ -1,7 +0,0 @@
-<div id="footer">
-  <%= link_to image_tag("#{"http://www.resolvedigital.com/images/" unless local_request?}refinery/resolve_digital_footer_logo.png", :alt => "Resolve Digital"), "http://www.resolvedigital.com", :target => "_blank", :id => "footer_logo" %>
-  <p>
-    Refinery built by <%= link_to "Resolve Digital", "http://www.resolvedigital.com", :target => "_blank" %>.
-    Copyright &copy; 2005-<%= Time.now.year %> Resolve Digital
-  </p>
-</div>

data/vendor/plugins/refinery/app/views/shared/_submenu.html.erb

@@ -1,5 +0,0 @@
-<% if (children = @page.root.children).any? -%>
-  <ul id='submenu'>
-    <%= render :partial => "/shared/submenu_branch", :collection => children %>
-  </ul>
-<% end -%>

data/vendor/plugins/refinery/app/views/shared/_submenu_branch.html.erb

@@ -1,10 +0,0 @@
-<% if submenu_branch.in_menu? %>
-<li<%= " class='selected'" if selected_page?(submenu_branch) or descendant_page_selected?(submenu_branch) %>>
-  <%= link_to submenu_branch.title, submenu_branch.url -%>
-  <% if (children = submenu_branch.children).any? %>
-  <ul>
-    <%= render :partial => "/shared/submenu_branch", :collection => children %>
-  </ul>
-  <% end %>
-</li>
-<% end %>

data/vendor/plugins/themes/themes.md

@@ -1,113 +0,0 @@
-# Themes
-
-## Introduction
-
-__Themes allow you to wrap up the design of your Refinery site into a single folder that is portable.__
-
-Refinery doesn't force you to learn a special templating language, but rather just uses the regular
-ERB views you're used to in Rails. This means creating a theme from your existing site is extremely easy.
-
-Think of a theme as your ``app/views`` directory with a few extra things like images, css and javascript.
-
-It's worth noting you don't need to use a theme if you don't want to. Placing files in the ``app/views`` directory like any other Rails app will work just fine. It's only if you want to wrap your design up into a single location that you would use a theme or allow your client to easily change between designs.
-
-## The Structure of a Theme
-
-Themes sit in your Rails app like this
-
-    app/
-    config/
-    db/
-    lib/
-    public/
-    themes/
-      |- mytheme/
-      |- othertheme/
-    plugins/
-    tests/
-
-Let's take the ``mytheme`` example theme shown above. This is how the theme is structured:
-
-    mytheme/
-       |- images
-       |    |- whatever.png
-       |    |- foo.jpg
-       |- javascripts
-       |    |- whatever.js
-       |- LICENSE
-       |- README
-       |- stylesheets/
-       |    |- application.css
-       |    |- whatever.css
-       |- views
-            |- pages
-            |    |- show.html.erb
-            |    |- index.html.erb
-            |- layouts
-                 |- application.html.erb
-             
-### Images
-
-Usually this would be just what you have in ``public/images`` except we move that to the theme instead.
-
-### Javascripts
-
-Same with javascripts, just what you normally have in ``public/javascripts`` but in this theme directory instead.
-
-### Readme
-
-The ``README`` file is just a description of your theme.
-
-### Views
-
-This is exactly the same as how you lay your views out in ``app/views/`` just instead of putting them in ``app/views/`` you put them into ``themes/mytheme/views/``
-
-## How do I make my own Theme?
-
-Create a folder with the name if your theme inside ``/themes`` e.g. ``/themes/mytheme`` and follow the directory structure outlined in 'The structure of a Theme'.
-
-## How do I select which Theme Refinery should use?
-
-In the admin area of Refinery go to the "Settings" area, locate the setting called "theme" and edit it.
-
-Set the value of that setting to the name of your themes folder. For example, if your theme is sitting in:
-
-    themes/my_theme
-
-set it to ``my_theme`` and hit save.
-
-## How do I install someone else's Theme?
-
-Just copy their theme directory into your themes folder and Refinery will see it.
-
-## How can I Convert my Current Views into a Theme?
-
-This should be fairly straightforward, just follow the directory structure outlined in 'The structure of a Theme'. 
-
-But there is one important difference that need to be addressed to convert your current site into a theme.
-
-If you have some CSS which refers to an image or URL:
-
-    #footer {
-      background: url('/images/footer_background.png') repeat-x;
-    }
-
-You need to update the URL so it requests ``/images/themes`` instead of just ``/images``. This tells Refinery we need to actually load this image from the theme and not just the public directory.
-
-So the result is simply:
-
-    #footer {
-      background: url('/theme/images/footer_background.png') repeat-x;
-    }
-
-This is the same with linking to Javascript and Stylesheets in your view. Say our ``application.html.erb`` layout had something like this:
-
-    <%= stylesheet_link_tag 'application' %>
-
-You just need to change that to:
-
-    <%= stylesheet_link_tag 'application', :theme => true %>
-    
-## I'm Stuck, is there an Example Theme?
-
-Yep, there is an example theme called "demolicious" that comes with Refinery located in ``/themes/demolicious``. If you find yourself getting stuck, just check out that theme and get a feel for how it works.

data/vendor/plugins/will_paginate/.manifest

@@ -1,43 +0,0 @@
-CHANGELOG.rdoc
-LICENSE
-README.rdoc
-Rakefile
-examples/apple-circle.gif
-examples/index.haml
-examples/index.html
-examples/pagination.css
-examples/pagination.sass
-init.rb
-lib/will_paginate.rb
-lib/will_paginate/array.rb
-lib/will_paginate/collection.rb
-lib/will_paginate/core_ext.rb
-lib/will_paginate/finder.rb
-lib/will_paginate/named_scope.rb
-lib/will_paginate/named_scope_patch.rb
-lib/will_paginate/version.rb
-lib/will_paginate/view_helpers.rb
-test/boot.rb
-test/collection_test.rb
-test/console
-test/database.yml
-test/finder_test.rb
-test/fixtures/admin.rb
-test/fixtures/developer.rb
-test/fixtures/developers_projects.yml
-test/fixtures/project.rb
-test/fixtures/projects.yml
-test/fixtures/replies.yml
-test/fixtures/reply.rb
-test/fixtures/schema.rb
-test/fixtures/topic.rb
-test/fixtures/topics.yml
-test/fixtures/user.rb
-test/fixtures/users.yml
-test/helper.rb
-test/lib/activerecord_test_case.rb
-test/lib/activerecord_test_connector.rb
-test/lib/load_fixtures.rb
-test/lib/view_test_process.rb
-test/tasks.rake
-test/view_test.rb

data/vendor/plugins/will_paginate/CHANGELOG.rdoc

@@ -1,139 +0,0 @@
-= 2.3.12, released 2009-12-01
-
-* make view helpers "HTML safe" for Rails 2.3.5 with rails_xss plugin
-
-= 2.3.11, released 2009-06-02
-
-* fix `enable_actionpack`
-
-= 2.3.10, released 2009-05-21
-
-* count_by_sql: don't use table alias with any adapters starting with "oracle"
-* Add back "AS count_table" alias to `paginate_by_sql` counter SQL
-
-= 2.3.9, released 2009-05-29
-
-* remove "AS count_table" alias from `paginate_by_sql` counter SQL
-* Rails 2.3.2 compat: monkeypatch Rails issue #2189 (count breaks has_many :through)
-* fix generation of page URLs that contain the "@" character
-* check for method existance in a ruby 1.8- and 1.9-compatible way
-* load will_paginate view helpers even if ActiveRecord is not loaded
-
-== 2.3.8, released 2009-03-09
-
-* Rails 2.3 compat: query parameter parsing with Rack
-
-== 2.3.7, released 2009-02-09
-
-* Removed all unnecessary &block variables since they cause serious memory damage and lots of subsequent gc runs.
-
-== 2.3.6, released 2008-10-26
-
-* Rails 2.2 fix: stop using `extract_attribute_names_from_match` inernal AR method, it no longer exists
-
-== 2.3.5, released 2008-10-07
-
-* update the backported named_scope implementation for Rails versions older than 2.1
-* break out of scope of paginated_each() yielded block when used on named scopes
-* fix paginate(:from)
-
-== 2.3.4, released 2008-09-16
-
-* Removed gem dependency to Active Support (causes trouble with vendored rails).
-* Rails 2.1: fix a failing test and a deprecation warning.
-* Cope with scoped :select when counting.
-
-== 2.3.3, released 2008-08-29
-
-* Ensure that paginate_by_sql doesn't change the original SQL query.
-* RDoc love (now live at http://mislav.caboo.se/static/will_paginate/doc/)
-* Rename :prev_label to :previous_label for consistency. old name still functions but is deprecated
-* ActiveRecord 2.1: Remove :include option from count_all query when it's possible.
-
-== 2.3.2, released 2008-05-16
-
-* Fixed LinkRenderer#stringified_merge by removing "return" from iterator block
-* Ensure that 'href' values in pagination links are escaped URLs
-
-== 2.3.1, released 2008-05-04
-
-* Fixed page numbers not showing with custom routes and implicit first page
-* Try to use Hanna for documentation (falls back to default RDoc template if not)
-
-== 2.3.0, released 2008-04-29
-
-* Changed LinkRenderer to receive collection, options and reference to view template NOT in
-  constructor, but with the #prepare method. This is a step towards supporting passing of
-  LinkRenderer (or subclass) instances that may be preconfigured in some way
-* LinkRenderer now has #page_link and #page_span methods for easier customization of output in
-  subclasses
-* Changed page_entries_info() method to adjust its output according to humanized class name of
-  collection items. Override this with :entry_name parameter (singular).
-    
-    page_entries_info(@posts)
-    #-> "Displaying all 12 posts"
-    page_entries_info(@posts, :entry_name => 'item')
-    #-> "Displaying all 12 items"
-    
-== 2.2.3, released 2008-04-26
-
-* will_paginate gem is no longer published on RubyForge, but on
-  gems.github.com:
-  
-    gem sources -a http://gems.github.com/  (you only need to do this once)
-    gem install mislav-will_paginate
-    
-* extract reusable pagination testing stuff into WillPaginate::View
-* rethink the page URL construction mechanizm to be more bulletproof when
-  combined with custom routing for page parameter
-* test that anchor parameter can be used in pagination links
-
-== 2.2.2, released 2008-04-21
-
-* Add support for page parameter in custom routes like "/foo/page/2"
-* Change output of "page_entries_info" on single-page collection and erraneous
-  output with empty collection as reported by Tim Chater
-  
-== 2.2.1, released 2008-04-08
-
-* take less risky path when monkeypatching named_scope; fix that it no longer
-  requires ActiveRecord::VERSION
-* use strings in "respond_to?" calls to work around a bug in acts_as_ferret
-  stable (ugh)
-* add rake release task
-
-
-== 2.2.0, released 2008-04-07
-
-=== API changes
-* Rename WillPaginate::Collection#page_count to "total_pages" for consistency.
-  If you implemented this interface, change your implementation accordingly.
-* Remove old, deprecated style of calling Array#paginate as "paginate(page,
-  per_page)". If you want to specify :page, :per_page or :total_entries, use a
-  parameter hash.
-* Rename LinkRenderer#url_options to "url_for" and drastically optimize it
-
-=== View changes
-* Added "prev_page" and "next_page" CSS classes on previous/next page buttons
-* Add examples of pagination links styling in "examples/index.html"
-* Change gap in pagination links from "..." to
-  "<span class="gap">&hellip;</span>".
-* Add "paginated_section", a block helper that renders pagination both above and
-  below content in the block
-* Add rel="prev|next|start" to page links
-
-=== Other
-
-* Add ability to opt-in for Rails 2.1 feature "named_scope" by calling
-  WillPaginate.enable_named_scope (tested in Rails 1.2.6 and 2.0.2)
-* Support complex page parameters like "developers[page]"
-* Move Array#paginate definition to will_paginate/array.rb. You can now easily
-  use pagination on arrays outside of Rails:
-
-    gem 'will_paginate'
-    require 'will_paginate/array'
-    
-* Add "paginated_each" method for iterating through every record by loading only
-  one page of records at the time
-* Rails 2: Rescue from WillPaginate::InvalidPage error with 404 Not Found by
-  default

data/vendor/plugins/will_paginate/LICENSE

@@ -1,18 +0,0 @@
-Copyright (c) 2007 PJ Hyett and Mislav Marohnić
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of 
-this software and associated documentation files (the "Software"), to deal in 
-the Software without restriction, including without limitation the rights to 
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of 
-the Software, and to permit persons to whom the Software is furnished to do so, 
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all 
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS 
-FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR 
-COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER 
-IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.