I recently moved our Discourse installation to a subfolder. After doing that, the “Show full post” button stopped working – you click to expand the content, but it doesn’t load the full post. Nothing changed in my WP Discourse configs. https://tecnoblog.net/comunidade/t/paramount-oferece-us-108-bi…

[imagen] Thiago_Mobilon: When accessing the embed url directly in the browser, it returns a 404 error: This is unrelated, this route only responds with an application/json content-type. https://tecnoblog.net/comunidade/posts/483289/expand-embed.json is returning "<div><div></div></div>\n<hr>\…

[imagen] renato: This is unrelated, this route only responds with an application/json content-type. Oh, ok! [imagen] renato: TopicEmbed.where(topic_id: 157441).pick(:embed_url) It returns the post url: discourse(prod)> TopicEmbed.where(topic_id: 157441).pick(:embed_url) => “``https:…

I had to debug this issues like this a couple of times and it’s complicated, so bear with me. Run the following script and share the output here # Replace with the topic ID or URL you're debugging topic_id = 386983 # 1. Check if TopicEmbed exists and its content te = TopicEmbed.find_by(topic_id: …

discourse(prod)> # Replace with the topic ID or URL you’re debugging discourse(prod)> topic_id = 386983 discourse(prod)> discourse(prod)> # 1. Check if TopicEmbed exists and its content discourse(prod)> te = TopicEmbed.find_by(topic_id: topic_id) discourse(prod)> puts “TopicEmbed exists: #{te.presen…

[imagen] Thiago_Mobilon: 386983 Are you sure this is the right topic id? https://tecnoblog.net/comunidade/t/-/386983 leads to a 404.

Oh that is it. The topic I linked is actually the 157462.

[imagen] renato: Are you sure this is the right topic id? My bad! Here the results for the correct topic ID TopicEmbed exists: true Embed URL: https://tecnoblog.net/noticias/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento Content cache present: true Content cache length: 22 Co…

[imagen] Thiago_Mobilon: Remote body length: 22 Remote title: Remote body: Did your Cloudflare bypass work? Looks like the body for https://tecnoblog.net/noticias/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento is just 22 chars, which no title tag.

[imagen] Falco: Did your Cloudflare bypass work? Yes! All requests from the discourse server are bypassed: [Screenshot 2025-12-12 at 14.44.21] What i’ve noticed is that the embed URL doesn’t have a trailing slash at the end. All urls should have the trailing slash. [Screenshot 2025-12-12…

[imagen] Thiago_Mobilon: What i’ve noticed is that the embed URL doesn’t have a trailing slash at the end. All urls should have the trailing slash. That is easy to test, try url = "https://tecnoblog.net/noticias/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento/" response = Topic…

El botón "Show Full Post" no funciona en instalaciones de subcarpetas

Soporte del producto

Falco (Falco) 11 Diciembre, 2025 21:54 8

Ah, ya veo. El tema al que enlacé es en realidad el 157462.

Tema		Respuestas	Vistas
Embed Discourse comments on another website via Javascript Integrations embedding , how-to	127	306807	2 Junio 2026
Embed URL Inconsistencies in Discourse Product Support embedding , wordpress	1	175	3 Enero 2026
Discourse embed blocked on "Loading Discussion..." Product Support embedding	5	2717	13 Octubre 2015
Discourse Comments stuck on "Loading..." Product Support	22	2433	18 Septiembre 2024
Embedding a list of Discourse Topics in another site Announcements embedding	91	24047	25 Febrero 2024

El botón "Show Full Post" no funciona en instalaciones de subcarpetas

Temas relacionados