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-bilhoes-em-dinheiro-para-tomar-warner-da-netflix/157441 When accessing the embed url directly in the browser, it returns a 404 error: https://tecnoblog.net/comunidade/posts/483289/expand-embed

[image] 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 " \n \n Este é um tópico de discussão auxiliar para a entrada original em https://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix \n" The should be the content. Did you also change the blog URL by any chance? app/models/topic_embed.rb 71834c898 url = TopicEmbed.where(topic_id: post.topic_id).pick(:embed_url) response = TopicEmbed.find_remote(url) body = response.body if post&.topic&.topic_embed && body.present? post.topic.topic_embed.update!( embed_content_cache: body.truncate(EMBED_CONTENT_CACHE_MAX_LENGTH), ) end body << TopicEmbed.imported_from_html(url) body The onebox display also feels odd to me, I’d expect it to have a cached truncated content instead, so I’m assuming body.present? is false in the above conditional. Can you enter the Rails console and check if TopicEmbed.where(topic_id: 157441).pick(:embed_url) shows you the correct blog content URL? Can you spot any related errors on https://tecnoblog.net/comunidade/logs?

[image] renato: This is unrelated, this route only responds with an application/json content-type. Oh, ok! [image] 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://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix” [image] renato: Can you spot any related errors on https://tecnoblog.net/comunidade/logs? I don’t think there’s any related errors in the log. [Screenshot 2025-12-09 at 19.14.33] [image] renato: Did you also change the blog URL by any chance? discourse/app/models/topic_embed.rb at 71834c898f2f3f5d11df3db6f9a5bab12acbccaa · discourse/discourse · GitHub Nop! The blog URL has always been `tecnoblog.net` Also worth mentioning that the server’s IP is bypassed in CF’s Firewall: [Screenshot 2025-12-09 at 19.18.40]

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: topic_id) puts "TopicEmbed exists: #{te.present?}" puts "Embed URL: #{te&.embed_url}" puts "Content cache present: #{te&.embed_content_cache.present?}" puts "Content cache length: #{te&.embed_content_cache&.length || 0}" puts "Content SHA1: #{te&.content_sha1}" # 2. Check the actual cached content (first 500 chars) puts "\n--- Cached content preview ---" puts te&.embed_content_cache&.truncate(500) # 3. Try fetching from the remote URL if te&.embed_url.present? puts "\n--- Attempting remote fetch ---" begin response = TopicEmbed.find_remote(te.embed_url) puts "Remote fetch success: #{response.present?}" puts "Remote body present: #{response&.body.present?}" puts "Remote body length: #{response&.body&.length || 0}" puts "Remote title: #{response&.title}" puts "Remote body: #{response&.body&.truncate(500)}" rescue => e puts "Remote fetch FAILED: #{e.message}" end end # 4. Check what expanded_for would return if te.present? puts "\n--- Testing expanded_for ---" post = Post.find(te.post_id) # Clear cache to force fresh fetch Discourse.cache.delete("embed-topic:#{topic_id}") begin expanded = TopicEmbed.expanded_for(post) puts "Expanded content present: #{expanded.present?}" puts "Expanded content length: #{expanded&.length || 0}" rescue => e puts "expanded_for FAILED: #{e.message}" end end # 5. Check relevant settings puts "\n--- Site Settings ---" puts "embed_truncate: #{SiteSetting.embed_truncate}" puts "allowed_embed_selectors: #{SiteSetting.allowed_embed_selectors}" puts "blocked_embed_selectors: #{SiteSetting.blocked_embed_selectors}" This will show why https://tecnoblog.net/comunidade/t/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento/157462?u=falco is failing

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.present?}” discourse(prod)> puts “Embed URL: #{te&.embed_url}” discourse(prod)> puts “Content cache present: #{te&.embed_content_cache.present?}” discourse(prod)> puts “Content cache length: #{te&.embed_content_cache&.length || 0}” discourse(prod)> puts “Content SHA1: #{te&.content_sha1}” discourse(prod)> discourse(prod)> # 2. Check the actual cached content (first 500 chars) discourse(prod)> puts “\n— Cached content preview —” discourse(prod)> puts te&.embed_content_cache&.truncate(500) discourse(prod)> discourse(prod)> # 3. Try fetching from the remote URL discourse(prod)* if te&.embed_url.present? discourse(prod)* puts “\n— Attempting remote fetch —” discourse(prod)* begin discourse(prod)* response = TopicEmbed.find_remote(te.embed_url) discourse(prod)* puts “Remote fetch success: #{response.present?}” discourse(prod)* puts “Remote body present: #{response&.body.present?}” discourse(prod)* puts “Remote body length: #{response&.body&.length || 0}” discourse(prod)* puts “Remote title: #{response&.title}” discourse(prod)* puts “Remote body: #{response&.body&.truncate(500)}” discourse(prod)* rescue => e discourse(prod)* puts “Remote fetch FAILED: #{e.message}” discourse(prod)* end discourse(prod)> end discourse(prod)> discourse(prod)> # 4. Check what expanded_for would return discourse(prod)* if te.present? discourse(prod)* puts “\n— Testing expanded_for —” discourse(prod)* post = Post.find(te.post_id) discourse(prod)* discourse(prod)* # Clear cache to force fresh fetch discourse(prod)* Discourse.cache.delete(“embed-topic:#{topic_id}”) discourse(prod)* discourse(prod)* begin discourse(prod)* expanded = TopicEmbed.expanded_for(post) discourse(prod)* puts “Expanded content present: #{expanded.present?}” discourse(prod)* puts “Expanded content length: #{expanded&.length || 0}” discourse(prod)* rescue => e discourse(prod)* puts “expanded_for FAILED: #{e.message}” discourse(prod)* end discourse(prod)> end discourse(prod)> discourse(prod)> # 5. Check relevant settings discourse(prod)> puts “\n— Site Settings —” discourse(prod)> puts “embed_truncate: #{SiteSetting.embed_truncate}” discourse(prod)> puts “allowed_embed_selectors: #{SiteSetting.allowed_embed_selectors}” discourse(prod)> puts “blocked_embed_selectors: #{SiteSetting.blocked_embed_selectors}” TopicEmbed exists: false Embed URL: Content cache present: false Content cache length: 0 Content SHA1: — Cached content preview — — Site Settings — embed_truncate: true allowed_embed_selectors: blocked_embed_selectors: => nil discourse(prod)> :thinking:

[image] 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.

[image] 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 Content SHA1: — Cached content preview — — Attempting remote fetch — Remote fetch success: true Remote body present: true Remote body length: 22 Remote title: Remote body: — Testing expanded_for — Expanded content present: true Expanded content length: 309 — Site Settings — embed_truncate: true allowed_embed_selectors: blocked_embed_selectors: => nil

[image] 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.

[image] 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 at 14.45.51] So maybe discourse is not following the redirect? But also, why is it saving the URL without the trailing slash?

[image] 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 = TopicEmbed.find_remote(url) puts "Remote fetch success: #{response.present?}" puts "Remote body present: #{response&.body.present?}" puts "Remote body length: #{response&.body&.length || 0}" puts "Remote title: #{response&.title}" puts "Remote body: #{response&.body&.truncate(500)}"

Le bouton "Afficher le message complet" ne fonctionne pas dans les installations en sous-dossier

Assistance produit

renato (Renato Atilio) Décembre 11, 2025, 9:51 6

Êtes-vous sûr que c’est le bon identifiant de sujet ? https://tecnoblog.net/comunidade/t/-/386983 mène à une page 404.

Sujet		Réponses	Vues
Embed Discourse comments on another website via Javascript Integrations embedding , how-to	127	307307	Juin 2, 2026
Embed URL Inconsistencies in Discourse Product Support embedding , wordpress	1	181	Janvier 3, 2026
Discourse embed blocked on "Loading Discussion..." Product Support embedding	5	2751	Octobre 13, 2015
Discourse Comments stuck on "Loading..." Product Support	22	2500	Septembre 18, 2024
Embedding a list of Discourse Topics in another site Announcements embedding	91	24294	Février 25, 2024

Le bouton "Afficher le message complet" ne fonctionne pas dans les installations en sous-dossier

Sujets connexes