And here's the change for anyone interested:
https://github.com/stephenmcd/mezzanine/pull/1636/files
That appears to be all 1.10 issues resolved! Assuming nothing else comes
up, I'll try and push a new release over the coming weeks when Django 1.10
is released.
On Mon, Jul 25, 2016 at 12:33 PM
On Mon, Jul 25, 2016 at 11:34 AM, Stephen McDonald
wrote:
> Alex and I have worked out most of the remaining issues:
> https://github.com/stephenmcd/mezzanine/pull/1635
>
> There's one major issue outstanding which is slightly laborious but should
> be relatively straightforward, noted in the Dja
Alex and I have worked out most of the remaining
issues: https://github.com/stephenmcd/mezzanine/pull/1635
There's one major issue outstanding which is slightly laborious but should
be relatively straightforward, noted in the Django 1.10 release notes
(https://docs.djangoproject.com/en/dev/rele
Hey there.
If you want to use the same codebase for multiple sites and domains,
option 3 is your best bet. You can even have different frontend themes
for each site, but all your installed apps will be the same. Each site
will have its own Admin as long as all your models inherit from
SiteRel
Hello
I created a VirtualEnv1, inside that mezzanine project Mezz1 for a domain
Site1.com.
I now want to make more websites for Site2.com.
How do I decide among the three choices:
1. Create a separate VirtualEnv2, inside that Mezz2 for new domain
Site2.com, OR
2. Create new mezzanine proj
