The NEW Official Unofficial Discourse bug tracker!
-
Because I am tired of Discourse bugs getting
- Lost
- Deleted
- Closed without resolution
- Scattered between what.tdwtf and meta.d
- Lost again
- Purged for being 'Old'
- etc.
I present to you DiscourseBugs.com
You can report here or over at meta.d, or directly to the bug tracker, I will try to keep things organized on the bug tracker for things like severity / dupes / etc. If you report to the tracker PLEASE KEEP IT PROFESSIONAL, AND DO ATTEMPT TO NOT DUPE REPORTS
I spent real money on it because I'm tired of shit, and it looks like we're stuck with shit. So if I'm going to be spending time bitching about it, might as well make an official record of bitching.
I am going to start with @Yamikuronue's list that she had compiled tonight (about 4-5 hours from now)
-
Your "link" isn't actually a link. Looks like they neuter incomplete links.
-
And we have a winner for the first bug.
-
I am going to start with @Yamikuronue's list she has compiled tonight
How did you know she's going to compile a list tonight?
CAN YOU READ FUTURES?!!>
-
Which should read as:
I am going to start with @Yamikuronue's list that she had compiled
-
CAN YOU READ FUTURES?!!>
Yes, but it's based on an unfixed vulnerability in Discourse.
-
Considering what you had for the href, I don't think any site would've handled the link correctly.
-
Nominated for pedantic dickweed badge.
-
DiscourseBugs.com? Yeah... it would. Make an HTML page and try it. (It has to be on the web though, specifically served over http/https, local file won't work since it preserves file:///)
-
Should we ping the meta.d boys, so they know they have a real bug tracker?
-
seconded!
-
Your link was:
<a href="DiscourseBugs.com">DiscourseBugs.com</a>Local IIS install running a page that has just "DiscourseBugs.com" as the href for the hyperlink (changed the text):
Trying a JSFiddle with the link the same way makes the URL it tries to go to "http://fiddle.jshell.net/_display/DiscourseBugs.com".
-
Yes, but it's based on an unfixed vulnerability in Discourse.
CAN TELL WHICH RACE CONDITION WILL WIN!?
sorry, capslock fixed. too much humor for me, my head exploded
-
- Posting bugs on discourse's own meta, where the devs expect them: good
- Posting bugs on TDWTF meta while discourse devs are watching: ok
- Posting bugs on TDWTF meta after discourse devs have left: ummm?
- Paying for a bug tracker that the software's authors didn't ask for and probably will never even visit: priceless
-
You just wait until I build the bot that scrapes meta.d and w.tdwtf bug categories and auto posts them to the bug tracker.
-
Just wanted to say thank you for this.
-
...and then?
-
And then poor @Yamikuronue doesn't have to compile a giant list of bug reports, only to have @eviltrout say he can't find them. We can pull a @CodingHorrorBot and link to our
blogbug tracker.
-
a bug tracker that the software's authors didn't ask for and probably will never even visit
That, of course, is the downside. Rational* developers would welcome this; DiscoDevs, not so much.
* Truly rational developers would, of course, have set up a real bug tracker from the start.
-
You just wait until I build the bot that scrapes meta.d and w.tdwtf bug categories and auto posts them to the bug tracker.
And later you can make little cardboard cutouts of Jeff and Sam and the others and make little plays with them:
- Jeff! What did the ticket #6512 tell you to do?
- <squaky voice> Errmm.. to add pagination, Mr. Matches?
- And what did you do?
- I... I... changed the colors in heatmaps?
- Jeff, Jeff, Jeff. You've been a baad software dev. And you know what happens with bad devs when they don't close their tickets?
- Oh no! Not the Mr. Bucket again! I'll be good Mr. Matches, I'll.... gurblbglug....
Little cutout Jeff is dunked into a glass of water.
-
I'm hoping to hijack @sam and @eviltrout, to give them work on a boring day. They seem likely to at least look from time to time.
-
10/10, would read again.
-
And later you can make little cardboard cutouts of Jeff and Sam and the others and make little plays with them:
+�
Seriously...glad I wasn't drinking anything when I read this.
-
You just wait until I build the bot that scrapes meta.d and w.tdwtf bug categories and auto posts them to the bug tracker.
I totally thought this was going to go the other way around... you were going to take @riking's bot and use it to scrape the bugtracker and dump them into meta.d
-
Step 2. Or as Discourse would say:
-
I'm probably going to use a combination of @riking, @VinDuv, @accalia's work to post to the bug tracker.
I might also create a mirror site that does a rendered version of the pages on what.thedailywtf.com - google has almost no data about any of our posts - discourse is a literal seo failure.
Which, consequently, means I'm going to hustle that 5 pounds from @Keith.
-
I totally thought this was going to go the other way around... you were going to take @riking's bot and use it to scrape the bugtracker and dump them into meta.d
Then use @riking's likebot spread across 10 accounts to like them in appropriate amounts to give them the correct weight in sam's custom bug like-order view.
-
... That is an amazing.
-
google has almost no data about any of our posts - discourse is a literal seo failure.
google search has worked fine for me on dicsourse, albeit a little slow to update... the problem for me is that the google link takes you to nowhere near the actual result they found thx2infiniscroll.
-
Google: what.thedailywtf.com
Google: what thedailywtf
Google: what the daily wtfNormal forums (IE: Google league of legends forums) return massive numbers of results when the primary domain is searched.
-
Which is similar to how it worked when searching for posts on CS.
-
AM CONFUSE:
Click that - see massive numbers of results?
-
Google league of legends forums
Returns massive # of results... across different subdomains.
-
Fortunately, search is functional enough to actually find stuff in the topic now.
-
Do I win?
-
For not searching actual words, no.
Googling leagueoflegends.com gives about the same kind of uselessness.
-
wat
-
-
Wat Tyler, reincarnated?
-
-
@Intercourse said:
Should we ping the meta.d boys, so they know they have a real bug tracker?
They would probably complain that they now have to watch even one more bug tracker and would therefore ignore it.
-
-
Promising progress.
-
Needs to work when searching
discourse bugs, including the space between the two words too
-
Baby steps.
-
You need to link it on the old CS forums. Google will have it at #1 in like 3.5 microseconds.
-
This is our bug tracker
bug
A bug report means <strong>something is broken, preventing normal/typical use of Discourse</strong>. Do be sure to search prior to submitting bugs. <a href="https://meta.discourse.org/t/how-to-write-a-good-bug-report/183671/">Include repro steps</a>, and only describe one bug per topic please.
You can see the 4 bugs we fixed in the last 24 hours here
bug
A bug report means <strong>something is broken, preventing normal/typical use of Discourse</strong>. Do be sure to search prior to submitting bugs. <a href="https://meta.discourse.org/t/how-to-write-a-good-bug-report/183671/">Include repro steps</a>, and only describe one bug per topic please.
-
hey now I see you trying to piggy back our tracker into our SEO.
-
That's cool, but don't worry, I'll help you out and show you how many you guys left on the table.
-
This is our bug tracker
<a href="https://meta.discourse.org/category/bug?status=open">https://meta.discourse.org/category/bug?status=open</a>You can see the 4 bugs we fixed in the last 24 hours here
<a href="https://meta.discourse.org/category/bug?status=closed">https://meta.discourse.org/category/bug?status=closed</a>Yeah, we've mentioned how WTF using a forum as a bug tracker is. Let's not get into that again.
