Have you managed to deploy a vanilla Mezzanine site? Knowing the expected
behavior will be crucial as you move toward customizing Mezzanine.

On Wed, Feb 24, 2016 at 6:34 PM, Petar Petrov <[email protected]> wrote:

> Ken,
>
> I have made the following steps:
> 1. Install mezzanine
> 2. generate an app called "bloga"
> 3. copied all settings from there to my general settings
> 4. i now have my website and the visitor blog part (minus some url and
> template issues i should be able to fix)
> 5. if i go to /admin i get to regular django admin actually, not the
> mezzanine admin:
> my urls contains:
> from bloga.bloga.urls import *
> # here my normal urls including url(r'^admin/', include(admin.site.urls)),
> # which if i remove gives me errors
> urlpatterns += blog_urls # which contains the generated mezzanine app url
> file.
>
> pp
>
> On Wed, Feb 24, 2016 at 1:22 PM, Ken Bolton <[email protected]> wrote:
>
>> Hi Petar,
>>
>> What have you tried?
>>
>> In my experience, "all models hooked to work with Django models" *do* "appear
>> in Mezzanine admin".
>>
>> -ken
>>
>> On Wed, Feb 24, 2016 at 6:20 PM, Petar Petrov <[email protected]> wrote:
>>
>>> So you are saying that all models hooked to work with Django models can
>>> appear in Mezzanine admin and be managed from there? How can we do that?
>>>
>>> On Wed, Feb 24, 2016 at 1:14 PM, Stephen McDonald <[email protected]>
>>> wrote:
>>>
>>>> Yes you're wrong.
>>>>
>>>> On Thu, Feb 25, 2016 at 10:05 AM, Petar Petrov <[email protected]> wrote:
>>>>
>>>>> Stephen,
>>>>>
>>>>> Well, the reason is that I already have models and custom things on my
>>>>> site that I would like to keep - databases of people, newsletter code
>>>>> generation, custom modules, etc. things that are not "pages"/"blog posts"
>>>>> so accordingly they are managed through the regular Django admin. Correct
>>>>> me if I am wrong, but the Mezzanine CMS is only for the content it
>>>>> provides.
>>>>>
>>>>> pp
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 24, 2016 at 12:55 PM, Stephen McDonald <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Sorry, I guess it wasn't clearly spelled out - there's no good reason
>>>>>> at all to try and have two admin sites running. You'd intentionally be
>>>>>> working *against* one of the best features Mezzanine has over other 
>>>>>> Django
>>>>>> based CMSes, in that the Mezzanine admin *is* the Django admin, just 
>>>>>> with a
>>>>>> different look to it. All your admin functionality that you supposedly 
>>>>>> want
>>>>>> to put in the "Django" admin should Just Work in the "Mezzanine" admin.
>>>>>>
>>>>>> Again, they're the same thing. Providing two admin interfaces to your
>>>>>> administrators does them a disservice, and Mezzanine very intentionally
>>>>>> aims to help you not have to do that.
>>>>>>
>>>>>> Hope that makes it clear for you.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 25, 2016 at 9:03 AM, Petar Petrov <[email protected]> wrote:
>>>>>>
>>>>>>> Well, that's what stackoverflow is, right?
>>>>>>>
>>>>>>> If he did
>>>>>>> - i will make my project
>>>>>>> - all people here will have easier time making it
>>>>>>> - i will write a tutorial that helps everybody around the world
>>>>>>> trying it out. maybe even someone might fork it or make it easier to 
>>>>>>> happen.
>>>>>>>
>>>>>>> So i don't see a reason why not. every private detail can be changed
>>>>>>> not to reflect his real site.
>>>>>>>
>>>>>>> my2c
>>>>>>>
>>>>>>> On Wed, Feb 24, 2016 at 11:50 AM, Ryne Everett <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Did you make it work with both admins - original Django admin and
>>>>>>>>> the CMS admin? If so, how?
>>>>>>>>
>>>>>>>>
>>>>>>>> AFAIK, nobody does this.
>>>>>>>>
>>>>>>>> On Wed, Feb 24, 2016 at 4:44 PM, Petar Petrov <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hmmm,
>>>>>>>>>
>>>>>>>>> That info was not enough for me i needed more guidance. Did you
>>>>>>>>> make it work with both admins - original Django admin and the CMS 
>>>>>>>>> admin? If
>>>>>>>>> so, how?
>>>>>>>>> Can you share your urls dispatcher to see how you have done it?
>>>>>>>>>
>>>>>>>>> If I make it work I will write a long detailed tutorial for
>>>>>>>>> everybody.
>>>>>>>>>
>>>>>>>>> pp
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Feb 24, 2016 at 3:56 AM, Encolpe Degoute <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I followed this today to transform my django site into mezzanine
>>>>>>>>>> site:
>>>>>>>>>>
>>>>>>>>>> http://mezzanine.jupo.org/docs/frequently-asked-questions.html#how-can-i-add-mezzanine-to-an-existing-django-project
>>>>>>>>>>
>>>>>>>>>> No more, no less.
>>>>>>>>>> The most painful was to review the url dispatcher.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> Le vendredi 12 février 2016 05:52:14 UTC+1, Petar Petrov a écrit :
>>>>>>>>>>>
>>>>>>>>>>> By looking at the docs (FAQ more specifically), it seems like it
>>>>>>>>>>> could be added as an app to a current project, even though pretty 
>>>>>>>>>>> much
>>>>>>>>>>> nothing has been said.
>>>>>>>>>>>
>>>>>>>>>>> So I decided to challenge myself and I spent a good chunk of
>>>>>>>>>>> todays day to make it work and i did get to dashboard, pages, blog 
>>>>>>>>>>> and then
>>>>>>>>>>> i realized I can't access the admin which has all the Rich text 
>>>>>>>>>>> editing
>>>>>>>>>>> etc.
>>>>>>>>>>>
>>>>>>>>>>> So was just curious if it is possible to have both admins work
>>>>>>>>>>> in like a reasonable time without rewriting tons of stuff, or 
>>>>>>>>>>> should I drop
>>>>>>>>>>> it as an idea, since there is virtually no guidance online. If you 
>>>>>>>>>>> have
>>>>>>>>>>> ideas on how to do it, please share, that would be awesome.
>>>>>>>>>>>
>>>>>>>>>>> Thanx!
>>>>>>>>>>> pp
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>> You received this message because you are subscribed to a topic
>>>>>>>>>> in the Google Groups "Mezzanine Users" group.
>>>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>>>> https://groups.google.com/d/topic/mezzanine-users/GINVTKyBMEg/unsubscribe
>>>>>>>>>> .
>>>>>>>>>> To unsubscribe from this group and all its topics, send an email
>>>>>>>>>> to [email protected].
>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "Mezzanine Users" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to [email protected].
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>>> the Google Groups "Mezzanine Users" group.
>>>>>>>> To unsubscribe from this topic, visit
>>>>>>>> https://groups.google.com/d/topic/mezzanine-users/GINVTKyBMEg/unsubscribe
>>>>>>>> .
>>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>>> [email protected].
>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Mezzanine Users" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to [email protected].
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Stephen McDonald
>>>>>> http://jupo.org
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "Mezzanine Users" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/mezzanine-users/GINVTKyBMEg/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> [email protected].
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Mezzanine Users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Stephen McDonald
>>>> http://jupo.org
>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Mezzanine Users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/mezzanine-users/GINVTKyBMEg/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> [email protected].
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Mezzanine Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/mezzanine-users/GINVTKyBMEg/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to