Ok,
What I did was modify how the dbgettext plugin loaded and changed the
registrations of the models.
You shouldn't have this problem without the plugin. Can you get the server
to run without apache? If you just use manage.py runserver?
Regards,
Andréas
2015-01-07 21:23 GMT+01:00 sarfaraz ahm
I have posted the entire issue in another post. After that I found your
reply.
https://groups.google.com/forum/#!topic/django-users/mOJRvLYjzDs
I m beginner in Django. I have configured Django/Python/ Apache/Mod_wsgi on
EC2 Amazon Windows instance. I see the similar error. I am not using any
p
Hi Sarfaraz,
Are you also having problems with the dbgettext plugin? Or is it with
another plugin?
Regards,
Andréas
2015-01-07 18:40 GMT+01:00 sarfaraz ahmed :
> I believe i am too facing the same issue. But from above conversation I am
> not able to get solution of this issue. Could please he
I believe i am too facing the same issue. But from above conversation I am
not able to get solution of this issue. Could please help me.
Regards,
Sarfaraz Ahmed
On Thursday, 4 December 2014 15:21:59 UTC+5:30, Andréas Kühne wrote:
>
> 2014-12-04 1:39 GMT+01:00 Carl Meyer >:
>
>> Hi Andreas,
>>
>
2014-12-04 1:39 GMT+01:00 Carl Meyer :
> Hi Andreas,
>
> On 12/03/2014 01:34 PM, Andreas Kuhne wrote:
> > I am trying to migrate our current website to django 1.7.
> >
> > Currently we are using a plugin called django-dbgettext to get parts of
> our
> > database translated (we are running in 10 di
Hi Andreas,
On 12/03/2014 01:34 PM, Andreas Kuhne wrote:
> I am trying to migrate our current website to django 1.7.
>
> Currently we are using a plugin called django-dbgettext to get parts of our
> database translated (we are running in 10 different languages). The problem
> is that django-dbget
I am trying to migrate our current website to django 1.7.
Currently we are using a plugin called django-dbgettext to get parts of our
database translated (we are running in 10 different languages). The problem
is that django-dbgettext starts by going through all of the models and does
this before
I'm not sure what the specific issue with migrations is but this article
has a nice trick (intended for making temporary models/tables) that would
allow you to bring in a model and get it to sync whenever you like. I'd
suggest putting this in your test setUp() method. It uses 'syncdb' cause
it's pr
Hi,
I'm trying to port my project to use Django 1.7. Everything is fine except
1 thing. Models inside tests folders.
Django 1.7 new migrations run *migrate* command internally. Before *syncdb
*was ran. That means if a model is not included in migrations - it won't be
populated to DB (and also t
9 matches
Mail list logo
