similar to: Modules Beta Comments

I track svn/trunk of Rails using svn:externals Some change to Rails committed in the last 1-2 days broke my subclass of ApplicationController The example, below, works with Rails 1.0, but in today''s svn, it dies with the following error: "superclass mismatch for class FooController" class ApplicationController < ActionController::Base end class FooController <

Hi guys, I would expect an ActionController-derived class to reload _completely_ in development mode. class FooController < ApplicationController include FancyStuffSupport def index # bla end # more actions here end However, the ''FancyStuffSupport'' is not reloaded, only the ''FooController'' itself. Can this behaviour be changed? I feel back

In my rspec_on_rails controlle rspec, I have this: require File.dirname(__FILE__) + ''/../spec_helper'' describe FooController, "with a foo" do it "should be false" do get ''index'' assigns[:foo].should be_false end end In my controller I have this: class FooController < ApplicationController def index @foo = FALSE end

I have a lot of controllers with virtually identical functionality for most actions. I''ve been using shared behaviours to DRY things up a bit, but I still have to create separate behaviours for each context before I can use the shared behaviours what I have now is a generic file which contains all the behaviours and examples common to all the controllers, and that file gets loaded from

Hi, In my test case below, it seems that ''initialize'' is called everytime ''hello'' is called. Is this by design, a bug, or my pilot error? class FooController < ApplicationController def initialize print "\n initialize \n" end def hello print "\n hello \n" end end I

Hello all. Is there a way to stop users from being able to access a controllers methods without affecting the ability of other controllers to use them? i.e FooController def secret #Stuff end end BarController def index redirect_to :controller => ''foo'', action => ''secret'', :id => ''007'' end end But directly

Are these two below the same thing? 1. module X module Y class Z 2. class X::Y::Z -- 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Hi, (This is my first post after months of appreciative lurking...) I''m trying to spec the following conditional controller macro: class ApplicationController < ActionController::Base # turn off session management for robots session :off, :if => lambda {|req| req.user_agent =~ /(Google|Slurp)/i } # ... end My current attempt seems to be quite unsuccessful: 1) when I

I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since

Hi! Is it possible to render the action within the after_filter method, or is the rendering performed before? I have something like this: class FooController after_filter :send def a @content=... end def b @content=.. end protected def send send_data(@content,...) end end However, when calling the action a or b, the @content doesn''t get sent, but instead

Hi all, I''m trying to output some info to see what''s happening in a controller during functional tests. Problem: ''print'' only works in the test code, but not in the production code that''s being called by the tests. Example: In FooControllerTest: def test_list print "1: starting" <<----- WORKS FINE get

Out of curiosity, I''ve seen the following fail: module Admin describe MyController ... end end But this works fine: describe Admin::MyController .. end Why? Scott

I am trying to create a plugin that adds a new IMAP capability. So far I have this: const char *foo_plugin_version = DOVECOT_ABI_VERSION; static struct module *foo_module; static imap_client_created_func_t *next_hook_client_created; static void foo_client_created(struct client **client) { str_append((*client)->capability_string, " XFOO"); if (next_hook_client_created !=

I''d like to split up my directly dispatched controller into a layered dispatch setup with one controller and two services derived from ActionWebService::Base. However, in doing this I found that logger is not a class_variable of AWS::Base. This kind of scares me away from using the layered dispatch mode, as I''d like to have logging in the method implementations. Is there a clean

Hello everyone: Right now I am writing spec on modules, which are provided by my colleagues. Some of the modules actually contain action methods. I tried very hard to spec those action methods in modules. But it seems that the rspec does not allow module spec to ''get'' action like controller does. After I saw the documentation, I then used :behaviour_type=>:controller.

INVITATION BETA EMAIL I have in the email that the app send to friend''s email address ------------------------ You are invited to ExampleApp.com click below to signup http://localhost:3000/signup.efweiuvwnjernfwkefwebhsohj ------------------------ But I have a dot in the url beteween http://localhost:3000 and the token I wish the following url

I am having a weird error that I have not had before... I''m bouncing it off the list to see if anyone else has had it, or to give me some pointers about how to find it. Basically, AUTOTEST will run (RSpec mode), fine, then suddenly, will complain that RAILS_ROOT is undefined. Then I stop and restart it, with no code change... no problem. It happens on different specs where I use

hi everyone in my dev machine, everything works flawlessly now when i uploaded my website on the server, it cannot acces User model anymore. all other pages work by the way. when i try to access User on console or by web, it shows: NameError in UsersController#signup uninitialized constant User /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:100:in

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

Hi, A question (& possible suggestion) about function calls. Is there an R idiom to eliminate the redundancy in the following common situation? foo <- function(x, control=ComplicatedDefault) { etc. } plotfoo <- function(x, foocontrol=ComplicatedDefault, ...) { y <- foo(x, control=foocontrol) lines(x,y,...) } The idea is that there are MANY