Laracast comments bugs

The comments have been reported to Jeffrey, and as far as whoops see my answer here.

https://laracasts.com/discuss/channels/general-discussion/switching-from-dev-develop-to-stable-60

Cool, is there an issue tracker where i can see what has been reported, status and report bugs officially?

Not really, you just have to search through this feedback channel, assuming the person posted it in the correct category.

Update, seems the post time bug has been fixed. will test the rest to see.

Bug 2 still persists

It seems Bug 3 has gotten worse, Now when editing comments the edit box does not go away (even tho the edit goes through) See: https://i.imgur.com/FQ6rWdJ.gifv

error

TypeError: "t.response.data.body is undefined"
    t https://laracasts.com/js/app.js?id=d069e02e2b313d67d700:1
vendor.js:1:245078
    Qe https://laracasts.com/js/vendor.js?id=65f9c83098145e784c22:1
    qe https://laracasts.com/js/vendor.js?id=65f9c83098145e784c22:1
    Ue https://laracasts.com/js/vendor.js?id=65f9c83098145e784c22:1
    ze https://laracasts.com/js/vendor.js?id=65f9c83098145e784c22:1

@JeffreyWay

@drwhat -

Bug 2 is fixed. That was a weird Vue issue where it wasn't picking up the Tribute autocomplete change.

The update comment box not going away was a small bug from a deploy earlier today. Should be fixed.

Thanks @jeffreyway the edit box nows goes away and mentions work, however the orginal bug with editing threads still parsists. Sorry to be a bother.

Also idea, Maybe you could make a github repo for the soul purpose of reporting bugs/feature requests on laracasts? Or do you have other official ways of doing so?

You could even do a series on it going through various bugs people report or new feartures. I know you dabbled with in one of your other series.

however the orginal bug with editing threads still parsists.

That was fixed too.

Maybe someone needs the Orkin man, just kidding. Sorry is the year 2019 The Orkin person.

@jeffreyway can I add a niggle.

When posting a reply, the tab key puts tab code into the reply.

After toggling the markdown preview, tab key now tabs to the next UI element and you have to revert to indenting with spaces.

@snapey Ah good catch. Fixing it right now.

@jeffreyway when looking at a forum post, all replies are in the correct timezone but the original question still shows the time offset.

Eg I see a post that on the index view says posted 5 minutes ago, but when it is opened it says posted 5 hours ago.