[mezzanine-users] BlogPost Proxy Admin

[John]

Hi Everyone,

I would like to create an admin interface for the BlogPost that will 
automatically add a category to the BlogPost being saved. 

It seems like the best way to do this is via a proxy model which I have 
created successfully along with the admin interface for the proxy model.

However I'm at a bit of a loss as to which function I should be overriding 
to add the BlogCategory. Initially I had overridden the proxy object save() 
model and this worked fine when creating the object directly. However when 
saving through the admin form it seems that the Categories, being an m2m, 
is overridden with the categories in the form during save_related(). I've 
attempted to append the category to the cleaned_data on the form however it 
is a query set.

This is my current solution:
class ProxyAdmin(BlogPostAdmin):
def save_related(self, request, form, formsets, change):
import pdb; pdb.set_trace()
proxy_cat = BlogCategory.objects.get(title='proxy_cat')
form.cleaned_data['categories'] = 
list(form.cleaned_data['categories'])
form.cleaned_data['categories'].append(proxy_cat)
super(BlogPostAdmin, self).save_related(request, form, formsets, 
change)

The key is to replace the categories query set with a list and append to 
that. It appears to work but does anyone foresee any problems with this? 
Does anyone have a better solution?

Thanks,
John



-- 
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/groups/opt_out.

Re: [mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Ross Laird]

Same goes for this bit:

.navbar-inverse .nav .active > a, .navbar-inverse .nav .active > a:hover, 
.navbar-inverse .nav .active > a:focus {
color: #ff;
background-color: #11;}



On Tuesday, 28 January 2014 19:43:28 UTC-8, Ross Laird wrote:
>
> This got me thinking. Here's the short answer:
>
> Change the highlighted colors to your desired background color and 
> gradient colors:
>
> .navbar-inverse .navbar-inner {
> background-color: #1b1b1b;
> background-image: -moz-linear-gradient(top, #22, #11);
> background-image: -webkit-gradient(linear, 0 0, 0 100%, from(#22), 
> to(#11));
> background-image: -webkit-linear-gradient(top, #22, #11);
> background-image: -o-linear-gradient(top, #22, #11);
> background-image: linear-gradient(to bottom, #22, #11);
> background-repeat: repeat-x;
> border-color: #252525;
> filter: 
> progid:DXImageTransform.Microsoft.gradient(startColorstr='#ff22', 
> endColorstr='#ff11', GradientType=0);}
>
>
> That will do it.
>
>
>
>
> On Tuesday, 28 January 2014 19:33:34 UTC-8, Ross Laird wrote:
>>
>> These kinds of things can be tough to assess, at a distance, without 
>> actually diving into the CSS code. One way to debug this is to use a 
>> customized CSS file that loads after the Mezzanine and Bootstrap CSS files. 
>> Changing the Bootstrap CSS directly won't always yield the results you 
>> desire, as various parts of the Bootstrap code are interconnected (through 
>> cascading) in ways that can be hard to track. Generally, you will be better 
>> off copying the CSS that applies to a given element, creating a new set of 
>> rules for that element in your custom CSS file, and hacking away on your 
>> own code. If this is an element issue (such CSS applied to a div), it 
>> should be fairly easy to find. If it's a cascade issue, it can be messy. 
>> (Use, with caution, temporarily, and only as a last resort, the !important 
>> flag to make sure that your rules are loaded and not Bootstrap's).
>>
>> Also, Bootstrap's use of background-image is discussed in threads like 
>> this 
>> one,
>>  
>> which explores both options (changing Bootstrap, and creating custom css).
>>
>> Also, background-color will always lie behind background-image. (The spec 
>> is here .) 
>> So, this suggests that one line of action might first be to remove 
>> background-image properties to get a look at what's behind everything. Then 
>> you can selectively add things back in.
>>
>> In the case of Bootstrap, most of the background-image rules do not 
>> actually load images but rather specify gradients, which will override any 
>> previously-declared background images (more 
>> here).
>>  
>> So, these various interactions can be quite complex. Start with what you 
>> can see when you take almost everything out, and go from there.
>>
>>
>> On Tuesday, 28 January 2014 18:49:47 UTC-8, Gordon Agress wrote:
>>>
>>> No, a Chrome console search for #navbar-inverse comes up empty on the 
>>> page in question.
>>>
>>> I think there is something in bootstrap-theme.css that introduces a 
>>> "background-image: fixed-gradient", of a white color, that sits atop the 
>>> background color.  When I edit base.html to comment out 
>>> bootstrap-theme.css, this issue goes away.  
>>>
>>> The footer background color issue seems to emerge because mezzanine.css 
>>> sets a value for the footer background-color, which is not overloaded by 
>>> the Cyborg theme.  I patched with an additional piece of CSS to provide 
>>> that overload.
>>>
>>> One other issue is that the 'Blog' title is overlapped by the navbar.  
>>> I'll tackle that in the morning.
>>>
>>> I'm new to CSS, and so first suspect operator error, but it looks little 
>>> like there have been changes to the base Mezzanine layout and CSS that 
>>> haven't been accomodated by Cyborg.
>>>
>>> I'm pretty sure my fixes can be incorporated into the CSS more smoothly.
>>>
>>>
>>> On Tue, Jan 28, 2014 at 8:06 PM, Ross Laird  wrote:
>>>
 Do you have the navbar-inverse class applied? That might play a role 
 here.


 On Tuesday, 28 January 2014 12:24:39 UTC-8, Gordon Agress wrote:
>
> I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but 
> the navbar is displaying as if its background color were white (rather 
> than 
> black).  I've checked the computed CSS styles, the background seems set 
> properly, but there are items sets to white, and I suppose these could be 
> dominating the background color setting.
>
> Still, the Bootswatch site has a nav bar, in black.  So something 
> seems off here.
>
> Has anyone else had similar issues with the Bootswatch tem

Re: [mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Ross Laird]

This got me thinking. Here's the short answer:

Change the highlighted colors to your desired background color and gradient 
colors:

.navbar-inverse .navbar-inner {
background-color: #1b1b1b;
background-image: -moz-linear-gradient(top, #22, #11);
background-image: -webkit-gradient(linear, 0 0, 0 100%, from(#22), 
to(#11));
background-image: -webkit-linear-gradient(top, #22, #11);
background-image: -o-linear-gradient(top, #22, #11);
background-image: linear-gradient(to bottom, #22, #11);
background-repeat: repeat-x;
border-color: #252525;
filter: 
progid:DXImageTransform.Microsoft.gradient(startColorstr='#ff22', 
endColorstr='#ff11', GradientType=0);}


That will do it.




On Tuesday, 28 January 2014 19:33:34 UTC-8, Ross Laird wrote:
>
> These kinds of things can be tough to assess, at a distance, without 
> actually diving into the CSS code. One way to debug this is to use a 
> customized CSS file that loads after the Mezzanine and Bootstrap CSS files. 
> Changing the Bootstrap CSS directly won't always yield the results you 
> desire, as various parts of the Bootstrap code are interconnected (through 
> cascading) in ways that can be hard to track. Generally, you will be better 
> off copying the CSS that applies to a given element, creating a new set of 
> rules for that element in your custom CSS file, and hacking away on your 
> own code. If this is an element issue (such CSS applied to a div), it 
> should be fairly easy to find. If it's a cascade issue, it can be messy. 
> (Use, with caution, temporarily, and only as a last resort, the !important 
> flag to make sure that your rules are loaded and not Bootstrap's).
>
> Also, Bootstrap's use of background-image is discussed in threads like 
> this 
> one,
>  
> which explores both options (changing Bootstrap, and creating custom css).
>
> Also, background-color will always lie behind background-image. (The spec 
> is here .) 
> So, this suggests that one line of action might first be to remove 
> background-image properties to get a look at what's behind everything. Then 
> you can selectively add things back in.
>
> In the case of Bootstrap, most of the background-image rules do not 
> actually load images but rather specify gradients, which will override any 
> previously-declared background images (more 
> here).
>  
> So, these various interactions can be quite complex. Start with what you 
> can see when you take almost everything out, and go from there.
>
>
> On Tuesday, 28 January 2014 18:49:47 UTC-8, Gordon Agress wrote:
>>
>> No, a Chrome console search for #navbar-inverse comes up empty on the 
>> page in question.
>>
>> I think there is something in bootstrap-theme.css that introduces a 
>> "background-image: fixed-gradient", of a white color, that sits atop the 
>> background color.  When I edit base.html to comment out 
>> bootstrap-theme.css, this issue goes away.  
>>
>> The footer background color issue seems to emerge because mezzanine.css 
>> sets a value for the footer background-color, which is not overloaded by 
>> the Cyborg theme.  I patched with an additional piece of CSS to provide 
>> that overload.
>>
>> One other issue is that the 'Blog' title is overlapped by the navbar.  
>> I'll tackle that in the morning.
>>
>> I'm new to CSS, and so first suspect operator error, but it looks little 
>> like there have been changes to the base Mezzanine layout and CSS that 
>> haven't been accomodated by Cyborg.
>>
>> I'm pretty sure my fixes can be incorporated into the CSS more smoothly.
>>
>>
>> On Tue, Jan 28, 2014 at 8:06 PM, Ross Laird  wrote:
>>
>>> Do you have the navbar-inverse class applied? That might play a role 
>>> here.
>>>
>>>
>>> On Tuesday, 28 January 2014 12:24:39 UTC-8, Gordon Agress wrote:

 I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
 navbar is displaying as if its background color were white (rather than 
 black).  I've checked the computed CSS styles, the background seems set 
 properly, but there are items sets to white, and I suppose these could be 
 dominating the background color setting.

 Still, the Bootswatch site has a nav bar, in black.  So something seems 
 off here.

 Has anyone else had similar issues with the Bootswatch templates?

>>>  -- 
>>> 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/wFraHvB4Sf0/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> mezzanine-use...@googlegroups.com.
>>> For m

Re: [mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Ross Laird]

These kinds of things can be tough to assess, at a distance, without 
actually diving into the CSS code. One way to debug this is to use a 
customized CSS file that loads after the Mezzanine and Bootstrap CSS files. 
Changing the Bootstrap CSS directly won't always yield the results you 
desire, as various parts of the Bootstrap code are interconnected (through 
cascading) in ways that can be hard to track. Generally, you will be better 
off copying the CSS that applies to a given element, creating a new set of 
rules for that element in your custom CSS file, and hacking away on your 
own code. If this is an element issue (such CSS applied to a div), it 
should be fairly easy to find. If it's a cascade issue, it can be messy. 
(Use, with caution, temporarily, and only as a last resort, the !important 
flag to make sure that your rules are loaded and not Bootstrap's).

Also, Bootstrap's use of background-image is discussed in threads like this 
one,
 
which explores both options (changing Bootstrap, and creating custom css).

Also, background-color will always lie behind background-image. (The spec 
is here .) So, 
this suggests that one line of action might first be to remove 
background-image properties to get a look at what's behind everything. Then 
you can selectively add things back in.

In the case of Bootstrap, most of the background-image rules do not 
actually load images but rather specify gradients, which will override any 
previously-declared background images (more 
here).
 
So, these various interactions can be quite complex. Start with what you 
can see when you take almost everything out, and go from there.


On Tuesday, 28 January 2014 18:49:47 UTC-8, Gordon Agress wrote:
>
> No, a Chrome console search for #navbar-inverse comes up empty on the page 
> in question.
>
> I think there is something in bootstrap-theme.css that introduces a 
> "background-image: fixed-gradient", of a white color, that sits atop the 
> background color.  When I edit base.html to comment out 
> bootstrap-theme.css, this issue goes away.  
>
> The footer background color issue seems to emerge because mezzanine.css 
> sets a value for the footer background-color, which is not overloaded by 
> the Cyborg theme.  I patched with an additional piece of CSS to provide 
> that overload.
>
> One other issue is that the 'Blog' title is overlapped by the navbar.  
> I'll tackle that in the morning.
>
> I'm new to CSS, and so first suspect operator error, but it looks little 
> like there have been changes to the base Mezzanine layout and CSS that 
> haven't been accomodated by Cyborg.
>
> I'm pretty sure my fixes can be incorporated into the CSS more smoothly.
>
>
> On Tue, Jan 28, 2014 at 8:06 PM, Ross Laird 
> > wrote:
>
>> Do you have the navbar-inverse class applied? That might play a role here.
>>
>>
>> On Tuesday, 28 January 2014 12:24:39 UTC-8, Gordon Agress wrote:
>>>
>>> I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
>>> navbar is displaying as if its background color were white (rather than 
>>> black).  I've checked the computed CSS styles, the background seems set 
>>> properly, but there are items sets to white, and I suppose these could be 
>>> dominating the background color setting.
>>>
>>> Still, the Bootswatch site has a nav bar, in black.  So something seems 
>>> off here.
>>>
>>> Has anyone else had similar issues with the Bootswatch templates?
>>>
>>  -- 
>> 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/wFraHvB4Sf0/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> mezzanine-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Gordon Agress]

No, a Chrome console search for #navbar-inverse comes up empty on the page
in question.

I think there is something in bootstrap-theme.css that introduces a
"background-image: fixed-gradient", of a white color, that sits atop the
background color.  When I edit base.html to comment out
bootstrap-theme.css, this issue goes away.

The footer background color issue seems to emerge because mezzanine.css
sets a value for the footer background-color, which is not overloaded by
the Cyborg theme.  I patched with an additional piece of CSS to provide
that overload.

One other issue is that the 'Blog' title is overlapped by the navbar.  I'll
tackle that in the morning.

I'm new to CSS, and so first suspect operator error, but it looks little
like there have been changes to the base Mezzanine layout and CSS that
haven't been accomodated by Cyborg.

I'm pretty sure my fixes can be incorporated into the CSS more smoothly.


On Tue, Jan 28, 2014 at 8:06 PM, Ross Laird  wrote:

> Do you have the navbar-inverse class applied? That might play a role here.
>
>
> On Tuesday, 28 January 2014 12:24:39 UTC-8, Gordon Agress wrote:
>>
>> I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the
>> navbar is displaying as if its background color were white (rather than
>> black).  I've checked the computed CSS styles, the background seems set
>> properly, but there are items sets to white, and I suppose these could be
>> dominating the background color setting.
>>
>> Still, the Bootswatch site has a nav bar, in black.  So something seems
>> off here.
>>
>> Has anyone else had similar issues with the Bootswatch templates?
>>
>  --
> 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/wFraHvB4Sf0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/groups/opt_out.

[mezzanine-users] Re: Problem moving or adding pages from the admin

[Jake Schmitz]

Yes. Here is the log I get when I load up the admin page to add pages.


   1. Uncaught TypeError: Property '$' of object [object Object] is not a 
   function 
Changelist.js:1
  1. (anonymous 
function)Changelist.js:1
  

   1. Uncaught TypeError: Property '$' of object [object Object] is not a 
   function 
page_tree.js:31
  1. (anonymous 
function)page_tree.js:31
  

   1. Uncaught TypeError: Property '$' of object [object Object] is not a 
   function 
navigation.js:1
  1. (anonymous 
function)navigation.js:1
  

   1. Uncaught TypeError: Cannot call method 'ajaxSetup' of undefined 
   
ajax_csrf.js:1
  1. (anonymous 
function)ajax_csrf.js:1
  

   1. Uncaught TypeError: Property '$' of object [object Object] is not a 
   function 


On Friday, January 24, 2014 11:04:35 PM UTC-8, Ryan Sadwick wrote:
>
> Any javascript errors showing up in your browser's console?
>
> On Friday, January 24, 2014 11:22:59 PM UTC-5, Jake Schmitz wrote:
>>
>>
>> For some reason I can only create pages from the quick add on the main 
>> admin page. When I try to add a page from within the actual list of all my 
>> pages, nothing happens. I cannot move the order of my pages around nor can 
>> I add a nested page. Any help would be appreciated.
>>
>

-- 
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/groups/opt_out.

[mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Ross Laird]

Do you have the navbar-inverse class applied? That might play a role here.

On Tuesday, 28 January 2014 12:24:39 UTC-8, Gordon Agress wrote:
>
> I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
> navbar is displaying as if its background color were white (rather than 
> black).  I've checked the computed CSS styles, the background seems set 
> properly, but there are items sets to white, and I suppose these could be 
> dominating the background color setting.
>
> Still, the Bootswatch site has a nav bar, in black.  So something seems 
> off here.
>
> Has anyone else had similar issues with the Bootswatch templates?
>

-- 
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/groups/opt_out.

[mezzanine-users] Re: Bootswatch Theme: Navbar doesn't display expected color

[Gordon Agress]

The navbar problem is caused by some conflict with bootstrap-theme.css -- 
commenting out the latter fixes the problem.  (I think the css injects a 
background-image that dominates the background color.)  However, I'm having 
the same problem with the footer, though I haven't thoroughly investigated 
yet.

On Tuesday, January 28, 2014 3:24:39 PM UTC-5, Gordon Agress wrote:
>
> I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
> navbar is displaying as if its background color were white (rather than 
> black).  I've checked the computed CSS styles, the background seems set 
> properly, but there are items sets to white, and I suppose these could be 
> dominating the background color setting.
>
> Still, the Bootswatch site has a nav bar, in black.  So something seems 
> off here.
>
> Has anyone else had similar issues with the Bootswatch templates?
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] Mezzanine and Google Analytics

[Gordon Agress]

I am.  I have the Mezzanine default in the footer, and a copy and paste of
the google code in .  The snippets are not the same.


On Tue, Jan 28, 2014 at 4:07 PM, Josh Cartmell  wrote:

> I don't think you should put it in two places (at best that will probably
> make things get double counted, at worst it will break analytics).  I think
> it usually takes about 24 hours for google to say it's installed.  Are you
> receiving analytics?
>
>
> On Tue, Jan 28, 2014 at 12:18 PM, Gordon Agress 
> wrote:
>
>> Thanks.  How long a lag?  Google calls for putting its code in , so
>> I currently have both in place.  Analytics reported installation shortly
>> after inclusion of the google code, so I suspect that's been the ticket.
>>
>> I don't suppose I need both, do I?
>>
>> On Monday, January 27, 2014 2:09:03 PM UTC-5, Josh Cartmell wrote:
>>
>>> Mezzanine's built in GA handling doesn't implement universal analytics
>>> (the code Google gives you) but it does work.  If you just put added your
>>> GA id to the site it often takes Google awhile to say that it is installed
>>> (even though it starts working instantly).  You definitely can override the
>>> template that the GA code is in if you want to upgrade to universal
>>> analytics.
>>>
>>>
>>> On Sun, Jan 26, 2014 at 3:19 PM, Gordon Agress wrote:
>>>
 I am trying to link a Mezzanine website to Google Adwords, but the
 JavaScript placed in the footer by Mezzanine (3.0.5) does not match the
 JavaScript specifiied by Google in its Google Analytics documentation.

 I've used the current Mezzanine language, by setting by
 GOOGLE_ANALYTICS_ID, and confirmed that the JS is appearing in the page
 footers.  But Google is still reporting that the tracking code is not
 installed.

 Am I missing something?  Or do I need to overload the footer_script
 template with the current Google specified language?


  --
 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/groups/opt_out.

>>>
>>>  --
>> 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/groups/opt_out.
>>
>
>  --
> 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/humKkNWSLX8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> mezzanine-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [mezzanine-users] Mezzanine and Google Analytics

[Josh Cartmell]

I don't think you should put it in two places (at best that will probably
make things get double counted, at worst it will break analytics).  I think
it usually takes about 24 hours for google to say it's installed.  Are you
receiving analytics?


On Tue, Jan 28, 2014 at 12:18 PM, Gordon Agress wrote:

> Thanks.  How long a lag?  Google calls for putting its code in , so
> I currently have both in place.  Analytics reported installation shortly
> after inclusion of the google code, so I suspect that's been the ticket.
>
> I don't suppose I need both, do I?
>
> On Monday, January 27, 2014 2:09:03 PM UTC-5, Josh Cartmell wrote:
>
>> Mezzanine's built in GA handling doesn't implement universal analytics
>> (the code Google gives you) but it does work.  If you just put added your
>> GA id to the site it often takes Google awhile to say that it is installed
>> (even though it starts working instantly).  You definitely can override the
>> template that the GA code is in if you want to upgrade to universal
>> analytics.
>>
>>
>> On Sun, Jan 26, 2014 at 3:19 PM, Gordon Agress wrote:
>>
>>> I am trying to link a Mezzanine website to Google Adwords, but the
>>> JavaScript placed in the footer by Mezzanine (3.0.5) does not match the
>>> JavaScript specifiied by Google in its Google Analytics documentation.
>>>
>>> I've used the current Mezzanine language, by setting by
>>> GOOGLE_ANALYTICS_ID, and confirmed that the JS is appearing in the page
>>> footers.  But Google is still reporting that the tracking code is not
>>> installed.
>>>
>>> Am I missing something?  Or do I need to overload the footer_script
>>> template with the current Google specified language?
>>>
>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[mezzanine-users] to add blog category and month as filters to keywords_for tag

[Andrey M]

Hi All

I develop the blog where blog categories are shown on different pages.
So I'd like to  show Tags and Archive (months) items only for current 
category.

As I can see, currently, it is not supported.  "keywords_for" doesn't have 
category/archive filters.
Could you please advise what the best way to implement it?

May it be added to the next Mezzanine release? 

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/groups/opt_out.

[mezzanine-users] Bootswatch Theme: Navbar doesn't display expected color

[Gordon Agress]

I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
navbar is displaying as if its background color were white (rather than 
black).  I've checked the computed CSS styles, the background seems set 
properly, but there are items sets to white, and I suppose these could be 
dominating the background color setting.

Still, the Bootswatch site has a nav bar, in black.  So something seems off 
here.

Has anyone else had similar issues with the Bootswatch templates?

-- 
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/groups/opt_out.

[mezzanine-users] Mezzanine

[Gordon Agress]

I'm trying to use the Bootswatch theme 'Cyborg' with Mezzanine, but the 
navbar is displaying as if its background color were white (rather than 
black).  I've checked the computed CSS styles, the background seems set 
properly, but there are items sets to white, and I suppose these could be 
dominating the background color setting.

Still, the Bootswatch site has a nav bar, in black.  So something seems off 
here.

Has anyone else had similar issues with the Bootswatch templates?

-- 
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/groups/opt_out.

Re: [mezzanine-users] Mezzanine and Google Analytics

[Gordon Agress]

Thanks.  How long a lag?  Google calls for putting its code in , so I 
currently have both in place.  Analytics reported installation shortly 
after inclusion of the google code, so I suspect that's been the ticket.

I don't suppose I need both, do I?  

On Monday, January 27, 2014 2:09:03 PM UTC-5, Josh Cartmell wrote:
>
> Mezzanine's built in GA handling doesn't implement universal analytics 
> (the code Google gives you) but it does work.  If you just put added your 
> GA id to the site it often takes Google awhile to say that it is installed 
> (even though it starts working instantly).  You definitely can override the 
> template that the GA code is in if you want to upgrade to universal 
> analytics.
>
>
> On Sun, Jan 26, 2014 at 3:19 PM, Gordon Agress 
> 
> > wrote:
>
>> I am trying to link a Mezzanine website to Google Adwords, but the 
>> JavaScript placed in the footer by Mezzanine (3.0.5) does not match the 
>> JavaScript specifiied by Google in its Google Analytics documentation.
>>
>> I've used the current Mezzanine language, by setting by 
>> GOOGLE_ANALYTICS_ID, and confirmed that the JS is appearing in the page 
>> footers.  But Google is still reporting that the tracking code is not 
>> installed.
>>
>> Am I missing something?  Or do I need to overload the footer_script 
>> template with the current Google specified language?
>>
>>
>>  -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

[mezzanine-users] Use smth like block.super.super for block overriding in mezzanine/django pages

[Andrey M]

Hi All,

I have created my own version of block_post_list.html (it uses overextends 
to extend original page) and I would like to override {% block 
breadcrumb_menu %}
However, I would like to execute super block in base.html and do not copy 
past it.

So, it seems I would like something like block.super.super which is not 
supported.

I understand it is common django noob question and I did not found direct 
answer but asking if any work around exists like 'overextends' feature to 
do it?
I have a lot of places which I need to replace/override but I'd like to 
keep original 'super.super' code working if possible and do not copy-paste 
it

Any ideas?

-- 
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/groups/opt_out.

[mezzanine-users] Multi Domain - But Related Content Question?

[Chad Dupuis]

Hello All,

I'm extremely new to mezzanine and django.  I'm in the process of 
rebuilding a large drupal site I've built over the years ( yinyanghouse.com 
) into a more modern framework and django/mezzanine is high on the list.

My question is on how best to setup the site.  

Currently we have one large site but it serves different purposes - a 
store, a theory section, a forum/community section and our personal 
acupuncture clinic.

I'd like to split this out into subdomains - store.yinyanghouse.com, 
community.yinyanghouse.com, etc.

The problem is that the store products for example show up on listings on 
the theory and community sections (as they relate to conditions, etc.)  So, 
currently, on a page like:
http://yinyanghouse.com/conditions-treated/alternative-natural-options-for-depression
 
 This would be in the theory section (i.e. www), but it pulls in data from 
the store and from the community sections.

Likely it's my ignorance of django, but can you setup multiple subdomains 
with a single database setup where I wouldn't be doing as many joins to get 
this data together?  Or would it be best to just leave it as one big site 
but use django themeing to simply retheme sections to give better 
abstraction between them without having clearly separate subdomains?

-- 
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/groups/opt_out.