#refinerycms

Refinery CMS removes HTML data attributes if the value is undefined or blank. This behavior causes Foundation examples to not work. For example, to use tooltips, Foundation suggests:

<span data-tooltip class="has-tip" title="Tooltips are awesome, you should totally use them!">extended information</span>

This won't work in Refinery CMS. Upon saving the code, the @data-tooltip@ attribute will be stripped from the record. The solution is to explicitly set @data-tooltip@ to a value:

I've dabbled with RefineryCMS over the past few days in order to quickly setup a site. I thought it would be a good opportunity to play with Foundation as well.

Since Foundation 5 was just released, I didn't find much documentation on how to integrate the two. Therefore, I've decided to share a small part of my findings.

In specific, the GitHub repository refinery-foundation demonstrates how to implement a Refinery drop-down menu with a Foundation front-end.

It seemed like a partially answered question on StackOverflow. The Flatiron School blog post was helpful but not complete either. So checkout the repository and see the commit-by-commit process or continue reading for a summary.

Caveat: As per comments below, this procedure has been verified with Rails 3.2.16, not Rails 4.

Install the refinerycms gem:

cd ~/Sites gem install refinerycms

Create the Rails app:

refinerycms refinery-foundation cd refinery-foundation

Add the foundation-rails gem to the Gemfile:

group :assets do gem 'foundation-rails' end

Install the gem and run the foundation generator:

bundle install rails g foundation:install

Note: If your web server was already running, you should restart for the changes to take effect.

Add the Zurb menu presenter and helper:

app/helpers/application_helper.rb

app/presenters/refinery/pages/zurb_menu_presenter.rb

Override the key Refinery files:

rake refinery:override view=layouts/application rake refinery:override view=refinery/_head

Tweak the overrides:

app/views/layouts/application.html.erb

app/views/refinery/_head.html.erb

app/views/refinery/_header.html.erb

Tweak the CSS:

// RefineryCMS Customization header { } #page { @include grid-row(); #body { @include grid-column(9); } .no_side_body #body { @include grid-column(12); } #side_body { @include grid-column(3); } } footer { } .top-bar { .title-area { z-index: 2; } }

RefineryCMS はRails3.2 で使えるCMSです。

AWS S3 と連携してherokuでも使えるので、ホームページのCMSとして使っています。

先日、RefineryCMSを使ったサイトでページを作成したら、エラーになりました。

ページは登録できていますが、表示はNot Foundで何よりも、管理画面でページのリストが表示できなくなりました。

NoMethodError (undefined method `to_slug' for nil:NilClass):

ログを調べるとこのエラー。ソースをたどると、どうやらi18n関連で問題が起きている様子。

さらに調べたところ、こちらが問題の原因でした。

Can't create new pages in fresh install using the gem · Issue #2466 · refinery/refinerycms

New Project doesn't load Home Page and can't add pages. · Issue #2450 · refinery/refinerycms

In a recent project using RefineryCMS the page speed analytics results keep indicating that the main application.js after compression is still showing trailing whitespaces and hence triggering 'js file requires compression' warnings when tested within google page speed

In an attempt to fix this I switched over to using the closure compiler during assets compilation. However after deploy the entire compiled javascript for refinery failed with the following error inside console:

is_match() is undefined

Refinery apparently doesn't like starting with anything but sqlite3.  So use the following steps to get it working with postgres:

Prerequisites: Refinery requires imagemagick, so get that installed somehow (brew install imagemagick with homebrew on Mac, apt-get install imagemagick on Debian/Ubuntu, etc.)

Assuming you have the ability to install Ruby gems (via rvm or whatever) already, gem install refinerycms.

Start with a basic Refinery site: refinerycms project_name

Inside the new project_name folder, move config/database.yml out of the way (or just delete it), and rename config/database.yml.postgresql to config/database.yml.

At the end of the Gemfile, add the line: gem 'pg' to enable the PostgreSQL database adapter.  Also comment out the gem 'sqlite3' line in the group :development, :test do block near the top of the file.

Run bundle to get the 'pg' adapter gem properly installed.

Edit config/database.yml and set all the proper database names, usernames, and passwords. (These should have already been set up by you or your database administrator.)

Run rake db:migrate and rake db:seed in the top level of the project directory.

In a recent refinerycms project I noticed a strange bug / error after upgrading the system to one of rails's security patches.

Within a custom engine model, there is a nested form which uses the cocoon gem to show and remove itself. Within the nested form itself, is a link to call the js image picker within refinerycms to select an image for upload. Problem is this: because the nested field is dynamic which means that the image selector link is not generated until the 'Add This' link is clicked and the nested form is on the screen, the image selector link does not get instantiated within a new nested model form.

This can be seen with this piece of js code from refinerycms-core ver 1.0.11, in public/javascripts/refinery/admin.js

$(document).ready(function(){ // other initialization code init_modal_dialogs(); })

init_modal_dialogs() is a function which opens up a modal window in an iframe for selecting images or attachments. Since my dialog selectors are not going to be present until the nested fields are added, I bind the click event to the live action once the link is clicked. e.g.

$('a.add_nested_image_link').live('click', function(e)){ init_modal_dialogs() })

This fixes the dialog open and also shows the currently selected image within the nested form.

To remove the image or to replace it is a bit tricky.

Refinerycms by default uses a class of '.remove_picked_image' to define the remove image link within the dialog. Here we have another problem. Since the dialog is not created until the nested model forms are added, we need to bind the 'remove_picked_image' links to the live event too else it won't work:

Please note that the above only works if you are using a nested model form within your own engine in refinerycms with the cocoon gem.