-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
has_and_belongs_to_many associations being restricted #55
Comments
In my example,
The code that produces the error is (
Request params are:
|
The fix for #31 appears to be the cause of this. The problem with this approach is that it's restricting calls on HABTM associations where there is no explicitly defined model/protect block. Is that intentional? This makes sense for has_many :through associations, but perhaps not for HABTM. Let me know your thoughts. I'd be happy to take a stab at a fix for this if you could provide some direction. Perhaps simply checking the reflection for HABTM and not restricting in that case will work? E.g. inside
(Perhaps there is a better way to check for habtm, but there have been some changes in the reflections behaviour in AR per rails/rails#14682) |
Any thoughts on this? |
You must be busy :) |
I'm upgrading to rails 4.1.5 and seem to keep running into protector-related issues. Have you had a chance to test things out in > 4.1?
The issue I'm running into now is the following error message on save:
This is despite having the strong_parameters config setting disabled. Any ideas?
The text was updated successfully, but these errors were encountered: