Closed modernNeo closed 4 years ago
Doesn't look likely given that we've had a 0007 migration since ~2018 and there's no occurrence of the string 0007_auto_20200413_2129
in the codebase's history. I'm afraid I don't know what direction to give you, but I can say with some confidence that it doesn't look like the answer is that we've deleted a migration here.
I think I sorta figured out the issue.
for reasons beyond me [since I am not advanced enough a django/python developer to say], if someone installs django_mailbox
versions 4.7.0<=x<=4.8.0
, running makemigrations
results in local django_mailbox
migrations being made in addition to the ones that comes with the module.
I was not aware previously that I should never be making my own migrations of third-party modules so I did not question it before but now that I learned the proper process, that presented a problem. just upping to latest version seems to solve it however.
tried to do a migration today and I got this error complaining about a non-existent migration
0007_auto_20200413_2129
but I do not see this migration under the migrations folder for the mailbox module. Was it a previous migration that had been removed? how can I resolve this issue?