By Attila Lengyel on Thursday, 14 August 2014
Posted in General Issues
Replies 7
Likes 0
Views 845
Votes 0
Hey team,

Just discovered a tiny hashtag issue at the stream filter page. Maybe it is deliberate, not sure, but here's how it looks like and how you can replicate it:

Click on an existing hashtag link in the stream, so you will be redirected to the stream filter page.
If you hit the sharebox, the predefined keyword will be there. If you leave your cursor at its original place (before the keyword), it's fine, works great as intended.
When you move your cursor after the keyword, your stream item will gain an extra # besides the hashtag, and there won't be any spaces for example between the hashtag & your own words.

Hope you can follow my drift, but I attached a screenshot, as well as a video to help you out tracking this down. Check it out pls: http://screencast.com/t/TlHnAJmO5f
Let me know, if this a normal phenomenon, or an existing issue Probably it's just a typo in the source code

One more closing question: at hashtag page, you cannot close the sharebox. Is that right by the way?
Hope this thread helps. Thanks in advance.
Regards,

Attila
Hello Attilia,

I have successfully replicate this issue with my local. This is a bug from our end and we'll fix this issue in the next release. Thank you for reporting in.

Thanks again and have a wonderful day.
·
Friday, 15 August 2014 13:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Attila,

I am sorry for the late reply.
I cannot replicate this issue with our local. Here my screenshot: http://screencast.com/t/iDul64ynFg . I cannot login to your site, either administrator and your site. http://screencast.com/t/5HMAPktQ and http://screencast.com/t/g7gLxE8B . It seems like you didn't activate our access yet. Can you provide us with backend access and FTP access as well so that we can help you debug this issue and fix it for you. We need this access in order to debug this issue since we cannot replicate this issue with our local.

Please be advise.
Thanks.
·
Friday, 15 August 2014 01:41
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mohd,

Thank you for your reply. It was quick, trust me.

I checked site details, and updated all the necessary information. I am really sorry about any inconvenience. Seems like it was a long time ago, when I wrote down these details.
Now you should be able to login at both backend & frontend with the provided credentials. If you do so, you will definitely be able to investigate further.

Thank you for your help in advance! Have a great day & weekend!

Regards,

Attila
·
Friday, 15 August 2014 02:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Atilla,

Hm, this is odd as I cannot seem to reproduce this issue on your site. When filtering tags from #worldcup's hashtag, this is what is appearing for me http://screencast.com/t/IMp3QL0l
·
Friday, 15 August 2014 03:04
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guys,

After giving it a double-check, now i know why A space " " causes the issue. If i leave the space before the hashtag without writing anything in front of it but write after it, will add an extra # before my keyword. If you delete that space, and then move your cursor behind the tag, it works. If you do not alter your cursor position after navigating to the hashtag filter page, the issue does not come up either. Okay, it's pretty hard to explain. : Have a look at this video please: http://screencast.com/t/uex91g5bPw41

I mean, do not get me wrong, it is neither a big deal, nor a major bug, probably most of the users would not notice it. But i was wondering if you would have any solution for this, or any of you has already experienced such things. Nevertheless, hope it can be helpful :-)

Thanks guys!
·
Friday, 15 August 2014 03:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Mohd,

Thanks for the quick reply and the patch provided in the upcoming release. I really appreciate your time & help. Have a great day too.
·
Saturday, 16 August 2014 17:24
·
0 Likes
·
0 Votes
·
0 Comments
·
You are most welcome Atilla
·
Saturday, 16 August 2014 23:01
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post