[mezzanine-users] Re: Proposal: can_move permission (was: page_move signals)
Is there no interest in this feature? I kinda need it right now. Can we decide one way or the other? The code is already there. Calling can_move() during page creation is separated into its own commit. Pull request: https://bitbucket.org/stephenmcd/mezzanine/pull-request/63/ -- 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: Proposal: can_move permission (was: page_move signals)
I'm for it given a few outstanding things: - If this only occurs in the move view now, I don't think we need the three-tuple return from can_move. Let's just have the api be raising a PageMoveException that can include the error message in it. - Need to document this (there's already a Page permissions section). - Need to include some tests. On Fri, Jun 6, 2014 at 9:05 PM, Ahmad Khayyat akhay...@gmail.com wrote: Is there no interest in this feature? I kinda need it right now. Can we decide one way or the other? The code is already there. Calling can_move() during page creation is separated into its own commit. Pull request: https://bitbucket.org/stephenmcd/mezzanine/pull-request/63/ -- 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. -- 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] Re: Amazon s3 storage backed, upload image to blog from admin HTTP 500 on demo site.
Hi Brad, Thanks again for the reply. I tried again with these settings (see https://github.com/fpghost/mezzdemo/blob/master/settings.py), and still the exact same error for me. This is proving stubborn indeed! I should note I'm working on the local dev server at the moment, so for my domain I just tried a few combos of localhost. Not sure if that is the right way. I'm curious though, is this working for anyone else? After all this is the out of box mezzanine install here, so it is very easy to reproduce (rip my requirements.txt and settings.py into mezzdemo dir): mkdir mezzdemo; cd mezzdemo virtualenv --no-site-packages mezzdemoenv source mezzdemoenv/bin/activate pip install -r requirements.txt cd ..; mezzanine-project mezzdemo python manage.py createdb python manage.py collectstatic The only thing you need to do is set your own env variables for aws secret key and id, and set own bucket_name in settings.py. Then try: python manage.py runserver and attempt to upload a picture to the media_lib... Does this work for others? -- 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: can't add mezzanine_agenda
if anyone interested - got this running by changing urls add to this: (^events/, include(mezzanine_agenda.urls)), thx rb On Wednesday, May 28, 2014 4:26:09 PM UTC-4, roland balint wrote: trying to get mezzanine_agenda working and it fails at this instruction; can anyone help? Add (^%s/ settings.EVENT_SLUG, include(mezzanine_agenda.urls)) to your urls.py thx rb -- 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] Attaching TinyMCE, with project-wide custom config, to the text field of a free-standing model.
This post shows a way of doing the above, but does end with a question.
I customised the TinyMCE HTML editor in the admins of the mezzanine pages
and blog posts. I did this by making a copy of the tinymce_setup.js into my
project, customising the copy, then pointing at it using the mezzanine
setting TINYMCE_SETUP_JS. This worked fine.
I added a new app to my project. It has a model which is unrelated to any
of the mezzanine page types. I wanted a text field in this model to have
tinyMCE attached to it. I was happy that timyMCE should behave exactly the
same as the pages and blog post content fields.
*How not to do it*
Neither of these worked:
1. Setting the CSS class name of the text field to mceEditor, in my
app's admin.py.
2. In the custom tinyMCE initialisation code, changing mode to exact
and adding an elements argument containing the CSS ID of my text field.
The problem seemed to be that the custom init code simply did not run for
my app/model.
*A way of doing it*
In my app's admin.py
from django.contrib import admin
from django.db import models
from mezzanine.core.forms import TinyMceWidget
from .models import MyModel
class MyModelAdmin(admin.ModelAdmin):
formfield_overrides = { models.TextField: {'widget' : TinyMceWidget}, }
admin.site.register(MyModel, StaffMemberAdmin)
No changes to the custom TinyMCE init code were needed.
*The Question*
I now have another app and model with a text field to which I need to
attach TinyMCE. However, this time I need to really restrict what TinyMCE
is allowed to do (so the client cannot mess the site up, sigh) so this
instance will need to run a different initialisation function i.e. it is
now app-specific rather than project-wide.
Can anybody suggest a way of doing this which won't cause deployment or
maintenance problems?
--
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: can't add mezzanine_agenda
What is the value of EVENT_SLUG in your settings? What error message did you get? (“^%s/“ settings.EVENT_SLUG, include(“mezzanine_agenda.urls”)) The above has the string-substitution operator missing between “^%s/“ and settings. On Fri, Jun 6, 2014 at 3:12 PM, roland balint rabal...@gmail.com wrote: if anyone interested - got this running by changing urls add to this: (^events/, include(mezzanine_agenda.urls)), thx rb On Wednesday, May 28, 2014 4:26:09 PM UTC-4, roland balint wrote: trying to get mezzanine_agenda working and it fails at this instruction; can anyone help? Add (^%s/ settings.EVENT_SLUG, include(mezzanine_agenda.urls)) to your urls.py thx rb -- 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: Saw that I should post my site here.
Maybe I'm just too old but I can't read the cover page hardly at all on a 24 monitor.. Just saying.. On Thursday, June 5, 2014 11:16:46 PM UTC-5, nathan wrote: My site(s) are mezzanine/django sites. The one that is pretty well polished is http://www.brokensoundbooking.com . I am making some changes that I think will be fantastic including a thumbnailable band photo for navigation menus. It is in my new Band page which inherits from the regular mezzanine page model. -Nate Thanks Stephen, Josh and all the great contributers. -- 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: Saw that I should post my site here.
I'll second Tom's mention of readability. Never use a texture under copy. The left and right sidebars require too much effort to read. Congratulations on getting the site up. On Fri, Jun 6, 2014 at 4:58 PM, Tom Brander tombran...@gmail.com wrote: Maybe I'm just too old but I can't read the cover page hardly at all on a 24 monitor.. Just saying.. On Thursday, June 5, 2014 11:16:46 PM UTC-5, nathan wrote: My site(s) are mezzanine/django sites. The one that is pretty well polished is http://www.brokensoundbooking.com . I am making some changes that I think will be fantastic including a thumbnailable band photo for navigation menus. It is in my new Band page which inherits from the regular mezzanine page model. -Nate Thanks Stephen, Josh and all the great contributers. -- 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] Attaching TinyMCE, with project-wide custom config, to the text field of a free-standing model.
I'm curious about the same thing. How to set the TinyMCE options either on
a per-field basis, or if necessary, by creating a custom field type. But
I'm guessing that even if I did that, it would be difficult to mix the
TinyMCE options for different fields on the same page... - John
On Fri, Jun 6, 2014 at 9:56 AM, Gary Ian Robertson g...@aardweb.co.uk
wrote:
This post shows a way of doing the above, but does end with a question.
I customised the TinyMCE HTML editor in the admins of the mezzanine pages
and blog posts. I did this by making a copy of the tinymce_setup.js into my
project, customising the copy, then pointing at it using the mezzanine
setting TINYMCE_SETUP_JS. This worked fine.
I added a new app to my project. It has a model which is unrelated to any
of the mezzanine page types. I wanted a text field in this model to have
tinyMCE attached to it. I was happy that timyMCE should behave exactly the
same as the pages and blog post content fields.
*How not to do it*
Neither of these worked:
1. Setting the CSS class name of the text field to mceEditor, in my
app's admin.py.
2. In the custom tinyMCE initialisation code, changing mode to exact
and adding an elements argument containing the CSS ID of my text field.
The problem seemed to be that the custom init code simply did not run for
my app/model.
*A way of doing it*
In my app's admin.py
from django.contrib import admin
from django.db import models
from mezzanine.core.forms import TinyMceWidget
from .models import MyModel
class MyModelAdmin(admin.ModelAdmin):
formfield_overrides = { models.TextField: {'widget' : TinyMceWidget},
}
admin.site.register(MyModel, StaffMemberAdmin)
No changes to the custom TinyMCE init code were needed.
*The Question*
I now have another app and model with a text field to which I need to
attach TinyMCE. However, this time I need to really restrict what TinyMCE
is allowed to do (so the client cannot mess the site up, sigh) so this
instance will need to run a different initialisation function i.e. it is
now app-specific rather than project-wide.
Can anybody suggest a way of doing this which won't cause deployment or
maintenance problems?
--
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] Show featured images with recent posts in filter_panel.html
Hello all,
Has anyone tried including featured images with the default recent posts
block? If so, I'd love to see how this is done.
Something like this:
{% block blog_recent_posts %}
{% blog_recent_posts 5 as recent_posts %}
{% if recent_posts %}
h3{% trans Recent Posts %}/h3
ul class=list-unstyled recent-posts
{% for recent_post in recent_posts %}
liimg src={{ MEDIA_URL }}{% thumbnail recent_post.featured_image 10 10
%}a href={{ recent_post.get_absolute_url }}
{{ recent_post.title }}/a/li
{% endfor %}
/ul
{% endif %}
{% endblock %}
--
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: modeltranslations - round 2
Hey everybody. I've been trying out Mathias master branch and everything is working smoothly. As I said, I'm also exploring ways to enable toggling translation fields in the Admin. Turns out Model Translation (MT) provides two admin classes (docs https://django-modeltranslation.readthedocs.org/en/latest/admin.html#tabbed-translation-fields-admin-classes) to include the required static resources for this purpose: TabbedTranslationAdmin and TabbedExternalJqueryTranslationAdmin. The first one seems to fail as it uses Django's jQuery, but the second one works as expected (though it looks kinda ugly in Grappelli) by using external jQuery resources. I have a couple of questions at this point: 1. Should we use these classes or create our own (considering Mezzanine already includes jQuery and jQuery UI)? 2. Should we create a toggle for each field (as MT does), or just a global toggle to hide/show all fields of a specified language? I favor the second option, as giving each field it's own toggle seems overly messy and confusing for the end user. Hope to hear from you soon. BTW, if you want to try out MT's default implementation, simply replace all occurrences of TranslationAdmin with TabbedExternalJqueryTranslationAdmin in mezzanine.core.admin. -- 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: Saw that I should post my site here.
Nice look with very, very poor readbility :/ On Friday, June 6, 2014 12:16:46 AM UTC-4, nathan wrote: My site(s) are mezzanine/django sites. The one that is pretty well polished is http://www.brokensoundbooking.com . I am making some changes that I think will be fantastic including a thumbnailable band photo for navigation menus. It is in my new Band page which inherits from the regular mezzanine page model. -Nate Thanks Stephen, Josh and all the great contributers. -- 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: modeltranslations - round 2
I tried Mathias branch so I could give feedback but couldn't create a project: http://hastebin.com/acasezifok.vhdl At a glance I tried re-ordering INSTALLED_APPS but that didn't resolve it. On Sat, Jun 7, 2014 at 10:26 AM, Eduardo Rivas jerivasmel...@gmail.com wrote: Hey everybody. I've been trying out Mathias master branch and everything is working smoothly. As I said, I'm also exploring ways to enable toggling translation fields in the Admin. Turns out Model Translation (MT) provides two admin classes (docs https://django-modeltranslation.readthedocs.org/en/latest/admin.html#tabbed-translation-fields-admin-classes) to include the required static resources for this purpose: TabbedTranslationAdmin and TabbedExternalJqueryTranslationAdmin. The first one seems to fail as it uses Django's jQuery, but the second one works as expected (though it looks kinda ugly in Grappelli) by using external jQuery resources. I have a couple of questions at this point: 1. Should we use these classes or create our own (considering Mezzanine already includes jQuery and jQuery UI)? 2. Should we create a toggle for each field (as MT does), or just a global toggle to hide/show all fields of a specified language? I favor the second option, as giving each field it's own toggle seems overly messy and confusing for the end user. Hope to hear from you soon. BTW, if you want to try out MT's default implementation, simply replace all occurrences of TranslationAdmin with TabbedExternalJqueryTranslationAdmin in mezzanine.core.admin. -- 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. -- 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] Re: modeltranslations - round 2
Odd, I just created a project without issue. This is my venv: Django==1.6.5 Mezzanine==3.1.3 #From Mathias' branch Pillow==2.4.0 South==0.8.4 argparse==1.2.1 bleach==1.4 django-debug-toolbar==1.2.1 django-modeltranslation==0.7.3 filebrowser-safe==0.3.3 future==0.9.0 grappelli-safe==0.3.10 html5lib==0.999 oauthlib==0.6.1 psycopg2==2.5.3 pytz==2014.4 requests==2.3.0 requests-oauthlib==0.4.0 six==1.6.1 sqlparse==0.1.11 tzlocal==1.0 wsgiref==0.1.2 I ran mezzanine-project and createdb --noinput. Have you done any other changes to settings? -- 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: modeltranslations - round 2
Real odd, works fine for me now and no matter what I try I can't reproduce the error I had. On Sat, Jun 7, 2014 at 2:09 PM, Eduardo Rivas jerivasmel...@gmail.com wrote: Odd, I just created a project without issue. This is my venv: Django==1.6.5 Mezzanine==3.1.3 #From Mathias' branch Pillow==2.4.0 South==0.8.4 argparse==1.2.1 bleach==1.4 django-debug-toolbar==1.2.1 django-modeltranslation==0.7.3 filebrowser-safe==0.3.3 future==0.9.0 grappelli-safe==0.3.10 html5lib==0.999 oauthlib==0.6.1 psycopg2==2.5.3 pytz==2014.4 requests==2.3.0 requests-oauthlib==0.4.0 six==1.6.1 sqlparse==0.1.11 tzlocal==1.0 wsgiref==0.1.2 I ran mezzanine-project and createdb --noinput. Have you done any other changes to settings? -- 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. -- 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.
