Just corrected a few things for the front-end language selector and pushed
an updated version of cartridge as well.
I tried the TabbedExternalJqueryTranslationAdmin class instead of
TranslationAdmin and couldn’t get the meta tag area to show. Does it happen
for you too? Or is there something
Hey James, the comment functionality is baked into Mezzanine (part of
mezzanine.generic), but comments are only present on the blog by default.
As long as you don't add it to anything you create there won't be any
outward facing comments on the site.
Since you've also unregistered them from the
Thanks Josh (want to try and make sure I'm using best practices) also I see
I have your website open in another tab :)
It bugs me it's not a simple case of just removing it like with the blog
app but oh well. I also don't like having things present if they don't need
to be ( hence a loose
Any pointer?
I don't want to destroy the project and re-deploy from scratch.
Il giorno mercoledì 4 giugno 2014 12:05:17 UTC+2, Federico Bruni ha scritto:
Hi all
I have a problem with the database migration during a deployment.
I have changed only the LANGUAGE_CODE variable in settings.py
Hey Federico, shot in the dark here, but was South definitely installed
when you deployed in the first place? I'm wondering if some of the records
of migrations are missing.
I could be totally off and I'm not sure how changing the language code
would affect the db.
On Tue, Jun 10, 2014 at
Hey Josh
no, South was not installed. I thought it was a dependency of Mezzanine,
but I see that it's optional:
https://pypi.python.org/pypi/Mezzanine/3.1.5
I've installed it, added it to the requirements and pushed to the
repository, but I'm getting the same error.
I've deployed from scratch.
I've just had this same problem and the command above didn't work at first.
It worked when I switched the local to english:
export LANG=C
pg_restore -c -d DATABASE FILE
Maybe it's just a coincidence?
2014-03-27 20:30 GMT+01:00 Federico Bruni fedel...@gmail.com:
I've resolved following the
Hi Ken,
Thank you. That helps a lot. It is now working perfectly.
Kind regards,
Jane
On Monday, 9 June 2014 13:55:02 UTC+1, green wrote:
Not sure what went wrong and where to start. I have
Cartridge==0.9.3
Django==1.6.4
Mezzanine==3.1.4
Problem: When click on product image in a full
Hi Danny,
My problem with just removing from templates ... it's just visually not
available but the code possibly still exists to process the comments or am
I wrong?
I could have tweaked things with a display:none bit of css to just remove
it visually from the admin menu but I'm still not
Thanks for the interest guys. Ibn, I recommend you take a look at the
Webfaction docs and read the fabfile to have an idea of what it does. Some
knowledge of Postgres and Git will also be useful. Finally, when you
deploy, keep in mind many settings have default values in fabsettings.py,
so
On Sun, Jun 8, 2014 at 8:18 AM, Ahmad Khayyat akhay...@gmail.com wrote:
There is one issue with the current approach. The exception message is
shown using Django messages, which displays the message at the top of the
page. If the page tree is scrolled down, the user will see that the illegal
11 matches
Mail list logo
