Multi-level association 3-deep works in the console, but fails every test and in production about counter_culture HOT 3 CLOSED

That's it? You have no other response to any of the other questions I asked? No interest whatsoever in what's going on here? This is a slightly-more-complicated- than-standard Rails relationship that your code does seem to handle outside of a website running, but then fails to work in an actual production environment, so clearly there's a major issue happening but yeah, who cares?

I'm so glad I spent all this time writing up a detailed report of the behavior to have it ignored and marked "completed" with a half-assed response that poorly echoes exactly what I already asked but written as a statement as if you discovered something I missed, complete with spelling errors in it.

Next time I encounter an issue using your software, I'll guess I'll just skip the "reporting it" part of the process entirely and go straight to just fucking myself. It's my fault for using your software and thus clearly my fault for encountering the issue. Thanks, once again, for absolutely nothing. So deeply sorry to have wasted your time.

from counter_culture.

This should work for more than two levels, there's even a spec that tests three levels. Looking at yoru code, my hunch is that the issue is you're trying to go through a has_many association when updating the counter cache. You're going recording -> performance -> played_songs—and I think maybe that doesn't work? In the test I linked above it goes just through belongs_to associations.

from counter_culture.

You need a check on your attitude. I provide this gem free of charge, it's open source. I work on it in my free time. I don't owe you anything since you pay me nothing.

from counter_culture.