Email-in blog entries get screwed up __name__

Bug #341149 reported by Paul Everitt
2
Affects Status Importance Assigned to Milestone
KARL3
Fix Released
High
Chris Rossi

Bug Description

Emailing in a blog entry gets a screwed up __name__ and isn't seated properly, meaning it doesn't actually show up in the blog listing. It's there, you just have to use the livesearch to find it. Doesn't show up in recent items on the community overview either.

Changed in karl3:
assignee: nobody → chris-archimedeanco
importance: Undecided → High
milestone: none → m5
Changed in karl3:
status: New → In Progress
Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Odd, I have confirmed non-working behavior on Carlos, but when I set up a local test in order to debug I don't see the problem.

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Ok, here's what I've learned:

Restarting karl causes blog entries to show up. So the issue is caching and stale data somehow, not the __name__.

The __name__ is generated using a different algorithm than for blog entries created via web ui. This should be fixed but is not the source of this problem.

My suspicion is that debugging this will also force me to figure out why Paul was seeing stale data with >1 mod_wsgi process.

In short, this is a stale data and caching problem.

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

Turns out this is due to caching of catalog queries, which has been disabled for now until multiprocess behavior can be figured out. This should also fix Paul's stale data problem when running multiple processes with mod_wsgi.

Changed in karl3:
status: In Progress → Fix Committed
Changed in karl3:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.