Thanks so much!! now I know where to look..
BTW Shouldn't both reportlab and pillow be in the requirements txt file??
They were the only two I needed to download separately..
On Wednesday, February 26, 2014 5:42:18 PM UTC-6, Danny S wrote:
The error is coming from sx/pisa3/__init__.py, line
Ah so its an add-on or purely custom. I thought this was a feature that is
already built in to Mez. If it isn't, it should. So when I am editing pages
I can edit a smaller chunk rather than the whole page. Plus the vanilla
editor makes a mess of the html so you easily get lost in the markup.
So after working with the django sites framework, I see how easy it is to
have multiple sites running Mezzanine in one instance. It works great if
you have a multiple language site and don't want to use the
internationalization built into Django and instead create a separate site
where the
This docs PR doesn't have a working example for localhost, but is at least an
attempt at documenting the process for HOST_THEMES:
https://github.com/stephenmcd/mezzanine/pull/961. Comments welcome on that PR.
Jeff
On Feb 27, 2014, at 2:18 PM, Radomir Wojcik rado...@cldssinc.com wrote:
So
I was already past that point, the docs help, I relied on peoples examples
from the mailing list. If I post a non-working example would someone be
able to fork it, fix it , tell me why it wasn't working? The doc here also
doesn't talk about base.html , Both of my themes have different
I confirm that this solved the same problem. More info here:
http://gunicorn-docs.readthedocs.org/en/latest/configure.html#configuration-file
It's been fixed two months ago:
https://github.com/stephenmcd/mezzanine/issues/870
Il giorno giovedì 16 gennaio 2014 12:35:58 UTC+1, Klamann, Norbert ha
It's really went written Jeff, thanks a lot. Will definitely merge in soon.
On Fri, Feb 28, 2014 at 8:19 AM, Jeff Pittman geoj...@me.com wrote:
This docs PR doesn't have a working example for localhost, but is at least
an attempt at documenting the process for HOST_THEMES:
Thanks Federico, I never stopped to realise that fix matched up with that
issue - good to know!
On Fri, Feb 28, 2014 at 10:42 AM, Federico Bruni fedel...@gmail.com wrote:
I confirm that this solved the same problem. More info here:
2014-02-26 13:18 GMT+01:00 our...@gmail.com:
Yes, I think fab create has to restart from the beginning. One more
advice, be sure that all Fabric settings in settings.py are completed (or
as much as you can). I tried to leave the field REPO_URL empty and fab
deploy didn't work until I set a
If the commit or the pull request message contains a reference to the issue
#number, then they will be linked each other. See:
https://help.github.com/articles/closing-issues-via-commit-messages
2014-02-28 1:03 GMT+01:00 Stephen McDonald st...@jupo.org:
Thanks Federico, I never stopped to
Tried to used the fix suggested but still getting the same error (FWIW I
never did get the message version 2.2 or higher needed),, so I'm suspecting
pisa is a no go with Python 3 and that it is simply failing??
Posted question in the xhtml2pdf group, linked below:
I'd say so, Stephen, at least until cartridge can be updated to use
xhtml2pdf instead of pisa (which seems to be an abandoned project).
At the moment, there's no dependency on reportlab in cartridge (only pisa),
but because pisa doesn't have reportlab in its own dependency list, it
couldn't hurt
Tom's pointed out in a private email that he's working with Python 3, and
reportlab 2.7 won't work on Python 3.
I'm still using python 2.7, so using an older reportlab is fine for me.
Should I still go ahead with the change to cartridge's setup.py (adding
reportlab==2.7 as a dependency) or
13 matches
Mail list logo
