Re: Allow slug to be prepopulated on edit

2010-10-25 Thread Hanne Moa
On 25 October 2010 15:19, rebus_ wrote: > IMHO, proper implementation in cases where slug is used in URI should at > least: > >  * remember the old slug for the object >  * return HTTP 301 [1] when the URI with the old slug is requested and >   have Location field set to a URI with a new slug So

Re: Allow slug to be prepopulated on edit

2010-10-25 Thread rebus_
On 25 October 2010 14:04, Justin Lilly wrote: > I don't believe there is. > > Historically, this is there because slug fields usually make their way > to be used > for URLs. As such, changing the title of an object shouldn't adjust its URL as > that can be bad for SEO and folks who might have book

Re: Allow slug to be prepopulated on edit

2010-10-25 Thread Justin Lilly
I don't believe there is. Historically, this is there because slug fields usually make their way to be used for URLs. As such, changing the title of an object shouldn't adjust its URL as that can be bad for SEO and folks who might have bookmarked it. You can, however, add your own javascript via

Allow slug to be prepopulated on edit

2010-10-25 Thread Alex
File "admin_modify.py" method "def prepopulated_fields_js(context)" Line 11: if context['add'] and 'adminform' in context: should be changed to if 'adminform' in context: to allow slug be auto updated every time and not only on the entity creation in admin. Is there any setting to do it without cha