I was able to get CE for ROR 3.1 installed finally today. It looks
like a few underlying modules have moved along since the latest
instructions have been written. Here is what I had to do to get it to
install in addition to the README instructions:
1) bin/rake community_engine:install:migrations failed until I added
the following lines to Rakefile:
          include Rake::DSL

2) bin/rake db:migrate failed because of No such file or directory -
config/application.yml so I ran:
          echo "community_name: Community Engine Test" >> config/
application.yml

3) bin/rake db:migrate failed with undefined method `context' for
#<Sprockets::Environment:0x00000100f9c828> - to fix the following line
must be added to Gemfile:
          gem 'sprockets', '2.0.0.beta.2'
Seems that betas 3-7 are pulled and 9 was giving me the error (along
with complaining that it was not compatible with rails 3.1.0.beta1 and
wanting rails 3.1.0.rc1). I did not try beta8.

4) For clarity for other noobs, application.htmp.erb is in app/views/
layouts/ and not views/layouts/

With this I can run rails server and browse to the site. I then went
through the Sign Up! link with no problems and followed it up with
rake community_engine:make_admin email=... The problem I am running
into now is that I can not log in. Every time I try I get:
Uh oh. We couldn't log you in with the username and password you
entered. Try again? Close this message
I also get the same message if I add a user and do not try to make it
an admin. Did I miss something?

Also there are plenty of deprecation warnings for
class_inheritable_attribute with some from communityengine/app/models/
photo.rb and some from authlogic/lib/authlogic/acts_as_authentic/
base.rb.

-- 
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/communityengine?hl=en.

Reply via email to