I didn't even need to use the debugger. I just ran with --verbosity 3, and it showed me all the places it looked for fixtures files. Strangely, it did not look for a fixtures dir immediately off my app's main dir, but it looked for one everywhere else. My app is called motor, and it lives in /usr/local/motor/motor. I had the initial_data file in /usr/local/motor/motor/fixtures, and here is where it looked:
Checking '/usr/local/motor/motor/../motor/ui/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/dispatch/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/core/data/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/core/reports/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/core/alerts/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/app/semvision/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/app/cdsem/fixtures' for fixtures... Checking '/usr/local/motor/motor/../motor/app/developer/fixtures' for fixtures... I would have thought it would have looked in /usr/local/motor/motor/fixtures. The reason it worked on my devel system is that had I FIXTURE_DIRS set in my setting file, back from when I was testing with the YAML files. In any case, I'll just move the file to core/data/fixtures. On Sat, Oct 13, 2012 at 2:28 PM, Larry Martell <larry.mart...@gmail.com> wrote: > Thanks Kurtis. That's will save me a bit of time. I'm going to dig > into it now. I'll let you know what I find. > > On Fri, Oct 12, 2012 at 2:25 PM, Kurtis Mullins > <kurtis.mull...@gmail.com> wrote: >> Whoops, sorry that was the master branch. Here you go: >> https://github.com/django/django/blob/1.4.1/django/core/management/commands/syncdb.py >> >> >> On Fri, Oct 12, 2012 at 4:24 PM, Kurtis Mullins <kurtis.mull...@gmail.com> >> wrote: >>> >>> Good luck to you! The code is here if you want to start crawling through >>> it for a good point to place a breakpoint: >>> https://github.com/django/django/blob/master/django/core/management/commands/syncdb.py >>> >>> >>> On Fri, Oct 12, 2012 at 3:30 PM, Larry Martell <larry.mart...@gmail.com> >>> wrote: >>>> >>>> On Fri, Oct 12, 2012 at 12:22 PM, Kurtis Mullins >>>> <kurtis.mull...@gmail.com> wrote: >>>> > On Fri, Oct 12, 2012 at 2:09 PM, Larry Martell >>>> > <larry.mart...@gmail.com> >>>> > wrote: >>>> >> >>>> >> >>>> >> So my client decided to use xml. I created the file and put it in >>>> >> fixtures/initial_data.xml. On my development machine, which is a Mac, >>>> >> it worked fine - running syncdb loaded the data. But on my client's >>>> >> machine, which is running CentOS, running syncdb did not load the data >>>> >> (it said 'Installed 0 object(s) from 0 fixture(s)'). But when I ran: >>>> >> >>>> >> manage.py loaddata fixtures/initial_data.xml >>>> >> >>>> >> That worked. Anyone have any ideas why sycndb worked on my mashine, >>>> >> but it's not working on theirs? >>>> > >>>> > >>>> > That's very weird. I haven't seen that affect off-hand. I've worked >>>> > with >>>> > Django on Linux (CentOS, Ubuntu, Debian) as well as OSX and it has >>>> > always >>>> > tended to work fine. I'm not sure on a solution other than to keep >>>> > checking >>>> > for inconsistencies or issues with the .xml file itself. Hopefully >>>> > someone >>>> > else who has ran into this problem before can chime in and offer some >>>> > help. >>>> > Good luck! >>>> >>>> Yeah, I don't think it's platform dependent. The xml file was pulled >>>> from our git repository, and it matches mine. And it works with >>>> loaddata. I'll have to set a breakpoint and see why manage doesn't see >>>> the file. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Django users" group. >>>> To post to this group, send email to django-users@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> django-users+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/django-users?hl=en. >>>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to django-users@googlegroups.com. >> To unsubscribe from this group, send email to >> django-users+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
