search for: signed_up

...case that requires a written notification to either a person or another system. The framework works by setting up all the email details, except the body, in methods on the service layer. Subject, recipients, sender, and timestamp are all set up this way. An example of such a method: def signed_up(recipient) @recipients = recipient @subject = "[Signed up] Welcome #{recipient}" @from = "system-OiTZALl8rpK0mm7Ywyx6yg@public.gmane.org" @sent_on = Time.local(2004, 12, 12) @body["recipient"] = recipient end The body o...

...nix style for running commands cd #{pkg} && rm -rf pkg && PKG_BUILD=#{build_number} rake pgem && cd .. and it is does not work under Windoze so I have to cd in each folder and run rake pgem manually. And there I have problems with tar ==LOG=== ln test/fixtures/test_mailer/signed_up.rhtml pkg/actionmailer-1.0.1/test/fixtures/test_mailer/signed_up.rhtml cd pkg tar zcvf actionmailer-1.0.1.tgz actionmailer-1.0.1 tar: Cannot use compressed or remote archives tar: Error is not recoverable: exiting now rake aborted! Command failed with status (2): [tar zcvf actionmailer-1.0.1.tgz a...

The build has been fixed. CHANGES ------- Revision 8820 committed by bitsweat on 2008-02-07 23:10:01 Remove empty .rhtml templates D /trunk/actionmailer/test/fixtures/templates/signed_up.rhtml D /trunk/actionmailer/test/fixtures/helper_mailer/use_example_helper.rhtml D /trunk/actionmailer/test/fixtures/first_mailer/share.rhtml D /trunk/actionmailer/test/fixtures/path.with.dots/multipart_with_template_path_with_dots.rhtml D /trunk/actionmailer/test/fixtures/test_mailer/signe...

...find any answer, so iy may not be related to Devise , so I debugged it .. . class Users::RegistrationsController < Devise::RegistrationsController .. # POST /resource/sign_up def create build_resource if resource.save if resource.active? set_flash_message :notice, :signed_up sign_in_and_redirect(resource_name, resource) else set_flash_message :notice, :inactive_signed_up, :reason => resource.inactive_message.to_s debugger expire_session_data_after_sign_in! redirect_to after_inactive_sign_up_path_for(resource) end...

I know in the model we can add validations. But how about if I need different validations depending on the controller. For example... 1) if the User is being created from the accounts controller, I want to REQUIRE the username be entered. 2) if the User is being created from the users controller, I want to NOT REQUIRE the username. validates_presence_of :username, :on => :create requires the