A fork of the [Solidus extension][1] for compatibility with [Solidus][7].
Good, clean content management of pages for Solidus, managing web content from Portal Liferay (7.1). You can use this to:
- Add and manage static pages such as an 'About' page.
- Show a static page instead of existing dynamic pages such as the home page, products pages, and taxon pages.
- Manage de web content with Portal Liferay
Add to your Gemfile
:
gem 'solidus_liferay_cms', github: '2bedigital/solidus_liferay_cms'
Run:
$ bundle install
$ bundle exec rails g solidus_liferay_cms:install
That's all!
Using the 'Pages' option in the admin tab, you can add static pages to your Solidus install. The page content can be pulled directly from the database, be a separate layout file or rendered as a partial.
In the admin tab, use the 'New page' option to create a new static page.
The title, slug, body, and meta fields will replace their respective page elements on load. The title, slug and body element are all required fields.
Body text provided without a layout / partial being specified will be loaded in the Solidus_application layout after it is pulled from the database.
To render an entire page without the Solidus_application layout, specify a
relative path to the layout file (eg. Solidus/layouts/layout_file_name
). This
file will not be prefixed with an underscore as it is a layout, not a partial.
To render a partial, specify the path in the layout file name and check the 'Render layout as partial' option. The path specified in the layout area will not have an underscore, but it will be required in the filename.
Also note the availability of the render_snippet helper which finds a page by its slug and renders the raw page body anywhere in your view.
Use the 'Show in' checkboxes to specify whether to display the page links in the header, footer or sidebar. The position setting alters the order in which they appear.
Finally, toggle the visibility using the 'Visible' checkbox. If it is unchecked, the page will not be available.
In the spirit of [free software][2], everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using prerelease versions
- by reporting [bugs][3]
- by suggesting new features
- by writing translations
- by writing or editing documentation
- by writing specifications
- by writing code (no patch is too small: fix typos, add comments, clean up inconsistent whitespace)
- by refactoring code
- by resolving [issues][3]
- by reviewing patches
Starting point:
- Fork the repo
- Clone your repo
- Run
bundle install
- Run
bundle exec rake test_app
to create the test application inspec/test_app
- Make your changes
- Ensure specs pass by running
bundle exec rspec spec
- Submit your pull request