Re: "RuntimeError: Error creating new content types."

Good tip. First upgrading to Django 1.7 then running the migrations then upgrading to 1.8 also fixed this for me :) On Sunday, July 26, 2015 at 9:50:19 AM UTC-7, Tobias McNulty wrote: > > I just ran into this issue as well when updating an old project to Django > 1.8. The only suitable

URL Generation

Hello all, I have an issue that I've been trying to work around in a generic fashion (so that I'm not repeating myself in views/templates). Let's say I have three models: # models class Organization(models.Model): name = models.CharField(max_length=250, null=False, blank=False, unique=True)

Re: "RuntimeError: Error creating new content types."

I just ran into this issue as well when updating an old project to Django 1.8. The only suitable workaround I found was to update first to Django 1.7 and fake the initial migrations for my apps (presumably Django's as well, though it seems to handle that automatically). Only then can you safely

Re: Model opinnions

It should, yes. But instead hardcoding /media in your templates, use {{ MEDIA_URL }} On 26 Jul 2015 11:57, wrote: > Yeah, there is a test image to do the work. But I'm not using HTML > elements to see it: I'm trying to directly see it with the URL, like when > you open a

Re: Thumbnails In Django

I also came across some problems with sorl-thumbnail. It cannot generate "cache" folder and thumbnail_kvstore is always empty. Please see more detail in this question . On Wednesday, July 22, 2015 at 3:37:11

Re: Model opinnions

Yeah, there is a test image to do the work. But I'm not using HTML elements to see it: I'm trying to directly see it with the URL, like when you open a Twitter image in a new tab. About the setup... MEDIA_ROOT = os.path.join(BASE_DIR, '/media/') MEDIA_URL = '/media/' So