No, it has not been solved yet. I still can not create an account with my
emailadres because it is allready in use. But when clicking on forgot
password it says that my emailadress is not yet in use.
?????
Elwin
2017-10-30 11:43 GMT+01:00 Peter Bienstman <email address hidden>:
> I assume this is solved now? If not, please let us know.
>
> ** Changed in: mnemosyne-proj
> Status: New => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1716993
>
> Title:
> login/ register error
>
> Status in The Mnemosyne Project:
> Fix Committed
>
> Bug description:
> When logging in with my existing account it tells me my username and
> email are not registerd. When trying to make an account it says i have
> allready used that username and email...
>
> Can you please help me logging in?
>
> My email is <email address hidden>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mnemosyne-proj/+bug/1716993/+subscriptions
>
Hello,
No, it has not been solved yet. I still can not create an account with my
emailadres because it is allready in use. But when clicking on forgot
password it says that my emailadress is not yet in use.
?????
Elwin
2017-10-30 11:43 GMT+01:00 Peter Bienstman <email address hidden>:
> I assume this is solved now? If not, please let us know. /bugs.launchpad .net/bugs/ 1716993 /bugs.launchpad .net/mnemosyne- proj/+bug/ 1716993/ +subscriptions
>
> ** Changed in: mnemosyne-proj
> Status: New => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> login/ register error
>
> Status in The Mnemosyne Project:
> Fix Committed
>
> Bug description:
> When logging in with my existing account it tells me my username and
> email are not registerd. When trying to make an account it says i have
> allready used that username and email...
>
> Can you please help me logging in?
>
> My email is <email address hidden>
>
> To manage notifications about this bug go to:
> https:/
>