8000 Profile name is not updated in published articles · Issue #283 · manshar/manshar · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Profile name is not updated in published articles #283

8000
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
azzenabidi opened this issue Feb 28, 2017 · 5 comments
Open

Profile name is not updated in published articles #283

azzenabidi opened this issue Feb 28, 2017 · 5 comments

Comments

@azzenabidi
Copy link
azzenabidi commented Feb 28, 2017

Hi! I updated my profile name(as shown in the attached screenshot) However, the profile name was not updated in published articles . Thanks!
P.S; I refreshed the web page many times and cleared the cache but in vain .

update-problem

@azzenabidi azzenabidi changed the title Profile name was not updated in published articles Profile name is not updated in published articles Feb 28, 2017
@mkhatib
Copy link
Member
mkhatib commented Feb 28, 2017

Thanks @azzenovic for filing. Will work on fixing this soon. A workaround for now to get it to update might be to edit the article and re-publish it. Let me know if that doesn't work.

@azzenabidi
Copy link
Author

ur welcome @mkhatib . Well I couldn't even login to begin with . I will report the new problem in a separate issue

@mkhatib
Copy link
Member
mkhatib commented Feb 28, 2017

@azzenovic the login issue might be related to AWS and Heroku being down - most of the internet is down currently because of issues with Amazon 😄

@azzenabidi
Copy link
Author

@mkhatib I see ! thanks for the info :D now I have to wait one more day to start creating content on manshar :(

@azzenabidi
Copy link
Author

@mkhatib I finally had access to my manshar account. I just wanted to inform you that the workaround you suggested works fine for me thanks !
looking forward to seeing the bug fix :D Keep up the good work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0