Potential Bug while using this project with south. about django-bootstrap3 HOT 9 CLOSED

Same here.
For now im uncommenting bootstrap3 in INSTALLED_APPS if i want to make changes...

from django-bootstrap3.

That sounds like a nice workaround. So you just comment out bootstrap 3 app
right before running syncdb? Any other issues that you might have noticed
by doing this?
On Dec 6, 2013 12:19 PM, "erSitzt" [email protected] wrote:

Same here.
For now im uncommenting bootstrap3 in INSTALLED_APPS if i want to make
changes...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-30021156
.

from django-bootstrap3.

Nope, works for me.

from django-bootstrap3.

Adding an empty models.py is no problem, but I use South myself all the time and have never encountered this problem. Have you ENABLED South for Bootstrap3 perhaps? That is not necessary.

from django-bootstrap3.

I have never enabled (not knowingly) it, but i would check if you can tell my how to do that :)

from django-bootstrap3.

There is an empty models.py for compatibility with tests etc. Please ensure you are running the latest version.

from django-bootstrap3.

I'm experiencing this bug.

Django==1.6.5
South==1.0
django-bootstrap3==4.8.2

from django-bootstrap3.

I still have this issue.

Django ==1.6.5
django-bootstrap3 == 4.8.2
south==1.0

from django-bootstrap3.

I'm sorry this is giving problems. It looks like a bug in South. Please try reordering your apps so that South comes last. Look at

How to get django-nose installed correctly?
http://stackoverflow.com/questions/12215520/how-to-get-django-nose-installed-correctly

for more information.

from django-bootstrap3.