RubyGems - refinerycms - Versions diffs - 0.9.6.34 → 0.9.7 - Mend

refinerycms 0.9.6.34 → 0.9.7

Files changed (1069) hide show

data/vendor/plugins/hpricot/test/test_paths.rb DELETED Viewed

@@ -1,25 +0,0 @@
-#!/usr/bin/env ruby
-require 'test/unit'
-require 'hpricot'
-require 'load_files'
-class TestParser < Test::Unit::TestCase
-  def test_roundtrip
-    @basic = Hpricot.parse(TestFiles::BASIC)
-    %w[link link[2] body #link1 a p.ohmy].each do |css_sel|
-      ele = @basic.at(css_sel)
-      assert_equal ele, @basic.at(ele.css_path)
-      assert_equal ele, @basic.at(ele.xpath)
-    end
-  end
-  def test_attr_brackets
-    doc = Hpricot('<input name="vendor[porkpies]"/>')
-    assert_equal 1, (doc/'input[@name^="vendor[porkpies]"]').length
-    assert_equal 1, (doc/'input[@name="vendor[porkpies]"]').length
-    assert_equal 0, (doc/'input[@name$="]]]]]"]').length
-    doc = Hpricot('<input name="vendor[porkpies][meaty]"/>')
-    assert_equal 1, (doc/'input[@name^="vendor[porkpies][meaty]"]').length
-  end
-end

data/vendor/plugins/hpricot/test/test_preserved.rb DELETED Viewed

@@ -1,88 +0,0 @@
-# -*- coding: utf-8 -*-
-#!/usr/bin/env ruby
-require 'test/unit'
-require 'hpricot'
-require 'load_files'
-unless "".respond_to?(:lines)
-  require 'enumerator'
-  class String
-    def lines
-      Enumerable::Enumerator.new(self, :each_line)
-    end
-  end
-end
-class TestPreserved < Test::Unit::TestCase
-  def assert_roundtrip str
-    doc = Hpricot(str)
-    yield doc if block_given?
-    str2 = doc.to_original_html
-    if RUBY_VERSION =~ /^1.9/
-      str2.force_encoding('UTF-8')
-    end
-    str.lines.zip(str2.lines).each do |s1, s2|
-      assert_equal s1, s2
-    end
-  end
-  def assert_html str1, str2
-    doc = Hpricot(str2)
-    yield doc if block_given?
-    assert_equal str1, doc.to_original_html
-  end
-  def test_simple
-    str = "<p>Hpricot is a <b>you know <i>uh</b> fine thing.</p>"
-    assert_html str, str
-    assert_html "<p class=\"new\">Hpricot is a <b>you know <i>uh</b> fine thing.</p>", str do |doc|
-      (doc/:p).set('class', 'new')
-    end
-  end
-  def test_parent
-    str = "<html><base href='/'><head><title>Test</title></head><body><div id='wrap'><p>Paragraph one.</p><p>Paragraph two.</p></div></body></html>"
-    assert_html str, str
-    assert_html "<html><base href='/'><body><div id=\"all\"><div><p>Paragraph one.</p></div><div><p>Paragraph two.</p></div></div></body></html>", str do |doc|
-      (doc/:head).remove
-      (doc/:div).set('id', 'all')
-      (doc/:p).wrap('<div></div>')
-    end
-  end
-  def test_escaping_of_contents
-    doc = Hpricot(TestFiles::BOINGBOING)
-    assert_equal "Fukuda’s Automatic Door opens around your body as you pass through it. The idea is to save energy and keep the room clean.", doc.at("img[@alt='200606131240']").next.to_s.strip
-  end
-  def test_files
-    assert_roundtrip TestFiles::BASIC
-    assert_roundtrip TestFiles::BOINGBOING
-    assert_roundtrip TestFiles::CY0
-  end
-  def test_fixup_link
-    doc = %{<?xml version="1.0" encoding="UTF-8"?><rss><channel><link>ht</link></channel></rss>}
-    assert_roundtrip doc
-    assert_equal Hpricot(doc).to_s,
-      %{<?xml version="1.0" encoding="UTF-8"?><rss><channel><link />ht</channel></rss>}
-    assert_equal Hpricot.XML(doc).to_s,
-      %{<?xml version="1.0" encoding="UTF-8"?><rss><channel><link>ht</link></channel></rss>}
-  end
-  def test_escaping_of_attrs
-    # ampersands in URLs
-    str = %{<a href="http://google.com/search?q=hpricot&amp;l=en">Google</a>}
-    link = (doc = Hpricot(str)).at(:a)
-    assert_equal "http://google.com/search?q=hpricot&l=en", link['href']
-    assert_equal "http://google.com/search?q=hpricot&l=en", link.attributes['href']
-    assert_equal "http://google.com/search?q=hpricot&l=en", link.get_attribute('href')
-    assert_equal "http://google.com/search?q=hpricot&amp;l=en", link.raw_attributes['href']
-    assert_equal str, doc.to_html
-    # alter the url
-    link['href'] = "javascript:alert(\"AGGA-KA-BOO!\")"
-    assert_equal %{<a href="javascript:alert(&quot;AGGA-KA-BOO!&quot;)">Google</a>}, doc.to_html
-  end
-end

data/vendor/plugins/hpricot/test/test_xml.rb DELETED Viewed

@@ -1,28 +0,0 @@
-#!/usr/bin/env ruby
-require 'test/unit'
-require 'hpricot'
-require 'load_files'
-class TestParser < Test::Unit::TestCase
-  # normally, the link tags are empty HTML tags.
-  # contributed by laudney.
-  def test_normally_empty
-    doc = Hpricot::XML("<rss><channel><title>this is title</title><link>http://fake.com</link></channel></rss>")
-    assert_equal "this is title", (doc/:rss/:channel/:title).text
-    assert_equal "http://fake.com", (doc/:rss/:channel/:link).text
-  end
-  # make sure XML doesn't get downcased
-  def test_casing
-    doc = Hpricot::XML(TestFiles::WHY)
-    assert_equal "hourly", (doc.at "sy:updatePeriod").inner_html
-    assert_equal 1, (doc/"guid[@isPermaLink]").length
-  end
-  # be sure tags named "text" are ok
-  def test_text_tags
-    doc = Hpricot::XML("<feed><title>City Poisoned</title><text>Rita Lee has poisoned Brazil.</text></feed>")
-    assert_equal "City Poisoned", (doc/"title").text
-  end
-end

data/vendor/plugins/images/images.md DELETED Viewed

@@ -1,53 +0,0 @@
-# Images
-![Refinery Images](http://refinerycms.com/system/images/0000/0616/images.png)
-## About
-All Refinery's images are stored in one place, the images plugin. You can customise what sized thumbnails are generated when an image is uploaded.
-Images and other file uploads are handled using [attachment_fu](http://github.com/technoweenie/attachment_fu)
-## Generating Thumbnails
-Refinery lets you generate a range of thumbnails when an image is uploaded so you can output this on a page in an appropriate size.
-To specify the sizes of your thumbnails edit the "Image Thumbnails" setting.
-This setting is stored as a serialized hash and is directly passed to [attachment_fu](http://github.com/technoweenie/attachment_fu)
-Here's what the default looks like
-    ---
-    :grid: c135x135
-    :lightbox: 500x500>
-    :dialog_thumb: c106x106
-    :medium: 225x255
-    :preview: c96x96
-    :thumb: 50x50
-    :side_body: 300x500
-Refinery requires some of these, so you won't want to delete any, but add new ones to meet your design needs. Each thumbnail is not just a size guide but a [RMagick geometry string](http://www.imagemagick.org/RMagick/doc/imusage.html#geometry) that allows you to define min and max size too.
-Refinery also extends the [geometry string](http://www.imagemagick.org/RMagick/doc/imusage.html#geometry) support to allow cropping. Here's some examples
-    :grid: c135x135
-This will crop (_that's what the "c" stands for_) the grid thumbnail down to ``135x135`` exactly, without stretching the image.
-_Note: you will have to restart your web server after changing this setting for the changes to take effect._
-## Using a Thumbnail Size in Your Theme or View
-Take the default thumbnails above to use the ``:side_body`` thumbnail I would collect that image out of the database and apply it like this in my view:
-    <%= image_fu @image, :side_body %>
-image_fu is a command we have created that automatically adds width and height attributes to the generated image so that web browsers render your pages more smoothly as they know in advance how big an image is going to be before it is fully downloaded.
-## Related Settings
-### "Preferred Image View"
-Set to ``"grid"`` to get your images to display as a grid of thumbnails
-Set to ``"list"`` to get your images to display as a list with image titles.

data/vendor/plugins/inquiries/inquiries.md DELETED Viewed

@@ -1,31 +0,0 @@
-# Inquiries
-![Refinery Inquiries](http://refinerycms.com/system/images/0000/0626/inquiries.png)
-## About
-__Refinery gives you a simple contact form that notifies you and the customer when an inquiry is made.__
-In summary you can:
-* Collect and manage inquiries
-* Specify who is notified when a new inquiry comes in
-* Customise an auto responder email that is sent to the person making the inquiry
-When inquiries come in, you and the customer are notified. The inquiry will now show up as an "open" inquiry. The idea is to deal with the inquiry and then "close" it so you know it's been sorted.
-## How do I get Notified?
-Go into your 'Inquiries' tab in the Refinery admin area and click on "Update who gets notified"
-## How do I Edit the Automatic Confirmation Email
-Go into your 'Inquiries' tab in the Refinery admin area and click on "Edit confirmation email"
-## But I don't want a Contact Form how do I kill it?
-Your contact form loads because you have a page in your site that is told to not just render a normal page, but load the contact form instead.
-By default this page is called "Contact Us". Go to your "Pages" tab in the Refinery admin area and click the edit icon on "Contact Us". Now click on "Hide/Show Advanced Options" and you'll see that a "Custom URL" is set to ``/inquiries/new``. Simply change this to nothing, or delete the contact us page.
-You might also want to remove the Inquiries plugin from your backend view. To do that, you go to the "Users" tab in the Refinery admin area, edit your user, uncheck "Inquiries" from the list of plugins you can access.

data/vendor/plugins/pages/pages.md DELETED Viewed

@@ -1,146 +0,0 @@
-# Pages
-![Refinery Pages](http://refinerycms.com/system/images/0000/0656/pages.png)
-## About
-One core part of Refinery is Pages. Plugins such as News and Inquiries hook to pages. The menu is rendered based off the structure of your pages.
-Pages have one key thing about them that is unique - page parts.
-## Page Parts
-![Refinery Page Parts](http://refinerycms.com/system/images/0000/0586/editing-page.png)
-### What are they?
-Think of a page part is a single piece of content on your page. At [Resolve Digital](http://www.resolvedigital.co.nz) we often simply use ``body`` and ``side_body``. One is for the main content and one is for the content which goes on a side bit of the page to display other information.
-### Default Page Parts
-You can change what the default page parts are called or add more by editing the "Default Page Parts" setting. This is a serialized array of names. The default looks like this
-    ---
-    - Body
-    - Side Body
-Edit this setting to suit your taste.
-### Adding Page Parts for Specific Pages
-You can add extra page parts to your pages by setting the "New Page Parts" to ``true``.
-Now do this
-* Edit the page you want to add a part to
-* Click the little "+" icon up by the page part tabs
-* Type the name of your new part and hit add.
-_Note: in the user-facing front end we call them "content sections" not "page parts"._
-## Page Options
-### Draft/Published
-You can have draft and published pages. This is controlled by checking and unchecking the "Save as Draft" field on the page form, when editing the page.
-### Custom Title
-There are three options for how the page title will be rendered on the front end.
-* ``None``: will just default to the page title
-* ``Text``: allows you to have a different name for the page in the backend to the front end (sometimes good for SEO)
-* ``Image``: If your designer is using a custom non-standard web font, this is ideal. Bang the image of your title right in there (_we don't recommend this though! Standard web fonts are always a good idea_)
-### Show in Menu
-You can hide a page from the navigation if you like by unchecking "show in menu". This is good for extra reference pages or even pages you might want to link someone up to directly but not "advertise" the pages existence on the menu.
-### Custom URL
-This allows you to make your page not link to a normal page but make it show something else. This could be a donation link to a completely different site or as Refinery uses it, you might want to link to another plugin.
-The "contact us" page for example has a Custom URL of ``/inquiries/new``, this is because we want it to load the inquiries form from the inquiries plugin instead.
-### WYMEditor (the visual editor)
-Refinery is backed by [WYMEditor](http://www.wymeditor.org/)
-It's a standards compliant editor that we've trimmed to only have what we feel is absolutely necessary. When you're editing the content in a page part you're using [WYMEditor](http://www.wymeditor.org/).
-You can also switch to "source" view and edit XHTML manually if the visual editor is not playing nice.
-### Custom Selectable Styles in WYMEditor
-![Refinery Page Editor Styles](http://refinerycms.com/system/images/0000/0596/editing-page-style.png)
-Some sites require a little more than just your standard bold and heading controls. This is where the "css" style drop down comes in handy.
-It allows your users to select a style you define. You need to edit/create a CSS file called ``theme.css``.
-This file should be located in ``/public/stylesheets/themes.css``
-Inside that file you define your styles like this
-    .category-name-style-name {
-      // apply your CSS rules here
-    }
-For example, if I wanted to add a style that allowed my users to highlight their text a light yellow colour, I would put this
-    .text-highlight-yellow {
-      background: LightYellow;
-    }
-Now edit ``public/javascripts/admin.js``. We're going to need to tell WYMEditor that we have some new styles it should load when the editor is loaded.
-Currently your ``admin.js`` file will have something like this
-    var wymeditorClassesItems = [
-        {name: 'text-align', rules:['left', 'center', 'right', 'justify'], join: '-'}
-     ,  {name: 'image-align', rules:['left', 'right'], join: '-'}
-     ,  {name: 'font-size', rules:['small','normal','large'], join: '-'}
-    ]
-Let's just breakdown a single WYMeditor line and understand it:
-    {name: 'font-size', rules:['small','normal','large'], join: '-'}
-``font-size`` is the name of the category and ``small``, ``normal``, ``large`` are the actual styles. So for this to match up with the styles in my theme.css file the class name has to be:
-    .font-size-small { // CSS rules here }
-    .font-size-normal { // CSS rules here }
-    .font-size-large { // CSS rules here }
-So going back to our text highlighting style above, we make the new style show up in the editor by changing our ``admin.js`` file to:
-    var wymeditorClassesItems = [
-        {name: 'text-align', rules:['left', 'center', 'right', 'justify'], join: '-'}
-     ,  {name: 'image-align', rules:['left', 'right'], join: '-'}
-     ,  {name: 'font-size', rules:['small','normal','large'], join: '-'}
-     ,  {name: 'text-highlight', rules:['yellow'], join: '-'}
-    ]
-### Dialogs that show from WYMEditor
-![Refinery Page Editor Link Dialog](http://refinerycms.com/system/images/0000/0636/link-dialog.png)
-## Page Link dialog
-The link dialog lets you link in several different ways:
-* To an internal page
-* To an external page
-* To an email address
-* To a resource you've uploaded in the Resources tab.
-## Insert Image dialog
-Simply lets you select from an existing image found in the Images tab or upload a new one right within the dialog.
-## Refinery Default Pages
-Some pages you have to keep in order for Refinery to stay fully functional:
-* Page not found - the default 404 page
-* Down for maintenance - renders when you're site is being updated.

data/vendor/plugins/rails_indexes/README.textile DELETED Viewed

@@ -1,46 +0,0 @@
-h1. Rails Indexes
-Rails indexes is a small package of 2 rake tasks that scan your application models and displays a list of columns that _probably_ should be indexed.
-note: there should be mode fields depending on your application design and custom queries.
-h2. Installation
-as a rails plugin:
-<pre>script/plugin install git://github.com/eladmeidar/rails_indexes.git</pre>
-h2. Usage
-<del>Display a simple report:</del>
-<pre><del>rake db:show_me_some_indexes</del></pre>
- - *deprecated*
-Display a migration for adding/removing all necessary indexes based on associations:
-<pre>rake db:show_me_a_migration</pre>
-Display a migration for adding/removing all necessary indexes based on AR::Base#find calls (including: find, find_by, find_all_by, find_by_x_and_y, find_all_by_x_and_y):
-<pre>rake db:show_me_ar_find_indexes</pre>
-Note that it would probably make more sense running those tasks on production, where you *actually* need those indexes to be added.
-* Add an option to create a migration that adds all the needed indexes.
-* Add an option to scan the application root tree for #find, #find_all_by and #find_by to get some more index-required columns.
-h2. Tests
-Requires SQLite3 installed, then just:
-<pre>rake</pre>
-to run the tests
-h4. Author:
-Elad Meidar
-"http://blog.eizesus.com":http://blog.eizesus.com
-Thanks:
-Eric Davis,
-"http://littlestreamsoftware.com":http://littlestreamsoftware.com
-Released under the same license as Ruby. No Support. No Warranty, no Pain.

data/vendor/plugins/rails_indexes/Rakefile DELETED Viewed

@@ -1,23 +0,0 @@
-require 'rake'
-require 'rake/testtask'
-require 'rake/rdoctask'
-desc 'Default: run unit tests.'
-task :default => :test
-desc 'Testing the rails indexes plugin.'
-Rake::TestTask.new(:test) do |t|
-  t.libs << 'lib'
-  t.libs << 'test'
-  t.pattern = 'test/**/*_test.rb'
-  t.verbose = true
-end
-desc 'Generate documentation for the rails_indexes plugin.'
-Rake::RDocTask.new(:rdoc) do |rdoc|
-  rdoc.rdoc_dir = 'rdoc'
-  rdoc.title    = 'RailsIndexes'
-  rdoc.options << '--line-numbers' << '--inline-source'
-  rdoc.rdoc_files.include('README')
-  rdoc.rdoc_files.include('lib/**/*.rb')
-end