I did manage to get my dev env to work, on windows, still not quite sure what the magic formula is. I dropped the database, did the migrate, skipped the loadusers, loaded the datadump and it seemed to work. However I'm going to try it on a clean setup to see if I can figure out the magic sequence and then I'll update the setup docs as needed. I'll also set up my Linux env and try it out there.
The windows env works well enough for me to start to poke around the system.
I did notice that the flags were not displaying in the UI.
Looking at the image path I can see that there is a double forward slash in the path. On Linux this is ignored which is why I suspect no one has worried about this, however on Windows it causes an error and won't load.
For example the URL for the flag on a series page is:
Which appears to be caused by this code:
gcd-django/templates/gcd/bits/series_issue_header.html
line 48: <img src="{{ STATIC_URL }}/img/gcd/flags/{{ series.country.code|lower }}.png" alt="{{ country }}" class="embedded_flag">
The STATIC_URL is set in settings.py as far as I can see and does already end in a "/". I see that other uses of the STATIC_URL in the templates and other code does not add an additional slash when constructing the path.
Similar code with an extra "/" appears in a few other places, for example the countries.html template.
<img src="{{ STATIC_URL }}/img/gcd/flags/{{ country.code|lower }}.png" alt=" " class="embedded_flag"> ({{ country.code|lower }}) {{ country }}<br/>
I didn't find any discussion of this in the groups, so just wanted to check in to see if this is a known issue and if there are any concerns with making this change.
Thanks
Phil