Upgrade error/mistake #1675
Replies: 4 comments 10 replies
-
Oh dear, replicated the same problem with my wife's logbook install. All stations claimed, clicked on the button to verify, logged in and the same problem. |
Beta Was this translation helpful? Give feedback.
-
Yes sadly it was the only safe method was to take first user, I knew it would affect a few but crossed fingers. |
Beta Was this translation helpful? Give feedback.
-
The gui shows my station locations, but no logbooks. If i look in the db, all my data is still in TABLE_HRD_CONTACTS_V01, however I don't have anything in station_logbooks or station_logbooks_relationship. Is there a way to force rerun the migration? The user_id in my station_profile is correct. |
Beta Was this translation helpful? Give feedback.
-
Any Advice resolving this issue. Read though the current replies and not fully understanding what the cause is. From memory I've only ever had one user on my log and one location Just updated to V2 clicking the claim buttons etc.. and getting the same "No Logbooks were found error" I can view my station location and it says there is QSO's there... |
Beta Was this translation helpful? Give feedback.
-
Post-upgrade, it says there are no logbooks configured.
On the other hand...
and
Pretty sure my old location was M0KHR, because all of the exported ADIF logs are as such, not a big loss, I guess I can import it all but I must have taken a wrong turn at some point.
Running on my Docker container, freshly baked, against my old, upgraded config files.
Beta Was this translation helpful? Give feedback.
All reactions