Needs standard Refinery SEO fields under advanced options about refinerycms-blog

[parndt]

we could extract refinery's into optimizes_for_search_engines or something

yep, a plugin for this would be awesome. Often when make custom engines, we need to be able to just automatically add those standard options.

[parndt]

Or maybe has_meta_tags to allow you to override the browser title, keywords, description etc. all the things that Presenters/@meta have in Refinery.

[ninadpachpute]

Any progress on this? I am new to rails but meanwhile I will give it a shot.

[parndt]

No progress has been made but we do have a little something internally related to this.

[johnbartram]

Is it possible to update the blog module to use the new seo_meta functionality in 0.9.9.14 and add in the form for the seo components on each post

[parndt]

yep will be doing so in the near future

[johnbartram]

hi phil, has there been any update on this? cheers

[parndt]

Yes these have been added.

See comparison: resolve/refinerycms-blog@03e105b...master

Hopefully we can release this with the next version but it may end up in version 1.5

[johnbartram]

Awesome, thanks Phil! So can i run the refinery update rake task to upgrade to this commit? Or do i need to wait until the version changes?

[parndt]

Yeah sorry but new version will be soon enough... Just have to coordinate a
few things. Or in your Gemfile you can specify:

gem 'refinerycms-blog', :git => 'git://
github.com/resolve/refinerycms-blog.git'

That will allow you to use it now.
Run bundle install and then rails generate refinerycms-blog and then rake
db:migrate

[keram]

Hello Phil,
thnx you for progress on this :-).

I get this error when i upgrade to this version and try show some blog posts:

Started GET "/blog/marcov%c3%a9-novinky" for at Fri May 06 19:19:09 +0200 2011
Processing by Blog::PostsController#show as HTML
Parameters: {"id"=>"marcové-novinky", "locale"=>:sk}
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/posts/_nav.html.erb (130.9ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/posts/_post.html.erb (144.1ms)
Rendered /home/keram/gems/gems/refinerycms-core-0.9.9.21/app/views/shared/admin/_error_messages.html.erb (1.0ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/shared/_categories.html.erb (0.1ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/shared/_tags.html.erb (1.5ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/shared/_posts.html.erb (133.2ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/shared/_rss_feed.html.erb (1.8ms)
Rendered shared/_content_page.html.erb (2.0ms)
Rendered /home/keram/gems/bundler/gems/refinerycms-blog-76708704c8bc/app/views/blog/posts/show.html.erb within layouts/application (379.5ms)
Completed in 434ms

ActionView::Template::Error (Refinery::BasePresenter doesn't know url. Define or delegate it.):
5: # if 'sections' is passed in as a local_assigns, all of this is ignored.
6: if local_assigns[:sections].blank?
7: # always have a title
8: sections = [{:yield => :body_content_title, :fallback => page_title, :title => true}]
9:
10: # append sections from this page.
11: @page.parts.inject(sections) do |s, part|
app/views/shared/_content_page.html.erb:8:in `_app_views_shared__content_page_html_erb___1820992394_70225744848220_7738604'

[johnbartram]

I get a similar error when i try to edit / create a new blog post in the backend.

[parndt]

Yeah.. that error's a pain.. it'll be fixed in RefineryCMS 1.0.0 and hence why the blog wasn't released yet.

[johnbartram]

Cool, sounds good. So when are you looking at releasing RefineryCMS 1.0.0?

[parndt]

At the moment the answer is "how long is a piece of string" but basically ASAP. The issue is when people file new issues that would look very bad in a 1.0.0 :-)

[ivanoats]

Thanks for considering this, it's a factor in my switch from WordPress to Refinery

[parndt]

As this has been implemented since v1.4 I'm closing this. Woohoo!