Issue when upgrade to 2.0.1
See original GitHub issueI just upgraded the library from 1.6 and got this error:
'Settings' object has no attribute 'LOCATION_FIELD'
Seems is not taking the default value since I don’t have any LOCATION_FIELD
setting.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Interval issue when upgrading to 2.0.1 #2952 - GitHub
It does seem to be related to drop chunks policies. I just ran into this error myself trying to upgrade from 1.7.5 to...
Read more >certificate issue while upgrade to 2.0.1 - VMware Communities
Now I would upgrade to 2.0.1 and it seems that through this process the install routine replaces the /etc/ssl/certs/ca-certificates.crt files, so it stops...
Read more >Upgrade from 2.0.x to 2.0.y - LemonLDAP::NG
Upgrading from 2.0.0 or 2.0.1 to later versions¶. If you have installed LemonLDAP::NG from official RPMs, you may run into bug #1757 and...
Read more >H2 version change issue from 1.4.200 to 2.0.202?
Yes, you need to upgrade them too together with H2, because their old versions don't work with new versions of H2. – Evgenij...
Read more >Migration to 2.0 - H2 Database Engine
The official way to upgrade is to export it into SQL script with the SCRIPT command USING YOUR CURRENT VERSION OF H2. Then...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@caioariede It seems to be like a result of the AppConfig not autoloading with the installed app.
I took a quick look at the docs and following the recommendation to add
location_field.apps.DefaultConfig
to INSTALLED_APPS solved issue.Is there a reason why you don’t autoload DefaultConfig with the app? Like this:
File:
location_field/__init__.py
BTW: Thanks for updating the package and releasing 2.0! It has been one of the few things keeping a project away from django 1.10
I’m having the same trouble with django-location-field==2.0.6. Copy pasting contents of \site-packages\location_field\apps.py into my settings fixed this. I am using Django > v2 though so perhaps this is an incompatibility thing.