Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Ok, I have found the problem. </p> <p>First of all, I assume you are using Rails 4. The reason you are getting this error is that <code>attr_protected</code> and <code>attr_accessible</code> have been removed from Rails 4 and placed in their own gem. Rails is now encouraging a new protection model. You can read about this in the <a href="https://github.com/rails/strong_parameters" rel="noreferrer">README</a>. If you would like to continue using the old behavior, you must include the <a href="https://github.com/rails/protected_attributes" rel="noreferrer">protected_attributes gem</a>. Hope that helps.</p> <p>EDIT: I've added clarification below since this is likely to be a common problem with users to upgrading to rails 4.</p> <p>If you would like to continue using <code>attr_accessible</code>, i.e. the Rails 3 way, simply add <code>gem protected_attributes</code> to your Gemfile. </p> <p>If you would like to start doing things the Rails 4 way, you must no longer use <code>attr_accessible</code>. Instead, you must move the attribute permission logic into the controller. Here is an example:</p> <pre><code>class UsersController &lt; ApplicationController def create # Using params[:user] without calling user_params will throw an error because # the parameters were not filtered. This is just some Rails magic. @user = User.new user_params if @user.save # Do whatever else render action: :new end end private def user_params # params.require(:user) throws an error if params[:user] is nil if current_user.nil? # Guest # Remove all keys from params[:user] except :name, :email, :password, and :password_confirmation params.require(:user).permit :name, :email, :password, :password_confirmation elsif current_user.has_role :admin params.require(:user).permit! # Allow all user parameters elsif current_user.has_role :user params.require(:user).permit :name, :email, :password, :password_confirmation end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMongoid w/ Rails, attr_accessible --> "No method found"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMax
    1. USMax
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COyour assumption is correct - i am using rails 4. I'll check into this when i get on my development machine
      singulars
      1. PO
      1. USsircapsalot
    2. COHey, so according to the readme you linked, it appears that the protection model is inside of rails. https://github.com/rails/strong_parameters#compatibility It says that it is bundled in with rails now, so i shouldn't have to use any gem to make this work.
      singulars
      1. PO
      1. USsircapsalot
    3. COThe README file was for the `strong_parameters` gem, which is the current Rails 4 standard. The second link is to the `protected_attributes` gem. The `protected_attributes`gem contains the `attr_accessible` method, but `protected_attributes` was removed from Rails 4. If you would like to continue using the `attr_accessible` method in rails 4, you must add the following to your Gemfile: `gem 'protected_attributes'`
      singulars
      1. PO
      1. USMax
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload