-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Follow button not showing the user is subscribed on the /subscriptions page #5485
Comments
If this issue is open to be worked upon, I would like to give it a try. Thanks! |
The user count is increased on refreshing the page. Also, we can add a toggle button for following or unfollowing a tag in the same subscription column. Currently, the "follow" button also changes to "following" when the page is refreshed. |
@divyabaid16 Can we divide the issue? |
Sure!! |
Should the user be allowed to delete their subscription from the tags page directly? |
Yeah that would also be great. Thank you for working on it. |
I have written a code for changing the text from "follow" to "following" when clicked. But, it only works once. I will have to refresh the page again for the click to work again. It can be because the query is set to work only for one action. What do you think about this @divyabaid16? |
@gautamig54 I guess you will need to make changes in routes.rb |
@gautamig54 Regarding this, a new layout of tags page was proposed by @jywarren in issue #5090 |
@Souravirus I want to work on this issue. |
@Souravirus I also want to work on this issue. |
Hi @Utiwari1999, sorry for the late reply. Yeah you can surely work on this. Thank you!! |
I believe this is resolved in the new design, thank you!!! |
Reported on #5182
The subscribe button is actually working in the backend but it's not being shown to the user. Also, the user count is not increased after clicking the follow button.
The page is this and here is the screenshot.
![image](https://user-images.githubusercontent.com/17192149/56131857-421e4280-5fa6-11e9-8abd-a738c6de25a2.png)
The text was updated successfully, but these errors were encountered: