unconfirmed_email is required for reconfirmable. For some reason this was enabled by default in config/intializers/devise.rb:

    config.reconfirmable = true

All you have to do is set this to false.

You miss unconfirmed_email column in db. 


add `t.reconfirmable` in migrations and run `rake db:migrate`


or if you&#39;re using devise &gt;= 2.0 


    t.string   :unconfirmed_email

I am working through [part4 of Symfony2][1], and while updating the controller and helper class code i got the following error message

    Undefined method &#39;getLatestBlogs&#39;. The method name must start with either
    findBy or findOneBy!

before i had put some code in controller that i shifted to my helper class as taught by tutorial, which result in the above error message.

    
    &lt;?php
    // src/Blogger/BlogBundle/Repository/BlogRepository.php
    namespace Blogger\BlogBundle\Repository;
    use Doctrine\ORM\EntityRepository;

    /**
     * BlogRepository
     * This class was generated by the Doctrine ORM. Add your own custom
     * repository methods below.
    */
    class BlogRepository extends EntityRepository
    {
     public function getLatestBlogs($limit = null)
     {
        $qb = $this-&gt;createQueryBuilder(&#39;b&#39;)
                   -&gt;select(&#39;b&#39;)
                   -&gt;addOrderBy(&#39;b.created&#39;, &#39;DESC&#39;);

        if (false === is_null($limit))
            $qb-&gt;setMaxResults($limit);

        return $qb-&gt;getQuery()
                  -&gt;getResult();
      } 
    }

And here is my controller file index Action Code:-

    // src/Blogger/BlogBundle/Controller/PageController.php
    class PageController extends Controller
    {
      public function indexAction()
      {
        $em = $this-&gt;getDoctrine()
                   -&gt;getEntityManager();

        $blogs = $em-&gt;getRepository(&#39;BloggerBlogBundle:Blog&#39;)
                    -&gt;getLatestBlogs();

        return $this-&gt;render(&#39;BloggerBlogBundle:Page:index.html.twig&#39;, array(
            &#39;blogs&#39; =&gt; $blogs
        ));
        }

        // ..
    }

I am attaching few lines from  /Entity/Blog.php file. please see if they are correct as per your answer.

    &lt;?php
    // src/Blogger/BlogBundle/Entity/Blog.php

    namespace Blogger\BlogBundle\Entity;
    use Doctrine\ORM\Mapping as ORM;

    /**
     * @ORM\Entity(repositoryClass=&quot;Blogger\BlogBundle\Repository\BlogRepository&quot;)
     * @ORM\Table(name=&quot;blog&quot;)
     * @ORM\HasLifecycleCallbacks()
     * @ORM\Entity
     */

    class Blog
     {
      /**
       * @ORM\Id
       * @ORM\Column(type=&quot;integer&quot;)
       * @ORM\GeneratedValue(strategy=&quot;AUTO&quot;)
       * @ORM\HasLifecycleCallbacks()
      */
      protected $id;
      --
      --
     }
Where Am I doing wrong ?



  [1]: http://tutorial.symblog.co.uk/docs/extending-the-model-blog-comments.html#Doctrine%202%20Repositories

The method name must start with either findBy or findOneBy. Undefined method Symfony?

This will redirect a request with a _temporary_ 302 HTTP status code:

    HttpServletResponse response;
    response.sendRedirect(&quot;http://somewhere&quot;);

But is it possible to redirect it with a _permanent_ 301 HTTP status code?

HttpServletResponse sendRedirect permanent

I just installed Devise in my app, configured the views and everything. However, when I click the sign up button I get this error:

    NameError in Devise::RegistrationsController#create
    undefined local variable or method `unconfirmed_email&#39; for #&lt;User:0x00000103721b28&gt;

Why is this? Also, I&#39;m using tlsmail to send emails out through my gmail business account. This might be a problem as well.

Undefined local variable or method `unconfirmed_email&#39; when registering users?

I just installed Devise in my app, configured the views and everything. However, when I click the sign up button I get this error:
<pre><code class="hljs language-sql">NameError in Devise::RegistrationsController#create
undefined local variable or method `unconfirmed_email' for #&#x3C;User:0x00000103721b28>
</code></pre>
Why is this? Also, I'm using tlsmail to send emails out through my gmail business account. This might be a problem as well.

In the logs I&#39;m seeing a `ROLLBACK`, but no exception is logged. Is there a way to find out what caused the ROLLBACK?

Here&#39;s the excerpt of the log:

      Phone Load (0.4ms)  SELECT &quot;phones&quot;.* FROM &quot;phones&quot; WHERE &quot;phones&quot;.&quot;id&quot; = $1 LIMIT 1  [[&quot;id&quot;, 980190963]]
       (0.2ms)  BEGIN
      User Load (0.4ms)  SELECT &quot;users&quot;.* FROM &quot;users&quot; WHERE &quot;users&quot;.&quot;phone_id&quot; = 980190963 LIMIT 1
       (0.2ms)  ROLLBACK
      Phone Load (0.4ms)  SELECT &quot;phones&quot;.* FROM &quot;phones&quot; WHERE &quot;phones&quot;.&quot;id&quot; = $1 LIMIT 1  [[&quot;id&quot;, 980190963]]
      User Load (0.4ms)  SELECT &quot;users&quot;.* FROM &quot;users&quot; WHERE &quot;users&quot;.&quot;phone_id&quot; = 980190963 LIMIT 1



how to find the cause of ActiveRecord ROLLBACK

So far I&#39;ve got:

 - :notice
 - :alert
 - :error

but is there definitive list, that can be used in place, such as in `redirect_to path, :error =&gt; &quot;Oh no!&quot;`?

What flash message types are available in Rails?

I have an old 2.1.1 Ruby on Rails application, with the system upgraded to use Ruby 1.8.7. It originally used 1.8.5 or so.

I want to upgrade it to Ruby 1.9.x for performance reasons, and possibly to a newer Ruby on Rails as well.

I cannot find any easy chart of compatibility between different Ruby versions and Ruby on Rails versions.

Will 2.1.1 work with Ruby 1.9.x? If not, how far do I need to upgrade it first, and what kind of issues am I likely to encounter? My application does complicated things to database layer, but the rest is fairly straightforward.

Which Ruby on Rails is compatible with which Ruby version?

I am using simple_form gem, I have a countries collection, it work fine when I select the country, and updated record will have the country id stored, but, when I try to edit the record, the chosen country is not selected by default at edit form.

Here is the code at edit form:

    = f.input :country_id, :collection =&gt; all_countries
    
Shouldn&#39;t simple_form view the selected country from the db ?

rails, simple_form, how to set selected index of a collection when page loaded?

I&#39;m using Rails 3.2 and have a migration that contains the code:

    add_column :users, :gift_aid, :integer, :default =&gt; 2
    # reset columns
    User.reset_column_information

    ... code here to load legacy data from sqlite3 database ...
    
    # now create a user with the loaded column data
    user = User.create( ...other cols..., 
                        :gift_aid =&gt; migrated_gift_aid_column_data,
                        ...other cols... )

and I get `unknown attribute: gift_aid` when running the migration. `User.column_names` shows the same list before and after the call to `reset_column_information`. 

Oddly when I manually drop the column in mysql and re-run the migration it works as expected. Starting from the first migration again with an empty database and it doesn&#39;t work so it&#39;s something to do with running all the migrations rather than the single one.

I have a couple of previous migrations on User model, both include `reset_column_information` and both work fine. 

I&#39;m really scratching my head on this one - anyone got any ideas


Model.reset_column_information does not reload columns in rails migration

So in Rails 3.2, ActiveSupport::Memoizable has been deprecated.

The message reads:

    DEPRECATION WARNING: ActiveSupport::Memoizable is deprecated and
    will be removed in future releases,simply use Ruby memoization
    pattern instead.

It refers to &quot;Ruby memoization pattern&quot; (singular) as if there&#39;s one pattern we should all know and refer to...

I presume they mean something like:

    def my_method
      @my_method ||= # ... go get the value
    end

or 
    
    def my_method
      return @my_method if defined?(@my_method)

      @my_method = # ... go get the value
    end

Is there something else I&#39;ve missed?

Which Ruby memoize pattern does ActiveSupport::Memoizable refer to?

I&#39;ve noticed that on rubygems.org a lot of the gems suggest you specify them by major version rather than exact version. For example...

[The haml-rails gem][1]...

    gem &quot;haml-rails&quot;, &quot;~&gt; 0.3.4&quot;  # &quot;$ bundle install&quot; will acquire the 
                                  # latest version before 1.0.

However, based on the [Bundler docs][2] it sounded to me like it would be better to nail down the exact version like this...

    gem &quot;haml-rails&quot;, &quot;0.3.4&quot;

So there&#39;s your haml-rails gem and all its dependencies won&#39;t drift forward. If you check out the project on a different machine a few weeks later and run `$ bundle install` you&#39;ll have precisely the same versions of everything you specified.

I&#39;ve seen point releases break stuff, and I thought part of the whole idea of Bundler was to &quot;`Bundle.lock`&quot; all your gem versions.

But on rubygems.org they use &quot;~&gt;&quot; a lot so maybe I&#39;m missing something?

Any clarification would be very helpful to me in understanding Bundler and gem management.


  [1]: http://rubygems.org/gems/haml-rails
  [2]: https://bundler.io/guides/using_bundler_in_applications.html#adding-gems

Should I specify exact versions in my Gemfile?

I am using Factory Girl to create two instances in my model/unit test for a Group. I am testing the model to check that a call to .current returns only the &#39;current&#39; groups according to the  expiry attribute as per below...

      describe &quot;.current&quot; do
        let!(:current_group) { FactoryGirl.create(:group, :expiry =&gt; Time.now + 1.week) }
        let!(:expired_group) { FactoryGirl.create(:group, :expiry =&gt; Time.now - 3.days) }

        specify { Group.current.should == [current_group] }
      end

My problem is that I&#39;ve got validation in the model that checks a new group&#39;s expiry is after today&#39;s date. This raises the validation failure below.

      1) Group.current 
         Failure/Error: let!(:expired_group) { FactoryGirl.create(:group, :expiry =&gt; Time.now - 3.days) }
         ActiveRecord::RecordInvalid:
           Validation failed: Expiry is before todays date

Is there a way to forcefully create the Group or get around the validation when creating using Factory Girl?

Factory-girl create that bypasses my model validation

Could somebody explain to me what the command `rake assets:clean` really does? Unfortunately the Rails Guides dont mention it. There is also the command `rake assets:cleanup`. Whats the difference?

Furthermore could somebody tell me when do I have to run `rake assets:precompile` in production. Do I run it on the server console after I deployed all my application files to my production server? Or do I `precompile` on my local machine and then do a deploy of all files?

Thanks all

Confusion about rake assets:clean / cleanup on the asset pipeline in rails

Where is devise implementation of `authenticate_user!` method?

I have been looking for it and have not found it so far.



where is devise implementation of &quot;authenticate_user!&quot; method?

How can I retrieve the CSRF token to pass with a JSON request?

I know that for security reasons [Rails is checking the CSRF token](http://weblog.rubyonrails.org/2011/2/8/csrf-protection-bypass-in-ruby-on-rails) on all the request types (including JSON/XML).

I could put in my controller `skip_before_filter :verify_authenticity_token`, but I would lose the CRSF protection (not advisable :-) ).

This similar (still not accepted) [answer](https://stackoverflow.com/questions/9044141/rails-devise-creating-new-users-via-json-request) suggests to

&gt; Retrieve the token with `&lt;%= form_authenticity_token %&gt;`

The question is how? Do I need to do a first call to any of my pages to retrieve the token and then do my real authentication with Devise? Or it is an information one-off that I can get from my server and then use consistently (until I manually change it on the server itself)?

rails - &quot;WARNING: Can&#39;t verify CSRF token authenticity&quot; for json devise requests

I&#39;m using rails 3.2 and devise 2.0 and I&#39;m quite new to Rails.

# Requirements #

I&#39;d like to achieve the following:

 - have 2 or more &quot;user&quot; models, eg. Member, Customer, Admin
 - all models share some required fields (eg. email and password)
 - each model may have some unique fields (eg. company for Customer only)
 - some fields may be shared but not have the same validation (eg. name is required for Customer but optional for Member)
 - all fields must be filled during the registration process, so the forms are different
 - the login form should be unique

# Possible solutions #

I googled and searched StackOverflow for quite a long time, but nothing seems right to me (I&#39;m a Java guy, sorry :) and now I&#39;m quite confused. Two solutions came up:

## Single devise user ##

That&#39;s the most frequent answer. Just create the default devise User and create relations between Member--&gt;User and Customer--&gt;User.
My concern here is how can I achieve a customized registration process for each model? I tried different things but all ended as a mess!

## Multiple devise users ##

This solves the custom registration process, and seems right to me, but the unique login form is a blocker. I found an answer on SO (&lt;https://stackoverflow.com/questions/7254734/devise-login-from-two-model&gt;) which suggests to override Devise::Models::Authenticatable.find_for_authentication(conditions).
That seems complicated (?) and since I&#39;m new to rails, I&#39;d like to know if that could work?

Thanks for your advice!

devise and multiple &quot;user&quot; models

I have an app setup where each user belongs to a company, and that company has a subdomain (I am using basecamp style subdomains). The problem that I am facing is that rails is creating multiple cookies (one for lvh.me and another for subdomain.lvh.me) which is causing quite a few breaks in my application(such as flash messages being persistent though out all requests once signed in).

I have this in my /cofig/initilizers/session_store.rb file:

    AppName::Application.config.session_store :cookie_store, key: &#39;_application_devise_session&#39;, domain: :all

The domain: :all seems to be the standard answer I found on Google, but that doesn&#39;t seem to be working for me. Any help is appreciated! 

Share session (cookies) between subdomains in Rails?

I am using the rails 4.0 branch of devise along with ruby 2.0.0p0 and Rails 4.0.0.beta1.

This is the kind of question where I am checking if I&#39;m doing it the right way, or if there are other things I should be doing. I&#39;m sure a lot of people moving to Rails 4.0 are facing the same problems (after googling for similar things).

I have read the following links:

 - https://stackoverflow.com/questions/11904105/devise-and-strong-parameters
 - https://gist.github.com/kazpsp/3350730
 - https://github.com/plataformatec/devise/tree/rails4#strong-parameters

Now using devise I created a User model, I created the following controller using the above gists (and made sure to include it in my routes file). My extra parameters are first_name and last_name.

    class Users::RegistrationsController &lt; Devise::RegistrationsController
      def sign_up_params
        params.require(:user).permit(:first_name, :last_name, :email, :password, :password_confirmation)
      end
      def account_update_params
        params.require(:user).permit(:first_name, :last_name, :email, :password, :password_confirmation, :current_password)
      end
      private :sign_up_params
      private :account_update_params
    end

Is there anything else I should be doing? Is this the best way of doing things from now on (since dropping attr_accessor). My forms seem to be working fine (both the new and update). The gists said to use &quot;resource_params&quot; but that always gave the &quot;Unpermitted parameters&quot; error in my server log.

Content Type	Original Author	Original Content on Stackoverflow
Question	varatis	View Question on Stackoverflow
Solution 1 - Ruby on-Rails	varatis	View Answer on Stackoverflow
Solution 2 - Ruby on-Rails	Fivell	View Answer on Stackoverflow

Undefined local variable or method `unconfirmed_email' when registering users?

Ruby on-Rails Problem Overview

Ruby on-Rails Solutions

Solution 1 - Ruby on-Rails

Solution 2 - Ruby on-Rails

HttpServletResponse sendRedirect permanent

The method name must start with either findBy or findOneBy. Undefined method Symfony?

Attributions