You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
While trying to change the download directory and having copied the files, none of my subscribed items apeared in the database.
Switching back to the default directory and copying the database back to it didnt prove any results.
I fear this might have been a mistake on my part, of maybe not copying the database files before changing directory, but my memory leaves me uncertain if this is indeed the case.
Is this a common error or a misshap on my part, and, most of all, is there a fix to this?
The text was updated successfully, but these errors were encountered:
check if a mimanganu subdirectory is created on desire new location, all the data need to be on this subdirectory on its respective subdirectories, like /dbs
on dbs if you have the app since long time database backup can be there to restore something.
check if a mimanganu subdirectory is created on desire new location
It seems that's what the problem was.
I belived the directory folder to be ~/mimanganu and not the directory where the folder was located. I'm now able to access the old database without problem.
But i am still unable to change directory to where i intended.
Is MiMangaNu unable to read/write to the external sd?
While trying to change the download directory and having copied the files, none of my subscribed items apeared in the database.
Switching back to the default directory and copying the database back to it didnt prove any results.
I fear this might have been a mistake on my part, of maybe not copying the database files before changing directory, but my memory leaves me uncertain if this is indeed the case.
Is this a common error or a misshap on my part, and, most of all, is there a fix to this?
The text was updated successfully, but these errors were encountered: