locking non-existent factoids should create empty ones
Bug #409108 reported by
Space Hobo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Yardbird |
Fix Released
|
Wishlist
|
Zen | ||
Bug Description
Currently the "lock" action will throw a 404 if the factoid specified does not exist. It can be handy to prevent people from creating noisy factoids right off the bat by locking them pre-emptively. The lock() view should use get_or_create instead of the get-or-404 function.
Related branches
lp:~shaboom/yardbird/shakalaka
- Space Hobo: Approve
- Diff: None lines
| Changed in yardbird: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Zen (shaboom) |
| milestone: | none → another-hairdo |
| Changed in yardbird: | |
| status: | Triaged → Fix Committed |
| Changed in yardbird: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
