Awesome, thanks!  Worked around it by comparing to .titles, but that didn't 
feel great. Thanks a bunch, -Ollie

On Wednesday, December 23, 2015 at 5:38:16 PM UTC-5, Stephen McDonald wrote:
>
> I dismissed this prematurely as working as intended, sorry about that.
>
> I just pushed a fix for it here:
>
>
> https://github.com/stephenmcd/mezzanine/commit/7a33f1a41973a0fc6c54d5d89233c10307d39503
>
>
>
> On Wed, Dec 23, 2015 at 9:00 AM, Oliver Rutherfurd <[email protected] 
> <javascript:>> wrote:
>
>> Hey, In the admin, the help text for Meta data => Title is "Optional 
>> title to be used in the HTML title tag. If left blank, the main title field 
>> will be used."  What I'm seeing in practice and from reading the code is 
>> that .meta_title property calls str(self) if there's no ._meta_data value, 
>> and that results in the Page.titles attribute being used instead of 
>> .title.  I filed a bug report (
>> https://github.com/stephenmcd/mezzanine/issues/1502), since that 
>> behavior is not what the documentation implies, but was told it's not a bug 
>> and to come here for help.  Because the .meta_title property always returns 
>> a value and I can't access the underlying field (._meta_title) because of 
>> the leading underscore, I don't see an easy way to have the template emit 
>> the ._meta_title if there is one or fall back on the .title if there isn't 
>> (in Jinja, I'd just do {{ page._meta_title or page.title }}).  Any help 
>> would be appreciated.  Thanks, -Ollie
>>
>> -- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Stephen McDonald
> http://jupo.org
>

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