Fix problem with USER_AFTER_REGISTER_ENDPOINT.

[carrete]

Per #177, this may or may not be correct nor complete.

[and-semakin]

Hi @carrete! Thank you for your contribution! I am afraid that we can not accept this changes to v0.6 branch as it is not actively developed or maintained. Could you please start your branch from master and specify master as a target of the PR? We have exactly the same code here in user_manager__views.py:498 with the same issues.

[carrete]

Hi @and-semakin , I see in the change history above you retargeted this pull-request for master and then switched it back to v0.6. What, if anything, do you need me to do?

[and-semakin]

Hi @carrete! Just wanted to try if it will work :)

Source branch (carrete:gh-issue-177) is started from 0.6 so it can not be merged into master without conflicts (file moved):

Could you please start your branch from master? I'm afraid that you will have to manually re-apply the same changes to the new file. If everything goes right than what I mean can be accomplished with the following git commands:

# go to your Flask-User fork repository
cd Flask-User

# change branch to master
git checkout master

# update your fork
git remote add upstream https://github.com/lingthio/Flask-User.git
git pull upstream master
git push origin master

# delete old branch
git branch -d gh-issue-177

# create new branch with the same name from master
git checkout -b gh-issue-177

# manually apply the same changes to `user_manager__views.py`
...

# commit changes
git add flask_user/user_manager__views.py
git commit -m "Fix #177"

# push branch to the same PR
git push --set-upstream origin --force gh-issue-177

I apologize for the inconvenience and the fact that this PR has been in review for so long. I can do it myself, but I really appreciate your contribution and want your name to be under this commit :)

Thank you!

[carrete]

@and-semakin Thanks for your very detailed instructions. How does it look now?