# Discourse Comments stuck on "Loading..."

**URL:** https://meta.discourse.org/t/discourse-comments-stuck-on-loading/267861
**Category:** Support
**Created:** [June 10, 2023, 4:12am UTC](https://meta.discourse.org/t/discourse-comments-stuck-on-loading/267861 "2023-06-10T04:12:03Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![fabsh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fabsh/32/311728_2.png) [@fabsh](https://meta.discourse.org/u/fabsh)
#### Post date: [June 16, 2023, 9:57am UTC](https://meta.discourse.org/t/discourse-comments-stuck-on-loading/267861/18 "2023-06-16T09:57:37Z")

</div>

The issue was indeed a bug in the latest Discourse version. Communiteq is patching it on my forum instance. For more info see here:

> [@Embedding is BROKEN in 3.0.4 (stable)](https://meta.discourse.org/t/change-in-3-0-4-broke-my-embedding-use-case/268559/7):
>
> So main has [this](https://github.com/discourse/discourse/blame/main/lib/topic_retriever.rb#LL49C5-L49C96) TopicEmbed.import\_remote(@embed\_url, user: User.find\_by(username\_lower: username.downcase)) and stable has [this](https://github.com/discourse/discourse/blame/stable/lib/topic_retriever.rb#L53) TopicEmbed.import\_remote(user, @embed\_url) Note the order of the parameters. Now the backport of the security patch [changed the function signature on stable](https://github.com/discourse/discourse/commit/5e3106387feb6de59d749202649971fb3c36ed41#diff-a9aa56fcefb13804a057905bdd06a402290431de865469884df64a9585b4206eL206) to the new parameter order,so def self.import\_remote(import\_user, url, opts = nil) became def self.import\_remote(url, opts = nil) and now the url parameter receives a User object. Changing the function ca…

---

_[View the full topic](https://meta.discourse.org/t/discourse-comments-stuck-on-loading/267861)._