support accepts_nested_attributes_for multi-destroy.
Fixed issue with update_positions that wasn't taking the 'scope_condition' into account
Merge pull request #47 from bastien/master

Fixed issue with update_positions that wasn't taking 'scope_condition' into account
version bump
Version incremented to 0.1.8 - no more warning on rails 3.2.7+
Merge pull request #46 from saberma/master

support accepts_nested_attributes_for multi-destroy
Introduce attr_accessible with :acts_as_list role
Fixed tests
Instructions for using an array with scope
Merge pull request #58 from AktionLab/scope_array_doc

Instructions for using an array with scope
Merge pull request #51 from fabn/attr-accessible-patch

Attr accessible patch, should solve #50
More reliable lower/higher item detection
Add missing order params
Problem:
changes in the attr accessable patch from fabn/attr-accessible-patch
cause a problem on any model which does not already have attr_accessible set
and as a result triggers the "Can't mass-assign protected attributes"

commit where problem was introduced:
md5: d8c24c026901071b22cac2201a80dd5608d268b0

test for problem:
The example included here in a test shows that adding attr_accessible to a model that
does not currently have mass assignment protection enabled, triggers mass_assignment
protection.

Solution:
I understand that this patch was inteded as a workaround, so as to add 'position'
to the list of available mass assignable attributes of the model,

The problem that required the offending patch is addressable in another manner:
it is not necessary to use 'update_attributes!' to set one known attribute.
instead, i have altered this to use update_attribute, as it doesn't trigger mass_assignment protection.
update_attribute only updates one attribute at a time, therefore avoiding 'mass' assignment.

-
that being said, it may still be desirable to add 'position' (or it's configured alternate)
to the list of mass_assignable attributes, but only if there is already such a list,

this patch performs a check to see if here is already a whitelist, and if so, adds itself to it.
Incorporates changes made by vesan

Vesan's idea of consolodating position changes into one method was a good one.
https://github.com/vesan/acts_as_list/tree/mass-assignment-protection-fix
And it successfully avoids mass assignment problems.

I have incorporated his work into my solution to a similar problem.
My fork has the additional advantage of:
- adding 'position_column' to the list of assignable attributes if there is such a list.
- having a regression test against accidentally triggering the same error again.
Merge pull request #60 from graemeworthy/master

attr-accessible can be damaging, is not always necessary.
Merge pull request #59 from miks/master

More reliable lower/higher item detection
Version bump for 0.1.9 release
add GitHub Flavored Markdown to README

* This makes the example code easier to read,
  especially when perusing the docs on github
Merge pull request #63 from phlipper/patch-1

add GitHub Flavored Markdown to README