On 20/02/2017 4:00 PM, carlos wrote:
Hi, any idea how to construct my get_absolute_url (127.0.0.1:8000/category-slug/id-slug-post <http://127.0.0.1:8000/category-slug/id-slug-post>)
for example i have my models like this
class Category(...):
    name = CharField(....)
    slug = SlugField(.....)

class MyModel(modesl.Model):
    post = models.CharField(....)
    slug = models.SlugField(.....)
    categories = models.ManyToMany(Category)

   def get_absolute_url(self):
return "/%s/%s-%s/" % (self.categories.slug, self.id <http://self.id>, self.slug)

  #error 'ManyRelatedManager' object has no attribute 'slug'
  in self.categories.slug

https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.ManyToManyField

https://docs.djangoproject.com/en/1.8/ref/models/fields/#django.db.models.ManyToManyField.through

The "through" table doesn't need a coded Django model if it is only used to relate the two different tables in the m2m relationship. However, if you want to include other data - such as a slug - then you need to code it explicitly.

The "through" table will already exist in your database so choose the same name for the model as you see there. It will only have two foreign key fields, one to each of the related tables after which it is named.

Once you have a model with the two FKs and your slug, makemigrations/migrate will adjust it to include the slug.




i would like this url in my page
127.0.0.1:8000/category-slug/id-slug-post <http://127.0.0.1:8000/category-slug/id-slug-post>

example
http://mydomain.com/food-green/120-one-hundry-food-green
domain.com <http://domain.com> / category slug   / pk - (dash) post slug

the problems is for my get_absolute_url see, one post have multiple category
the error is:
'ManyRelatedManager' object has no attribute 'slug'

what is the best way to do this?

any idea?

Cheers

--
att.
Carlos Rocha
--
You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com <mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com <mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAM-7rO0wbik3zq5Tj_Fc9dhQNASnLd%2Bx5mA4Xp%3DAzkKyPS%2BQtg%40mail.gmail.com <https://groups.google.com/d/msgid/django-users/CAM-7rO0wbik3zq5Tj_Fc9dhQNASnLd%2Bx5mA4Xp%3DAzkKyPS%2BQtg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3583eb1a-6b7c-29bc-d670-5245d7813cac%40dewhirst.com.au.
For more options, visit https://groups.google.com/d/optout.

Reply via email to