Hi Karim,
If you search the mailing list for "character encoding", you will find this
topic covered in detail. It sounds like the database locale is off. When I
first encountered this problem, the Mezzanine `fabfile.py` was my guide to
fixing it.
-ken
On Fri, Jun 30, 2017 at 3:52 PM, Karim wro
Hello, I got a couple of exceptions on production caused by Unicode, but I
have no idea how to fix without edit the blog. Is related to the LANG?
(actually 'it_IT')
Here the traceback:
Internal Server Error: /blog/klaipėdoj-gyvena-mergaitė-vardu-dolce-gabana/
UnicodeEncodeError at /blog/klaipė
I have injected extra text field
Settins.py
EXTRA_MODEL_FIELDS = (
(
"mezzanine.blog.models.BlogPost.opis",
"mezzanine.core.fields.RichTextField",
("opis",),
{"blank": True},
),
)
my translation.py looks like this:
from modeltranslation.tran
Thanks Eduardo, that sounds like a good approach.
On 30 June 2017 at 17:14, Eduardo Rivas wrote:
> Hey Roger. Here's how I've done it in the past:
>
> - Create a Django app in your project to hold your static files and
> templates (I name it "theme" since it holds everything related to the
> vis
Hey Roger. Here's how I've done it in the past:
- Create a Django app in your project to hold your static files and
templates (I name it "theme" since it holds everything related to the
visual styles of the site).
- Inside theme/static/ setup your frontend tooling. I use Webpack to
compile S
Any suggestions for an efficient methodology to deal with css vendor
prefixes?
As this will probably tie in, anyone got a nice strategy for using SASS? (
I would really love to use Foundation6 with mezzanine, I find the code much
more semantic than bootstrap and way quicker to code)( I know I c
