Relentless Simplicity :: The Bonanzle Tech Blog

Hi all. No update for Rails 2.1 ? I’ve a lot of difficulties with routes
undefined local variable or method `users_path’
or
undefined local variable or method `new_session_path’
even my restful seems kaput:
No route matches “/login” with {:method=>:get}
:((((
if someone has an idea…
I’m running Rails 2.1.2 & engines 2.1.2

mode autoresponse: It seems that ‘map.from_plugin :savage_beast’ is not working in my route.rb…
If I take all routes defined in ‘vendor/plugins/savage_beast/routes.rb’ and put it directly in route.rb of my app, it’s working. cool.

We use it on our site. http://www.rubysoccer.com

@Ravi: The problem you mentioned about Reply to Topic link not working, is because in the layout application.html, “application.js” is wrongly included before “prototype”, “effects” (hence the show/hide/toggle functions weren’t working)

Bill, please correct the actual plugin code. Loving the Savage Beast! I am about to launch it on my site: http://www.chictini.com

Hello!

Thanks, William, for a great Beast rewrite. We needed something like that and forked Savage Beast into Aep Beast, to have it Rails 2.1 - compatible and improve the code a bit:
http://blog.aenima.pl/2008/12/4/aep-beast-a-modern-beast-forum-fork

It wouldn’t be possible without your Savage Beast though

You might get this error after upgrading to Rails 2.2:

uninitialized constant Rails::Plugin::Dependencies

You need change savage_beast/init.rb:
Rails::Plugin::Dependencies

to

ActiveSupport::Dependencies

Zac

I was ALSO having issues with a users_path variable not being found.

Adding map.resources :users to routes.rb didn’t fix it, but when I moved the map.from_plugin :savage_beast so that it happened before the map.resources :users line, then everything started working.

–Tyler

Does anyone know a good way to port the data/postings from an existing Beast forum to Savage beast?
(is it even possible?)

thanks.

I am able to run it successfully with Rails 2.1.0 and 2.3.2 - see my script at http://bananacoding.com/oxite.aspx/Blog/Savage-Beast-Forum-Installation

Hope this helps,
-Jirapong

Note: In part 2.1, “Redcloth” should be “RedCloth” - with a capital ‘C’. The gem install could not find gem “Redcloth” otherwise.

gem install RedCloth

Do you think that it will work without engines plugin on Rails 2.3. ?

I’m also running into the uninitialized constant ForumsController problem…I do have that line added to environment.rb…feels like repeatedly slamming myself against a brick wall as a rails newbie sometimes!

We have been using it on our site: http://www.cricketfantasies.com..Amazing plugin!

Hi, nice plugin

I think

By the way, I had to do

gem install RedCloth

(not gem install Redcloth)

I installed everything as instructed above, and when i start server, or infact even when i run rake (for migrations) or generator (for scaffolding) it is breaking and throwing up this error : c:/ruby/lib/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/core_ext/module/aliasing.rb:31:in `alias_method’: undefined method `initialize_schema_information’ for module `ActiveRecord::ConnectionAdapters::SchemaStatements’ (NameError) Any clue why this mite be happening?

Hi Bill,

I downloaded your Savage Beast to work with my Rails 2.3 project. Here are the changes I needed to make:
* need a version of engines that’s compatible with the version of Rails, since a lot of code has been moving
from Engines to Rails (git://github.com/lazyatom/engines.git)
* the migration should be renamed before copying to the migration directory so it doesn’t conflict (I’m using timestamped migrations)
* in init.rb, need to change “Dependencies.load_once_paths.delete(path)” to “ActiveSupport::Dependencies.load_once_paths.delete(path)”
(dependencies are part of ActiveSupport now, according to http://sagarkulkarni.com/2009/03/02/getting-weborb-to-work-with-rails-22-const_missing-uninitia-lized-constant-railsplugindependencies/)
* (note for Mac users, no RedCloth precompiled version for Mac, so you need XTools installed)
* according to Rails 2.3 release notes, no need to “Add the line “map.from_plugin :savage_beast” to your routes.rb” as rails now automatically includes your mappings, but I still needed to add it.
* I got the error message “Rails::Plugins::RedCloth not found”, even though I had installed RedCloth as a gem. To get around this, I had to add the line “config.gem “RedCloth”" in my environment.rb.
* got this warning message “/Users/jobsearch/Documents/Rails/19gale/vendor/plugins/white_list_formatted_content/init.rb:5: warning: default `to_a’ will be obsolete”
* this is because “Object.to_a” will dissapear in Ruby 1.9. Changed to Array(options)
* got warning “DEPRECATION WARNING: formatted_forum_posts_path() has been deprecated. Please pass format to the standard forum_posts_path method instead.. (called from _run_erb_vendor47plugins47savage_beast47app47views47forums47show46html46erb at vendor/plugins/savage_beast/app/views/forums/show.html.erb:33)”
* changed “formatted_forum_posts_path(@forum, :rss)” to “forum_posts_path(@forum, :format => :rss)” wherever found
* got error “undefined method `to_i’ for {:page=>nil}:Hash” on line #25 of forums_controller.rb
* paginate method is being called improperly, as it uses default arguments, not options.
* changed “@forum.topics.paginate :page => params[:page]” to “@forum.topics.paginate( params[:page] ? params[:page] : 1 )” and fixed the problem.
* (note if you pass 0 or nil as the page #, you get an array, not a collection back).
* same issue (paginate method) for topics_controller, same fix
* got error “undefined method `email’ for “#”:User”. Your documentation doesn’t mention you need an “email” method for user.
* got warning “DEPRECATION WARNING: truncate takes an option hash instead of separate length and omission arguments.”
* changed all instances of truncate(a,b) to truncate(a,:length=>b). Includes 2 instances in white_list_formatted_content/init.rb
* when I click on “Reply to topic”, nothing happens. There doesn’t appear to be a function ReplyForm.init()
* plugin javascript was not included. I added an extra “content_for :head” in topics/show.html.erb as I’m not sure if I want this script available for the rest of my application.
* “\n \n”
* Fixed typo “Administator” => “Administrator” in topics/show.html.erb (not related to port, but just to let you know…)

Hope this information is useful,

Thomas O’Dell

William, that’s some great news. Care to share github repo address? Maybe you could use some work from our fork of SB:
http://github.com/aenima/aep_beast/tree/master

Actually, William, it would be cool if you contacted me (via email or any-method from my website) — we did some work with our fork of Savage Beast (named it Aep_Beast) to make it Rails 2.1-compliant (and clean up some code ;)) and I think you could use/merge our fork and start from that point onwards.

Hi Bill, looking forward to a 2.3 compatible Savage Beast. Let me know if/when code is pushed to GitHub. I would love to help out; I think it would be great for a current project I’m working on.

I’ve implemented this using the steps above and implemented current_user and login_required.

I’m seeing the forums index and I can create a new forum. But I don’t see a “new topic” button on the topics index page.

Ideas?

Also, does anyone have an example of application.rb?

What’s the actual code I put in application.rb to include the AuthenticationSystem? When it says override, do I write my specific code for those functions in the AuthenticationSystem file or in Application.rb?

I’ve gotten the New Topic button to display, but now when I go to start a new topic, I get this error:

You have a nil object when you didn’t expect it!
The error occurred while evaluating nil.display_name

Line 8: 8:

This is in my Application.rb:

def current_user
@current_user ||= ((session[:user_id] && User.find_by_id(session[:user_id])) || 0)
end

I also tried:

def current_user
User.find_by_id(session[:user_id])
end

Why is “current_user” nil in the New Topic page?

Thanks

@Andy
Have you tried User.find(session[:user_id])?