[mezzanine-users] Re: Different Static Url for Each Site in MultiTenancy

[Matt Mansour]

One approach I am looking into is adding / overiding the static template 
context processor. But I am wondering if there is a cleaner way. Or 
something simple that I am overlooking. 

On Friday, November 20, 2015 at 4:48:28 PM UTC-8, Matt Mansour wrote:
>
> Howdy all -
>
> I am working on multi tenancy mezzanine project. I define a static URL in 
> settings (in this case a Cloudfront URL). However, the static URL needs to 
> change to match the site I am accessing. 
>
> For example, if I am on *example.com * I want my 
> static url to render as *media.example.com/static/ 
> ... * Likewise, if I am on *example2.com 
> * I want my static url to render as 
> *media.example2.com/static/ 
> *
>
> Has anyone here had to implement something similar? 
>
> Unfortunately when images are rendered from a different domains than the 
> site domain strange things can happen; like Facebook share reach 
> diminishing, as their current algo seems to associate that sort of thing as 
> spam.
>
> Cheers
>

-- 
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] Different Static Url for Each Site in MultiTenancy

[Matt Mansour]

Howdy all -

I am working on multi tenancy mezzanine project. I define a static URL in 
settings (in this case a Cloudfront URL). However, the static URL needs to 
change to match the site I am accessing. 

For example, if I am on *example.com* I want my static url to render as 
*media.example.com/static/... * Likewise, if I am on *example2.com* I want 
my static url to render as *media.example2.com/static/*

Has anyone here had to implement something similar? 

Unfortunately when images are rendered from a different domains than the 
site domain strange things can happen; like Facebook share reach 
diminishing, as their current algo seems to associate that sort of thing as 
spam.

Cheers

-- 
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] Re: Talk about Mezzanine in Django Girls São José dos Campos Brazil

[Mario R. Osorio]

Oi Maria. Eu não falo Português, mas eu posso ler e entender porque eu falo 
espanhol.

I went through your presentation and I think you did a great job. Yours is 
a simple yet powerful presentation, just like Mezzanine is a simple yet 
powerful CMS. And by the way, there is nothing wrong with your English; you 
made yourself understood and that is the goal.

Good job & congratulations!



Oi Maria. Eu não falo Português, mas eu posso ler e entender e eu falo 
espanhol
On Friday, November 20, 2015 at 3:49:02 PM UTC-5, Julyane Miranda wrote:
>
> Hi people, I'm here because Stephen Mcdonald asked me to send the link of 
> my talk on a Mezzanine CMS.
> (
> https://docs.google.com/presentation/d/1acbovjoG5Tb_5Ll-691mNloWnl2AgnrjbD_prkQn2Gs/pub?start=false&loop=false&delayms=3000&slide=id.p28
> )
>
> I met Mezzanine 3 years ago, where I started a code sharing website for 
> robotics projects.
>
> I am in love with mezzanine, and decided to start releasing the tool in 
> Brazil among girls who want to learn programming.
>
> This edition of Django Girls was my first presentation on the mezzanine 
> and have had good feedback, with some girls who said they like a lot and 
> felt motivated to start a blog with Mezzanine.
>
> I'm also learning from it all and want to do more and more.
>
> My presentation follows in Portuguese, if someone has ideas and want to 
> contribute to this presentation we optimize for the next event, please 
> contact me so I can create a means of edition shareable.
>
> I'm sorry for bad English.
>
> Hugs;
>

-- 
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] Re: Access FileField in a Page model

[Nkansah Rexford]

Got it working

-- 
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 FileField in a Page model

[Nkansah Rexford]

I can access 'page.homepage.heading' in the same template. The 
page.homepage is available in the context, however, just the 
.featured_image is empty. 

And checking from the db, that field doesn't exist, but the image shows up 
in Admin.

On Friday, November 20, 2015 at 9:19:43 PM UTC, Kenneth Bolton wrote:
>
> Hi,
>
> I think you want to read 
> http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-isn-t-the-homepage-a-page-object-i-can-edit-via-the-admin
> .
>
> The first thing is to install Django Debug Toolbar. It will help you see 
> the context being sent to the templates. You will be able to inspect `page` 
> and see if it has `homepage`, and if 'homepage' has `featured_image`.
>
> Those two should get you going.
>
> -ken
>
>
>
> On Fri, Nov 20, 2015 at 2:46 PM, Nkansah Rexford  > wrote:
>
>> I have a field:
>> class HomePage(Page):
>> featured_image = FileField(verbose_name=_("Featured Image"),
>>   
>>  upload_to=upload_to("main.HomePage.featured_image", "homepage"),
>>format="Image", max_length=255,
>>null=True, blank=True)
>>
>>
>>
>> In my templates, what do I do to get the featured_image to show? I've 
>> loaded mezzanine_tags
>>
>> According to the Blog Post example (referred to it, because devs here 
>> love pointing to source code as examples), this is how it was done:
>> 
>>
>>
>> This is what I have:
>> 
>>
>>
>> But it doesn't work. According to: 
>> http://mezzanine.jupo.org/docs/utilities.html#thumbnail, the thumbnail 
>> should work on my situation. Its not working,
>>
>> Anything I'm missing?
>>
>> -- 
>> 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 FileField in a Page model

[Ken Bolton]

Hi,

I think you want to read
http://mezzanine.jupo.org/docs/frequently-asked-questions.html#why-isn-t-the-homepage-a-page-object-i-can-edit-via-the-admin
.

The first thing is to install Django Debug Toolbar. It will help you see
the context being sent to the templates. You will be able to inspect `page`
and see if it has `homepage`, and if 'homepage' has `featured_image`.

Those two should get you going.

-ken



On Fri, Nov 20, 2015 at 2:46 PM, Nkansah Rexford 
wrote:

> I have a field:
> class HomePage(Page):
> featured_image = FileField(verbose_name=_("Featured Image"),
>
>  upload_to=upload_to("main.HomePage.featured_image", "homepage"),
>format="Image", max_length=255,
>null=True, blank=True)
>
>
>
> In my templates, what do I do to get the featured_image to show? I've
> loaded mezzanine_tags
>
> According to the Blog Post example (referred to it, because devs here love
> pointing to source code as examples), this is how it was done:
> 
>
>
> This is what I have:
> 
>
>
> But it doesn't work. According to:
> http://mezzanine.jupo.org/docs/utilities.html#thumbnail, the thumbnail
> should work on my situation. Its not working,
>
> Anything I'm missing?
>
> --
> 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] Re: Access FileField in a Page model

[Nkansah Rexford]

I dropped to shell, and found this to be strange:
>>> x = HomePage.objects.get(pk=1)
>>> x

>>> x.title
u'Home'
>>> x.slug
u'/'
>>> x.heading
u"Okay, you're welcome"
>>> x.subheading
u'We believe in change by the people for the people. We believe people can 
take development into their own hands.'
>>> x.featured_image
u''
>>> 


Why and how? 

-- 
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] Re: Access FileField in a Page model

[Nkansah Rexford]

I dropped to shell, and found this to be strange:
>>> x = HomePage.objects.get(pk=1)
>>> x

>>> x.title
u'Home'
>>> x.slug
u'/'
>>> x.heading
u"Okay, you're welcome"
>>> x.subheading
u'We believe in change by the people for the people. We believe people can 
take development into their own hands.'
>>> x.featured_image
u''
>>> 


Why and how? 

-- 
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] Talk about Mezzanine in Django Girls São José dos Campos Brazil

[Julyane Miranda]

Hi people, I'm here because Stephen Mcdonald asked me to send the link of 
my talk on a Mezzanine CMS.
(https://docs.google.com/presentation/d/1acbovjoG5Tb_5Ll-691mNloWnl2AgnrjbD_prkQn2Gs/pub?start=false&loop=false&delayms=3000&slide=id.p28)

I met Mezzanine 3 years ago, where I started a code sharing website for 
robotics projects.

I am in love with mezzanine, and decided to start releasing the tool in 
Brazil among girls who want to learn programming.

This edition of Django Girls was my first presentation on the mezzanine and 
have had good feedback, with some girls who said they like a lot and felt 
motivated to start a blog with Mezzanine.

I'm also learning from it all and want to do more and more.

My presentation follows in Portuguese, if someone has ideas and want to 
contribute to this presentation we optimize for the next event, please 
contact me so I can create a means of edition shareable.

I'm sorry for bad English.

Hugs;

-- 
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 FileField in a Page model

[Nkansah Rexford]

I have a field:
class HomePage(Page):
featured_image = FileField(verbose_name=_("Featured Image"),
  
 upload_to=upload_to("main.HomePage.featured_image", "homepage"),
   format="Image", max_length=255,
   null=True, blank=True)



In my templates, what do I do to get the featured_image to show? I've 
loaded mezzanine_tags

According to the Blog Post example (referred to it, because devs here love 
pointing to source code as examples), this is how it was done:



This is what I have:



But it doesn't work. According 
to: http://mezzanine.jupo.org/docs/utilities.html#thumbnail, the thumbnail 
should work on my situation. Its not working,

Anything I'm missing?

-- 
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] Re: Mezzanine social auth

[Nkansah Rexford]

I'm using Allauth in my project with mezzanine, and its working fine, 
unless you want to thrown in features Allauth doesn't have

-- 
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] Search engine performance and technology?

[Matt Mansour]

Hi A.B -

Mezzanine by default searches the models / hits the database directly. It
works very well, until your dataset starts to get very large or you have
tons of traffic coming in. Then you'll probably want to implement a
solution such as elastic search. But there is no need to implement elastic
search right out of the gate, unless you know your initial launch will have
500M+ records or tons of traffic.

Cheers,
Matt

On Fri, Nov 20, 2015 at 1:09 AM, A.B.  wrote:

> Is it done by elastic search? How are first hand experiences with the
> performance of Mezzanine search engine and how was it implemented?
>
> --
> 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.

Re: [mezzanine-users] Field Injection Will Not Migrate

[R.J. Jackson]

Thanks! Ill keep this in mind next time.  i managed to get the Field 
Injection to work.

On Thursday, November 19, 2015 at 8:23:24 PM UTC-5, Sam Kingston wrote:
>
> I just wanted to add there is a third way of doing this, and that is 
> creating a model in your own app and adding a OneToOne field to the Blog 
> model. I now use that method exclusively instead of EXTRA_MODEL_FIELDS and 
> it is much cleaner and easier to maintain. 

-- 
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] Trying To Understand Mezzanine

[R.J. Jackson]

Hello,

So I had worked with Django and feel like I have a pretty good 
understanding of that.  When working with Mezzanine, Ive read through the 
docs and some tutorials, and still feel a little lost.  So from what I have 
read, its just a basic Django project, and implementing your own models, 
views...etc are fine.  So what I have done is created a simple featured 
project Boolean using field injection.  I would like the main page to 
display all the featured projects.  So am I correct to assume that the 
proper approach is to create your own web app, create a view that query's 
it from the DB, and then add it to the template?

Or maybe there is a tutorial or a specific part of the doc that you can 
recommend, I apologize if this is such a simple question i just keep going 
in circles.  Thanks.

-- 
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] Field Injection Will Not Migrate

[R.J. Jackson]

Yes you were dead on, I just deleted the migrations and it worked fine.

On Thursday, November 19, 2015 at 4:37:15 PM UTC-5, Eduardo Rivas wrote:
>
> It looks like you have a migration file inside Mezzanine's source code. If 
> you see the name of the migration that raises the exception, it's 
> blog.0007_auto_20151119 (meaning it was created on November 19, 2015, by 
> your injected field I presume). Remove that file and the associated .pyc 
> file and Mezzanine should go back to normal.
>
> Now, regarding field injection in Mezzanine 4, it's not as simple as it 
> was in the Mezzanine 3 days. There are essentially two ways of doing it: 
> One is explained by the official docs 
> ,
>  
> and the other is a method developed by Josh Cartmell 
>  (look for the 
> field injection section in that article). I use the first one, as it is 
> less brittle and somewhat supported by Django itself. It is not as elegant 
> though, and will require you to manually maintain the migration history of 
> all models with injected fields and any model that inherits from them.
>
> Both methods have the same goal: to make sure that the migrations for your 
> injected fields exist in your project, not in Mezzanine's source. Doing 
> otherwise is a nightmare for collaborating with other devs and deploying.
>

-- 
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] Search engine performance and technology?

[A.B.]

Is it done by elastic search? How are first hand experiences with the 
performance of Mezzanine search engine and how was it implemented?

-- 
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.