Seems to be an issue with comments trying to load. I'm seeing a 400 on GETs to the comments embed endpoint.
https://www.freecodecamp.org/news/what-is-gatsby-and-why-its-time-to-get-on-the-hype-train/
I tried poking at a few other pages and seeing the same thing, like https://www.freecodecamp.org/news/how-make-a-windows-10-usb-using-your-mac-build-a-bootable-iso-from-your-macs-terminal/
I'm not sure if this is the right URL, but if it is, it looks like the embed is set up wrong:
https://www.freecodecamp.org/forum/embed/comments?embed_url=%7B%7Burl%20absolute%3D%22true%22%7D%7D
@colbyfayock thanks a lot for catching this.
This is a regression that we introduced last night accidentally.
Here is what happened:
Sorry about the inconvenience and thanks once again.
This has been resolved after reverting the recent changes.
We are yet to deploy the feature that @scissorsneedfoodtoo is working on to fix. Re-opening.
@raisedadead I think we can close this since we are no longer using the embed.
I think we can close this since we are no longer using the embed.
Yup, we do not.
But there is no communication either about what happened to the comments. This should be left open or a feature issue should be opened with the explanation.
I'll defer to you.
@raisedadead Is the intent to no longer show a link for the comments at all? i thought the hope was to show a link with a count instead of the widget
@colbyfayock, a new solution is in the works that will create topics on the forum and display a link and comment count on each post.
Additionally we are investigating ways we could have optional notifications sent to authors for new comments as well.
fwiw, it's kind of a bummer that there's no longer even a link to the comments on the page. is there a reason why there wouldn't simply be a link to the comments while the main solution is being produced? completely removing a feature while the final solution is being developed isn't a great way to develop and maintain features.
for this particular case, this prevents easy access to the comments of a post, particularly for authors, where now I'm struggling to find it in the forums.
The current functionality as it was implemented was fragile and completely broken to the point where we had to remove it. Discourse gives you very little control on what you can do with it out of the box. A custom solution needs dev and time.
As of now as @ahmadabdolsaheb has mentioned the new solution is in works. Unfortunately there is no ETA when it will be out.
We understand the frustration and request your patience.
Closing as stale. Feel free to create a new issue regarding comments on articles if desired. But this particular issue is no longer present since comments aren't there. Thanks and happy coding 馃帀
Most helpful comment
@colbyfayock thanks a lot for catching this.
This is a regression that we introduced last night accidentally.
Here is what happened:
Sorry about the inconvenience and thanks once again.