Opened 13 years ago

Last modified 12 years ago

#216 closed defect

What happens when you set a slug to an existing objectid? Anything bad? — at Version 4

Reported by: Christopher Allan Webber Owned by:
Priority: major Milestone: 0.3.3
Component: programming Keywords: bitesized review
Cc: sebastian@… Parent Tickets:

Description (last modified by Christopher Allan Webber) 

Probably not, though that seems a bit nasty / tricky!

We might want to prevent someone from doing that though it probably
isn't a big deal.

Change History (4)

comment:1 by Will Kahn-Greene, 13 years ago

The original url for this bug was ​http://bugs.foocorp.net/issues/514 .

comment:2 by Jakob Kramer, 13 years ago

Yes, something bad. If you set the slug of Media #2 to '1', you can't edit or delete Media #1 anymore. Maybe the uploader of Media #1 can even delete Media #2 like that…

Last edited 13 years ago by Jakob Kramer (previous) (diff)

comment:3 by Jakob Kramer, 13 years ago

Priority: trivial → major

comment:4 by Christopher Allan Webber, 13 years ago

Description: modified (diff)

I have been thinking the "optionally look up by slug OR id" is a mistake. We should just require slugs (even if the same as the id, who cares) and look up via that only. Does that seem like a reasonable solution?

Note: See TracTickets for help on using tickets.