# L'email con l'aggiornamento disponibile contiene un link non valido alle note di rilascio

**URL:** https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389
**Category:** Bug
**Tags:** email-templates
**Created:** [20 Maggio 2026, 4:56am UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389 "2026-05-20T04:56:04Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![fhe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fhe/32/113345_2.png) [@fhe](https://meta.discourse.org/u/fhe)
#### Post date: [20 Maggio 2026, 4:56am UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389/1 "2026-05-20T04:56:05Z")

</div>

Manca la `v` prima del numero di versione e ciò genera un errore 404.

> Scopri le novità nelle note di rilascio

collega a

`https://releases.discourse.org/changelog/2026.5.0-latest.1`

invece di

`https://releases.discourse.org/changelog/v2026.5.0-latest.1`

---

<div class="post-metadata">

### Author: ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [21 Maggio 2026, 11:30pm UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389/2 "2026-05-21T23:30:33Z")

</div>

> [@fhe](#):
>
> Manca la `v` prima del numero di versione e ciò causa un errore 404.

Ho una PR qui per correggere il link nei template `new_version_mailer...` aggiungendo la `v` alla stringa dell’URL.

> <https://github.com/discourse/discourse/pull/40237>
>
> Added a hardcoded \`v\` in the \`new\_version\_mailer\` URL strings so that it it reso…lves the correct link to the \[change log releases\](https://releases.discourse.org/) -\> (ie: https://releases.discourse.org/changelog/v2026.5.0 instead of \`https://releases.discourse.org/changelog/2026.5.0\`
> 
> see this bug topic: https://meta.discourse.org/t/-/403389

Può essere corretto anche localmente sul tuo sito modificando le stringhe degli URL in `new_version_mailer.text_body_template` e `new_version_mailer_with_notes.text_body_template`.

 ![Screenshot 2026-05-21 alle 16.33.09](https://global.discourse-cdn.com/meta/original/4X/d/1/2/d126dabb5746ebe2b16e30b4e07d88b49514e503.png)

---

<div class="post-metadata">

### Author: ![fhe](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fhe/32/113345_2.png) [@fhe](https://meta.discourse.org/u/fhe)
#### Post date: [22 Maggio 2026, 4:18am UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389/3 "2026-05-22T04:18:27Z")

</div>

Grazie! Non avevo pensato che potessi risolvere anche localmente, quindi questo è davvero utile.

---

<div class="post-metadata">

### Author: ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [22 Maggio 2026, 3:09pm UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389/4 "2026-05-22T15:09:52Z")

</div>

La PR è stata unita, quindi questo dovrebbe essere risolto al prossimo aggiornamento.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [24 Maggio 2026, 10:00pm UTC](https://meta.discourse.org/t/email-with-update-available-has-invalid-link-to-release-notes/403389/5 "2026-05-24T22:00:14Z")

</div>

Questa discussione è stata automaticamente chiusa dopo 2 giorni. Non sono più ammesse nuove risposte.