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

[imagem] Thiago_Mobilon: Is there a way to force discourse to update all the embed urls from a category, following it to the final destination? Run te = TopicEmbed.find_by(topic_id: 157462) te.embed_url = te.embed_url + "/" te.save Does that fixes https://tecnoblog.net/comunidade/t/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento/157462 ?

It works! But is there a fix for cases like this? [imagem] Thiago_Mobilon: For example, in this post, the url used to be: https://tecnoblog.net/486925/o-que-e-pirataria-digital/ Now, it changed to: https://tecnoblog.net/responde/o-que-e-pirataria-digital/ Gemini suggested this code: # Configuração CATEGORY_SLUG = 'tb' category = Category.find_by(slug: CATEGORY_SLUG) unless category puts "ERRO: Categoria '#{CATEGORY_SLUG}' não encontrada." exit end puts "Iniciando varredura completa de URLs na categoria '#{category.name}'..." puts "Isso pode demorar dependendo da quantidade de tópicos e da resposta do seu site..." count_updated = 0 count_errors = 0 count_ok = 0 Topic.where(category_id: category.id).find_each do |topic| current_url = topic.custom_fields["embed_url"] # Pula se não tiver embed_url next unless current_url.present? begin # Faz a requisição GET seguindo redirects response = Faraday.get(current_url) final_url = response.env.url.to_s # Se a requisição foi bem sucedida (200 OK) if response.status == 200 # Verifica se a URL final é diferente da URL salva no banco # A comparação ignora diferenças sutis se necessário, mas aqui comparamos string exata if final_url != current_url puts "\n[ATUALIZAR] Tópico ##{topic.id}:" puts " De: #{current_url}" puts " Para: #{final_url}" topic.custom_fields["embed_url"] = final_url topic.save_custom_fields(true) count_updated += 1 else # print "." # Descomente para ver progresso visual (pontinhos) count_ok += 1 end else puts "\n[ERRO HTTP #{response.status}] Tópico ##{topic.id} - URL: #{current_url}" count_errors += 1 end rescue Faraday::ConnectionFailed, Faraday::TimeoutError => e puts "\n[FALHA DE CONEXÃO] Tópico ##{topic.id} - URL: #{current_url} - #{e.message}" count_errors += 1 rescue StandardError => e puts "\n[ERRO GERAL] Tópico ##{topic.id} - #{e.message}" count_errors += 1 end # Opcional: Pausa pequena para não sobrecarregar seu servidor WordPress # sleep 0.1 end puts "\n\nResumo Final:" puts "------------------------------------------------" puts "Tópicos Verificados (OK): #{count_ok}" puts "Tópicos Atualizados: #{count_updated}" puts "Erros Encontrados: #{count_errors}" puts "------------------------------------------------"

[imagem] Thiago_Mobilon: It works! Finally some progress :sweat_smile: [imagem] Thiago_Mobilon: But is there a fix for cases like this? A script like that is a great idea, just take a backup before running it. Even a backup of just this small table would be great.

[imagem] Falco: A script like that is a great idea, just take a backup before running it. Ok! I’ll try to run it later, when the team finishes their shift.

Hey guys, I see the trailing slash has struck again :slight_smile: [trailing slashes are] the principal issue it appears. When using Embed Discourse comments on another website via Javascript you control that via a parameter, it’s super easy to fix. Just at note that all topic embeds in Discourse strip trailing slashes from the embed_url; see TopicEmbed.normalize_url. As a result of a separate case involving the intersection of javascript embeds and WP Discourse embeds we standardised this handling across both methods of embeds. See Apply TopicEmbed url normalisation to embed urls inserted in the PostCreator by angusmcleod · Pull Request #30641 · discourse/discourse · GitHub @Thiago_Mobilon In the course of this move did you also update your Discourse? It may be that we’re seeing the application of the standardisation of embed_url normalization to WP Discourse embeds being applied here as a result of an update of your Discourse, which occurred at the same time as the move to the subfolder installation. What version of Discourse are you currently running? (and what version were you running prior to the move, if you know that?) Just a side note that when I run these two commands locally on the latest version of Discourse, I’m getting the same result, namely the HTML body of the article # with trailing slash TopicEmbed.find_remote("https://tecnoblog.net/noticias/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento/") # without trailing slash TopicEmbed.find_remote("https://tecnoblog.net/noticias/governo-renova-app-da-cnh-para-baratear-obtencao-do-documento") # produces the same result Did you perhaps make a change on the Wordpress side of things? ** edit Ah reading this topic a bit more closely I see that your issue is perhaps not to do with your move of Discourse to a subfolder installation, or trailing slashes, rather it is perhaps your migration of your Wordpress urls, i.e. For example, in this post, the url used to be: https://tecnoblog.net/486925/o-que-e-pirataria-digital/ Now, it changed to: https://tecnoblog.net/responde/o-que-e-pirataria-digital/ So perhaps the issue is that you have topic_embeds.embed_url with your old url structure and FinalDestination is not resolving the new urls for whatever reason (i.e. it’s unable to follow a redirect) In that case you will either need to ensure that your old blog urls redirect to your new blog urls, or you’ll need to migrate the topic_embeds.embed_url. On the migration front, note that your script is incorrect, e.g. topic.custom_fields["embed_url"] is not where the embed_url is stored. Here’s what I would suggest if you want to go the migration route (as opposed to redirecting your old blog urls to the new ones). First, confirm your issue is an incorrect blog url format in topic_embeds.embed_url by looking at an example, e.g. TopicEmbed.find_by(topic_id: 157441). Then, if you see that the issue is indeed that you have the old url format saved in that column, run this to update all of the old format embed_urls in a specific category: category_id = # enter a category id here TopicEmbed.joins(:topic).where(topics: { category_id: category_id }).find_each do |embed| new_url = embed.embed_url.sub(%r{/\d+/}, "/responde/") embed.update!(embed_url: new_url) if new_url != embed.embed_url end Note that the regex substitution of the old format to the new (sub(%r{/\d+/}, "/responde/")) is just a guess based on the example you provided. You can test the effect of that on your real urls here: https://regex101.com/

Hi Angus! [imagem] angus: Ah reading this topic a bit more closely I see that your issue is perhaps not to do with your move of Discourse to a subfolder installation, or trailing slashes, rather it is perhaps your migration of your Wordpress urls, i.e. No, these are different issues. Trailing slash started when we moved to subfolder, but there are also old URLs from years ago that have a different slug, now. [imagem] angus: In the course of this move did you also update your Discourse? I had to rebuild the installation, so yeah, i think that this new standard might be the cause. My suggestion to fix this issue: can’t Discourse follow at least one or two redirects to retrieve the data? That would fix the trailing slash issue and also buletproof the website in case of possible URL changes in the future. Also, it’s safer, since there would be no need to run scripts to update old topics, that could also do some damage in the database.

[imagem] Thiago_Mobilon: can’t Discourse follow at least one or two redirects to retrieve the data? It does :slight_smile: Are you able to access the instance this is running on? If so, could you run the following and tell me the result: ./launcher enter app rails c TopicEmbed.find_by(topic_id: 157441).as_json

discourse(prod)> TopicEmbed.find_by(topic_id: 157441).as_json Serializing ActiveRecord models (TopicEmbed) without specifying fields is not allowed. Use a Serializer, or pass the :only option to #serializable_hash. More info: ``https://meta.discourse.org/t/-/314495 => {“id”=>56685, “topic_id”=>157441, “post_id”=>483289, “embed_url”=> “``https://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix”``, “content_sha1”=>nil, “created_at”=>“2025-12-08T17:54:07.585Z”, “updated_at”=>“2025-12-09T18:04:33.539Z”, “deleted_at”=>nil, “deleted_by_id”=>nil, “embed_content_cache”=>“”} discourse(prod)>

Did you edit the output before you shared it? Just looking at the embed_url value it’s “``https://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix”`` Could you just run the same command again, but this time: ./launcher enter app rails c TopicEmbed.find_by(topic_id: 157441).embed_url If what you shared is indeed the value of embed_url in your db, then that is the issue, and I’ll make a small PR to discourse/discourse to handle edge cases like this where the embed_url has ended up in a malformed state. https://github.com/discourse/discourse/pull/36753

[imagem] angus: Did you edit the output before you shared it? Just looking at the embed_url value it’s Nop! Just copied and pasted it here. About this backticks at the begining and ending of the url, i think it was just an error trying to format the text here in the topic, using the code button. [imagem] Thiago_Mobilon: “``https://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix”``, [imagem] angus: Could you just run the same command again discourse(prod)> TopicEmbed.find_by(topic_id: 157441).embed_url => “https://tecnoblog.net/noticias/paramount-oferece-us-108-bilhoes-em-dinheiro-para-tomar-warner-da-netflix” discourse(prod)> Here you can see a topic that was created using Embed JS: https://tecnoblog.net/comunidade/t/microsoft-edge-ganha-copilot-mode-que-promete-realizar-tarefas-usando-ia-tecnoblog/157661 The “Show Full Post” doesn’t work in this topic either.

Botão "Mostrar Post Completo" não funciona em instalações de subpasta

Suporte ao Produto

Falco (Falco) 23 Dezembro , 2025 22:03 33

@Thiago_Mobilon a correção foi implementada, você pode atualizar, por favor?

Tópico		Respostas	Vistas
Embed Discourse comments on another website via Javascript Integrations embedding , how-to	127	306998	2 Junho , 2026
Embed URL Inconsistencies in Discourse Product Support embedding , wordpress	1	177	3 Janeiro , 2026
Discourse embed blocked on "Loading Discussion..." Product Support embedding	5	2727	13 Outubro , 2015
Discourse Comments stuck on "Loading..." Product Support	22	2450	18 Setembro , 2024
Embedding a list of Discourse Topics in another site Announcements embedding	91	24146	25 Fevereiro , 2024

Botão "Mostrar Post Completo" não funciona em instalações de subpasta

Related topics