Re: Unique app name error problem when building a Wagtail multisite solution

Hi Melvyn, thanks for your answer. Unfortunately switching the CMS isn't an option. And even if I skip the multisite requirements i could think of usecases where it might be a problem in just a django project as well, wanting to have a similar project structure, doesn't it? Am Donnerstag, 22.

Re: Unique app name error problem when building a Wagtail multisite solution

Hi, On Wednesday 21 December 2016 14:30:32 'Matthias Brück' via Django users wrote: > is this really just not possible? What I found is this: > > you can't have two apps with the same name, even if they have > different > > fully qualified module paths > > https://groups.google.com/forum/#!msg/

Re: Unique app name error problem when building a Wagtail multisite solution

is this really just not possible? What I found is this: you can't have two apps with the same name, even if they have different > fully qualified module paths https://groups.google.com/forum/#!msg/django-users/AMYLfQo6Ba4/Y-57B0i7qy4J How would you guys handle this? -- You received this mes

Unique app name error problem when building a Wagtail multisite solution

Hi all, I want to build a Wagtail multisite solution and I'm running into problems with unique application labels. I would like to have the following project structure: project | |--app1 ||--core ||--pages |... |--app2 ||--core ||--pages |... Even whe