Re: [mezzanine-users] Migration to Jazzband / Code Shelter

[Wim Feijen]

Hi!

Sorry I am late to the party. I just wanted to say that we use Mezzanine 
for a few websites, and are interested in helping maintain it and helping 
in bring it up to date to 2.0.  

For me the Jazzband umbrella would work and we would like to contribute in 
that way. 

For reference, I came across this interesting post of what happened with 
django-fiber, a similar case where the original creators handed over 
maintenance, see: 
https://github.com/django-fiber/django-fiber/issues/244

Basically, the creator Dennis Bunskoek proposed:

"I like the idea of a maintenance-mode project under 
django-fiber/django-fiber with multiple maintainers. Me and some colleagues 
of mine would like to be a maintainer as well, since we also use Django 
Fiber in a lot of sites.

What would be a good way forward for this?
Some thoughts:

   - create django-fiber/django-fiber repo (multiple admins?)
   - invite maintainers (as contributors / admins?)
   - communicate in the README of this repo (ridethepony/django-fiber) that 
   the project has moved
   - change owner of PyPI package django-fiber, add multiple owners / 
   maintainers (how exactly? anyone got experience with this?)"

And that's what happened.


Let's go for Jazzband, but if that fails, we have an alternative as well. 

Best regards,

Wim

Op woensdag 8 januari 2020 10:11:29 UTC+1 schreef Pete Dermott:
>
> I have created an issue on the jazzband-roadies Github 
>  mentioning Stephen. 
> To reiterate again - I'm not trying to step on anyone's toes, I just would 
> like to get this moving so we can have a 2.0 compatible release ready for 
> when April rolls around and 1.11 is no longer supported.
>
> On Friday, 13 December 2019 10:41:21 UTC, Pete Dermott wrote:
>>
>> Hi Eduardo,
>>
>> I've been in contact jezdez - one of the Jazzband roadies to discuss this 
>> in the #jazzband IRC channel.
>>
>> Jazzband exists to lower the barrier of entry for maintenance and remove 
>> the single-developer-problem that we currently have. It's not a guarantee 
>> of maintenance but it should help simplify releases and would give us the 
>> opportunity to get more eyes on the upgrade to 2.2 that we so drastically 
>> need.
>>
>> As a next step he has encouraged us to create an issue 
>>  proposing the 
>> transfer and mention Stephen and any other contributors that may be 
>> interested in helping with the transfer and future maintenance, I expect 
>> you or Stephen may be the best person to do this as you will have the 
>> required level of access.
>>
>> On Thursday, 12 December 2019 23:47:47 UTC, Eduardo Rivas wrote:
>>>
>>> Hi Pete,
>>>
>>>  
>>>
>>> Thanks for bringing this over to the mailing list. I’m one of the 
>>> contributors to Mezzanine and still use it almost daily. I’m glad others 
>>> still want to see the project move forward.
>>>
>>>  
>>>
>>> Do Jazzband or Code Shelter have contributors on standby ready to take 
>>> in projects and perform maintenance tasks? I’m not entirely clear on how 
>>> they work, just want to make sure I understand correctly.
>>>
>>>  
>>>
>>> *From: *Pete Dermott
>>> *Sent: *Tuesday, December 10, 2019 8:24 AM
>>> *To: *Mezzanine Users
>>> *Subject: *[mezzanine-users] Migration to Jazzband / Code Shelter
>>>
>>>  
>>>
>>> Following on from the discussion on GitHub issue #1928 
>>> 
>>>
>>>  
>>>
>>> Throughout 2019 there has been 1 commit to the master Github repo, we 
>>> haven't had a full release since August 2018 and there are a number 
>>> outstanding changes that are waiting to go into a new release. We still 
>>> don't have Django 2 support despite it being released in December 2018 and 
>>> Django 3 is now out and available for development.
>>>
>>>  
>>>
>>> I use Mezzanine a lot in my day to day projects but I don't feel like I 
>>> personally have the skill to take it forward and make it fully compatible 
>>> with the changes to Django and jQuery that are required.
>>>
>>>  
>>>
>>> Basically, I feel that this project needs a bit of help to keep it 
>>> relevant. Thankfully there are maintainer communities in Jazzband 
>>> and Code Shelter  
>>> that may be able to help us. I feel that handing the project over to them 
>>> should at least ensure that active Mezzanine projects are not left exposed 
>>> when 1.11 is deprecated in April 2020.
>>>
>>>  
>>>
>>> Also - just to note - this is in no way mean to denigrate the hard work 
>>> that Stephen and others have done over the years with this project, it 
>>> speaks volumes about the quality of the codebase that Mezzanine is still my 
>>> Django CMS of choice after all this time.
>>>
>>> -- 
>>> 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, sen

[mezzanine-users] Re: Mezzanine beyond Django 1.10

[Wim Feijen]

Hello,

I was wondering what we can do to help in the release of a new stable 
Mezzanine which supports Django 1.11 LTS or Django 2.0?

Unfortunately we work in an environment where stability is of much more 
importance than using a quick leading edge release. 

We are stuck in a situation where dropping Mezzanine is actually being 
considered as an option. I would rather help the open source project 
Mezzanine forward than drop it. So that's why I feel forced to bump my 
question. Apologies for that.

Best regards,

Wim


Op woensdag 10 januari 2018 17:38:07 UTC+1 schreef Wim Feijen:
>
> Hello,
>
> The latest Mezzanine release 4.2.3 support Django up to Django 1.10, which 
> does not receive security updates anymore. See: 
> https://www.djangoproject.com/download/#supported-versions
>
> How can we help to release a new version of Mezzanine which support Django 
> 1.11 LTS or Django 2.0?
>
> Although I love the high quality of development branches, using a 
> development branch (git version) of Mezzanine is not possible for us, 
> because it is not stable enough.
>
> Best regards,
>
> Wim
>
>

-- 
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] Mezzanine beyond Django 1.10

[Wim Feijen]

Hello,

The latest Mezzanine release 4.2.3 support Django up to Django 1.10, which 
does not receive security updates anymore. See: 
https://www.djangoproject.com/download/#supported-versions

How can we help to release a new version of Mezzanine which support Django 
1.11 LTS or Django 2.0?

Although I love the high quality of development branches, using a 
development branch (git version) of Mezzanine is not possible for us, 
because it is not stable enough.

Best regards,

Wim

-- 
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] Forcing Page Link to open in new window

[Wim Feijen]

Hi Christian,

Thanks for your fork and commit! I have difficulties in viewing your 
changes because of all changes in translation files. 

If you want, can you create a new diff and then I will take a look at it?

Best regards,

Wim


On Sunday, 4 September 2016 20:06:55 UTC+2, Christian Wiegand wrote:
>
> Since i had this problem recently, i implemented this functionality for 
> me. The change is available under 
> https://github.com/christianwgd/mezzanine/commit/a94dff7a7cabb864ee14329f571a94e338f47cf7
>
> Maybe someone wants to do a short review. Its no rocket science, but it is 
> my first code change to mezzanine. If it is ok, i could create a PR to 
> merge that to mezzanine.
>
> Christian
>

-- 
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] Re: URL field does not show up in Admin when editing a link

[Wim Feijen]

Hi all,

I ran into the same problem. I find it confusing that we sometimes hide the 
link, the more so when we have trouble explaining what happened.  

My proposal is to just show the url all the time, and point out that: 
"Things might break when you change this. Don't change it unless you know 
what you are doing." in the help_text.

In my case, the end user is smart and knows what he is doing. And urls were 
pointing at the live site in stead of the test site, while still remaining 
hidden so the end user could not solve it.

I would rather give a warning than create limitations.

Let me know if you find this desirable and I will make a pull request when 
I find time.

Wim 


On Wednesday, 15 October 2014 21:02:14 UTC+2, Christopher Vo wrote:
>
> Or perhaps "greyed out" so you can't edit it but at least you know where 
> the link points to. That was the main problem for me; the end user wanted 
> to know what the link was pointing to but it wouldn't even show in the 
> admin.
>
> Christopher Vo
> On Oct 15, 2014 2:15 PM, "Josh Cartmell" > 
> wrote:
>
>> No problem, I think someday it would be nice to update it so there was a 
>> setting somewhere that would toggle this behavior, that way if you really 
>> did know what you were doing and had accidentally set a slug that 
>> overlapped a URL you could fix it without having to mess with the database 
>> directly.
>>
>> Good luck!
>>
>> On Wed, Oct 15, 2014 at 11:19 AM, Christopher Vo > > wrote:
>>
>>> Yes, this seems to be what is happening. It's linked to an existing url 
>>> and so it's preventing its modification.
>>> Now that I think of it, this is a desirable behavior on a production 
>>> site.
>>> Thanks for your help Josh. 
>>>
>>> Christopher Vo
>>>
>>> On Wed, Oct 15, 2014 at 11:14 AM, Josh Cartmell >> > wrote:
>>>
 I'm not sure why I didn't think of this before, but I think I 
 understand what is happening now.  If the slug field matches a url 
 somewhere in a urls.py Mezzanine hides it.  This is to prevent an admin 
 user modifying it, not realizing the slug needs to match the url.

 Does the url you set match an existing url?

 On Wed, Oct 15, 2014 at 10:35 AM, Christopher Vo >>> > wrote:

> And here is where it's happening in the PageAdmin's view methods.
> Apparently it hides the slug field if you have overridden it. 
> I'm not sure why that would make sense.
>
> kwargs["extra_context"].update({
> "hide_delete_link": not content_model.can_delete(request),
> "hide_slug_field": content_model.overridden(),
> })
>
> Christopher Vo
>
> On Wed, Oct 15, 2014 at 10:27 AM, Christopher Vo  > wrote:
>
>> I found where it's happening in the source output:
>>
>> 
>> 
>> /* These are set in PageAdmin's view methods, and 
>> mezzanine.core.admin.SingletonAdmin */
>> .slug {display:none !important;}
>> 
>> 

Re: [mezzanine-users] Blog archive context has English month_name, even on a Dutch site.

[Wim Feijen]

Thanks Stephen, that totally works for me! 

In addition, I was reading through many pages while googling for several 
solutions and I was totally amazed by all the answers you are giving. 
Thanks for all that tremendous amount of work! In Dutch we say: petje af.  


On Wednesday, 27 January 2016 23:39:15 UTC+1, Stephen McDonald wrote:
>
> Thanks for the info - I've fixed it here:
>
>
> https://github.com/stephenmcd/mezzanine/commit/cf7f7eadd138d9635751d2c2825492ef4749b238
>
> On Thu, Jan 28, 2016 at 3:35 AM, Wim Feijen  > wrote:
>
>> Hi, I clarified the subject.
>>
>> I propose to pass the selected month in the blog archives as an integer 
>> to the template to solve the mentioned problem and will commit a pull 
>> request for this.
>>
>> WIm
>>
>> On Wednesday, 23 December 2015 15:43:15 UTC+1, Wim Feijen wrote:
>>>
>>> Hello,
>>>
>>> For my blog archive pages, I like to use a pull-down where the selected 
>>> month is selected. 
>>>
>>> For that, I want to compare the selected year and month - which are in 
>>> the url, for example /blog/archive/2015/12/ and passed as context variables 
>>> into the template - and compare them with the year and month of all the 
>>> months in the archive pull-down.
>>>
>>> For me it gets difficult because the month from the url is converted 
>>> using a dictionary.
>>>
>>> See: 
>>> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/views.py
>>> line 4.  from calendar import month_name
>>> line 38.  month = month_name[int(month)]
>>>
>>> My site is Dutch, but month_name gives me English names. In another 
>>> multilingual site, the English version works fine, but the Dutch site does 
>>> not. Compare:
>>> https://www.roominreturn.nl/en/blog/archive/2015/7/ 
>>> https://www.roominreturn.nl/nl/blog/archive/2015/7/ 
>>>
>>> What would be a proper solution? 
>>>
>>> For me, one solution would be if the blog views passed the selected 
>>> month as an integer into the context. But maybe there are other solutions?
>>>
>>> Currently, I am using in my template:
>>>   
>>> {% with year as selected_year %}
>>> {% with month as selected_month %}
>>> {# YEAR: {{ selected_year }} MONTH: {{ 
>>> selected_month }} for debugging #}
>>> {% block blog_months %}
>>> {% blog_months as months %}
>>> {% if months %}
>>>
>>> >> class="table-title">Nieuwsarchief
>>>
>>> >> id="archive-dropdown">
>>> Kies een 
>>> maand...
>>>
>>> {% for month in months %}
>>>
>>> {% ifchanged 
>>> archive_month.date.year %}
>>> >> disabled="disabled">{{ month.date.year }}
>>> {% endifchanged %}
>>>
>>> >> if month.date|date:"Y" == selected_year and month.date|date:"F" == 
>>> selected_month|lower %} selected="selected" {% endif %}>
>>> {{ month.date|date:"F" }} 
>>>  ({{ month.post_count }})
>>>
>>> 
>>> 
>>>
>>> {% endfor %}
>>>
>>> 
>>>
>>> {% endif %}
>>> {% endblock %}
>>> {% endwith %}
>>> {% endwith %}
>>> 
>>>
>>>
>>> Thanks for your help!
>>>
>> -- 
>> 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.
>>
>
>
>
> -- 
> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Blog archive context has English month_name, even on a Dutch site.

[Wim Feijen]

Hi, I clarified the subject.

I propose to pass the selected month in the blog archives as an integer to 
the template to solve the mentioned problem and will commit a pull request 
for this.

WIm

On Wednesday, 23 December 2015 15:43:15 UTC+1, Wim Feijen wrote:
>
> Hello,
>
> For my blog archive pages, I like to use a pull-down where the selected 
> month is selected. 
>
> For that, I want to compare the selected year and month - which are in the 
> url, for example /blog/archive/2015/12/ and passed as context variables 
> into the template - and compare them with the year and month of all the 
> months in the archive pull-down.
>
> For me it gets difficult because the month from the url is converted using 
> a dictionary.
>
> See: 
> https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/views.py
> line 4.  from calendar import month_name
> line 38.  month = month_name[int(month)]
>
> My site is Dutch, but month_name gives me English names. In another 
> multilingual site, the English version works fine, but the Dutch site does 
> not. Compare:
> https://www.roominreturn.nl/en/blog/archive/2015/7/ 
> https://www.roominreturn.nl/nl/blog/archive/2015/7/ 
>
> What would be a proper solution? 
>
> For me, one solution would be if the blog views passed the selected month 
> as an integer into the context. But maybe there are other solutions?
>
> Currently, I am using in my template:
>   
> {% with year as selected_year %}
> {% with month as selected_month %}
> {# YEAR: {{ selected_year }} MONTH: {{ 
> selected_month }} for debugging #}
> {% block blog_months %}
> {% blog_months as months %}
> {% if months %}
>
> Nieuwsarchief
>
>  id="archive-dropdown">
> Kies een 
> maand...
>
> {% for month in months %}
>
> {% ifchanged 
> archive_month.date.year %}
>  disabled="disabled">{{ month.date.year }}
> {% endifchanged %}
>
>  if month.date|date:"Y" == selected_year and month.date|date:"F" == 
> selected_month|lower %} selected="selected" {% endif %}>
> {{ month.date|date:"F" }}  ({{ 
> month.post_count }})
>
> 
> 
>
> {% endfor %}
>
> 
>
> {% endif %}
> {% endblock %}
> {% endwith %}
> {% endwith %}
> 
>
>
> Thanks for your help!
>

-- 
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] blog month_name

[Wim Feijen]

Hello,

For my blog archive pages, I like to use a pull-down where the selected 
month is selected. 

For that, I want to compare the selected year and month - which are in the 
url, for example /blog/archive/2015/12/ and passed as context variables 
into the template - and compare them with the year and month of all the 
months in the archive pull-down.

For me it gets difficult because the month from the url is converted using 
a dictionary.

See: https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/blog/views.py
line 4.  from calendar import month_name
line 38.  month = month_name[int(month)]

My site is Dutch, but month_name gives me English names. In another 
multilingual site, the English version works fine, but the Dutch site does 
not. Compare:
https://www.roominreturn.nl/en/blog/archive/2015/7/ 
https://www.roominreturn.nl/nl/blog/archive/2015/7/ 

What would be a proper solution? 

For me, one solution would be if the blog views passed the selected month 
as an integer into the context. But maybe there are other solutions?

Currently, I am using in my template:
  
{% with year as selected_year %}
{% with month as selected_month %}
{# YEAR: {{ selected_year }} MONTH: {{ 
selected_month }} for debugging #}
{% block blog_months %}
{% blog_months as months %}
{% if months %}

Nieuwsarchief


Kies een 
maand...

{% for month in months %}

{% ifchanged 
archive_month.date.year %}
{{ month.date.year }}
{% endifchanged %}


{{ month.date|date:"F" }}  ({{ 
month.post_count }})




{% endfor %}



{% endif %}
{% endblock %}
{% endwith %}
{% endwith %}



Thanks for your help!

-- 
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] Inlines javascript does not seem to work

[Wim Feijen]

Thanks Eduardo!

That solves it. :)

On 21 December 2015 at 15:40, Eduardo Rivas  wrote:

> Sorry, to be clear, the BookInline class should subclass
> TabularDynamicInlineAdmin instead of admin.TabularInline.
>
>
> --
> 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/S9-9W9vzTK4/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/d/optout.
>



-- 
Wim Feijen
Eigenaar

Tussen kerst en oud en nieuw zijn wij gesloten.

Go2People Websites
Nieuwe Herengracht 49
1011 RN Amsterdam

T:  020 737 0378 / 06  3316
W: http://go2people-websites.nl

-- 
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] Re: TinyMCE4 - Problems on deployed site

[Wim Feijen]

Actually, it is insecure to have part of your website https secured and 
part not, because cookies can easily be intercepted. So it's always a good 
idea to secure the whole site.

On Tuesday, 10 November 2015 23:02:47 UTC+1, iain ross wrote:
>
> On Wed, 11 Nov 2015 07:07:29 +1030 
> Danny > wrote: 
>
> > My overall solution was to make my entire site HTTPS... not elegant, 
> > I know, but probably better in this security conscious world :) 
>
> and don't forget ranking: 
>
> http://googlewebmastercentral.blogspot.co.uk/2014/08/https-as-ranking-signal.html
>  
>
> -- 
>
> Regards, 
> Iain. 
>

-- 
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] Is it possible to replace an image?

[Wim Feijen]

In the media library, I can edit a filename. Is it possible to replace an 
image, keeping all underlying links intact, so the image gets updated in 
all pages where I am using it? 

-- 
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] Mezzanine 3.2

[Wim Feijen]

Hello,

First of all, congratulations to the core team! Nice that it is official 
now. :) Great to see a one-man project evolve and thanks for all your 
contributions! 

Second, I'm looking forward to using Mezzanine 3.2. Like Django, can I 
install a release candidate which I can try? Or should I use master?

Thanks for your help.

Wim


-- 
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] Adding a featured_image to a Page

[Wim Feijen]

Hello,

I'd like to add a featured_image to the Page model. 

Following the advice on 
http://mezzanine.jupo.org/docs/content-architecture.html#creating-custom-content-types,
 
I created my own Page model.

in models.py:

from django.db import models
from mezzanine.pages.models import Page
from mezzanine.core.fields import FileField


class FeaturedPage(Page):
featured_image = FileField(blank=True, null=True, upload_to=
'featured_images')




in admin.py:

from django.contrib import admin
from mezzanine.pages.admin import PageAdmin
from .models import FeaturedPage


admin.site.register(FeaturedPage, PageAdmin)



Now when I want to add a FeaturedPage, the richtextfield content field 
disappears from the admin! Why is that? If you have any idea, please let me 
know.

I'm using 
Django==1.6.6
Mezzanine==3.1.10



Thanks for your help!

-- 
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] Media library alt tags?

[Wim Feijen]

Hi Stephen,

Thanks for publishing mezzanine and maintaining it!

I probably don't understand what you are saying. Did you say that the media 
gallery is just a (really nice) wrapper around the file system and that it 
is different with galleries? 

For SEO reasons I'd like to use alt tags for all my images. Is there a(n 
easy) way to do that and how?

Thanks for your suggestions,

Wim



On Monday, 3 February 2014 00:07:50 UTC+1, Stephen McDonald wrote:
>
> Hi Ross,
>
> The media library simply wraps the file system - there's no database 
> behind it, and subsequently nowhere to store additional meta data like you 
> describe.
>
> If you look at the gallery page type, you'll see it implements its 
> collection of images using the database, with a field for the file (backed 
> by the media library) and a field for the description, which is the 
> approach you're looking for.
>
>
> On Mon, Feb 3, 2014 at 5:15 AM, Ross Laird  > wrote:
>
>> I try to be standards-compliant whenever possible. The W3 spec 
>>  for images requires an alt 
>> tag for most images: "When an a element that creates a hyperlink, or a 
>> button element, has no textual content but contains one or more images, the 
>> alt attributes must contain text that together convey the purpose of the 
>> link or button." As far as I can tell, Mezzanine's media library does not 
>> provide a way to add alt tags to images, so if I want to use those images 
>> in sliders and the like, I can't provide alt text for them (for use in a 
>> caption, for example). I can, of course, add alt tags directly to images 
>> used in templates, but this is not a flexible solution.
>>
>> Or maybe I'm just missing something really obvious. Is there an alt tag 
>> function somewhere in Mezzanine?
>>
>> -- 
>> 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.
>>
>
>
>
> -- 
> 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 mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Featured images for pages

[Wim Feijen]

Hi,

I really like being able to use featured images in a flash with the 
BLOG_USE_FEATURED_IMAGE setting! 

Personally, I would also enjoy having a setting like 
PAGE_USE_FEATURED_IMAGE, which would do the same for pages and adds a 
featured image there. 

Would that be an idea?

Wim

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