Question

I’m working on installing Engage!

I followed the installation instructions found here: http://engagecsm.com/readme

Installation steps I did:

1. Add Engage! to the application’s Gemfile: gem ‘engagecsm’.
2. Install it: bundle install.
3. Run the generator: rails generate engage User.
4. Run the migrations: rake db:migrate.

Now, I can go to localhost:3000/engage

This is what shows up:

Now, when I hit “Create Topic”, nothing happens on the site. I look at my rails server console and I see this: (Easier to view here https://i.stack.imgur.com/xKBER.png, full stack trace found at the bottom)

So I start googling, and I see things like this:

• Can't mass-assign protected attributes: user
• http://guides.rubyonrails.org/security.html#mass-assignment

I already added attr_accessible :user to my User model, but that didn’t work.

Here’s my User model:

Also, I can’t see how I have access to Engage models and such, see here’s my directory:

Does anyone know how to fix this? If you want any other information, please tell me and I’ll provide screenshots.

Any help is greatly appreciated. Thank you!

EDIT #1 – Adding application controller picture and full stack trace

This is the only place I can see anything with Engage! in controllers (I don’t have a User controller at this time)

Here’s the full stack trace:

EDIT #2 – Add engage environment:

Also, we have Devise (and OmniAuth I believe…) installed. Therefore, we have “current_user”, but I don’t know if we have a “username” or “email” method, unless that comes standard with Devise or something

EDIT #3 – As Geoff suggested, I looked at line 46 of the topics_controller. That line is the following:

@topic.votes.create(:user => engage_current_user)

Answer 1

it’s one of Engage! developers here. I can see there are two problems with Engage! described above.

We have found the solution to the first (the one that you have solved with attr_accessible :user), so expect a Rubygems update soon.

The second (the fact that topics are not actually displayed on the index page) is connected with the changes in the cancan gem. We still have to figure out the best way to approach this, but a quick workaround is to lock the cancan version in the Gemfile as follows: gem 'cancan', '1.6.7'.

We will let you know when the updates addressing these issues will be available at Rubygems.

Cheers!