refinerycms 0.9.8.9 → 0.9.9

data/vendor/refinerycms/core/config/locales/ru.yml

@@ -1,61 +0,0 @@
-ru:
-  welcome:
-    there_are_no_users: "Ни одного пользователя не создано. Вы будете первым."
-    remember_admin_location: "Запомнить администратора как:" 
-    lets_start: "Ок, давайте введем настройки для входа в систему..."
-    continue: "Далее..."
-  admin:
-    menu:
-      reorder_menu: Изменить порядок в меню
-      reorder_menu_done: Сохранить такой порядок в меню
-    search: Поиск
-    search_submit: Далее
-    search_results_for: "Результаты поиска для «{{query}}»"
-    search_no_results: Ничего не найдено
-    images:
-      existing_image:
-        submit_insert: Вставить
-  refinery:
-    other: "Иначе {{what}}"
-    reorder: "Поменять порядок {{what}}"
-    reorder_done: "Закончено {{what}}"
-    crudify:
-      created: "{{what}} создан(а)."
-      updated: "{{what}} отредактирован(а)."
-      destroyed: "{{what}} уничтожен(а)."
-  shared:
-    site_bar:
-      log_out: Выйти
-      switch_to_your_website: Перейти на сайт
-      switch_to_your_website_editor: Перейти в панель управления
-    admin:
-      message:
-        close: Закрыть
-      continue_editing:
-        save_and_continue_editing: Сохранить и продолжить
-      form_actions:
-        or: или
-        save: Сохранить
-        or_cancel: или
-        cancel: Отмена
-        or_continue: или
-        cancel_lose_changes: "Cancelling will lose all changes you've made to this {{object_name}}"
-        delete: Удалить
-        previous: Предыдущее
-        next: Следующее
-      image_picker:
-        none_selected: "There is currently no {{what}} selected, please click here to add one."
-        remove_current: "Remove current {{what}}"
-        change: Click here to pick a image
-        image: image
-        show: Show
-      resource_picker:
-        none_selected: "There is currently no {{what}} selected, please click here to add one."
-        current: "Current {{what}}"
-        download_current: "Download current {{what}}"
-        opens_in_new_window: Opens in a new window
-        remove_current: "Remove current {{what}}"
-        resource: resource
-    message:
-      close: Закрыть
-      close_this_message: Закрыть это сообщение

data/vendor/refinerycms/core/config/locales/sl.yml

@@ -1,68 +0,0 @@
-sl:
-  welcome:
-    there_are_no_users: "Trenutno še ni nobenega uporabnika, zato vas moramo najprej namestiti."
-    remember_admin_location: "Zapomnite si vaše administracijsko področje v Refinery je:"
-    lets_start: "Vredu najprej vas bomo namestili, da se boste potem lahko prijavili..."
-    continue: "Nadaljuj..."
-  admin:
-    menu:
-      reorder_menu: Spremeni vrsti red zavihkov
-      reorder_menu_done: "Končaj s prerazporeditvijo zavihkov."
-    dialogs:
-      show:
-        save: Shrani
-        cancel: Prekliči
-  refinery:
-    other: "Drugo %{what}"
-    reorder: "Spremeni vrstni red %{what}"
-    reorder_done: "Končaj s prerazporeditvijo %{what}"
-    crudify:
-      created: "%{what} je bil uspešno ustvarjen"
-      updated: "%{what} je bil uspešno ustvarjen"
-      destroyed: "%{what} je bil uspešno odstranjen"
-  shared:
-    site_bar:
-      log_out: Odjavite se
-      switch_to_your_website: "Preklopite na vašo spletno stran"
-      switch_to_your_website_editor: "Preklopite na urejevalnik spletne strani"
-    admin:
-      message:
-        close: Zapri
-      continue_editing:
-        save_and_continue_editing: "Shrani & nadaljuj z urejanjem"
-      form_actions:
-        save: Shrani
-        cancel: Prekliči
-        cancel_lose_changes: "S preklicem bodo izgubljene vse spremembe, ki ste jih naredili na %{object_name}."
-        delete: Izbriši
-        previous: Nazaj
-        next: Naprej
-        close: Zapri
-      image_picker:
-        none_selected: "Trenutno ni izbrana nobena %{what}, prosimo kliknite tukaj da dodate eno."
-        remove_current: "Odstrani trenutno %{what}"
-        change: Kliknite tukaj za izbiro slike
-        show: Prikaži
-      resource_picker:
-        none_selected: "Trenutno ni izbrana nobena %{what}, prosimo kliknite tukaj da dodate eno."
-        current: "Trenutna %{what}"
-        download_current: "Prenesi trenutno %{what}"
-        opens_in_new_window: Odpri v novem oknu
-        remove_current: "Odstrani trenutno %{what}"
-        resource: vir
-      search:
-        button_text: Išči
-        results_for: Iskalni rezultati za '%{query}'
-        no_results: Ni bilo zadetkov
-      delete:
-        message: Ali ste prepričani da želite odstraniti '%{title}'?
-      error_messages:
-        problems_in_following_fields: Prišlo je do težav v naslednjih poljih
-      help: pomoč
-    message:
-      close: Zapri
-      close_this_message: Zapri to sporočilo
-    draft_page_message:
-      not_live: Ta stran še ni javno dostopna.
-    footer:
-      copyright: Vse pravice pridržane ©

data/vendor/refinerycms/core/config/locales/zh-CN.yml

@@ -1,65 +0,0 @@
-zh-CN:
-  welcome:
-    there_are_no_users: "There are no users yet, so we'll set you up first."
-    remember_admin_location: "Remember your Refinery admin area is at:"
-    lets_start: "Alright let's get you setup so you can login..."
-    continue: "Continue..."
-  admin:
-    menu:
-      reorder_menu: Reorder menu
-      reorder_menu_done: "I'm done reordering the menu"
-    images:
-      existing_image:
-        submit_insert: Insert
-  refinery:
-    other: "Other %{what}"
-    reorder: "Reorder %{what}"
-    reorder_done: "Done Reordering %{what}"
-    crudify:
-      created: "%{what} was successfully added."
-      updated: "%{what} was successfully updated."
-      destroyed: "%{what} was successfully destroyed."
-  shared:
-    site_bar:
-      log_out: Log out
-      switch_to_your_website: Switch to your website
-      switch_to_your_website_editor: Switch to your website editor
-    admin:
-      continue_editing:
-        save_and_continue_editing: "Save & continue editing"
-      form_actions:
-        or: or
-        save: Save
-        or_cancel: or
-        cancel: Cancel
-        or_continue: or
-        cancel_lose_changes: "Cancelling will lose all changes you've made to this %{object_name}"
-        delete: Delete
-        previous: Previous
-        next: Next
-        close: Close
-      image_picker:
-        none_selected: "There is currently no %{what} selected, please click here to add one."
-        remove_current: "Remove current %{what}"
-        change: Click here to pick a image
-        image: image
-        show: Show
-      resource_picker:
-        none_selected: "There is currently no %{what} selected, please click here to add one."
-        current: "Current %{what}"
-        download_current: "Download current %{what}"
-        opens_in_new_window: Opens in a new window
-        remove_current: "Remove current %{what}"
-        resource: resource
-      search:
-        button_text: Search
-        results_for: Search results for '%{query}'
-        no_results: Sorry, no results found
-      delete:
-        message: Are you sure you want to delete '%{title}'?
-        title: Remove this %{object_name} forever
-      edit:
-        title: Edit this %{object_name}
-    message:
-      close: Close
-      close_this_message: Close this message

data/vendor/refinerycms/core/config/routes.rb

@@ -1,15 +0,0 @@
-Refinery::Application.routes.draw do
-
-  match 'wymiframe(/:id)', :to => 'refinery/fast#wymiframe', :as => :wymiframe
-
-  scope(:path => 'refinery', :as => 'admin', :module => 'admin') do
-    resources :refinery_core
-  end
-
-  match '/refinery/flash',                 :to => 'admin/refinery_core#render_flash_messages'
-  match '/refinery/update_menu_positions', :to => 'admin/refinery_core#update_plugin_positions'
-
-  scope(:path => 'refinery', :as => 'admin', :module => 'admin') do
-    resources :dialogs # FIXME: Rails 3, :only => [:show]
-  end
-end

data/vendor/refinerycms/core/crud.md

@@ -1,197 +0,0 @@
-# The Magical Mixin: Crudify (create, read, update & delete)
-
-## Introduction
-
-__Most controllers Refinery and other apps do four common things, create, read, update and delete stuff.__ Instead of writing the same logic for these actions over and over again we wrap all this functionality up into what we called ``crudify``.
-
-``crudify`` takes these four basic actions and extends them to allow easy paging, searching and sorting too.
-
-Although this single file is included in Refinery, you could take just this single file and use it in any app you like.
-
-The best part about ``crudify`` is that this gives you a smart default and if there is anything you want to work differently just override that method.
-
-## Where is it located?
-
-``vendor/refinerycms/core/lib/refinery/crud.rb``
-
-## How do I use it in my engines?
-
-All you need to do is call ``crudify`` in your controller.
-
-If you used the Refinery generator you're plugin will already be using ``crudify``.
-
-### Example
-
-    class NewsItemsController < ApplicationController
-
-      crudify :news_item, :order => "created_at DESC"
-
-    end
-
-### Complex Example
-
-    class NewsItemsController < ApplicationController
-
-      crudify :news_item, :order => "created_at DESC",
-                          :conditions => 'published = true',
-                          :sortable => false,
-                          :searchable => true,
-                          :include => [:author],
-                          :paging => true,
-                          :search_conditions => ''
-
-    end
-
-## What can you configure with ``crudify``?
-
-### ``:title_attribute``
-
-Default value is ``title``
-
-This is the human readable value you want ``crudify`` to use throughout. Just choose an attribute that is on your model that is short and descriptive to what the model is.
-
-#### Example
-
-On a page model you'd probably use "title" (which is default so you don't need to specify this)
-
-#### Example 2
-
-On a ``team_member`` model you'd probably want to use an attribute like ``name``.
-
-### ``:order``
-
-Default value is ``position ASC``
-
-This is the position that is used when listing out what you're crudifying. If you have ``:sortable`` set to ``true`` you probably want to have your ``:order`` set to ``position ASC`` so it uses the order you have set when sorting.
-
-If you have a news area, it makes more sense to sort by ``posted_at``. So you might set it like this
-
-    :order => "posted_at DESC"
-
-### ``:conditions``
-
-Default value is ``nil``
-
-This will filter down the list of items you have when you're asking for all records.
-
-An example here is say you're crudifying a photos table that uses attachment_fu. Attachment_fu creates several photo records, 1 for the main photo and others for it's "children" thumbnails. Those thumbnails have a parent id set.
-
-So when viewing a list of the images you have you don't want it to show all the thumbnails too, you just want to each see unique image listed so you need to apply some conditions to hide the thumbnails.
-
-You do that like this:
-
-    :conditions => {:parent_id => nil}
-
-### ``:sortable``
-
-Default value is ``true``
-
-Enabling ``:sortable`` gives you several handy methods which "just work" with sortable JavaScript lists. One of the methods is ``update_positions()`` which handles saving the new position items have been sorted into.
-
-### ``:searchable``
-
-Default value is ``true``
-
-When this option is ``true``, the routes are modified so when you go to the next page of results the search continues on.
-
-### ``:include``
-
-Default value is ``[]``
-
-For performance optimisation, sometimes you might want to eager load other related models to this one. For example a ``news_post`` might below to a ``user`` who wrote the post. But in our index view we're printing out the name of each user.
-
-Instead of having to look up each user for each of the ``news_posts`` we iterate over, the ``:include`` option allows you to load the ``news_post`` and user all at the same time which'll allow you to save on expensive database queries.
-
-Here's an example of that.
-
-    class NewsItem
-
-      belongs_to :user
-
-    end
-
-    class NewsItemsController < ApplicationController
-
-      crudify :news_item, :order => "created_at DESC", :include => [:user]
-
-    end
-
-### ``:paging``
-
-Default value is ``true``
-
-The ``:paging`` option tells ``crudify`` you don't just want one big long list but rather to break it out into pages and support paging methods uses [will_paginate](http://wiki.github.com/mislav/will_paginate/).
-
-### ``:search_conditions``
-
-Default value is ``nil``
-
-Similar to the ``:conditions`` options, ``:search_conditions`` just apply these conditions when delivering search results.
-
-## Easy Accessor Methods
-
-``crudify`` automatically writes up finder methods for the model you're crudifying. The easier way to explain this is with an example.
-
-Say we have a pages controller that is going to manage pages.
-
-    class PagesController < ApplicationController
-
-      crudify :page
-
-    end
-
-In this controller, automatically I have these methods:
-
-    find_page()
-    find_all_pages()
-
-So say I wanted to change the way all pages are found, all I do is override the ``find_all_pages`` method.
-
-    class PagesController < ApplicationController
-
-      crudify :page
-
-      def find_all_pages
-        @pages = Page.find(...) # apply any logic I want here to get all pages.
-      end
-
-    end
-
-## Overriding or Extending Crudify
-
-Before overriding anything, the best thing to do is check out how the default works. Read the ``vendor/plugins/refinery/lib/crud.rb`` and see what code it's injecting into your controller.
-
-Pick the method you want to override and then override it in your controller.
-
-Let's go back to the example above with the pages controller.
-
-    class PagesController < ApplicationController
-
-      crudify :page
-
-    end
-
-Say every time someone deletes a page I want my ``NotificationMailer`` to email me to say someone just deleted a page.
-
-When I look in the ``crud.rb`` file I see that my controller has this added to it
-
-    def destroy
-      flash[:notice] = "'\#{@#{singular_name}.#{options[:title_attribute]}}' was successfully deleted." if @#{singular_name}.destroy
-      redirect_to admin_#{plural_name}_url
-    end
-
-To override this all I would is create my own delete method that works the same but just with my mailer code on it.
-
-    class PagesController < ApplicationController
-
-      crudify :page
-
-      def destroy
-        if @page.destroy
-          flash[:notice] = "'#{@page.title}' was successfully deleted."
-          NotificationMailer.deliver_page_deleted(@page) # sends me an email to say a page was deleted
-        end
-        redirect_to admin_pages_url
-      end
-
-    end

data/vendor/refinerycms/core/engines.md

@@ -1,218 +0,0 @@
-# Extending Refinery with Engines
-
-## Introduction
-
-__Refinery is designed to be easily extended so you can quickly customise your Refinery site to manage new areas you want to add to your site. If you see something you want to customise, the chances are you can customise it.__
-
-The main way of extending Refinery is through adding new engines to your app. By default you can edit pages in Refinery's backend, but how do you add a new section to manage like products?
-
-## The Refinery Generator
-
-The Refinery generator is a standard Rails generator that functions just like the scaffold generator. It allows you to quickly add new managed sections to the Refinery backend and get the front end views for free.
-
-To see how to use the generator run
-
-    rails generate refinery_engine
-
-Usage instructions should appear.
-
-## Example of Using the Generator
-
-Let's say you have a client who has a range of products they want to show on their website. You've considered using a few pages to manage the products but you've decided it would be much nicer if there was a separate place that had forms dedicated to managing products.
-
-First decide what fields they need to manage. In our case, the client is going to want to edit the title and description of each product. They would also like a little "facts panel" to show on the right of the page.
-
-So go to the root of your project and run
-
-    rails generate refinery_engine
-
-This will output the help on how to use the generator. To generate the new section we want to manage products we run:
-
-    rails generate refinery_engine product title:string description:text image:image brochure:resource
-
-The generator will output a list of files it generated. You'll notice there is a new engine that has been added in ``vendor/engines/products``. This is where both the backend and front end files are held for this new products area.
-
-Engines are treated like gems. When you generate a new engine it adds the gem dependency for this engine to the end of your ``Gemfile``. Because your ``Gemfile`` has changed you now need to run:
-
-    bundle install
-    
-When the products engine was generated a products generator was also created. This installs any migrations and seeds into your Rails app. Here's how to finish off the install
-
-    rails generate refinerycms_products
-    rake db:migrate
-
-Start up your app by running ``ruby script/server`` go to [http://localhost:3000](http://localhost:3000) and you'll see instantly a new menu item called "products". Click on that and you'll see there are no products yet.
-
-Now go to the backend of your site by visiting [http://localhost:3000/refinery](http://localhost:3000/refinery) and logging in. You'll see a new tab called "Products", click on that and then click "Add a new product", fill the form and add an example product. Now go back to the front end and you'll see your product is showing up in the products part of your site.
-
-Now you have a fully managed products section in Refinery, nice.
-
-If you want to modify your generated engine you need to understand the basic structure of how they work.
-
-## The Structure of an Engine
-
-Think of a engine in Refinery as a small Rails app. Engines have a structure that is extremely similar to a Rails app. Here's an example of Refinery's pages engine (located in Refinery's ``vendor/refinerycms/pages/`` folder)
-
-    pages
-      |- app
-      |   |- controllers
-      |   |   |- admin
-      |   |   |    |- pages_dialogs_controller.rb
-      |   |   |    |- page_parts_controller.rb
-      |   |   |    |- pages_controller.rb
-      |   |   |- pages_controller.rb
-      |   |- helpers
-      |   |   |- pages_helper.rb
-      |   |- models
-      |   |   |- page.rb
-      |   |- views
-      |       |- pages
-      |       |   |- home.html.erb
-      |       |   |- show.html.erb
-      |       |- admin
-      |           |- pages
-      |               |- _form.html.erb
-      |               |- edit.html.erb
-      |               |- index.html.erb
-      |               |- new.html.erb
-      |- config
-      |   |- routes.rb
-      |- rails
-          |- init.rb
-
-
-### app/controllers
-
-In this example you see one "public" controller ``app/controllers/pages_controller`` that is responsible for managing the front end when I view a page.
-
-### app/controllers/admin
-
-This bit is important. It's where all the controllers are held to manage pages in the Refinery back end in this example. You can ignore the ``pages_dialogs_controller.rb`` and ``page_parts_controller.rb`` for now and let's just focus on the ``admin/pages_controller.rb`` file. Here's what that looks like inside at a basic level:
-
-    class Admin::PagesController < Admin::BaseController
-
-      crudify :page, :conditions => {:parent_id => nil},
-                     :order => "position ASC", :paging => false
-
-    end
-
-This single controller allows us to create, read, update and delete pages in the backend. With a little bit of Refinery magic we utilise the [crudify mixin](http://github.com/resolve/refinerycms/blob/master/vendor/refinerycms/core/crud.md) which gives us all of these regular features out of the box.
-
-How crudify works is an entire topic of it's own. Checkout the [crudify documentation](http://github.com/resolve/refinerycms/blob/master/vendor/refinerycms/core/crud.md) to get an insight into how that works.
-
-### app/views and app/helpers
-
-Works exactly the same as ``app/views`` and ``app/helpers`` in a normal Rails app. You just put the views and helpers related to this engine in here instead of in your actual main app directory.
-
-### config/routes.rb
-
-Works exactly the same as ``config/routes.rb`` in your app except this routes file only loads the routes for this engine.
-
-### rails/init.rb
-
-This file runs when your site is started up. All is does is registers this engine with Refinery so it knows that it exists, how to handle it in the Refinery admin menu and how to render recent activity on the Dashboard (see "Getting your Engine to Report Activity in the Dashboard")
-
-NOTE: The latest version of Refinery requires that you only specify a engine.name. plugin.title &amp; plugin.description will be looked up by the I18n system.
-
-# pages/lib/pages.rb
-    Refinery::Plugin.register do |plugin|
-      plugin.name = "pages"
-      plugin.version = 1.0
-      plugin.menu_match = /(refinery|admin)\/page(_dialog|part)?s$/
-      plugin.activity = {
-        :class => Page,
-        :url_prefix => "edit_",
-        :title => "title",
-        :created_image => "page_add.png",
-        :updated_image => "page_edit.png"
-      }
-    end
-
-# pages/config/locales/en.yml
-    en:
-      plugins:
-        refinery_pages:
-          title: Pages
-          description: Manage content pages
-
-## Getting your Engine to Report Activity in the Dashboard
-
-Recent activity reporting is built right in, so all you need to do is follow the convention below and your engine will start showing up in the recent activity list of the Dashboard.
-
-In our example above we showed the use of ``plugin.activity`` for the pages engine.
-
-    Refinery::Plugin.register do |plugin|
-      plugin.name = "pages"
-      plugin.version = 1.0
-      plugin.menu_match = /(refinery|admin)\/page(_dialog|part)?s$/
-      plugin.activity = {
-        :class => Page,
-        :url_prefix => "edit_",
-        :title => "title",
-        :created_image => "page_add.png",
-        :updated_image => "page_edit.png"
-      }
-    end
-
-Here's what the different activity options mean:
-
-### Required
-
-    :class
-    # the name of the class we're watching.
-
-    :url_prefix
-    # Just use "edit_" if you're not sure how this works.
-    #
-    # When it says "'About' page was updated about 4 hours ago", the page title "About"
-    # is linked to that page in a way we specify.  So by setting "_edit" as a :url_prefix what
-    # we're doing is making it link to the page that allows us to edit this page.
-    # So the next result is edit_admin_page_url(page)
-
-    :title
-    # which attribute on the :class should be in the activty message. In our case it's "title"
-    # because we want it to run something like this "#{page.title} was updated about ...."
-
-### Optional
-
-    :created_image and :updated_image
-    # the activity monitor knows if something is created or updated and shows a different icon
-    # depending on how you want that to look. You can specify the filename to any image you
-    # want in the public/images/refinery/icons/ directory.
-
-## Search Engine Optimisation: Improving the default URLs
-
-In our example above we extended Refinery to manage a products area. The problem is when I look at a product on the front end I get a URL like [http://localhost:3000/products/1](http://localhost:3000/products/1) but I would really like it to be something like [http://localhost:3000/products/my-product](http://localhost:3000/products/my-product)
-
-To achieve this all you need to do is open up the product model (found in ``/vendor/plugins/products/app/models/product.rb``) and add the following line inside your class:
-
-    has_friendly_id :title, :use_slug => true
-
-Note you want to change ``:title`` to the field which you want to show up in the URL.
-
-This will work just fine for new products added from this point, but you'll want to migrate any existing products you have to use this new URL format. All you have to do is save each product you have in the database to make it create a nice URL for you.
-
-    ruby script/console
-    >> Product.all.each {|p| p.save };nil
-
-Now all the products in your database will have nice URLs.
-
-## How to get a WYSIWYG editor to show on your form fields
-
-Refinery uses a standards compliant visual editor called [WYMeditor](http://www.wymeditor.org/)
-
-_Note: When using the Refinery generator, if you apply a field type of "text" to any of your fields, they automatically load as a WYMEditor._
-
-The WYSIWYG editor can only be applied to a ``textarea``. All you need to do is add a class of "wymeditor widest" to a ``textarea`` in your form and a WYSIWYG WYMEditor will load right in place.
-
-### Example
-
-Again going back to our product plugin example if you had this in your ``vendor/plugins/products/app/views/admin/products/_form.html.erb`` file:
-
-    <%= f.text_area :description %>
-
-Just change that to:
-
-    <%= f.text_area :description, :class => "wymeditor widest" %>
-
-Refresh and you're done.