Rails 4 - mailboxer attr_accessible

Question

I'm trying to get Mailboxer on Rails4 working, but didn't had any luck with this.

my conversations_controller.rb looks like this ->

class ConversationsController < ApplicationController
before_filter :authenticate_user!
helper_method :mailbox, :conversation

def create
    recipient_emails = conversation_params(:recipients).split(',')
    recipients = User.where(email: recipient_emails).all

    conversation = current_user.
        send_message(recipients, *conversation_params(:body, :subject)).conversation

    redirect_to conversation
end

def reply
    current_user.reply_to_conversation(conversation, *message_params(:body, :subject))
    redirect_to conversation
end

def trash
    conversation.move_to_trash(current_user)
    redirect_to :conversations
end

def untrash
    conversation.untrash(current_user)
    redirect_to :conversations
end

private

def mailbox
    @mailbox ||= current_user.mailbox
end

def conversation
    @conversation ||= mailbox.conversations.find(params[:id])
end

def conversation_params(*keys)
    fetch_params(:conversation, *keys)
end

def message_params(*keys)
    fetch_params(:message, *keys)
end

def fetch_params(key, *subkeys)
    params[key].instance_eval do
        case subkeys.size
            when 0 then self
            when 1 then self[subkeys.first]
            else subkeys.map{|k| self[k] }
        end
    end
end

end

and my application_controller.rb like this ->

class ApplicationController < ActionController::Base
before_filter :configure_permitted_parameters, if: :devise_controller?
# Prevent CSRF attacks by raising an exception.
# For APIs, you may want to use :null_session instead.
protect_from_forgery with: :exception



protected

def configure_permitted_parameters
    devise_parameter_sanitizer.for(:sign_up) do |u|
        u.permit(:name, :email, :password, :password_confirmation, :provide, :uid)
    end
    devise_parameter_sanitizer.for(:account_update) do |u|
        u.permit(:name, :email, :password, :current_password, :password_confirmation, :first_name, :last_name, :user_bio,
                         :country, :gender, :facebook_link, :twitter_link, :pinterest_link, :provider, :uid, :recipients, :body,
                         :subject, :conversations, :conversation, :message, :mailbox)
    end
end

def conversations_params
    params.require(:conversations).permit(:recipients, :body, :subject,
                                                                                :conversations, :conversation, :message)
end

end

On loading a Page i Get ->

`attr_accessible` is extracted out of Rails into a gem. Please use new recommended protection model for params(strong_parameters) or add `protected_attributes` to your Gemfile to use old one.

score 3 · Accepted Answer · answered Aug 13 '13 at 18:46

3

Based on https://github.com/ging/mailboxer/pull/159, you can either:

add protected_attributes to your gemfile
use the master branch of ging/mailboxer

answered Aug 13 '13 at 18:46

Jesse Wolgamott

40,197
4
83
109

Well there is only the Master branch, which i am using :( – Mini John Aug 13 '13 at 18:49
I'm decently sure you are using the last stable gem that was deployed. if you are using edge/master, it would be `gem 'mailboxer', github: 'ging/mailboxer'` – Jesse Wolgamott Aug 13 '13 at 20:44
I don't quite get this (sry im a little new). On Github there is only one Branch so whats the difference if i put in my gemfile gem 'mailboxer' or gem 'mailboxer', github: 'ging/mailboxer' ? Thank you – Mini John Aug 14 '13 at 13:32
`gem 'mailboxer'` will use the last stable deployed gem version, which does not include many changes in the master branch. If you specify `gem 'mailboxer', github: 'ging/mailboxer'`, you will get all latest changes (edge). – Jesse Wolgamott Aug 14 '13 at 14:29
It's the difference in running 1.0-stable and the bleeding edge. – Jesse Wolgamott Aug 14 '13 at 14:30

Rails 4 - mailboxer attr_accessible

1 Answers1