RubyGems - locomotivecms - Versions diffs - 3.0.0.rc3 → 3.0.0.rc4 - Mend

locomotivecms 3.0.0.rc3 → 3.0.0.rc4

Files changed (126) hide show

checksums.yaml +4 -4
data/Gemfile +3 -3
data/README.md +1 -1
data/app/assets/stylesheets/locomotive/unauthorized/_public.scss +7 -4
data/app/controllers/locomotive/errors_controller.rb +4 -0
data/app/helpers/locomotive/errors_helper.rb +2 -4
data/app/models/locomotive/concerns/content_entry/csv.rb +4 -0
data/app/models/locomotive/concerns/content_entry/slug.rb +0 -2
data/app/models/locomotive/concerns/content_type/sync.rb +2 -2
data/app/models/locomotive/concerns/page/templatized.rb +1 -1
data/app/models/locomotive/concerns/site/access_points.rb +3 -3
data/app/models/locomotive/theme_asset.rb +0 -1
data/app/views/locomotive/developers_documentation/_wagon.html.slim +2 -2
data/app/views/locomotive/devise_mailer/reset_password_instructions.html.slim +1 -0
data/app/views/locomotive/errors/no_site.json +1 -0
data/app/views/locomotive/shared/_sidebar.html.slim +1 -1
data/app/views/locomotive/shared/_sidebar_without_site.html.slim +1 -1
data/app/views/locomotive/shared/header/_account_menu.html.slim +2 -2
data/config/locales/en.yml +1 -1
data/config/routes.rb +4 -2
data/lib/generators/locomotive/install/install_generator.rb +9 -9
data/lib/generators/locomotive/install/templates/carrierwave.rb +23 -12
data/lib/generators/locomotive/install/templates/carrierwave_aws.rb +36 -0
data/lib/generators/locomotive/install/templates/mongoid.yml +97 -35
data/lib/locomotive/dependencies.rb +1 -1
data/lib/locomotive/middlewares/site.rb +10 -4
data/lib/locomotive/mongoid/patches.rb +1 -1
data/lib/locomotive/steam_adaptor.rb +6 -4
data/lib/locomotive/version.rb +1 -1
data/spec/dummy/config/application.rb +0 -3
data/spec/dummy/config/initializers/devise.rb +128 -58
data/spec/dummy/config/mongoid.yml +95 -78
data/spec/models/locomotive/content_entry_spec.rb +6 -6
data/spec/requests/locomotive/steam/cache_spec.rb +1 -1
data/spec/requests/site_spec.rb +25 -0
data/spec/support/mongoid.rb +2 -0
metadata +16 -189
data/features/api/accounts.feature +0 -43
data/features/api/authentication.feature +0 -41
data/features/api/authorization/accounts.feature +0 -165
data/features/api/authorization/content_assets.feature +0 -147
data/features/api/authorization/content_entries.feature +0 -202
data/features/api/authorization/content_types.feature +0 -237
data/features/api/authorization/current_site.feature +0 -30
data/features/api/authorization/memberships.feature +0 -225
data/features/api/authorization/pages.feature +0 -189
data/features/api/authorization/sites.feature +0 -212
data/features/api/authorization/snippets.feature +0 -179
data/features/api/authorization/theme_assets.feature +0 -185
data/features/api/authorization/translations.feature +0 -253
data/features/api/content_entries.feature +0 -184
data/features/api/content_types.feature +0 -156
data/features/api/editable_elements.feature +0 -190
data/features/api/entries_custom_fields.feature +0 -150
data/features/api/memberships.feature +0 -26
data/features/api/pages.feature +0 -72
data/features/backoffice/authorization/account_settings.feature +0 -28
data/features/backoffice/authorization/content_type.feature +0 -35
data/features/backoffice/authorization/current_site.feature +0 -53
data/features/backoffice/authorization/inline_front_end_editing.feature +0 -46
data/features/backoffice/authorization/pages.feature +0 -95
data/features/backoffice/authorization/theme_assets.feature +0 -50
data/features/backoffice/content_types/edit.feature +0 -20
data/features/backoffice/content_types/email.feature +0 -26
data/features/backoffice/content_types/has_many.feature +0 -80
data/features/backoffice/content_types/integer.feature +0 -26
data/features/backoffice/content_types/localized.feature +0 -63
data/features/backoffice/content_types/many_to_many.feature +0 -70
data/features/backoffice/content_types/tags.feature +0 -22
data/features/backoffice/content_types/uniqueness.feature +0 -29
data/features/backoffice/contents.feature +0 -93
data/features/backoffice/editable_elements.feature +0 -22
data/features/backoffice/installation.feature +0 -33
data/features/backoffice/login.feature +0 -33
data/features/backoffice/mounting.feature +0 -13
data/features/backoffice/my_account.feature +0 -22
data/features/backoffice/pages.feature +0 -73
data/features/backoffice/regressions.feature +0 -19
data/features/backoffice/site.feature +0 -71
data/features/backoffice/snippets.feature +0 -39
data/features/backoffice/theme_assets.feature +0 -72
data/features/backoffice/translations.feature +0 -50
data/features/public/basic.feature +0 -30
data/features/public/contact_form.feature +0 -98
data/features/public/content_entries.feature +0 -69
data/features/public/editable_elements.feature +0 -138
data/features/public/has_many.feature +0 -8
data/features/public/inheritance.feature +0 -157
data/features/public/inline_front_end_editing.feature +0 -26
data/features/public/many_to_many.feature +0 -64
data/features/public/new_contact_form.feature +0 -95
data/features/public/pages.feature +0 -116
data/features/public/pagination.feature +0 -8
data/features/public/robots.feature +0 -22
data/features/public/session.feature +0 -40
data/features/public/sitemap.feature +0 -74
data/features/public/snippets.feature +0 -21
data/features/public/tablerow.feature +0 -42
data/features/public/tags.feature +0 -45
data/features/step_definitions/api_steps.rb +0 -179
data/features/step_definitions/backoffice/mounting_steps.rb +0 -22
data/features/step_definitions/backoffice_steps.rb +0 -47
data/features/step_definitions/content_assets_steps.rb +0 -12
data/features/step_definitions/content_types_steps.rb +0 -135
data/features/step_definitions/current_site_steps.rb +0 -43
data/features/step_definitions/editable_elements_steps.rb +0 -24
data/features/step_definitions/membership_steps.rb +0 -19
data/features/step_definitions/more_web_steps.rb +0 -131
data/features/step_definitions/page_steps.rb +0 -133
data/features/step_definitions/pagination_steps.rb +0 -35
data/features/step_definitions/pickle_steps.rb +0 -100
data/features/step_definitions/relationships_steps.rb +0 -110
data/features/step_definitions/site_steps.rb +0 -111
data/features/step_definitions/snippet_steps.rb +0 -37
data/features/step_definitions/theme_asset_steps.rb +0 -64
data/features/step_definitions/translation_steps.rb +0 -7
data/features/step_definitions/web_steps.rb +0 -225
data/features/step_definitions/within_steps.rb +0 -14
data/features/support/cleaner.rb +0 -4
data/features/support/env.rb +0 -82
data/features/support/factory_girl.rb +0 -2
data/features/support/http.rb +0 -22
data/features/support/locales.rb +0 -5
data/features/support/paths.rb +0 -62
data/features/support/pickle.rb +0 -24
data/features/support/selectors.rb +0 -57

data/features/public/new_contact_form.feature DELETED Viewed

@@ -1,95 +0,0 @@
-Feature: Contact form [New way]
-  As a visitor
-  In order to keep in touch with the site
-  I want to be able to send them a message
-  Background:
-    Given I enable the CSRF protection for public submission requests
-    Given I have the site: "test site" set up
-    And I have a custom model named "Messages" with
-      | label       | type      | required    |
-      | Email       | string    | true        |
-      | Message     | text      | true        |
-      | Category    | select    | true        |
-    And I have "Design, Code, Business" as "Category" values of the "Messages" model
-    And I enable the public submission of the "Messages" model
-    And a page named "contact" with the template:
-      """
-      <html>
-        <head></head>
-        <body>
-          {% if message %}Thanks {{ message.email }}{% endif %}
-          {% model_form "messages" %}
-            <label for="email">E-Mail Address</label>
-            <input type="text" id="email" name="content[email]" />
-            {% if message.errors.email %}Email is required{% endif %}
-            <label for="category">Category</label>
-            <select id="category" name="content[category]">
-              <option value=""></option>
-              {% for name in contents.messages.category_options %}
-              <option value="{{ name }}">{{ name }}</option>
-              {% endfor %}
-            </select>
-            <label for="message">Message</label>
-            <textarea name="content[message]" id="message"></textarea>
-            <input name="submit" type="submit" id="submit" value="Submit" />
-          {% endmodel_form %}
-        </body>
-      </html>
-      """
-    And a page named "contact_with_redirection" with the template:
-      """
-      <html>
-        <head></head>
-        <body>
-          {% model_form "messages", success: "/success" %}
-            <label for="email">E-Mail Address</label>
-            <input type="text" id="email" name="content[email]" />
-            {% if message.errors.email %}Email is required{% endif %}
-            <label for="category">Category</label>
-            <select id="category" name="content[category]">
-              <option value=""></option>
-              {% for name in contents.messages.category_options %}
-              <option value="{{ name }}">{{ name }}</option>
-              {% endfor %}
-            </select>
-            <label for="message">Message</label>
-            <textarea name="content[message]" id="message"></textarea>
-            <input name="submit" type="submit" id="submit" value="Submit" />
-          {% endmodel_form %}
-        </body>
-      </html>
-      """
-    And a page named "success" with the template:
-      """
-      Thanks {{ message.email }}!
-      """
-  Scenario: Use the url of the current page for the contact form
-    When I view the rendered page at "/contact"
-    Then the rendered output should look like:
-      """
-      <form method="POST" enctype="multipart/form-data">
-      """
-  Scenario: Sending a message with success
-    When I view the rendered page at "/contact"
-    And I fill in "E-Mail Address" with "did@locomotivecms.com"
-    And I fill in "Message" with "LocomotiveCMS rocks"
-    And I select "Code" from "Category"
-    And I press "Submit"
-    Then I should see "Thanks did@locomotivecms.com"
-  Scenario: Display errors
-    When I view the rendered page at "/contact"
-    And I fill in "Message" with "LocomotiveCMS rocks"
-    And I press "Submit"
-    Then I should see "Email is required"
-  Scenario: Redirection after success
-    When I view the rendered page at "/contact_with_redirection"
-    And I fill in "E-Mail Address" with "estelle@locomotivecms.com"
-    And I fill in "Message" with "LocomotiveCMS rocks"
-    And I select "Code" from "Category"
-    And I press "Submit"
-    Then I should see "Thanks estelle@locomotivecms.com!"

data/features/public/pages.feature DELETED Viewed

@@ -1,116 +0,0 @@
-Feature: Pages
-  As a designer
-  In order to improve my site navigation
-  I want to list its pages
-Background:
-  Given I have the site: "test site" set up with name: "test site"
-Scenario: List all of them
-  Given a page named "all" with the template:
-    """
-    {% for page in site.pages %}{{ page.title }}, {% endfor %}
-    """
-  When I view the rendered page at "/all"
-  Then the rendered output should look like:
-    """
-    Home page, Page not found, All,
-    """
-Scenario: Scoped listing
-  Given a page named "hidden-page" with the template:
-    """
-    Hidden content
-    """
-  And the page "hidden-page" is unpublished
-  And a page named "hidden-pages" with the template:
-    """
-    {% with_scope published: false %}
-      {% for page in site.pages %}{{ page.slug }}, {% endfor %}
-    {% endwith_scope %}
-    """
-  When I view the rendered page at "/hidden-pages"
-  Then the rendered output should look like:
-    """
-    hidden-page,
-    """
-Scenario: link_to tag
-  Given the site "test site" has locales "en, es"
-  And a page named "about-us" with the handle "about-us"
-  And the page named "about-us" has the title "Acerca de" in the "es" locale
-  And a page named "page-with-links" with the template:
-    """
-    {% locale_switcher %}
-    {% link_to about-us %}
-    {% link_to about-us, locale: es %}
-    {% link_to about-us %}
-      <i class="icon-info-sign"></i> {{ target.title }}
-    {% endlink_to %}
-    """
-  And the page named "page-with-links" has the title "Página con links" in the "es" locale
-  When I view the rendered page at "/page-with-links"
-  Then the rendered output should look like:
-    """
-    <a href="/about-us">About us</a>
-    <a href="/es/acerca-de">Acerca de</a>
-    <a href="/about-us">
-      <i class="icon-info-sign"></i> About us
-    </a>
-    """
-  When I follow "es"
-  Then the rendered output should look like:
-    """
-    <a href="/es/acerca-de">Acerca de</a>
-    <a href="/es/acerca-de">Acerca de</a>
-    <a href="/es/acerca-de">
-      <i class="icon-info-sign"></i> Acerca de
-    </a>
-    """
-Scenario: link_to templatized page
-  Given I have a custom model named "Articles" with
-      | label       | type      | required    |
-      | Title       | string    | true        |
-  And I have entries for "Articles" with
-    | title             |
-    | Hello world       |
-  And a templatized page for the "Articles" model and with the template:
-    """
-    Here is the title: "{{ article.title }}"
-    """
-  And a page named "page-with-links" with the template:
-    """
-    {% for article in contents.articles %}
-      Link to article: {% link_to article %}
-    {% endfor %}
-    """
-  When I view the rendered page at "/page-with-links"
-  And I follow "Hello world"
-  Then the rendered output should look like:
-  """
-  Here is the title: "Hello world"
-  """
-Scenario: Default locale fallback
-  Given the site "test site" has locales "en, es"
-  And a page named "only-english" with the template:
-    """
-    Only english, please
-    """
-  When I view the rendered page at "/es/only-english"
-  Then I should see "Only english, please"
-Scenario: fetch_page tag
-  Given a page named "print-the-slug-of-a-page" with the template:
-    """
-    {% fetch_page this-is-the-page-handle as my_page %}
-    {{ my_page.slug }}
-    """
-  And a page named "this-is-the-slug" with the handle "this-is-the-page-handle"
-  When I view the rendered page at "/print-the-slug-of-a-page"
-  Then the rendered output should look like:
-    """
-    this-is-the-slug
-    """

data/features/public/pagination.feature DELETED Viewed

@@ -1,8 +0,0 @@
-Feature: Pagination
-  As a designer
-  In order to display a sensible amount of items per page
-  I want to be able to paginate through models
-  Scenario: Paginating through a model
-    Given I have a site set up
-    Then I should be able to display paginated models

data/features/public/robots.feature DELETED Viewed

@@ -1,22 +0,0 @@
-Feature: Robots
-  As a designer
-  I want to be able to define a robots.txt file for my site
-Background:
-  Given I have the site: "test site" set up
-Scenario: Simple robots text
-  Given a robot_txt set to "robots text value"
-  When I view the rendered page at "/robots.txt"
-  Then the rendered output should look like:
-    """
-    robots text value
-    """
-Scenario: Robots.txt should provide access to request_host and all other liquid variables
-  Given a robot_txt set to "host: {{request_host}} path: {{path}}"
-  When I view the rendered page at "/robots.txt"
-  Then the rendered output should look like:
-    """
-    host: test.example.com path: /robots.txt
-    """

data/features/public/session.feature DELETED Viewed

@@ -1,40 +0,0 @@
-Feature: Session
-  As a designer
-  I want to record objects in the session and reach them later
-Background:
-  Given I have the site: "test site" set up
-  And a page named "store" with the template:
-    """
-    Store a string in the session. {% session_assign foo = 'monkey' %}
-    """
-  And a page named "retrieve" with the template:
-    """
-    Retrieve a string from the session: {{ session.foo }}.
-    """
-  And a page named "release" with the template:
-    """
-    Remove a string from the session. {% session_assign foo = null %}
-    """
-Scenario: Store and retrieve a string in session
-  When I view the rendered page at "/retrieve"
-  Then the rendered output should look like:
-    """
-    Retrieve a string from the session: .
-    """
-  When I view the rendered page at "/store"
-  And I view the rendered page at "/retrieve"
-  Then the rendered output should look like:
-    """
-    Retrieve a string from the session: monkey.
-    """
-Scenario: Remove a object from the session
-  When I view the rendered page at "/store"
-  And I view the rendered page at "/release"
-  And I view the rendered page at "/retrieve"
-  Then the rendered output should look like:
-    """
-    Retrieve a string from the session: .
-    """

data/features/public/sitemap.feature DELETED Viewed

@@ -1,74 +0,0 @@
-Feature: Sitemap
-  As a designer
-  I want to have an automatically generated sitemap
-Background:
-  Given I have the site: "test site" set up
-Scenario: Simple sitemap
-  Given a page named "about" with the template:
-    """
-    <html>
-      <body>About us</body>
-    </html>
-    """
-  When I go to the sitemap
-  Then the response status should be 200
-  And I should see the following xml output:
-    """
-    <?xml version="1.0" encoding="UTF-8"?>
-    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
-      <url>
-        <loc>http://test.example.com:9886</loc>
-        <priority>1.0</priority>
-      </url>
-      <url>
-        <loc>http://test.example.com:9886/about</loc>
-        <lastmod>:now</lastmod>
-        <priority>0.9</priority>
-      </url>
-    </urlset>
-    """
-Scenario: Templatized page
-  Given I have a custom model named "Articles" with
-      | label       | type      | required    |
-      | Title       | string    | true        |
-      | Body        | text      | true        |
-  And I have entries for "Articles" with
-    | title             | body                    |
-    | Hello world       | Lorem ipsum             |
-    | Lorem ipsum       | Lorem ipsum...          |
-  And a templatized page for the "Articles" model and with the template:
-    """
-    <html>
-      <body>Template for an article</body>
-    </html>
-    """
-  When I go to the sitemap
-  Then the response status should be 200
-  And I should see the following xml output:
-    """
-    <?xml version="1.0" encoding="UTF-8"?>
-    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
-      <url>
-        <loc>http://test.example.com:9886</loc>
-        <priority>1.0</priority>
-      </url>
-      <url>
-        <loc>http://test.example.com:9886/articles</loc>
-        <lastmod>:now</lastmod>
-        <priority>0.9</priority>
-      </url>
-      <url>
-        <loc>http://test.example.com:9886/articles/hello-world</loc>
-        <lastmod>:now</lastmod>
-        <priority>0.9</priority>
-      </url>
-      <url>
-        <loc>http://test.example.com:9886/articles/lorem-ipsum</loc>
-        <lastmod>:now</lastmod>
-        <priority>0.9</priority>
-      </url>
-    </urlset>
-    """

data/features/public/snippets.feature DELETED Viewed

@@ -1,21 +0,0 @@
-Feature: Snippets
-  As a designer
-  I want to insert re-usable piece of code among pages
-Background:
-  Given I have the site: "test site" set up
-  And a snippet named "yield" with the template:
-    """
-    HELLO WORLD !
-    """
-Scenario: Simple include
-  Given a page named "hello-world" with the template:
-    """
-    My application says {% include 'yield' %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says HELLO WORLD !
-    """

data/features/public/tablerow.feature DELETED Viewed

@@ -1,42 +0,0 @@
-Feature: TableRow liquid tags
-  As a designer
-  I want to be able to use the tablerow liquid tag with locomotive contents
-Background:
-  Given I have the site: "test site" set up
-  And I have a custom model named "Projects" with
-    | label         | type      | required  |
-    | Name          | string    | true      |
-  And I have entries for "Projects" with
-    | name        | _position |
-    | Project 1   | 1         |
-    | Project 2   | 2         |
-    | Project 3   | 3         |
-Scenario: Use the tablerow tag
-  Given a page named "project-table" with the template:
-    """
-    <h1>Projects</h1>
-    <table>
-    {% tablerow project in contents.projects cols: 2 %}
-    {{ project.name }}
-    {% endtablerow %}
-    </table>
-    """
-  When I view the rendered page at "/project-table"
-  Then the rendered output should look like:
-    """
-    <h1>Projects</h1>
-    <table>
-    <tr class="row1">
-    <td class="col1">
-    Project 1
-    </td><td class="col2">
-    Project 2
-    </td></tr>
-    <tr class="row2"><td class="col1">
-    Project 3
-    </td></tr>
-    </table>
-    """

data/features/public/tags.feature DELETED Viewed

@@ -1,45 +0,0 @@
-Feature: Tagged content
-  As a designer
-  In order to organize my content
-  I want to be able to tag it
-Background:
-  Given I have the site: "test site" set up
-  And I have a custom model named "Posts" with
-    | label         | type      | required    |
-    | Title         | string    | true        |
-    | Body          | string    | false       |
-    | Tags          | tags      | false       |
-  And I have entries for "Posts" with
-    | title             | body          | tags              |
-    | Fashion post      | Fashion body  | blogging, fashion |
-    | Diet post         | Diet body     | blogging, diet    |
-Scenario: Navigate by tags
-  Given a page named "my-posts" with the template:
-    """
-    {% if params.tag %}
-     {% with_scope tags: params.tag %}
-       {% assign posts = contents.posts.all %}
-     {% endwith_scope %}
-    {% else %}
-     {% assign posts = contents.posts.all %}
-    {% endif %}
-    {% for post in posts %}
-     {{ post.title }}<br>
-     {% for tag in post.tags %}
-     <a href="/my-posts?tag={{ tag }}">{{ tag }}</a>
-     {% endfor %}
-     <hr>
-    {% endfor %}
-    """
-  When I view the rendered page at "/my-posts"
-  Then I should see "Fashion post"
-  And I should see "Diet post"
-  When I follow "blogging"
-  Then I should see "Fashion post"
-  And I should see "Diet post"
-  When I follow "fashion"
-  Then I should see "Fashion"
-  And I should not see "Diet"

data/features/step_definitions/api_steps.rb DELETED Viewed

@@ -1,179 +0,0 @@
-def api_base_url
-  "http://#{Locomotive::Site.first.domains.first}/locomotive/api/"
-end
-def do_api_request(type, url, param_string_or_hash = nil)
-  begin
-    if param_string_or_hash
-      if param_string_or_hash.is_a? Hash
-        params = param_string_or_hash
-      else
-        # Do memory substitution from json_spec
-        params = JSON.parse(JsonSpec.remember(param_string_or_hash))
-      end
-    else
-      params = {}
-    end
-    transform_filenames_to_fixtured_files(params)
-    @json_response = do_request(type, api_base_url, url,
-                               params.merge({ 'CONTENT_TYPE' => 'application/json' }))
-  rescue Pundit::NotAuthorizedError, Mongoid::Errors::DocumentNotFound
-    @error = $!
-  end
-end
-def last_json
-  @json_response.try(:body) || page.source
-end
-def last_status
-  @json_response.try(:status) || page.status
-end
-# Deal with file fields
-def file_fields
-  @file_fields ||= []
-end
-def add_file_field(json_path)
-  file_fields << json_path
-end
-def get_field_at_path(hash, path)
-  val = hash
-  path.split('/').each do |key|
-    if val.is_a?(Array)
-      val = val[key.to_i]
-    elsif val.has_key?(key)
-      val = val[key]
-    else
-      return nil
-    end
-  end
-  val
-end
-def set_field_at_path(hash, path, value)
-  obj = hash
-  keys = path.split('/')
-  last_key = keys.slice!(-1)
-  keys.each do |key|
-    if obj.is_a?(Array)
-      obj = obj[key.to_i]
-    else
-      obj = obj[key]
-    end
-  end
-  obj[last_key] = value
-end
-def transform_filenames_to_fixtured_files(params)
-  file_fields.each do |path|
-    filename = get_field_at_path(params, path)
-    return unless filename
-    file = Rack::Test::UploadedFile.new(Rails.root.join('..', 'fixtures', filename))
-    set_field_at_path(params, path, file)
-  end
-end
-Given /^I have an? "([^"]*)" API token$/ do |role|
-  @membership = Locomotive::Site.first.memberships.where(:role => role.downcase).first \
-    || FactoryGirl.create(role.downcase.to_sym, :site => Locomotive::Site.first)
-  login_params = {
-    'email'     => @membership.account.email,
-    'password'  => 'easyone'
-  }
-  response = do_request('POST', api_base_url, 'tokens.json',
-                        login_params.merge({ 'CONTENT_TYPE' => 'application/json' }))
-  if response.status == 200
-    @auth_token = JSON.parse(response.body)['token']
-  else
-    raise JSON.parse(response.body)['message']
-  end
-  add_default_params(:auth_token => @auth_token)
-end
-Given /^I do not have an API token$/ do
-  @auth_token = nil
-end
-Given /^the JSON request at "([^"]*)" is a file$/ do |path|
-  add_file_field(path)
-end
-When /^I visit "([^"]*)"$/ do |path|
-  @json_response = get("http://#{@site.domains.first}#{path}", { auth_token: @auth_token }, { 'CONTENT_TYPE' => 'application/json' })
-end
-# http://stackoverflow.com/questions/9009392/racktest-put-method-with-json-fails-to-convert-json-to-params
-When /^I post to "([^"]*)"$/ do |path|
-  @json_response = post("http://#{@site.domains.first}#{path}", '', { 'CONTENT_TYPE' => 'application/json' })
-end
-When /^I post to "([^"]*)" with:$/ do |path, json_string|
-  @json_response = post("http://#{@site.domains.first}#{path}", json_string, { 'CONTENT_TYPE' => 'application/json' })
-end
-When /^I do an API (\w+) (?:request )?to ([\w.\/]+)$/ do |request_type, url|
-  do_api_request(request_type, url)
-end
-When /^I do an API (\w+) (?:request )?to ([\w.\/]+) with:$/ do |request_type, url, param_string|
-  do_api_request(request_type, url, param_string)
-end
-Then /^an access denied error should occur$/ do
-  if @error
-    @error.is_a?(CanCan::AccessDenied).should be_true
-  else
-    last_status.should == 401
-  end
-end
-Then /^it should not exist$/ do
-  if @error
-    @error.is_a?(Mongoid::Errors::DocumentNotFound).should be_true
-  else
-    last_status.should == 404
-  end
-end
-When /^I do a multipart API (\w+) (?:request )?to ([\w.\/]+) with base key "([^"]*)" and:$/ \
-    do |request_type, url, base_key, table|
-  params = {}
-  params = table.rows_hash
-  params.each do |key, filename|
-    params[key] = Rack::Test::UploadedFile.new(Rails.root.join('..', 'fixtures', filename))
-  end
-  do_api_request(request_type, url, { base_key => params })
-end
-Then /^the JSON at "([^"]*)" should match \/(.+)\/$/ do |path, regex|
-  parse_json(last_json, path).should =~ /#{regex}/
-end
-Then /^the response content type should match \/(.+)\/$/ do |regex|
-  @json_response.header['Content-Type'].should =~ /#{regex}/
-end
-Then /^the JSON at "([^"]*)" should be the time "(.+)"$/ do |path, time_str|
-  format = '%Y-%m-%dT%H:%M:%S%Z'
-  json_time_str = parse_json(last_json, path)
-  json_time = Time.strptime(json_time_str, format)
-  time = Time.strptime(time_str, format)
-  json_time.should == time
-end
-Then /^I print the JSON response$/ do
-  puts %{JSON (status=#{@json_response.status}): "#{last_json}" / #{last_json.inspect}}
-end
-Then /^I print the editable elements for page "([^"]*)"$/ do |id|
-  puts @site.pages.find(id).editable_elements.inspect
-end

data/features/step_definitions/backoffice/mounting_steps.rb DELETED Viewed

@@ -1,22 +0,0 @@
-Given /^the engine is mounted on a non standard path$/ do
-  Rails.application.routes.draw do
-    mount Locomotive::Engine => '/my-custom-path', as: 'locomotive'
-    match '/foo' => 'foo#index', as: 'foo'
-  end
-end
-Then /^I should be able to access the backend$/ do
-  # Ensure we can access the backend
-  visit '/my-custom-path'
-  page.should have_content 'LocomotiveCMS'
-  # Ensure we can update the homepage content
-  within('#pages-list') do
-    click_link 'Home page'
-  end
-  click_button 'Save'
-  page.should have_content 'Page was successfully updated'
-  # Reset the routes back to normal once we are done
-  Rails.application.reload_routes!
-end