Can't add new people to articles about source HOT 7 CLOSED

This is definitely a caching issue. I can reproduce locally now with caching on, and then the problem goes away with caching off. Will keep poking at it.

from source.

Which cache setting did you change? The middleware one? The memcache one? Something else?

from source.

As far as I know, no cache settings have changed in a while. It's possible that this is a bug that's only now coming to light because we haven't needed to edit these m2m lists in the admin.

I'm testing different combinations of cache settings locally to see what needs to happen, but it feels like the problem is related to django-cache-machine's queryset caching.

from source.

This is a little worse than I realized. Turns out if I make a new person, I can't add him or her to anything.

For example, we can't publish a new article by Dan Schultz, because he didn't already have a profile, and now that he does, I can't attach him to a code entry or to the article he wrote for us.

from source.

Oy.

On Tue, Oct 16, 2012 at 2:27 PM, kissane [email protected] wrote:

This is a little worse than I realized. Turns out if I make a new person,
I can't add him or her to anything.

For example, we can't publish a new article by Dan Schultz, because he
didn't already have a profile, and now that he does, I can't attach him to
a code entry or to the article he wrote for us.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/87#issuecomment-9503246.

from source.

Workaround from Ryan:

Add new people before doing anything else, then make new articles/entries that include them. (Don't open the "add an article" page and enter a new person into the system halfway through. Even if you save the person before saving the new article for the first time, it won't work.)

That should do the trick for new posts. Later, we'll get to existing posts.

from source.

So the problem is with using django-cache-machine's CachingManager as a standard way to handle a model's objects. I have a fix for this, with an open pull request against the dev site. Would be smart to try this there first.

#95

I can automatically merge this pull request, but I would love it if someone can look this over first. It's very straightforward, but extra eyes and all that.

from source.