Thanks you James,
To make it more clear. Let's say I have companies(entities) and
products(sub-entities) to be more clear. Regarding the urls I use the main
urls.py to include the urls.py from each app.
urlpatterns = [
url(r'^admin/', admin.site.urls),
url(r'^companies/', include('company.urls', namespace='company'))
In the entity app the urls.py :
urlpatterns = [
url(r'^$', CompanyListView.as_view(), name='list'),
url(r'^add/$', EntityCreateView.as_view(), name='create'),
*Normal View*
/companies/ - listing all
/companies/company-name/ - details about a company
/companies/products/ - listing all products of a company
/products/ - listing all products
/products/product/ - details about a product
*Editor*
/account/ - dashboard)
/account/add - adding a company, the company is actually the account, no
other info for account, and is onetoone relationship with user
/account/edit -update company data
/account/company-name/products/add - add a product to company
/account/company-name/product-name/edit - update product info
The account app I try to use is to control the account, even if doesn't
exist a model. I understand that I can use multiple urls patterns in
urls.py for an app in general, *but can you gave me an example for the case
above ? *(having just two apps companies and products)
-------- At the view level ----------------------------
In the Dashboard(account) first I verify if the company exist and
activated(approved by admin(boolean field).
If the company doesn't exist(first time) show the CreateView(CBV) form, if
exists and activated show the company info and others and if it is not
activated show a Pending message.
Based on the solutions you presented, I think is having a generic view
(empty with only logic or with one of the cases(pending,exist and active))
and to redirect to different urls and corresponding views.
Or you think there is a better approach ?
--
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 [email protected].
To post to this group, send email to [email protected].
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/7cbff87a-4823-47ae-b06e-c061234d67e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.