I made some progress on understanding this, but haven't quite gotten past
the problem. One thing I learned was that I mixed up the use of the
STATIC_ROOT and STATIC_URL, but fixing it didn't seem to do much.
Here are what appear to be the relevant configs.
local_settings.py:
STATIC_URL =
You could possibly use a templatetag, but if you have a working solution
now I wouldn't worry too much about it
On Thu, Mar 20, 2014 at 3:30 PM, laperl japo...@gmail.com wrote:
Hello,
finally I found the solution using context processors. Are there any
other better form to do that?
Thank
Hello,
I've been trying to get Mezzanine(3.0.9) to work with South but I keep
getting this error:
Exception:
Your project contains migrations that include one of the fields
from mezzanine.generic in its Migration.model dict: possibly
KeywordsField, CommentsField or RatingField.
Hey Karthik, you need to comment things like that out in your own
migrations. Open up each of your migrations files and search for
'mezzanine.generic.fields' and comment out any line that contains it and is
in the models dict.
On Fri, Mar 21, 2014 at 8:58 AM, Karthik Kannan
Hey Josh,
I got what you're saying so I need to modify all files in my migrations
folder? it starts with 0001_initial.py and goes until 0006.
Thanks once again! :)
Karthik
On Friday, March 21, 2014 9:34:45 PM UTC+5:30, Josh Cartmell wrote:
Hey Karthik, you need to comment things like that
Exactly, not Mezzanine's migrations, but any migrations that are specific
to apps in your project =)
On Fri, Mar 21, 2014 at 9:16 AM, Karthik Kannan karthikk@gmail.comwrote:
Hey Josh,
I got what you're saying so I need to modify all files in my migrations
folder? it starts with
I wonder if STATIC_ROOT is the source of your problem. Have you tried
different settings for that, including STATIC_ROOT = /static/ ? I don't
use nginx (I use Apache), but looking at your config, I wonder if the
webserver is looking for static files in a folder that Django appends with
another
I think you're probably right, Ross. I noticed that when we did some
updates to the theme locally and some static files were accidentally
missing, internally the dev server produced a 404 error as evidenced by the
server output. However, on the browser it showed up as a 500 error. I
suspect
Hello,
I'm reading a bit and seems that template tags have better performance than
context processors, because context processors call the database for every
view.
I will try to use this in the future.
Thank you very much for the responses, It helps me a lot!
--
You received this message
Hello,
I am working in injecting fields in an existing model, It seems to work but
I have some questions:
- Is it possible to encapsulate all the code inside de app, not using the
global settings.py EXTRA_MODEL_FIELDS?
- I edited the settings.py and put the code inside EXTRA_MODEL_FIELDS,
Hey Ziwei, you are correct, fabric doesn't currently support python 3. Per
http://docs.fabfile.org/en/1.8/ is works with 2.5-2.7.
On Sun, Mar 16, 2014 at 10:42 PM, Ziwei Zhou ziweiz...@gmail.com wrote:
Hi
Is the current fabfile.py working in python 3 environment? I tried to run
fab under
Interesting... I've been having the same problem. I'm deploying to a VPS at
digitalocean.com running Ubuntu 12.04 64 bit. If I reboot the server I can
deploy successfully for awhile, but after some time (an hour or two)
something begins killing the migration step. If I log on to the server and
12 matches
Mail list logo
