recipient: <%= user.email_address %>


but to no avail.  Seems like the mailer was loaded before the model so the user object was not yet available.  A solution that I came up with, though kind of hacky, was to tokenize the yml with placeholders that are dynamically replaced by the mailer at runtime.

My .yml file now looks like this:


email_notifications:
activate:
from: acct_activations@company.com
recipients: @USER_EMAIL@
bcc: devuser@company.com
subject: Activate your new account (@USER_COMPANY@)


and in my mailer I added a method to do the replacement:

def replace_yaml_tokens(yaml_doc, user)
yaml_obj = YAML::dump( yaml_doc )
yaml_obj.gsub!(/\@USER_EMAIL\@/, user.email_address)
yaml_obj.gsub!(/\@USER_COMPANY\@/, user.company)
YAML::load( yaml_obj )
end


finally it was a simple call after initializing the mailer to do the replacement.

mailer=replace_yaml_tokens(YAML::load( File.open( "#{RAILS_ROOT}/config/activation.yml" ) )['email_notifications']['activate'], user);


Like I said, maybe not the best solution, but one that worked for me!

Tweet This Post

Logon to
Oracle using sys as sysdba and execute the following:

ALTER SYSTEM SET PROCESSES=150 SCOPE=SPFILE;

After changing the PROCESSES parameter restart your Oracle service.  I recently encountered this on a rails project I’m currently working on with an Oracle XE installation running in a Windows XP VM.  It seems like the default process level was set to 40 so running the rake tests consistently, but sporadically produced these errors at random intervals.

Tweet This Post