Hi, > Some of our more common models are shared throughout our app ecosystem > and we frequently run into a problem with get_absolute_url/permalink/ > etc of generating required URLs, in particular looking at user A's > interaction with a model vs user B's that may occur in a completely > separate part of the app. > > Example: > > We track a list of Office objects. Several users interact with these > office objects via /a/offices/id/ URLs. > > The public interacts with Office objects at /b/washington/ (the slug > of the office). > > While not ideal in the sense that 1 "object" == 1 URL, surely I'm not > the only one with this issue -- I want to use the URL tools in Django > -- but from what I've read/seen/tested/used, this is outside of the > machinery Django provides.
Why not simply define another function like get_absolute_url_for_user_B which would reverse your url for user B ? If you're having different urls for the object, you'll have somewhere that tells which one to use anyway. Regards, Xavier. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
