[Busy][v2.5.4]Clicking Comment Button from Post Feed with #editor as the First Tag (Main Category) Redirects to the Editor
Actually it wasn't me who found this bug, but Terry. I'm the one who eventually deduced that this same issue occurs in busy. To make the long story short, Terry found this bug while checking a new feature in ulogs.org, and I was the one who investigated and introduced the fix. Knowing the cause of the bug helped me discover that the same issue would occur in busy as well (because ulogs.org was forked from busy).
I already reported this to busy's repository as well, I just didn't have the time to make a post about it. Here's the link to the github issue.
Project Information
- Repository:
https://github.com/busyorg/busy - Project Name: Busy
- Issue: https://github.com/busyorg/busy/issues/2096
Expected behavior
When clicking "Comment" icon from the feed or from the post, it should go to the post's #comment section and allow the user to write a comment.
Actual behavior
When you click "Comment" icon from the feed or from a post, it redirects to the Editor to create a new post.
How to reproduce
- Go to https://busy.org/created/editor
- Look for a post that has editor as its first tag (e.g., https://busy.org/editor/@east.autovote/editor-test#comments)
Or go directly to the post. - Click the "Comment" icon
Result
Redirects to the editor instead of the post's comment section.
- Browser: Chrome Version 67.0.3396.99 (Official Build) (64-bit)
- Operating system: Windows 10
Recording Of The Bug
Hi @eastmael, thanks for the contribution.
Apparently the issue has been fixed cause I am unable to replicate the said behavior. Well, the developers already made a PR to that effect, closing the ticket. Thanks to @jrawsthorne.
The title contained sufficient information. One could tell the bug behavior even before going through the content of the post.
The report is short, with just enough relevant explanation to cover the expected and actual behavior. So were the steps.
Although its been fixed, the category gives extra points for detecting and analysing what possibly led to the bug. The same applies when you propose a fix. You could include these in your next reports.
Thanks again for the contribution, I look forwad to your next report.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Hello @fego, if you check the issue I'm the one who registered the ticket. So I think this was a valid bug. The posting in Steemit was just delayed ny four days.
Thanks for the review as well. This was just a quick reply.
Thank you for your review, @fego!
So far this week you've reviewed 12 contributions. Keep up the good work!
Hey @eastmael
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
I am so glad to see you after many many days missed the technical stuff which you provides.
Hope you learned something from it despite it being technical. :)
Great bug spotting there right on time glad someone caught that thing messsing up busy :)
Yup, these bugs are hiding somewhere beneath the codes. :)