replacing attr_protected and attr_accessible with strong_params
first take on strong_parameters - two functional tests failing

I think those tests fail because of strong_parameters have different responses
in case of errors
update tests and fix me::passwords controller
loosen requirements for new page screen

can't have page params already.
remove old unit test for attr_protected

we use strong parameters now
fix page creation with strong_parameters

we need to check for the page_type in the Pages::CreateController before
trying to build a page.

Also we were not using strong params in the CreateAssetPageController.
remove unused actions with outdated code from gallery

We're now using the assets controller for all of the uploading etc.

This removes some old code that did quite a few nice things like extract zip files. However multi file drag&drop makes that less necessary anyway.

Leaving a note in case someone wants to bring back the old things
use strong params in page extensions
test Me::PasswordsController
attempt to fix ranked vote page test

Somehow the second drag&drop does not work.
fix task state assignment
use strong params for rate_many_page
cleanup task model internals a bit
Merge pull request #62 from azul/security/strong_params

Security/strong params