[Rails] Re: Rails 2.3 not supported?
Rob Olson wrote in post #1049878: > I was surprised as well. The previous security issue in August 2011 > that affected 2.3 received a fix and a new release. I also haven't > seen an announcement that that had changed. > > That said, I don't blame the core team for wanting to drop Rails 2.3. > They are already supporting 3 branches in the 3.x line. Not to mention current work on Rails 4.0: http://weblog.rubyonrails.org/2011/12/20/rails-master-is-now-4-0-0-beta -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3 not supported?
I was surprised as well. The previous security issue in August 2011 that affected 2.3 received a fix and a new release. I also haven't seen an announcement that that had changed. That said, I don't blame the core team for wanting to drop Rails 2.3. They are already supporting 3 branches in the 3.x line. On Mar 1, 1:15 pm, "Paul E. G. Lynch" wrote: > The security fix announcement today sent to the rubyonrails-security > group implied that Rails 2.3 is no longer supported. Is that the > case? Did I miss an announcement somewhere? Is there a list of > supported releases somewhere? (What was I supposed to be paying > attention to?) Thanks, > > --Paul -- 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3.x documentation archive?
It was definitely unclear as where to find the archived documentation. Even Google gave me trouble finding it Finally I came across: http://rdoc.info/docs/rails/2.3.8/frames On Sep 13, 5:48 am, gamov wrote: > api.rubyonrails.org/v2.3.8/index.html > guides.rubyonrails.org/v2.3.8 > > On Sep 11, 3:00 am, Tom wrote: > > > Hi, > > > I'm a developer on several projects using rails 2.3.4 and since the > > release of 3.0, I haven't been able to find any documentation for > > 2.3.4 online. I have the rdocs from the gem install, but haven't been > > able to find anything else. > > > Is this stuff archived somewhere? > > > Thanks! > > -Tom -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3.x documentation archive?
api.rubyonrails.org/v2.3.8/index.html guides.rubyonrails.org/v2.3.8 On Sep 11, 3:00 am, Tom wrote: > Hi, > > I'm a developer on several projects using rails 2.3.4 and since the > release of 3.0, I haven't been able to find any documentation for > 2.3.4 online. I have the rdocs from the gem install, but haven't been > able to find anything else. > > Is this stuff archived somewhere? > > Thanks! > -Tom -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3.x documentation archive?
Tom wrote: > Hi, > > I'm a developer on several projects using rails 2.3.4 and since the > release of 3.0, I haven't been able to find any documentation for > 2.3.4 online. Then you haven't been looking very hard. :) We've had this discussion already, so you could have searched the list archives; in any case, railsbrain.com and railsapi.com both maintain documentation for old versions of Rails. > I have the rdocs from the gem install, but haven't been > able to find anything else. > > Is this stuff archived somewhere? > > Thanks! > -Tom Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org Sent from my iPhone -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3.x documentation archive?
Tom wrote: > Hi, > > I'm a developer on several projects using rails 2.3.4 and since the > release of 3.0, I haven't been able to find any documentation for > 2.3.4 online. I have the rdocs from the gem install, but haven't been > able to find anything else. > > Is this stuff archived somewhere? > > Thanks! > -Tom I agree with Tom -- Posted via http://www.ruby-forum.com/. -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: [Rails 2.3] Adding a "phase" to the ActiveRecord Lifecycle
On Tuesday 13 April 2010, Phoenix Rising wrote: > Because the user can add multiple items and other items to their > order, as well as set the "object" on their order at any point in the > ordering process, I can't call the validations I want after > save. I'd much rather have a before/after "card_charged" step in > the lifecycle, and run a validation before the card is charged, then > one after it's charged. I think the best way would be to use a state machine, as you indicated yourself in a paragraph I snipped. Second best would be to use conditional validations, see the :if and :unless options on all the validates_something methods. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: (Rails 2.3) Upstream mongrel cluster: how to find out mongrel instance (port) which handles request
I was using the following lines in my _debug.html.erb partial:
<% session.cgi.inspect.split(/,/).each{ |key| @mongrel_port = key
if(key =~ /@port/)} %>
<%= @mongrel_port %>
Greetings, Thomas
On 25 Dez., 00:41, ak wrote:
> Thomas, I'm still on Rails 2.1 and would like to do exactly what you
> were doing? What is the Rails 2.1 way? Call
> session.cgi.handler.listener.port ? Will that give the port number of
> the actual instance?
>
> On Dec 8, 3:50 pm, Thomas wrote:
>
>
>
> > For debugging purpose I find it helpful to see which mongrel out of an
> > upstream cluster, specifically which port number, handles an actual
> > request. For example, let the load balancer operate on port 3000
> > (development) and the upstream mongrel cluster operating on ports 4000
> > upto 4002, then I would like to see not only the port 3000 (eg. using
> > request.host_with_port in a controller) but also the port number of
> > the actual mongrel instance.
>
> > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001
> > or 4002), however, I was not able to figure this out in Rails 2.3
> > which is using the rack middleware.
>
> > Any idea, how to do it?
>
> > Greetings and thanks!
> > Thomas
--
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 rubyonrails-t...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: (Rails 2.3) Upstream mongrel cluster: how to find out mongrel instance (port) which handles request
Thomas, I'm still on Rails 2.1 and would like to do exactly what you were doing? What is the Rails 2.1 way? Call session.cgi.handler.listener.port ? Will that give the port number of the actual instance? On Dec 8, 3:50 pm, Thomas wrote: > For debugging purpose I find it helpful to see which mongrel out of an > upstream cluster, specifically which port number, handles an actual > request. For example, let the load balancer operate on port 3000 > (development) and the upstream mongrel cluster operating on ports 4000 > upto 4002, then I would like to see not only the port 3000 (eg. using > request.host_with_port in a controller) but also the port number of > the actual mongrel instance. > > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001 > or 4002), however, I was not able to figure this out in Rails 2.3 > which is using the rack middleware. > > Any idea, how to do it? > > Greetings and thanks! > Thomas -- 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: (Rails 2.3) Upstream mongrel cluster: how to find out mongrel instance (port) which handles request
This helped! Though, a bit strange, the only "hint" for the mongrel port is in request.env["rack.errors"] which is an IO object pointing the logfile of the mongrel. It is something like "/somepath/mongrel.400x.log". Hence request.env["rack.errors"].inspect[/mongrel\.\d+/] verboses the mongrel port of the request. Thanks, this solves my problem, Thomas On 9 Dez., 14:06, Kristian Hellquist wrote: > Does request.env.inspect gives you any hint? > > 2009/12/9 Thomas : > > > > > Hi Kristian, this also results in port number '3000', and not in the > > port number of the upstream mongrel. > > > On 9 Dez., 09:46, Kristian Hellquist > > wrote: > >> Cant you just do `request.server_port' in controller? > > >> 2009/12/9 Thomas : > > >> > For debugging purpose I find it helpful to see which mongrel out of an > >> > upstream cluster, specifically which port number, handles an actual > >> > request. For example, let the load balancer operate on port 3000 > >> > (development) and the upstream mongrel cluster operating on ports 4000 > >> > upto 4002, then I would like to see not only the port 3000 (eg. using > >> > request.host_with_port in a controller) but also the port number of > >> > the actual mongrel instance. > > >> > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001 > >> > or 4002), however, I was not able to figure this out in Rails 2.3 > >> > which is using the rack middleware. > > >> > Any idea, how to do it? > > >> > Greetings and thanks! > >> > Thomas > > >> > -- > > >> > 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 rubyonrails-t...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > rubyonrails-talk+unsubscr...@googlegroups.com. > >> > For more options, visit this group > >> > athttp://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 rubyonrails-t...@googlegroups.com. > > To unsubscribe from this group, send email to > > rubyonrails-talk+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Re: [Rails] Re: (Rails 2.3) Upstream mongrel cluster: how to find out mongrel instance (port) which handles request
Does request.env.inspect gives you any hint? 2009/12/9 Thomas : > Hi Kristian, this also results in port number '3000', and not in the > port number of the upstream mongrel. > > > On 9 Dez., 09:46, Kristian Hellquist > wrote: >> Cant you just do `request.server_port' in controller? >> >> 2009/12/9 Thomas : >> >> >> >> > For debugging purpose I find it helpful to see which mongrel out of an >> > upstream cluster, specifically which port number, handles an actual >> > request. For example, let the load balancer operate on port 3000 >> > (development) and the upstream mongrel cluster operating on ports 4000 >> > upto 4002, then I would like to see not only the port 3000 (eg. using >> > request.host_with_port in a controller) but also the port number of >> > the actual mongrel instance. >> >> > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001 >> > or 4002), however, I was not able to figure this out in Rails 2.3 >> > which is using the rack middleware. >> >> > Any idea, how to do it? >> >> > Greetings and thanks! >> > Thomas >> >> > -- >> >> > 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 rubyonrails-t...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > rubyonrails-talk+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://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 rubyonrails-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: (Rails 2.3) Upstream mongrel cluster: how to find out mongrel instance (port) which handles request
Hi Kristian, this also results in port number '3000', and not in the port number of the upstream mongrel. On 9 Dez., 09:46, Kristian Hellquist wrote: > Cant you just do `request.server_port' in controller? > > 2009/12/9 Thomas : > > > > > For debugging purpose I find it helpful to see which mongrel out of an > > upstream cluster, specifically which port number, handles an actual > > request. For example, let the load balancer operate on port 3000 > > (development) and the upstream mongrel cluster operating on ports 4000 > > upto 4002, then I would like to see not only the port 3000 (eg. using > > request.host_with_port in a controller) but also the port number of > > the actual mongrel instance. > > > With Rails 2.1 I used session.cgi to spot the mongrel port (4000, 4001 > > or 4002), however, I was not able to figure this out in Rails 2.3 > > which is using the rack middleware. > > > Any idea, how to do it? > > > Greetings and thanks! > > Thomas > > > -- > > > 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 rubyonrails-t...@googlegroups.com. > > To unsubscribe from this group, send email to > > rubyonrails-talk+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
[Rails] Re: Rails 2.3 Model.touch(:column) always also updates :updated_at???
So... I put it all into the mySQL triggers now. Saves a lot of ActiveRecord overhead anyway, and keeps this very low-level issue/ optimization away from the "business logic" of the application. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Model.touch(:column) always also updates :updated_at???
Well, I'm using separate timestamps for associated objects as an aid for cache-key generation, to avoid throwing out too many cache entries needlessly. I could look at the updated_at of the associated items themselves - but guess what, I want to save database queries :-) So adding another table is not quite the way. I consider writing my own (SQL-based!) method, especially after finding out through the lighthouse ticket mentioned previously that all the validations are called. I have quite a few triggers and procedures in the database already anyway doing stuff behind rails' back, I would just like to limit those to certain critical areas, and a (non-frequent) timestamp update wasn't on my list of things to do through trigger rather than through actvierecord. Thanks, Michael On Oct 16, 3:06 pm, Patrick Doyle wrote: ... > Create a separate table with a 1:1 relationship to your current table ... --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Model.touch(:column) always also updates :updated_at???
In the mean time, can you work around this issue with something like: Create a separate table with a 1:1 relationship to your current table Migrate the field you want to touch to the new table. Touch the field in that table, which will leave the updated_at field in your original table alone. You could even make the new table without the timestamps fields, if you wanted. --wpd --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Model.touch(:column) always also updates :updated_at???
> Michael, is the attribute that you're passing to the touch method a field of > type datetime or date? If not, then it only makes > sense that field that you're passing to the touch method is one of those. It is "datetime". But anyway, just looking at the code for "touch" I can't see how it's is supposed to NOT always write updated_at - it uses write_attribute which as far as I found out only changes the in-memory object, there must be a "save" somewhere else and that goe4s through the usual validations etc. There's a lighthouse ticket for "touch" calling for it not to do validations (https://rails.lighthouseapp.com/projects/ 8994-ruby-on-rails/tickets/2520-patch-activerecordtouch-without- validations). --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Model.touch(:column) always also updates :updated_at???
On Fri, Oct 16, 2009 at 4:57 AM, michael.hasenst...@googlemail.com < michael.hasenst...@googlemail.com> wrote: > > Hi, > > Am I the only one (i.e. something I do is wrong), or does the touch- > method always update updated_at, even though giving it a column to use > INSTEAD is meant to update just that column??? > > Thanks, > > Michael > > Michael, is the attribute that you're passing to the touch method a field of type datetime or date? If not, then it only makes sense that field that you're passing to the touch method is one of those. Good luck, -Conrad > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and production mode
Marnen Laibow-Koser wrote: > It's only necessary if you can't set environment variables on the system > you're running on. > > Best, > -- > Marnen Laibow-Koser > http://www.marnen.org > mar...@marnen.org I see. Thanks. -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and production mode
Pål Bergström wrote: > Is it necessary to add ENV['RAILS_ENV'] ||= 'production' in rails 2.3.x > environment.rb? It's not there by default anymore. It's only necessary if you can't set environment variables on the system you're running on. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
I was having the same problem. I use NotRemoteRunner in dev mode and StarlingRunner in production right now. I found that putting the following code in development.rb solved my problem: config.after_initialize do Workling::Remote.dispatcher = Workling::Remote::Runners::NotRemoteRunner.new end Thanks! -ajg- Freddy Andersen wrote: > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > your Workling loader a after_init like so: > > config.after_initialize do > Workling::Remote.dispatcher = > Workling::Remote::Runners::StarlingRunner.new > end -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
Hi Marnen Laibow-Koser Thanks a lot I installed git on my server and finally i was able to install active_scaffold plugin. Thanks a lot to all, for ur quick replays On Jul 31, 10:42 am, seenu wrote: > i tried even with http also, it is just creating active_scaffold > folder and nothing happens my ruby version is 1.8.6 > > Thanks for suggestions > > help me out > > On Jul 31, 2:08 am, Kieran P wrote: > > > You may not have Git installed. I ran into this issue before. Try the > > http protocol instead and see if that makes a difference. > > > > script/plugin installhttp://github.com/activescaffold/active_scaffold.git > > > Regards > > Kieran > > > On Jul 30, 10:52 pm, seenu wrote: > > > > the command i used > > > C:\InstantRails\rails_apps\new_pb>script/plugin install > > > git://github.com/activescaffold/active_scaffold.git > > > > On Jul 30, 3:49 pm, seenu wrote: > > > > > Hi, > > > > > I have upgraded to rails 2.3 and active_scaffold plugin is not > > > > working. > > > > when i run this command it creates a active_sacaffold folder in vendor/ > > > > plugins, but its an empty folder. I googled but found no way to > > > > install it. > > > > > Please help! --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
i tried even with http also, it is just creating active_scaffold folder and nothing happens my ruby version is 1.8.6 Thanks for suggestions help me out On Jul 31, 2:08 am, Kieran P wrote: > You may not have Git installed. I ran into this issue before. Try the > http protocol instead and see if that makes a difference. > > > script/plugin installhttp://github.com/activescaffold/active_scaffold.git > > Regards > Kieran > > On Jul 30, 10:52 pm, seenu wrote: > > > the command i used > > C:\InstantRails\rails_apps\new_pb>script/plugin install > > git://github.com/activescaffold/active_scaffold.git > > > On Jul 30, 3:49 pm, seenu wrote: > > > > Hi, > > > > I have upgraded to rails 2.3 and active_scaffold plugin is not > > > working. > > > when i run this command it creates a active_sacaffold folder in vendor/ > > > plugins, but its an empty folder. I googled but found no way to > > > install it. > > > > Please help! --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
You may not have Git installed. I ran into this issue before. Try the http protocol instead and see if that makes a difference. > script/plugin install http://github.com/activescaffold/active_scaffold.git Regards Kieran On Jul 30, 10:52 pm, seenu wrote: > the command i used > C:\InstantRails\rails_apps\new_pb>script/plugin install > git://github.com/activescaffold/active_scaffold.git > > On Jul 30, 3:49 pm, seenu wrote: > > > Hi, > > > I have upgraded to rails 2.3 and active_scaffold plugin is not > > working. > > when i run this command it creates a active_sacaffold folder in vendor/ > > plugins, but its an empty folder. I googled but found no way to > > install it. > > > Please help! --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
seenu wrote: > the command i used > C:\InstantRails\rails_apps\new_pb>script/plugin install > git://github.com/activescaffold/active_scaffold.git Do you have a git client installed and in your path? Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
What version of Ruby are you running? On Jul 30, 7:22 am, seenu wrote: > No, i don't know exactly if it work with rails 2.3.3 > > Thanks > > On Jul 30, 3:57 pm, Conrad Taylor wrote: > > > On Thu, Jul 30, 2009 at 3:49 AM, seenu wrote: > > > > Hi, > > > > I have upgraded to rails 2.3 and active_scaffold plugin is not > > > working. > > > when i run this command it creates a active_sacaffold folder in vendor/ > > > plugins, but its an empty folder. I googled but found no way to > > > install it. > > > > Please help! > > > Are you sure that the plugin works with 2.3.3? If not, I would check with > > the author. > > > -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
No, i don't know exactly if it work with rails 2.3.3 Thanks On Jul 30, 3:57 pm, Conrad Taylor wrote: > On Thu, Jul 30, 2009 at 3:49 AM, seenu wrote: > > > Hi, > > > I have upgraded to rails 2.3 and active_scaffold plugin is not > > working. > > when i run this command it creates a active_sacaffold folder in vendor/ > > plugins, but its an empty folder. I googled but found no way to > > install it. > > > Please help! > > Are you sure that the plugin works with 2.3.3? If not, I would check with > the author. > > -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
On Thu, Jul 30, 2009 at 3:49 AM, seenu wrote: > > > Hi, > > I have upgraded to rails 2.3 and active_scaffold plugin is not > working. > when i run this command it creates a active_sacaffold folder in vendor/ > plugins, but its an empty folder. I googled but found no way to > install it. > > Please help! Are you sure that the plugin works with 2.3.3? If not, I would check with the author. -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3.x and active_scaffold Installation
the command i used C:\InstantRails\rails_apps\new_pb>script/plugin install git://github.com/activescaffold/active_scaffold.git On Jul 30, 3:49 pm, seenu wrote: > Hi, > > I have upgraded to rails 2.3 and active_scaffold plugin is not > working. > when i run this command it creates a active_sacaffold folder in vendor/ > plugins, but its an empty folder. I googled but found no way to > install it. > > Please help! --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: rails 2.3 view caching in development
On Tue, Jun 23, 2009 at 10:16 AM, trybeee wrote: > > Anybody knows hot to disable views caching in development on rails 2.3? > This should already be set in config/environments/development.rb config.action_controller.perform_caching = false Andrew Timberlake http://ramblingsonrails.com http://MyMvelope.com - The SIMPLE way to manage your savings --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Localized Views issues with IE
This might be the solution you are looking for http://agilerails.wordpress.com/2009/05/27/ie-throws-file-download-security-warning-on-form-submit/ On May 24, 11:07 pm, chris wrote: > Hey all, > > Having issues under IE with localized views... whenever it tries to > get a xxx.fr.html.erb IE spits out a File Download Security Warning > dialog ?!? > Firefox works fine... and I cant seem to find any info on the web of > issues of this kind... I'm seeing these problems locally and on my > VPS. > > My Env.: > Rails 2.3.2 > RubyGems 1.3.2 > Ruby 1.8.6 > > Thanks, > Chris --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 memcache performance drop
On Sun, May 24, 2009 at 10:07 AM, erik wrote: > > Hi- > Could tell me how you replaced it? I just installed the newest gem > 1.7.2 and would like to use it with rails. What's the procedure to > remove the bundled gem? > Thanks. > Erik > > On Apr 8, 8:14 pm, Ryan Allen wrote: > > It turned out that the bundled memcache client that came with > > ActiveSupport (1.6.5) was, for some reason, _much_ slower than the one > > we were using before the Rails 2.3 upgrade (we were using fiveruns- > > memcache-client (1.5.0.5), the one that has retries built in). > > > > We've replaced the bundled memcache client with our old one, and it > > performs much better. > > > > On Apr 8, 1:52 pm, Clinton wrote: > > > > > After much effort I upgraded our fairly large Rails app from 2.1 to > > > 2.3. After deployment yesterday I noticed an across the board > > > increase in response times. It seems that every call to memcache now > > > takes 10x longer than before. Here are some example numbers from my > > > development log (below), with memcache running locally. We see > > > similar scale of performance drop in production as well - average > > > memcache call before 2ms, now 20ms. It adds up to a significant hit. > > > > > Before Rails 2.3 upgrade: > > > > > Cached fragment hit: views/homepage_recent_blog_posts (0.00043) > > > Cached fragment hit: views/homepage_active_threads (0.00033) > > > Cached fragment hit: views/homepage_weekly_feature (0.00029) > > > Cached fragment hit: views/homepage_recent_approved_items (0.00036) > > > Cached fragment hit: views/homepage_popular_items (0.00037) > > > Cached fragment hit: views/number_of_members (0.00032) > > > > > After Rails 2.3 upgrade: > > > > > Cached fragment hit: views/homepage_recent_blog_posts (3.2ms) > > > Cached fragment hit: views/homepage_active_threads (3.5ms) > > > Cached fragment hit: views/homepage_weekly_feature (2.9ms) > > > Cached fragment hit: views/homepage_recent_approved_items (2.8ms) > > > Cached fragment hit: views/homepage_popular_items (3.1ms) > > > Cached fragment hit: views/number_of_members (6.7ms) > > > > > Before I start delving into the memcache internals in Rails 2.3, has > > > anyone else experienced this degradation on their apps? Is there a > > > magic 'make it fast again' switch that I can flick? > I was told by Mike Perham that Rails 2.3+ will automatically use any memcache-client gem you have greater than 1.6.4. Good luck, -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 memcache performance drop
Hi- Could tell me how you replaced it? I just installed the newest gem 1.7.2 and would like to use it with rails. What's the procedure to remove the bundled gem? Thanks. Erik On Apr 8, 8:14 pm, Ryan Allen wrote: > It turned out that the bundled memcache client that came with > ActiveSupport (1.6.5) was, for some reason, _much_ slower than the one > we were using before the Rails 2.3 upgrade (we were using fiveruns- > memcache-client (1.5.0.5), the one that has retries built in). > > We've replaced the bundled memcache client with our old one, and it > performs much better. > > On Apr 8, 1:52 pm, Clinton wrote: > > > After much effort I upgraded our fairly large Rails app from 2.1 to > > 2.3. After deployment yesterday I noticed an across the board > > increase in response times. It seems that every call to memcache now > > takes 10x longer than before. Here are some example numbers from my > > development log (below), with memcache running locally. We see > > similar scale of performance drop in production as well - average > > memcache call before 2ms, now 20ms. It adds up to a significant hit. > > > Before Rails 2.3 upgrade: > > > Cached fragment hit: views/homepage_recent_blog_posts (0.00043) > > Cached fragment hit: views/homepage_active_threads (0.00033) > > Cached fragment hit: views/homepage_weekly_feature (0.00029) > > Cached fragment hit: views/homepage_recent_approved_items (0.00036) > > Cached fragment hit: views/homepage_popular_items (0.00037) > > Cached fragment hit: views/number_of_members (0.00032) > > > After Rails 2.3 upgrade: > > > Cached fragment hit: views/homepage_recent_blog_posts (3.2ms) > > Cached fragment hit: views/homepage_active_threads (3.5ms) > > Cached fragment hit: views/homepage_weekly_feature (2.9ms) > > Cached fragment hit: views/homepage_recent_approved_items (2.8ms) > > Cached fragment hit: views/homepage_popular_items (3.1ms) > > Cached fragment hit: views/number_of_members (6.7ms) > > > Before I start delving into the memcache internals in Rails 2.3, has > > anyone else experienced this degradation on their apps? Is there a > > magic 'make it fast again' switch that I can flick? --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 and TimeZone
I encountered this problem today with Rails 2.3 and SQL Server. It
turns out the problem is a bug in the activerecord-sqlserver-adapter
gem; it uses Time.mktime to parse the datetime entries coming from the
database, but Time.mktime is affected the the TZ environment variable
of the Rails application. Unless ENV['TZ'] is set to "GMT" or "UTC"
the local timezone will be applied to the UTC time value being read
from the database. I monkey patched the gem by modifying lib/
active_record/connection_adapters/sqlserver_adapter.rb to change all
invocations of Time.mktime to Time.gm instead, which does the same
thing except ignores the current timezone and creates the Time object
in UTC. I've submitted a patch to the people that I think might be
maintaining the gem, so hopefully this will be a non-issue in future
versions of activerecord-sqlserver-adapter.
If anyone has a better solution to suggest, then please do let me
know.
I do have a warning to anyone using a non-standard
config.active_record.default_timezone value as a workaround: setting
this value causes Rails to store your time data in non-UTC values,
which is bad. It is an even worse solution if your timezone observes
daylight savings because then you cannot even recover the correct time
from your database for 1 hour each year.
--
Michael H Buselli
On Apr 6, 8:48 am, Chris Johnson wrote:
> We also had issues with this. One thing that seemed to work (and might not
> in your situation) was to convert to localtime then convert back to UTC,
> don't ask me why. We had the issue when posting a UTC time as a hidden
> field to (because the localtime was shown to the user) and then needed to
> compare with the database time to get it to work.
>
> date_time =
> (params[:audit][:date_time].to_time).localtime.strftime('%Y-%m-%d
> %H:%M:%S').to_time
>
> @date_time = date_time.utc.strftime('%Y-%m-%d %H:%M:%S')
>
> if you have more questions hit me up on gTalk ch...@johnsonch.com
>
> -Chris
>
> On Mon, Apr 6, 2009 at 7:03 AM, Paul Mcconnon <
>
>
>
> rails-mailing-l...@andreas-s.net> wrote:
>
> > Hi there,
>
> > has anyone come up with a way around this problem?
>
> > It seems to be related to SQL server only. I only seem to have the
> > problem since upgrading from a Rails 2.0 app to 2.3
>
> > I have set both
>
> > config.time_zone = 'UTC'
> > config.active_record.default_timezone = 'UTC'
>
> > I have tried changing
>
> > My dates are being adjusted (having an hour removed) when written to the
> > database (as I am in Uk daylight savings time) but they don't get
> > readjusted on the way back (As I suppose there are no offsets stored in
> > SQL server datetime columns)
>
> > Is there any way to switch time-zone support off altogether and stop any
> > adjustment happening at all?
>
> > Regards,
>
> > Paul
>
> > Rick Schumeyer wrote:
> > > My rails 2.3 app is interpreting times retrieved from the database as
> > > local (in my case, Eastern) instead of UTC. I created a test table in
> > > a SQL Server database with one row. The table is called events and
> > > contains an "edate" column. The value is "2009-03-30 12:00", and is a
> > > UTC time.
>
> > > environment.rb contains
> > > config.time_zone = 'UTC'
>
> > > The output from script/console is below. (results are identical to
> > > using a browser)
>
> > > It looks like rails is assuming the database value is really a local
> > > time, and it adds four hours to get UTC. But that is wrong, since the
> > > time is already UTC.
>
> > > What else do I need to do to convince rails to leave the time value
> > > alone, since it *is* a UTC value?
>
> > > I can get the correct value by extracting the "Time" with no zone, and
> > > then recreating a new TimeWithZone. But that can't be the best way!
>
> > > Loading development environment (Rails 2.3.2)
> > >>> Time.zone
> > > => # > > @name="UTC">
> > >>> event=Event.find(1)
> > > => #
> > >>> event.edate
> > > => Mon, 30 Mar 2009 16:00:00 UTC +00:00
> > >>> zutc= ActiveSupport::TimeZone.new('UTC')
> > > => # > > @tzinfo=#, @utc_offset=0, @name="UTC">
> > >>> correct_time =
> > ActiveSupport::TimeWithZone.new(event.edate.localtime,zutc)
> > > => Mon, 30 Mar 2009 12:00:00 UTC +00:00
>
> > --
> > Posted viahttp://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Hi guys,
I got the same problem this morning. workling throws memcache error on
2.3
Found out that after_init solution works. And if you are using
workling + spawner, these lines work fine with me
config.after_initialize do
Workling::Remote::Runners::SpawnRunner.options = { :method
=> :spawn }
Workling::Remote.dispatcher =
Workling::Remote::Runners::SpawnRunner.new
end
Cheers!
On Apr 9, 10:09 pm, tomrossi7 wrote:
> Steve,
>
> I put a debugger statement in the plugin to figure out the problem.
> The error is definitely telling you that memcache hasn't been loaded.
> You may need to move that require 'memcache' statement around to make
> sure it is loading. Let me know what you find...
>
> Thanks,
> Tom
>
> On Apr 9, 9:18 am, Steve Odom wrote:
>
> > Unfortunately it didn't solve the problem. I guess I could switch over
> > to starling and that might solve it.
>
> > On Apr 8, 9:16 am, tomrossi7 wrote:
>
> > > Ugh. But did it solve the problem?
>
> > > On Apr 8, 9:59 am, Steve Odom wrote:
>
> > > > Thanks Tom. The crappy part is I'm not using memcache for anything at
> > > > the moment.
>
> > > > Steve
>
> > > > On Apr 8, 7:31 am, tomrossi7 wrote:
>
> > > > > Steve,
>
> > > > > Try throwing require 'memcache' in your environment.rb? I think that
> > > > > is how I finally got around it...
>
> > > > > Thanks,
> > > > > Tom
>
> > > > > On Apr 7, 11:19 pm, Steve Odom wrote:
>
> > > > > > I'm having the same issue as Tom, but I'm not using Starling. I'm
> > > > > > using spawn. I don't have anything in an initializer to wrap in a
> > > > > > after_initialize.
>
> > > > > > Any ideas how to get workling to work in 2.3?
>
> > > > > > Steve
>
> > > > > > On Apr 7, 7:14 pm, Freddy Andersen wrote:
>
> > > > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap
> > > > > > > your Workling loader a after_init like so:
>
> > > > > > > config.after_initialize do
> > > > > > > Workling::Remote.dispatcher =
> > > > > > > Workling::Remote::Runners::StarlingRunner.new
> > > > > > > end
>
> > > > > > > On Mar 20, 6:42 am, TomRossi7 wrote:
>
> > > > > > > > One of the plugins I use is Workling. It throws the following
> > > > > > > > error
> > > > > > > > when I try to run it under 2.3:
>
> > > > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/
> > > > > > > > dependencies.rb:443:in `load_missing_constant': uninitialized
> > > > > > > > constantMemCache(NameError)
>
> > > > > > > > The offending line is:
>
> > > > > > > > @@memcache_client_class ||= ::MemCache
>
> > > > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed
> > > > > > > > with
> > > > > > > > 2.3 that could cause the error. Anyone have some ideas?
>
> > > > > > > > Thanks!
> > > > > > > > Tom
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3
Binh Ly wrote: > Hello, > > I've been looking on the Internet for how to use libxml within Rails. > What I'm seeing is a little confusing. If you install the libxml gem, > will Rails automatically use that because its installed or do you have > to explicitly set libxml to be the default after you've installed it? > > This posting > > http://www.coffeepowered.net/2009/03/16/things-to-do-when-upgrading-to-rails-23/ > > Says to set this in the environment file. > >1. > ActiveSupport::XmlMini.backend = 'LibXML' > > But when I do that my app crashes. Anyone have any experience with > this? > If you could provide the entire backtrace, it would be much easier to diagnose. Michael Guterl -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Steve, I put a debugger statement in the plugin to figure out the problem. The error is definitely telling you that memcache hasn't been loaded. You may need to move that require 'memcache' statement around to make sure it is loading. Let me know what you find... Thanks, Tom On Apr 9, 9:18 am, Steve Odom wrote: > Unfortunately it didn't solve the problem. I guess I could switch over > to starling and that might solve it. > > On Apr 8, 9:16 am, tomrossi7 wrote: > > > Ugh. But did it solve the problem? > > > On Apr 8, 9:59 am, Steve Odom wrote: > > > > Thanks Tom. The crappy part is I'm not using memcache for anything at > > > the moment. > > > > Steve > > > > On Apr 8, 7:31 am, tomrossi7 wrote: > > > > > Steve, > > > > > Try throwing require 'memcache' in your environment.rb? I think that > > > > is how I finally got around it... > > > > > Thanks, > > > > Tom > > > > > On Apr 7, 11:19 pm, Steve Odom wrote: > > > > > > I'm having the same issue as Tom, but I'm not using Starling. I'm > > > > > using spawn. I don't have anything in an initializer to wrap in a > > > > > after_initialize. > > > > > > Any ideas how to get workling to work in 2.3? > > > > > > Steve > > > > > > On Apr 7, 7:14 pm, Freddy Andersen wrote: > > > > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > > > > > your Workling loader a after_init like so: > > > > > > > config.after_initialize do > > > > > > Workling::Remote.dispatcher = > > > > > > Workling::Remote::Runners::StarlingRunner.new > > > > > > end > > > > > > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > > > > > > One of the plugins I use is Workling. It throws the following > > > > > > > error > > > > > > > when I try to run it under 2.3: > > > > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > > > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > > > > > constantMemCache(NameError) > > > > > > > > The offending line is: > > > > > > > > @@memcache_client_class ||= ::MemCache > > > > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed > > > > > > > with > > > > > > > 2.3 that could cause the error. Anyone have some ideas? > > > > > > > > Thanks! > > > > > > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Unfortunately it didn't solve the problem. I guess I could switch over to starling and that might solve it. On Apr 8, 9:16 am, tomrossi7 wrote: > Ugh. But did it solve the problem? > > On Apr 8, 9:59 am, Steve Odom wrote: > > > Thanks Tom. The crappy part is I'm not using memcache for anything at > > the moment. > > > Steve > > > On Apr 8, 7:31 am, tomrossi7 wrote: > > > > Steve, > > > > Try throwing require 'memcache' in your environment.rb? I think that > > > is how I finally got around it... > > > > Thanks, > > > Tom > > > > On Apr 7, 11:19 pm, Steve Odom wrote: > > > > > I'm having the same issue as Tom, but I'm not using Starling. I'm > > > > using spawn. I don't have anything in an initializer to wrap in a > > > > after_initialize. > > > > > Any ideas how to get workling to work in 2.3? > > > > > Steve > > > > > On Apr 7, 7:14 pm, Freddy Andersen wrote: > > > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > > > > your Workling loader a after_init like so: > > > > > > config.after_initialize do > > > > > Workling::Remote.dispatcher = > > > > > Workling::Remote::Runners::StarlingRunner.new > > > > > end > > > > > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > > > > > One of the plugins I use is Workling. It throws the following error > > > > > > when I try to run it under 2.3: > > > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > > > > constantMemCache(NameError) > > > > > > > The offending line is: > > > > > > > @@memcache_client_class ||= ::MemCache > > > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > > > > > 2.3 that could cause the error. Anyone have some ideas? > > > > > > > Thanks! > > > > > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 memcache performance drop
It turned out that the bundled memcache client that came with ActiveSupport (1.6.5) was, for some reason, _much_ slower than the one we were using before the Rails 2.3 upgrade (we were using fiveruns- memcache-client (1.5.0.5), the one that has retries built in). We've replaced the bundled memcache client with our old one, and it performs much better. On Apr 8, 1:52 pm, Clinton wrote: > After much effort I upgraded our fairly large Rails app from 2.1 to > 2.3. After deployment yesterday I noticed an across the board > increase in response times. It seems that every call to memcache now > takes 10x longer than before. Here are some example numbers from my > development log (below), with memcache running locally. We see > similar scale of performance drop in production as well - average > memcache call before 2ms, now 20ms. It adds up to a significant hit. > > Before Rails 2.3 upgrade: > > Cached fragment hit: views/homepage_recent_blog_posts (0.00043) > Cached fragment hit: views/homepage_active_threads (0.00033) > Cached fragment hit: views/homepage_weekly_feature (0.00029) > Cached fragment hit: views/homepage_recent_approved_items (0.00036) > Cached fragment hit: views/homepage_popular_items (0.00037) > Cached fragment hit: views/number_of_members (0.00032) > > After Rails 2.3 upgrade: > > Cached fragment hit: views/homepage_recent_blog_posts (3.2ms) > Cached fragment hit: views/homepage_active_threads (3.5ms) > Cached fragment hit: views/homepage_weekly_feature (2.9ms) > Cached fragment hit: views/homepage_recent_approved_items (2.8ms) > Cached fragment hit: views/homepage_popular_items (3.1ms) > Cached fragment hit: views/number_of_members (6.7ms) > > Before I start delving into the memcache internals in Rails 2.3, has > anyone else experienced this degradation on their apps? Is there a > magic 'make it fast again' switch that I can flick? --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Ugh. But did it solve the problem? On Apr 8, 9:59 am, Steve Odom wrote: > Thanks Tom. The crappy part is I'm not using memcache for anything at > the moment. > > Steve > > On Apr 8, 7:31 am, tomrossi7 wrote: > > > Steve, > > > Try throwing require 'memcache' in your environment.rb? I think that > > is how I finally got around it... > > > Thanks, > > Tom > > > On Apr 7, 11:19 pm, Steve Odom wrote: > > > > I'm having the same issue as Tom, but I'm not using Starling. I'm > > > using spawn. I don't have anything in an initializer to wrap in a > > > after_initialize. > > > > Any ideas how to get workling to work in 2.3? > > > > Steve > > > > On Apr 7, 7:14 pm, Freddy Andersen wrote: > > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > > > your Workling loader a after_init like so: > > > > > config.after_initialize do > > > > Workling::Remote.dispatcher = > > > > Workling::Remote::Runners::StarlingRunner.new > > > > end > > > > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > > > > One of the plugins I use is Workling. It throws the following error > > > > > when I try to run it under 2.3: > > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > > > constantMemCache(NameError) > > > > > > The offending line is: > > > > > > @@memcache_client_class ||= ::MemCache > > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > > > > 2.3 that could cause the error. Anyone have some ideas? > > > > > > Thanks! > > > > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Thanks Tom. The crappy part is I'm not using memcache for anything at the moment. Steve On Apr 8, 7:31 am, tomrossi7 wrote: > Steve, > > Try throwing require 'memcache' in your environment.rb? I think that > is how I finally got around it... > > Thanks, > Tom > > On Apr 7, 11:19 pm, Steve Odom wrote: > > > I'm having the same issue as Tom, but I'm not using Starling. I'm > > using spawn. I don't have anything in an initializer to wrap in a > > after_initialize. > > > Any ideas how to get workling to work in 2.3? > > > Steve > > > On Apr 7, 7:14 pm, Freddy Andersen wrote: > > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > > your Workling loader a after_init like so: > > > > config.after_initialize do > > > Workling::Remote.dispatcher = > > > Workling::Remote::Runners::StarlingRunner.new > > > end > > > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > > > One of the plugins I use is Workling. It throws the following error > > > > when I try to run it under 2.3: > > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > > constantMemCache(NameError) > > > > > The offending line is: > > > > > @@memcache_client_class ||= ::MemCache > > > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > > > 2.3 that could cause the error. Anyone have some ideas? > > > > > Thanks! > > > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
Steve, Try throwing require 'memcache' in your environment.rb? I think that is how I finally got around it... Thanks, Tom On Apr 7, 11:19 pm, Steve Odom wrote: > I'm having the same issue as Tom, but I'm not using Starling. I'm > using spawn. I don't have anything in an initializer to wrap in a > after_initialize. > > Any ideas how to get workling to work in 2.3? > > Steve > > On Apr 7, 7:14 pm, Freddy Andersen wrote: > > > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > > your Workling loader a after_init like so: > > > config.after_initialize do > > Workling::Remote.dispatcher = > > Workling::Remote::Runners::StarlingRunner.new > > end > > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > > One of the plugins I use is Workling. It throws the following error > > > when I try to run it under 2.3: > > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > > dependencies.rb:443:in `load_missing_constant': uninitialized > > > constantMemCache(NameError) > > > > The offending line is: > > > > @@memcache_client_class ||= ::MemCache > > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > > 2.3 that could cause the error. Anyone have some ideas? > > > > Thanks! > > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
I'm having the same issue as Tom, but I'm not using Starling. I'm using spawn. I don't have anything in an initializer to wrap in a after_initialize. Any ideas how to get workling to work in 2.3? Steve On Apr 7, 7:14 pm, Freddy Andersen wrote: > I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap > your Workling loader a after_init like so: > > config.after_initialize do > Workling::Remote.dispatcher = > Workling::Remote::Runners::StarlingRunner.new > end > > On Mar 20, 6:42 am, TomRossi7 wrote: > > > One of the plugins I use is Workling. It throws the following error > > when I try to run it under 2.3: > > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > > dependencies.rb:443:in `load_missing_constant': uninitialized > > constantMemCache(NameError) > > > The offending line is: > > > @@memcache_client_class ||= ::MemCache > > > I don't know a lot aboutmemcache, so I'm not sure what changed with > > 2.3 that could cause the error. Anyone have some ideas? > > > Thanks! > > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Upgrade Issue with MemCache
I'm not sure why this happens, BUT in rails 2.3.2 you have to wrap your Workling loader a after_init like so: config.after_initialize do Workling::Remote.dispatcher = Workling::Remote::Runners::StarlingRunner.new end On Mar 20, 6:42 am, TomRossi7 wrote: > One of the plugins I use is Workling. It throws the following error > when I try to run it under 2.3: > > /Library/Ruby/Gems/1.8/gems/activesupport-2.3.2/lib/active_support/ > dependencies.rb:443:in `load_missing_constant': uninitialized > constantMemCache(NameError) > > The offending line is: > > @@memcache_client_class ||= ::MemCache > > I don't know a lot aboutmemcache, so I'm not sure what changed with > 2.3 that could cause the error. Anyone have some ideas? > > Thanks! > Tom --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 and TimeZone
We also had issues with this. One thing that seemed to work (and might not
in your situation) was to convert to localtime then convert back to UTC,
don't ask me why. We had the issue when posting a UTC time as a hidden
field to (because the localtime was shown to the user) and then needed to
compare with the database time to get it to work.
date_time =
(params[:audit][:date_time].to_time).localtime.strftime('%Y-%m-%d
%H:%M:%S').to_time
@date_time = date_time.utc.strftime('%Y-%m-%d %H:%M:%S')
if you have more questions hit me up on gTalk ch...@johnsonch.com
-Chris
On Mon, Apr 6, 2009 at 7:03 AM, Paul Mcconnon <
rails-mailing-l...@andreas-s.net> wrote:
>
> Hi there,
>
> has anyone come up with a way around this problem?
>
> It seems to be related to SQL server only. I only seem to have the
> problem since upgrading from a Rails 2.0 app to 2.3
>
> I have set both
>
> config.time_zone = 'UTC'
> config.active_record.default_timezone = 'UTC'
>
> I have tried changing
>
> My dates are being adjusted (having an hour removed) when written to the
> database (as I am in Uk daylight savings time) but they don't get
> readjusted on the way back (As I suppose there are no offsets stored in
> SQL server datetime columns)
>
> Is there any way to switch time-zone support off altogether and stop any
> adjustment happening at all?
>
> Regards,
>
> Paul
>
>
>
> Rick Schumeyer wrote:
> > My rails 2.3 app is interpreting times retrieved from the database as
> > local (in my case, Eastern) instead of UTC. I created a test table in
> > a SQL Server database with one row. The table is called events and
> > contains an "edate" column. The value is "2009-03-30 12:00", and is a
> > UTC time.
> >
> > environment.rb contains
> > config.time_zone = 'UTC'
> >
> > The output from script/console is below. (results are identical to
> > using a browser)
> >
> > It looks like rails is assuming the database value is really a local
> > time, and it adds four hours to get UTC. But that is wrong, since the
> > time is already UTC.
> >
> > What else do I need to do to convince rails to leave the time value
> > alone, since it *is* a UTC value?
> >
> > I can get the correct value by extracting the "Time" with no zone, and
> > then recreating a new TimeWithZone. But that can't be the best way!
> >
> > Loading development environment (Rails 2.3.2)
> >>> Time.zone
> > => # > @name="UTC">
> >>> event=Event.find(1)
> > => #
> >>> event.edate
> > => Mon, 30 Mar 2009 16:00:00 UTC +00:00
> >>> zutc= ActiveSupport::TimeZone.new('UTC')
> > => # > @tzinfo=#, @utc_offset=0, @name="UTC">
> >>> correct_time =
> ActiveSupport::TimeWithZone.new(event.edate.localtime,zutc)
> > => Mon, 30 Mar 2009 12:00:00 UTC +00:00
>
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 and TimeZone
Hi there,
has anyone come up with a way around this problem?
It seems to be related to SQL server only. I only seem to have the
problem since upgrading from a Rails 2.0 app to 2.3
I have set both
config.time_zone = 'UTC'
config.active_record.default_timezone = 'UTC'
I have tried changing
My dates are being adjusted (having an hour removed) when written to the
database (as I am in Uk daylight savings time) but they don't get
readjusted on the way back (As I suppose there are no offsets stored in
SQL server datetime columns)
Is there any way to switch time-zone support off altogether and stop any
adjustment happening at all?
Regards,
Paul
Rick Schumeyer wrote:
> My rails 2.3 app is interpreting times retrieved from the database as
> local (in my case, Eastern) instead of UTC. I created a test table in
> a SQL Server database with one row. The table is called events and
> contains an "edate" column. The value is "2009-03-30 12:00", and is a
> UTC time.
>
> environment.rb contains
> config.time_zone = 'UTC'
>
> The output from script/console is below. (results are identical to
> using a browser)
>
> It looks like rails is assuming the database value is really a local
> time, and it adds four hours to get UTC. But that is wrong, since the
> time is already UTC.
>
> What else do I need to do to convince rails to leave the time value
> alone, since it *is* a UTC value?
>
> I can get the correct value by extracting the "Time" with no zone, and
> then recreating a new TimeWithZone. But that can't be the best way!
>
> Loading development environment (Rails 2.3.2)
>>> Time.zone
> => # @name="UTC">
>>> event=Event.find(1)
> => #
>>> event.edate
> => Mon, 30 Mar 2009 16:00:00 UTC +00:00
>>> zutc= ActiveSupport::TimeZone.new('UTC')
> => # @tzinfo=#, @utc_offset=0, @name="UTC">
>>> correct_time = ActiveSupport::TimeWithZone.new(event.edate.localtime,zutc)
> => Mon, 30 Mar 2009 12:00:00 UTC +00:00
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Sessions
Your suggestion helped a lot! I've followed a slightly different approach,
but using your idea. What I did was add the following private method in my
login controller:
def session_user_id(id)
ActiveRecord::Base.connection.update("UPDATE sessions SET user_id =
#{id} WHERE session_id = '#{request.session.session_id}'")
end
And then I just do this in the login action:
session[:user] = user.id
session_user_id(session[:user])
I think that there is an advantage in this approach. No need to deal with
any custom session classes and the method is only available where it should
be.
cheers!
On Wed, Apr 1, 2009 at 9:17 PM, Scottie35 wrote:
>
> On Mar 26, 12:45 pm, Danilo Castilho wrote:
> > I've just upgraded to Rails 2.3.2. I am using active_record_store as
> > my session approach and session.model is deprecated. I was using that
> > to update a couple extra session db columns. Does anyone knows what is
> > the best approach for that now, since ActiveRecord::SessionStore does
> > not help that much?
>
> I had the exact same problem, and I couldn't find any help anywhere.
> So I played with it until I got it to work. This is what I did to put
> the user id in the sessions table upon login:
>
> In session.rb:
>
> class Session < ActiveRecord::Base
>def self.update_user_id(id, sess_id)
>connection.update("UPDATE sessions SET user_id = '#{id}'
> WHERE
> session_id = '#{sess_id}'")
>end
> end
>
> In login action in the controller:
>
> if session[:userid] = User.authenticate(params[:user][:username],
> params[:user][:password])
>Session.update_user_id(session[:userid], request.session.session_id)
>[...]
>
> IOW, this:
>
> session.model.user_id = session[:userid]
>
> becomes this:
>
> Session.update_user_id(session[:userid], request.session.session_id)
>
> Apparently one has to call "session[:userid]" or in order to
> "activate" the session since it is now lazy (ie it won't load unless
> you access it). Otherwise, the "request.session.session_id" part won't
> work.
>
> Hope this helps!
>
> >
>
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Sessions
On Mar 26, 12:45 pm, Danilo Castilho wrote:
> I've just upgraded to Rails 2.3.2. I am using active_record_store as
> my session approach and session.model is deprecated. I was using that
> to update a couple extra session db columns. Does anyone knows what is
> the best approach for that now, since ActiveRecord::SessionStore does
> not help that much?
I had the exact same problem, and I couldn't find any help anywhere.
So I played with it until I got it to work. This is what I did to put
the user id in the sessions table upon login:
In session.rb:
class Session < ActiveRecord::Base
def self.update_user_id(id, sess_id)
connection.update("UPDATE sessions SET user_id = '#{id}' WHERE
session_id = '#{sess_id}'")
end
end
In login action in the controller:
if session[:userid] = User.authenticate(params[:user][:username],
params[:user][:password])
Session.update_user_id(session[:userid], request.session.session_id)
[...]
IOW, this:
session.model.user_id = session[:userid]
becomes this:
Session.update_user_id(session[:userid], request.session.session_id)
Apparently one has to call "session[:userid]" or in order to
"activate" the session since it is now lazy (ie it won't load unless
you access it). Otherwise, the "request.session.session_id" part won't
work.
Hope this helps!
--~--~-~--~~~---~--~~
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 rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Nested models
Yeah, thanks, I did end up finding that and it has been helpful... On Mar 22, 10:04 pm, JL Smith wrote: > This should get you going...also check out the links at the end under > "Resources". > > http://ryandaigle.com/articles/2009/2/1/what-s-new-in-edge-rails-nest... --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 Nested models
This should get you going...also check out the links at the end under "Resources". http://ryandaigle.com/articles/2009/2/1/what-s-new-in-edge-rails-nested-attributes --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 really checks for presence of $RAILS_ROOT/public/index.html
On 21 Mar., 01:28, Sudhir wrote: > Just sharing a Rail 2.3.2 upgrade experience. My app was running on > 2.1.1 before I upgraded. > > Most things worked but I could not get my default route in routes.rb > to work. The default route URL was "/". I had a route like this in > routes.rb as the very last route: > > map.connect "", :controller => "foo", :action => "bar" > > So users who went to the base URL would be directed to the foo > controller. > > This stopped working with Rails 2.3.2 and I wasted half a day figuring > out what was wrong. Turns out, I just needed to delete public/ > index.html. That's it. The same route works perfectly after deleting > that file. > > There is a comment in the Rails code which mentions this but I don't > see it in the documentation for Rails routes. On 21 Mar., 01:28, Sudhir wrote: > Just sharing a Rail 2.3.2 upgrade experience. My app was running on > 2.1.1 before I upgraded. > > Most things worked but I could not get my default route in routes.rb > to work. The default route URL was "/". I had a route like this in > routes.rb as the very last route: > > map.connect "", :controller => "foo", :action => "bar" > > So users who went to the base URL would be directed to the foo > controller. > > This stopped working with Rails 2.3.2 and I wasted half a day figuring > out what was wrong. Turns out, I just needed to delete public/ > index.html. That's it. The same route works perfectly after deleting > that file. > > There is a comment in the Rails code which mentions this but I don't > see it in the documentation for Rails routes. As far as I know your web server will always look in the /public directory to see if any files matches the request, if not it will pass the request on to the app server. So this really shouldn't have worked before either... And by the way, you usually use map.root to make a route that matches a request to the root: map.root :controller => "foo", :action => "bar" -- Cheers, David Knorr http://twitter.com/rubyguy --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 and helpers within plugins
Got it, Just put in my init.rb some lines like: ActionView::Base.send :include, ResourcesHelper ActionView::Base.send :include, AcApplicationHelper ActionView::Base.send :include, LookupHelper thanks On 20 mar, 17:28, acras wrote: > I'm starting to get it. Engines Plugin did some kind of generic > include, making the helpers within a plugin to be available within the > app. > My question now is: how can I do it the best way? > > On 20 mar, 17:18, acras wrote: > > > > > Hi, > > > I'm porting a plugin of mine to work with rails 2.3. My plugin is > > based in engines. > > I'm doing good so far, the only problem is with helpers. Rails seems > > not to recognize helpers from my plugin. > > > Anyone ran into this issue? --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 and helpers within plugins
I'm starting to get it. Engines Plugin did some kind of generic include, making the helpers within a plugin to be available within the app. My question now is: how can I do it the best way? On 20 mar, 17:18, acras wrote: > Hi, > > I'm porting a plugin of mine to work with rails 2.3. My plugin is > based in engines. > I'm doing good so far, the only problem is with helpers. Rails seems > not to recognize helpers from my plugin. > > Anyone ran into this issue? --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 deleting sessions
Ouch, you're right ! I've the same problem, I watch the API and solved ! Try this: ActiveRecord::SessionStore::Session.delete_all ['updated_at < ?', 24.hours.ago] Have fun ! > The following line no longer works in 2.3: > > ActiveRecord::SessionStore.delete_all ['updated_at < ?', 24.hours.ago] > > Does anyone know how to do this in 2.3? > > Thanks, > Jay > > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 deleting sessions
Jay wrote: > The following line no longer works in 2.3: > > ActiveRecord::SessionStore.delete_all ['updated_at < ?', 24.hours.ago] > > Does anyone know how to do this in 2.3? Do you really need to go though Rails to do this? I think I would just write a simple script and execute it in a cron task to clear out old sessions. As far as I can tell, as long as the sessions fit the criteria for cookie based session stores, it seems to me like a very clean way to deal session data. That way the server and database are relieved from the burden of dealing with sessions. I am also looking forward to the day when it becomes feasible to use HTML 5.0 local storage to keep session data. I believe this will be the final solution to dealing with persistent data for web applications. It eliminates the current limitations of cookie based sessions while simultaneously pushing state related information out to the client-side where, IMHO, it belongs. -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
That did it! So anyone reading this, don't forget to "passenger- install-apache2-module" after running a gem update for 2.1.2 Thanks Matt. On Mar 18, 6:16 am, yaphi wrote: > That could very well be it because yes I forgot to do that. Thank you. > > On Mar 17, 8:45 pm, Matt Jones wrote: > > > > > As a sanity check, did you update the location of Passenger in your > > Apache config? > > I've made that mistake... > > > --Matt Jones > > > On Mar 17, 3:09 pm, yaphi wrote: > > > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > > > required) > > > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > > I can no longer login using the latest passenger + Rails 2.3 with the > > > > > restful_authentication plugin. If I run a quick "script/server" > > > > > everything is fine. Anyone else having trouble with this? > > > > > Hi, did you update your project configuration files? i.e. rake > > > > rails:update > > > > > -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
That could very well be it because yes I forgot to do that. Thank you. On Mar 17, 8:45 pm, Matt Jones wrote: > As a sanity check, did you update the location of Passenger in your > Apache config? > I've made that mistake... > > --Matt Jones > > On Mar 17, 3:09 pm, yaphi wrote: > > > > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > > required) > > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > I can no longer login using the latest passenger + Rails 2.3 with the > > > > restful_authentication plugin. If I run a quick "script/server" > > > > everything is fine. Anyone else having trouble with this? > > > > Hi, did you update your project configuration files? i.e. rake > > > rails:update > > > > -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
As a sanity check, did you update the location of Passenger in your Apache config? I've made that mistake... --Matt Jones On Mar 17, 3:09 pm, yaphi wrote: > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > required) > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > I can no longer login using the latest passenger + Rails 2.3 with the > > > restful_authentication plugin. If I run a quick "script/server" > > > everything is fine. Anyone else having trouble with this? > > > Hi, did you update your project configuration files? i.e. rake > > rails:update > > > -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
That's the funny part. I get no errors it just spits me back to the login screen. I'm digging into it now and hopefully I find something. On Mar 17, 3:53 pm, Conrad Taylor wrote: > On Tue, Mar 17, 2009 at 12:48 PM, yaphi wrote: > > > Yeah it works when I run script/server which is using mongrel I guess? > > Won't work with my local passenger install. I'll just wait a while > > maybe there's something that changed. > > > On Mar 17, 3:40 pm, Conrad Taylor wrote: > > > On Tue, Mar 17, 2009 at 12:09 PM, yaphi wrote: > > > > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > > > > required) > > > > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > > > I can no longer login using the latest passenger + Rails 2.3 with > > the > > > > > > restful_authentication plugin. If I run a quick "script/server" > > > > > > everything is fine. Anyone else having trouble with this? > > > > > > Hi, did you update your project configuration files? i.e. rake > > > > > rails:update > > > > > > -Conrad > > > > Hi, did you verify that restful_authentication plugin is compatible with > > > Rails 2.3.2? > > > I tend to make a copy of my rails project and experiment with the copy > > when > > > moving > > > to the next release. > > > > -Conrad > > Hi, when you say won't work, you should provide any information about the > error > messages that you're seeing in the web browser or log file. This will help > people > help you. > > -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
On Tue, Mar 17, 2009 at 12:48 PM, yaphi wrote: > > Yeah it works when I run script/server which is using mongrel I guess? > Won't work with my local passenger install. I'll just wait a while > maybe there's something that changed. > > > On Mar 17, 3:40 pm, Conrad Taylor wrote: > > On Tue, Mar 17, 2009 at 12:09 PM, yaphi wrote: > > > > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > > > required) > > > > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > > > I can no longer login using the latest passenger + Rails 2.3 with > the > > > > > restful_authentication plugin. If I run a quick "script/server" > > > > > everything is fine. Anyone else having trouble with this? > > > > > > Hi, did you update your project configuration files? i.e. rake > > > > rails:update > > > > > > -Conrad > > > > Hi, did you verify that restful_authentication plugin is compatible with > > Rails 2.3.2? > > I tend to make a copy of my rails project and experiment with the copy > when > > moving > > to the next release. > > > > -Conrad > Hi, when you say won't work, you should provide any information about the error messages that you're seeing in the web browser or log file. This will help people help you. -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
Yeah it works when I run script/server which is using mongrel I guess? Won't work with my local passenger install. I'll just wait a while maybe there's something that changed. On Mar 17, 3:40 pm, Conrad Taylor wrote: > On Tue, Mar 17, 2009 at 12:09 PM, yaphi wrote: > > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > > required) > > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > I can no longer login using the latest passenger + Rails 2.3 with the > > > > restful_authentication plugin. If I run a quick "script/server" > > > > everything is fine. Anyone else having trouble with this? > > > > Hi, did you update your project configuration files? i.e. rake > > > rails:update > > > > -Conrad > > Hi, did you verify that restful_authentication plugin is compatible with > Rails 2.3.2? > I tend to make a copy of my rails project and experiment with the copy when > moving > to the next release. > > -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
On Tue, Mar 17, 2009 at 12:09 PM, yaphi wrote: > > Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 > required) > > On Mar 17, 3:05 pm, Conrad Taylor wrote: > > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > > > I can no longer login using the latest passenger + Rails 2.3 with the > > > restful_authentication plugin. If I run a quick "script/server" > > > everything is fine. Anyone else having trouble with this? > > > > Hi, did you update your project configuration files? i.e. rake > > rails:update > > > > -Conrad > > > Hi, did you verify that restful_authentication plugin is compatible with Rails 2.3.2? I tend to make a copy of my rails project and experiment with the copy when moving to the next release. -Conrad --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
Yup. I did that, upgraded to Passenger 2.1.2 (which Rails 2.3 required) On Mar 17, 3:05 pm, Conrad Taylor wrote: > On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > > I can no longer login using the latest passenger + Rails 2.3 with the > > restful_authentication plugin. If I run a quick "script/server" > > everything is fine. Anyone else having trouble with this? > > Hi, did you update your project configuration files? i.e. rake > rails:update > > -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3, restful_authentication, and passenger
On Tue, Mar 17, 2009 at 5:03 AM, yaphi wrote: > > I can no longer login using the latest passenger + Rails 2.3 with the > restful_authentication plugin. If I run a quick "script/server" > everything is fine. Anyone else having trouble with this? Hi, did you update your project configuration files? i.e. rake rails:update -Conrad > > > > --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 problem...
The problem was Erubis. This (faster erb renderer) doesn't work with Rails 2.2.2 and 2.3 yet. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
[Rails] Re: Rails 2.3 problem...
It seems to be something with form_for and blocks or something?! It does NOT appear in Rails 2.2.2 however :S -- Posted via http://www.ruby-forum.com/. --~--~-~--~~~---~--~~ 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~--~~~~--~~--~--~---
