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/basic.feature DELETED Viewed

@@ -1,30 +0,0 @@
-Feature: Engine
-  As a designer
-  I want to be able to build simple page html layouts
-  that render correctly to the client
-Background:
-  Given I have the site: "test site" set up
-Scenario: Simple Page
-  Given a page named "hello-world" with the template:
-    """
-    Hello World
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    Hello World
-    """
-Scenario: Missing 404 page
-  Given a page named "hello-world" with the template:
-    """
-    Hello World
-    """
-  And the page "404" is unpublished
-  When I view the rendered page at "/madeup"
-  Then the rendered output should look like:
-    """
-    No Page!
-    """

data/features/public/contact_form.feature DELETED Viewed

@@ -1,98 +0,0 @@
-Feature: Contact form [Old 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>
-          <form action="{{ contents.messages.public_submission_url }}" method="post">
-            {% csrf_param %}
-            <input type="hidden" value="/success" name="success_callback" />
-            <input type="hidden" value="/contact" name="error_callback" />
-            <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" />
-          </form>
-        </body>
-      </html>
-      """
-    And a page named "success" with the template:
-      """
-      Thanks {{ message.email }}
-      """
-  Scenario: Setting the right url for the contact form
-    When I view the rendered page at "/contact"
-    Then the rendered output should look like:
-      """
-      <form action="/entry_submissions/messages" method="post">
-      """
-  Scenario: Prevents users to post messages if the public submission option is disabled
-    Given I disable the public submission of the "Messages" model
-    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 press "Submit"
-    Then I should not see "Thanks did@locomotivecms.com"
-  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: Can not send a message if the csrf tag is missing
-    Given I delete the following code "{% csrf_param %}" from the "contact" page
-    When I view the rendered page at "/contact"
-    And I press "Submit"
-    Then I should see "Content of the home page"
-  Scenario: Can send a message if the csrf protection is disabled
-    Given I disable the CSRF protection for public submission requests
-    And 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: Make sure to use the right locale
-    When I view the rendered page at "/contact"
-    And the locale of the current ruby thread changes to "fr"
-    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"

data/features/public/content_entries.feature DELETED Viewed

@@ -1,69 +0,0 @@
-Feature: Content entries
-  As a designer
-  I want to list and filter the entries of a
-  content type I designed through to the back-office and
-  I should be able to display the entries from a liquid template
-Background:
-  Given I have the site: "test site" set up
-  And I have a custom model named "Articles" with
-    | label         | type      | required    |
-    | Title         | string    | true        |
-    | Body          | string    | false       |
-    | Hidden        | boolean   | false       |
-    | Published at  | date      | false       |
-  And I have entries for "Articles" with
-    | title             | body                    | published_at  | hidden  |
-    | Hello world       | Lorem ipsum             | 2015-01-01    | false   |
-    | Lorem ipsum       | Lorem ipsum...          | 2013-03-23    | false   |
-    | Yadi Yada         | Lorem ipsum...          | 2013-03-23    | true    |
-Scenario: List all of them
-  Given a page named "my-articles" with the template:
-    """
-    {% for article in contents.articles %}{{ article.title }}, {% endfor %}
-    """
-  When I view the rendered page at "/my-articles"
-  Then the rendered output should look like:
-    """
-    Hello world, Lorem ipsum, Yadi Yada
-    """
-Scenario: Filter by a boolean
-  Given a page named "my-articles" with the template:
-    """
-    {% with_scope hidden: false %}
-    {% for article in contents.articles %}{{ article.title }}, {% endfor %}
-    {% endwith_scope %}
-    """
-  When I view the rendered page at "/my-articles"
-  Then the rendered output should look like:
-    """
-    Hello world, Lorem ipsum
-    """
-Scenario: Filter by a date
-  Given a page named "my-articles" with the template:
-    """
-    {% with_scope published_at.lte: now %}
-    {% for article in contents.articles %}{{ article.title }}, {% endfor %}
-    {% endwith_scope %}
-    """
-  When I view the rendered page at "/my-articles"
-  Then the rendered output should look like:
-    """
-    Lorem ipsum, Yadi Yada
-    """
-Scenario: Filter with regexp
-  Given a page named "my-articles" with the template:
-    """
-    {% with_scope title: /ello|adi/ %}
-    {% for article in contents.articles %}{{ article.title }}, {% endfor %}
-    {% endwith_scope %}
-    """
-  When I view the rendered page at "/my-articles"
-  Then the rendered output should look like:
-    """
-    Hello world, Yadi Yada
-    """

data/features/public/editable_elements.feature DELETED Viewed

@@ -1,138 +0,0 @@
-Feature: Editable elements
-  As a designer
-  I want to define content which will be edited by the website editor
-Background:
-  Given I have the site: "test site" set up
-Scenario: Simple short text element
-  Given a page named "hello-world" with the template:
-    """
-    My application says {% editable_short_text 'a_sentence', hint: 'please enter a new sentence' %}Hello world{% endeditable_short_text %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Hello world
-    """
-Scenario: Updating a page
-  Given a page named "hello-world" with the template:
-    """
-    My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}
-    {% block main %}Main{% endblock %}
-    """
-  When I update the "hello-world" page with the template:
-    """
-    My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}
-    {% block main %}Main{% endblock %}
-    {% block sidebar %}{% editable_short_text 'title' %}Default sidebar title{% endeditable_short_text %}{% endblock %}
-    """
-  And I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Hello world
-    Main
-    Default sidebar title
-    """
-Scenario: Modified short text element
-  Given a page named "hello-world" with the template:
-    """
-    My application says {% editable_short_text 'a_sentence', hint: 'please enter a new sentence' %}Hello world{% endeditable_short_text %}
-    """
-  And the editable element "a_sentence" in the "hello-world" page with the content "Bonjour"
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Bonjour
-    """
-Scenario: Short text element inside a block
-  Given a page named "hello-world" with the template:
-    """
-    {% block main %}My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}{% endblock %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Hello world
-    """
-Scenario: Not modified short text element inside a block and with page inheritance
-  Given a page named "hello-world" with the template:
-    """
-    {% block main %}My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}{% endblock %}
-    """
-  Given a page named "another-hello-world" with the template:
-    """
-    {% extends hello-world %}
-    """
-  When I view the rendered page at "/another-hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Hello world
-    """
-Scenario: Modified short text element inside a block and with page inheritance
-  Given a page named "hello-world" with the template:
-    """
-    {% block main %}My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}{% endblock %}
-    """
-  Given a page named "another-hello-world" with the template:
-    """
-    {% extends hello-world %}
-    """
-  And the editable element "a_sentence" for the "main" block in the "another-hello-world" page with the content "Bonjour"
-  When I view the rendered page at "/another-hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Bonjour
-    """
-Scenario: Combine inheritance and update
-  Given a page named "hello-world" with the template:
-    """
-    My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}
-    {% block main %}Main{% endblock %}
-    """
-  Given a page named "another-hello-world" with the template:
-    """
-    {% extends hello-world %}
-    {% block main %}Another Main{% endblock %}
-    """
-  When I update the "hello-world" page with the template:
-    """
-    My application says {% editable_short_text 'a_sentence' %}Hello world{% endeditable_short_text %}
-    {% block main %}Main{% endblock %}
-    {% block sidebar %}{% editable_short_text 'title' %}Default sidebar title{% endeditable_short_text %}{% endblock %}
-    """
-  And I view the rendered page at "/another-hello-world"
-  Then the rendered output should look like:
-    """
-    My application says Hello world
-    Another Main
-    Default sidebar title
-    """
-Scenario: Insert editable files
-  Given a page named "hello-world" with the template:
-    """
-    My application file is {% editable_file 'a_file', hint: 'please enter a new file' %}/default.pdf{% endeditable_file %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application file is /default.pdf
-    """
-Scenario: Simple select element
-  Given a page named "hello-world" with the template:
-    """
-    {% block menuecontent %}{% editable_control 'menueposition', options: 'top=Top of the Page,bottom=Bottom of the Page' %}bottom{% endeditable_control %}{% endblock %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    bottom
-    """

data/features/public/has_many.feature DELETED Viewed

@@ -1,8 +0,0 @@
-Feature: Has Many Association
-  As a designer
-  In order to make dealing with models easier
-  I want to be able to display other models that have a has many association
-  Scenario: Paginating a has many association
-    Given I have a site set up
-    Then I should be able to view a paginated list of a has many association

data/features/public/inheritance.feature DELETED Viewed

@@ -1,157 +0,0 @@
-Feature: Inheritance
-  As a designer
-  I want to be able to build more complex page html layouts
-  with shared template code
-  that render correctly to the client
-Background:
-  Given I have the site: "test site" set up
-Scenario: Liquid Inheritance with a single block
-  Given a page named "above-and-below" with the template:
-    """
-    <div class="header"></div>
-    <div class="body">
-      {% block body %}{% endblock %}
-    </div>
-    <div class="footer"></div>
-    """
-  And a page named "hello-world-with-layout" with the template:
-    """
-    {% extends 'above-and-below' %}
-    {% block body %}Hello World{% endblock %}
-    """
-  When I view the rendered page at "/hello-world-with-layout"
-  Then the rendered output should look like:
-    """
-    <div class="header"></div>
-    <div class="body">
-      Hello World
-    </div>
-    <div class="footer"></div>
-    """
-Scenario: Update a parent page and see modifications in descendants
-  Given a page named "base" with the template:
-    """
-    My application say: {% block something %}Lorem ipsum{% endblock %}
-    """
-  And a page named "hello-world" with the template:
-    """
-    {% extends 'base' %}
-    {% block something %}Hello World{% endblock %}
-    """
-  When I update the "base" page with the template:
-    """
-    My application says: {% block something %}Lorem ipsum{% endblock %}
-    """
-  When I view the rendered page at "/hello-world"
-  Then the rendered output should look like:
-    """
-    My application says: Hello World
-    """
-Scenario: Liquid Inheritance with multiple blocks
-  Given a page named "layout-with-sidebar" with the template:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">
-        {% block sidebar %}DEFAULT SIDEBAR CONTENT{% endblock %}
-      </div>
-      <div class="body">
-        {% block body %}DEFAULT BODY CONTENT{% endblock %}
-      </div>
-    </div>
-    <div class="footer"></div>
-    """
-  And a page named "hello-world-multiblocks" with the template:
-    """
-    {% extends 'layout-with-sidebar' %}
-    {% block body %}Hello world{% endblock %}
-    """
-  When I view the rendered page at "/hello-world-multiblocks"
-  Then the rendered output should look like:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">
-        DEFAULT SIDEBAR CONTENT
-      </div>
-      <div class="body">
-        Hello world
-      </div>
-    </div>
-    <div class="footer"></div>
-    """
-Scenario: Multiple inheritance (layout extending another layout)
-  Given a page named "layout-with-sidebar" with the template:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">{% block sidebar %}DEFAULT SIDEBAR CONTENT{% endblock %}</div>
-      <div class="body">
-        {% block body %}DEFAULT BODY CONTENT{% endblock %}
-      </div>
-    </div>
-    <div class="footer"></div>
-    """
-  And a page named "custom-layout-with-sidebar" with the template:
-    """
-    {% extends 'layout-with-sidebar' %}
-    {% block sidebar %}Custom sidebar{% endblock %}
-    {% block body %}Hello{% endblock %}
-    """
-  And a page named "hello-world-multiblocks" with the template:
-    """
-    {% extends 'custom-layout-with-sidebar' %}
-    {% block body %}{{ block.super }} world{% endblock %}
-    """
-  When I view the rendered page at "/hello-world-multiblocks"
-  Then the rendered output should look like:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">Custom sidebar</div>
-      <div class="body">
-        Hello world
-      </div>
-    </div>
-    <div class="footer"></div>
-    """
-Scenario: Page extending a layout with multiple embedded blocks which extends another template
-  Given a page named "layout-with-sidebar" with the template:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">{% block sidebar %}DEFAULT SIDEBAR CONTENT{% endblock %}</div>
-      <div class="body">
-        {% block body %}Hello{% endblock %}
-      </div>
-    </div>
-    <div class="footer"></div>
-    """
-  And a page named "custom-layout-with-sidebar" with the template:
-    """
-    {% extends 'layout-with-sidebar' %}
-    {% block body %}{{ block.super }} {% block main %}mister{% endblock %}{% endblock %}
-    """
-  And a page named "hello-world-multiblocks" with the template:
-    """
-    {% extends 'custom-layout-with-sidebar' %}
-    {% block body/main %}{{ block.super }} Jacques{% endblock %}
-    """
-  When I view the rendered page at "/hello-world-multiblocks"
-  Then the rendered output should look like:
-    """
-    <div class="header"></div>
-    <div class="content">
-      <div class="sidebar">DEFAULT SIDEBAR CONTENT</div>
-      <div class="body">
-        Hello mister Jacques
-      </div>
-    </div>
-    <div class="footer"></div>
-    """

data/features/public/inline_front_end_editing.feature DELETED Viewed

@@ -1,26 +0,0 @@
-@wip
-@javascript
-Feature: Engine
-  As an author
-  In order to easily be able to modify the contents of my website
-  I want to be able to edit the sites content on the front end
-  Background:
-    Given I have the site: "test site" set up
-    And I am an authenticated "author"
-  Scenario: Editing a short text field
-    Given a page named "about" with the template:
-    """
-    <html>
-      <head>{% inline_editor %}</head>
-      <body>{% editable_short_text 'owner' %}Tom{% endeditable_short_text %} owns this website</body>
-    </html>
-    """
-    When I view the rendered page at "/about"
-    Then I should see "edit"
-    When I follow "edit"
-    And I type the content "Mario" into the first editable field
-    And I follow "save"
-    And I view the rendered page at "/about"
-    Then I should see "Mario owns this website"

data/features/public/many_to_many.feature DELETED Viewed

@@ -1,64 +0,0 @@
-Feature: Many to Many Association
-  As a designer
-  In order to make dealing with models easier
-  I want to be able to display other models that have a many to many association
-  Background:
-    Given I have the site: "test site" set up
-    And I have a custom model named "Articles" with
-      | label       | type      | required    |
-      | Title       | string    | true        |
-      | Body        | string    | false       |
-    And I have a custom model named "Projects" with
-      | label       | type      | required    | target  |
-      | Name        | string    | true        |         |
-      | Description | text      | false       |         |
-    And I set up a many_to_many relationship between "Articles" and "Projects"
-    And I have entries for "Articles" with
-      | title             | body                    |
-      | Hello world       | Lorem ipsum             |
-      | Lorem ipsum       | Lorem ipsum...          |
-    And I have entries for "Projects" with
-      | name              | description             |
-      | My sexy project   | Lorem ipsum             |
-      | Foo project       | Lorem ipsum...          |
-      | Bar project       | Lorem ipsum...          |
-      | Baz project       | Lorem ipsum...          |
-    And I attach the "My sexy project" project to the "Hello world" article
-    And I attach the "Baz project" project to the "Hello world" article
-    And I attach the "Foo project" project to the "Hello world" article
-  Scenario: Displaying the entries of a many to many association
-    Given a page named "article-projects" with the template:
-      """
-      {% assign article = contents.articles.first %}
-      <h1>Projects for {{ article.title }}</h1>
-      <ul>
-      {% for project in article.projects %}<li>{{ project.name }}</li>
-      {% endfor %}
-      </ul>
-      """
-    When I view the rendered page at "/article-projects"
-    Then the rendered output should look like:
-      """
-      <h1>Projects for Hello world</h1>
-      <ul>
-      <li>My sexy project</li>
-      <li>Baz project</li>
-      <li>Foo project</li>
-      </ul>
-      """
-  Scenario: Displaying the entries of a many to many association by a different thread
-    Given the "Projects" model was created by another thread
-    And a page named "article-projects" with the template:
-      """
-      {% assign article = contents.articles.first %}{% for project in article.projects %}{{ project.name }}, {% endfor %}
-      """
-    When I view the rendered page at "/article-projects"
-    Then the rendered output should look like:
-      """
-      My sexy project, Baz project, Foo project
-      """