Well it is of course personal preference. I used this feature quite a lot
for a Mezzanine based blog. I liked to have a predefined classes dropdown
in my theme that a user can select with no knowledge of HTML (e.g.
Right-aligned Captioned Image, Left-aligned Captioned Image), and I
like the
In previous versions of Mezzanine there was an Advanced Tab when the user
clicked Insert/Edit image in a blog post. This tab allowed the user to
add custom classes, styles, borders and alignment. It seems to be
completely missing with the new Mezzanine and TinyMCE 4.
Is it just a matter of
Well re the How To part of my question, it is just a matter of adding
image_advtab: true, to the tinymce_init.js file copied to your theme. But
I still wonder if this is the intended default for Mezzanine. Surely most
people would prefer the advanced tab on by default? Also the advanced tab
I finally got around to upgrading this project to mezz4 and the new
tinymce4. However, the same problem still occurs with django-compressor and
the footer_scripts.html..Everything works if this include is outside of
the compress block, but if you put it in the compress block you see 404s
I get how to do this on a normal page, but I'm still struggling to see how
to do this in the Mezz admin. Which views/templates should I be looking at
in order to wrap the code that generates the tabular inlines in a {%
pagination_for ... %} etc
On Wednesday, 1 July 2015 00:33:03 UTC+7, Lee H
In tinymce it's easy to add a link to an existing blog post by just adding
a link then selecting Link list, and picking the blog post from the list.
I believe this has a number of advantages as the link is not hard coded.
Nevertheless, I like to use pagedown for a blog with lots of code on it,
The template block for related posts in the blog detail template has `for
post in blog_post.related_posts.all`, shouldn't it be
`for post in blog_post.related_posts.published` (or rather published for
that user...)?
The way things are now, if a related post is unpublished it still gets
linked
Many thanks Josh, that's very helpful!
--
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
After killing myself to try and work out what throws this bad request (400)
error when filebrowser-safe is installed and when MEDIA_ROOT is set to non
''. I finally (through blood sweat and tears), worked out that it comes
from the safe_join function of the django-storages s3boto.py. Because I
One option is just to `pip uninstall filebrowser-safe`, then Mezzanine
reverts back to the usual Django file upload (no need to change settings).
Of course then you can't manage the media library, only upload, but it's
not slow at least. Can anyone confirm if the bottlebeck is due to the
Just another note: if filebrowser-safe is uninstalled this bad request 400
does not occur, regardless if MEDIA_ROOT is set to some local fs, or empty,
so I guess it must be a problem with filebrowser when MEDIA_ROOT is
something other than ' ', and s3 storages being used.
--
You received this
Did anyone find a fix for this? I'm doing exactly the same thing with the
S3BotoStorageMixin, and can confirm the media browsing is cripplingly slow.
It often just times out completely.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To
###
### STORAGE ##
###
# The custom storage just allows definition of different 'locations'
so media goes in media/ static goes in /static
# within the bucket. Otherwise same as S3 boto
There is one other simpler way to get this working
MEDIA_ROOT = ''# stops django throwing bad request 400 in admin
when looking at blogpost detail
then thumbnails will attempt to temporarily write to the local filesystem
in the dir 'uploads' relative the point of execuation, so if
I have something of a dilemma. On my production server I get the infinitely
unhelpful message of Bad Request (400), whenever I try to access the
detail of a BlogPost in the admin.
This occurs wether DEBUG is True/False. It doesn't occur when viewing a
BlogPost on the regular site, whether
I find that if I put the `{% include includes/footer_scripts.html %}`
within the django-compressor `{% compress js %}` block, I get quite a few
404s.
These are for plugins that tinymce wants to use, e.g.
`plugins/fullscreen/editor_plugin.js`.
The problem seems to be that with compression on
On one of my pages I have a model called MapPlace (it's basically just a
place name and some geo coords), I add it to the admin as an inline
of the page like
from mezzanine.core.admin import TabularDynamicInlineAdmin,
class MapPlaceInline(TabularDynamicInlineAdmin):
model =
*Background*
I created a multilingual site theme for mezzanine using the new
multi-lingual support.
I had to do two things:
1) Add translations.py file to the theme app, which defined translations
for my custom page models that subclass Mezzanine pages.
2) Split my theme app into two apps:
Thanks Mathias,
I think it must have been using the old ordering of INSTALLED_APPS, since
my settings file came from pre-upgrade Mezzanie. On a clean Mezzanine, I no
longer got the error.
--
You received this message because you are subscribed to the Google Groups
Mezzanine Users group.
To
Hey Eduardo,
Many thanks for the reply. Yes, you are right, using the django-newsletter
development branch from github (which has upgrades for the newer django
migrations without south) things worked, and this error no longer occurred.
--
You received this message because you are
Thanks for the reply Eduardo
I upgraded to the master branch, pip install
git+https://github.com/stephenmcd/mezzanine.git, (which also upgraded
django to 1.8), and I now get the error:
Traceback (most recent call last):
File manage.py, line 29, in module
I want to use the Mezzanine multilingual site feature, so I can have
different form labels and rich text content depending on whether my site is
the en or fr version.
I installed django-modeltranslation and added modeltranslation to my
INSTALLED_APPS, also setting USE_MODELTRANSLATION = True,
Hi,
As far as a I can see, the tinyMCE default editor does not provide a way to
add captions to images embedded in a blog post? (the description/title are
there, but not a caption field).
Are captions really missing or am I being blind? Seems pretty basic
functionality...
If they are missing,
In `editable.css` there is
.editable-form p {
.
.
line-height: 0!important;
}
This means when the user clicks to edit inline say a blog post in which the
content is formatted using p tags, the
text appears squashed up in the preview pop-up window.
What is the logic behind setting
Hi Josh,
Yes maybe it could be done with plain old CSS...I'll have a think.
In the meantime I wrote the following filter:
@register.filter(name='comment_level')
def
comment_level(comment):
I wanted to build a custom Page that incorporates a form, but also has some
other things that can be tweaked (e.g. a section heading), something like:
from mezzanine.forms.models import Form
class MyFormPage(Form):
secheading = models.CharField(max_length=200,
help_text='A heading on
Thanks for the reply Abhinav, I appreciate it.
By use existing form app logic, you essentially mean I just copypaste
from the Form model in the Mezzanine source, only adding some extra fields
myself?
Field injection looks promising, I'll have a good read.
Upto now, I've just added a form to
27 matches
Mail list logo
