Closed losingle closed 12 years ago
@losingle which gem verision of refinerycms-news
are you using?
@ugisozols gem ver '1.8.24'
gem 'refinerycms', '~> 2.0.0' gem 'refinerycms-i18n', '~> 2.0.0' gem "refinerycms-news", '~> 2.0.0' gem 'refinerycms-page-images', '~> 2.0.0'
This is a zsh thing, not a refinery thing. zsh tries to do its autocompletion magic on , so you'll have to write it as \.
@robyurkowski Thank you. you're right.
Cool. Make a rake task so it's easy and works everywhere. Certain views like show, home, header, footer, menu should be defaults.
No views should be overridden by default.
I disagree. A CMS should give you control. You're making it dumber, more magical, and harder to figure out by hiding them.
And harder to update on every new version if we decided that those templates could be better or removed. You can override whatever you want but it is opt in.
I'm of the opinion that upgrading the CMS shouldn't override the HTML for the front-end. It actually takes a bit of digging to find out what needs to be overridden.
Here's a couple of thoughts from a brand new refinerycms user. https://gist.github.com/3496883
Don't get me wrong, I'm really liking the cms, but the defaults and hidden views were unnecessary obstacles. Control over the templates and views is an absolute must for me, I'm really surprised even the application layout is hidden by default.
rake refinery:override view=refinery/news/items/*
zsh: no matches found: view=refinery/news/items/*