Hi there,CE has not been tested or upgraded for 2.3.4 compatibility yet. To ensure that things work correctly, please use the latest supported version of Rails (2.3.2). If you're worried about the latest Rails security vulnerability <http://weblog.rubyonrails.org/2009/9/4/ruby-on-rails-2-3-4>, you're better off just applying the relevant<http://weblog.rubyonrails.org/2009/9/4/xss-vulnerability-in-ruby-on-rails> patches<http://weblog.rubyonrails.org/2009/9/4/timing-weakness-in-ruby-on-rails>instead of using 2.3.4.
Thanks, Bruno On Tue, Sep 15, 2009 at 9:21 AM, jnimety <[email protected]> wrote: > > Hi all, I'm using community_engine 1.0.2, rails 2.3.4, and ruby > 1.8.7. I just installed community_engine for the first time and was > encountering "stack level too deep" errors when trying to visit /user > and when trying to save changes to my user account. > > I narrowed the issue down to plugins using "alias_method_chain". > Apparently if a module using alias_method_chain is loaded more then > once this will cause an infinite loop between the methods created with > alias_method_chain (google alias_method_chain and "stack level too > deep", there are plenty of discussions). > > Anyway, I wanted to share my solution, which was to tell ActiveSupport > to only load community_engine once by adding the following to the > Rails::Initializer.run block: > > config.after_initialize do > ActiveSupport::Dependencies.load_once_paths = > ActiveSupport::Dependencies.load_once_paths.select { |path| (path =~ / > (community_engine)/).nil? } > end > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
