do i need a custom admin app or should i just use django admin?

[Arya]

i'm planning to build a full ecommerce business to business website. there are several user types.

premium users need to create products and edit them. they need to  communicate to each other. see statistics and access some premium content.

do you suggest to user the default django admin? or i'm better off creating a custom admin app ?

[Andréas Kühne]

I would advise you to not use django admin. Django admin is fine in development and for quickly doing crud. However if you need to change something in the workflow in admin, it is doable but rather hard. Creating the views using Class based views is rather simple if you use generic views - so that's what I would do.

Regards,

Andréas

--
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...@googlegroups.com.
To post to this group, send email to django...@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/5215792d-621b-4f61-86de-8ac94b18022f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Farris]

Think of the Django Admin as a tool for developers or Database Admins.  IMO, it should never be used by an end user.  Create views as Andreas mentioned and give those views permissions.

[Rajat Chopra]

What are the reasons not to use Django Admin? 

Also with regards to creating views and giving those views permissions - are there any examples someone can point to help illustrate?

[James Farris]

Read the docs regarding this.

https://docs.djangoproject.com/en/2.2/topics/auth/default/#permissions-and-authorization

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/1LpORyVyQls/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users...@googlegroups.com.

To post to this group, send email to django...@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/2b4f9ad1-2c29-42ca-b585-3b96e0a07118%40googlegroups.com.

[Andréas Kühne]

I have built a system using django admin for the main interface. It's doable - however - I wouldn't do it again. The main reason is that getting things working quickly is easy. You get a simple interface that can do CRUD. You then add grappelli (or some other system) to get a nicer interface. And then you start nesting things.

Now your problems start. The admin interface gives you a lot of functionality out of the box, BUT the problem is that you need to follow the exact guidelines for this to work. You start working with formsets and specialcases and it takes a long time to write the code. So the initial fast setup makes it hard do develop features in the long run. 

At least that's my experience.

Regards,

Andréas

--

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...@googlegroups.com.

[Andréas Kühne]

Regarding views and permissions, this is build into class based views. Look here: 

https://docs.djangoproject.com/en/2.2/topics/auth/default/#limiting-access-to-logged-in-users-that-pass-a-test

Regards,

Andréas

Den mån 17 juni 2019 kl 20:31 skrev Rajat Chopra <cho...@gmail.com>:

--

[Andréas Kühne]

Sorry - wrong link - look here:

https://docs.djangoproject.com/en/2.2/topics/auth/default/#the-permissionrequiredmixin-mixin

Regards,

Andréas