Re: [mezzanine-users] Re: Mezzanine Deployment Instructions lacking and unusable

[Joshua Hepburn]

 

HI Ken,
Unfortunately it didn't. I had to manually enable supervisor to start on 
boot:

sudo systemctl enable supervisor

Otherwise it was a manual start after each boot.
However, this only seems to happen on Ubuntu Server 16.04, but not on other 
distros.
Josh 

On Wednesday, 8 March 2017 00:31:25 UTC+10, Kenneth Bolton wrote:
>
> Hi Joshua,
>
> Do those gateway errors go away pretty quickly? If I understand what you 
> are describing, that is Gunicorn restarting, which can take several moments.
>
> Henro: I tried to provide some assistance to you in IRC, but never heard 
> back regarding the FABRIC dictionary in your settings. I falsely assumed 
> that meant your itch had been scratched and you had moved on to bigger and 
> better things with Mezzanine. It is understandable that you would lash out 
> at the documentation and community, but I believe everyone in the greater 
> software community would encourage you to stick with it. The Mezzanine 
> documentation builds on a lot of foundational elements from Django and 
> Python. We have no idea where you (or any other correspondent) stands on 
> the continuum of knowledge and experience. If you let us, we will attempt 
> to learn what you need to get this working and become a contributor to our 
> growing community.
>
> Deepening my appreciation,
> ken
>
> On Tue, Mar 7, 2017 at 4:13 AM, Joshua Hepburn  > wrote:
>
>>
>> Henro,
>>
>> Django Deployment docs -  
>> https://docs.djangoproject.com/en/dev/howto/deployment/ - however this 
>> explains for apache and mod_wsgi, whereas the default fabric file that 
>> mezzanine uses caters for gunicorn and Nginx.
>>
>> I think it needs to be said though, that the official Mezzanine 
>> deployment doc / guide, works perfectly. Had no issues on deploying my very 
>> first mezzanine project.
>>
>> The only error I've had is actually not related to Mezzanine but to 
>> supervisor - causes bad gateway errors on server reboot.
>>
>> -- 
>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Access field of Page subclass in template

[Jochen Breuer]

Thanks Stephen! I've overlooked that!


Am Mittwoch, 8. März 2017 22:59:27 UTC+1 schrieb Stephen McDonald:
>
> Docs have you covered 
>
>
> http://mezzanine.jupo.org/docs/content-architecture.html#displaying-custom-content-types
>
> On Mar 8, 2017 1:40 PM, "Jochen Breuer"  
> wrote:
>
>>
>> Hello everyone,
>>
>> I've got a Page subclass with some additional fields. Everything works 
>> perfectly. But now I need to implement a side-bar navigation which should 
>> display a field from the Page subclass. The relevant template code looks 
>> like roughly this:
>>
>> {% for page in page_branch %}
>> {{ page.city }},
>> {% endfor %}
>>
>> city would be the field created in the Page subclass. Is there any way to 
>> achieve this without reimplementing the template tags needed here?
>>
>> The Page subclass looks like this:
>>
>> class MyOwnPage(Page):
>> city = models.CharField(max_length=255, verbose_name=_(u"City"))
>> content = RichTextField(_("Content"))
>> …
>> search_fields = ("content",)
>>
>>
>> Thanks!
>>
>> Jochen
>>
>> -- 
>> 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 mezzanine-use...@googlegroups.com .
>> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Access field of Page subclass in template

[Stephen McDonald]

Docs have you covered

http://mezzanine.jupo.org/docs/content-architecture.html#displaying-custom-content-types

On Mar 8, 2017 1:40 PM, "Jochen Breuer"  wrote:

>
> Hello everyone,
>
> I've got a Page subclass with some additional fields. Everything works
> perfectly. But now I need to implement a side-bar navigation which should
> display a field from the Page subclass. The relevant template code looks
> like roughly this:
>
> {% for page in page_branch %}
> {{ page.city }},
> {% endfor %}
>
> city would be the field created in the Page subclass. Is there any way to
> achieve this without reimplementing the template tags needed here?
>
> The Page subclass looks like this:
>
> class MyOwnPage(Page):
> city = models.CharField(max_length=255, verbose_name=_(u"City"))
> content = RichTextField(_("Content"))
> …
> search_fields = ("content",)
>
>
> Thanks!
>
> Jochen
>
> --
> 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 mezzanine-users+unsubscr...@googlegroups.com.
> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Access field of Page subclass in template

[Jochen Breuer]

Hello everyone,

I've got a Page subclass with some additional fields. Everything works 
perfectly. But now I need to implement a side-bar navigation which should 
display a field from the Page subclass. The relevant template code looks 
like roughly this:

{% for page in page_branch %}
{{ page.city }},
{% endfor %}

city would be the field created in the Page subclass. Is there any way to 
achieve this without reimplementing the template tags needed here?

The Page subclass looks like this:

class MyOwnPage(Page):
city = models.CharField(max_length=255, verbose_name=_(u"City"))
content = RichTextField(_("Content"))
…
search_fields = ("content",)


Thanks!

Jochen

-- 
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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.