On Tue, Apr 19, 2011 at 2:13 PM, David Kahn <[email protected]>wrote:
> > > On Tue, Apr 19, 2011 at 1:36 PM, David Kahn > <[email protected]>wrote: > >> >> >> On Tue, Apr 19, 2011 at 1:25 PM, Philip Hallstrom <[email protected]>wrote: >> >>> So, if anyone has made it this far, I guess my next question would be >>>> as to how I can confirm whether active support (in particular the file >>>> mentioned above is getting loaded). Actually if Phillip, or someone else >>>> (running Ruby 1.8.7-p334 and Rails 3.0.7 ideally on Snow Leopard mac or >>>> close) to this set up can send me their output of >>>> DateTime.now.methods.sort, >>>> it would at least confirm things. >>>> >>>> >>>> ruby 1.8.7, rails 2.3.8.... >>>> http://pastefree.pjkh.com/pastes/155 >>>> >>>> ruby 1.9.2, rails 3.0.7 >>>> http://pastefree.pjkh.com/pastes/156 >>>> >>>> ruby 1.8.7, rails 3.0.7 >>>> http://pastefree.pjkh.com/pastes/157 >>>> >>> >>> Thanks Phillip, well this one confirms my environment has something wrong >>> and is pretty clearly not something wrong with either Rails or Ruby. Well >>> for now I think I am just going to work the project under 1.9.2 and then >>> move it back to 1.8.7 for the client/production, not ideal but nor is >>> creating vm or rebuilding my laptop at the moment. >>> >>> >>> Or install RVM and ditch the system ruby entirely?? I'll admit I don't >>> remember if you've already gone that direction or not... >>> >> >> Yeah, thats what's scary is that I have been using rvm the whole way >> through. Actually I just discovered that I have a dependency on an engine >> built in 1.8.7 so I guess I am going to have to do something to my >> environ... >> > > > I GOT IT!!! And I did it by trying to change to ruby 1.9.2 and remembering > that I have an engine dependency which uses 1.8.7.... and when I commented > the code below I get a good DateTime object. Looks like (have to prove it > after lunch), that what is below overrides the application config and as > such something important does not happen. Thanks everyone for the help and > sorry it is such a lame answer... > > # initializer "my_engine.load_config" do |app| > # config_file = "#{Rails.root}/config/config.yml" > # if File.exists?(config_file) > # ::APP_CONFIG = > YAML.load_file(config_file)[Rails.env].symbolize_keys! > # ActionMailer::Base.smtp_settings = APP_CONFIG[:smtp] > # ActionMailer::Base.default(APP_CONFIG[:mailer_defaults]) > # else > # puts "No config.yml file found, run 'rails g my_engine:install'" > # end > # end > > More info for posteriority if this ends up helping anyone: the actual conflict was the gem 'home_run' which was not referenced in my project but in the engine it depends on, unbenownst to me. Once the dependency was removed from the engine, DateTime began to function correctly. I suspect that this problem might have to do with my local environment as home_run creates native extensions. I will try to post back here with final results if and when I rebuild or have a new mac, but until then we just removed the gem. > >> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
