once or twice a week i get the echo notification
"Beta Features was linked from [No page]."
its not always the Beta Features page, but frequently is.
See Also:
once or twice a week i get the echo notification
"Beta Features was linked from [No page]."
its not always the Beta Features page, but frequently is.
See Also:
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • jmatazzoni | T73534 Frequently getting broken echo notifications: "was linked from [No page]" | |||
Resolved | Catrope | T52829 Echo notifications should show the page name instead of [No page] if the page was deleted | |||
Resolved | Legoktm | T107823 Rewrite EchoNotificationFormatter | |||
Resolved | Legoktm | T60726 Echo: refactor duplicate icon handling code into getNotificationIconUrl() | |||
Resolved | SBisson | T121067 Write email formatter that uses presentation models |
I recall us fixing this some time ago. Not sure if the issue was exactly the thing we fixed, though.
I'll close this for now - please reopen should you still encounter the problem!
Note that this is by e-mail. These happen in the web UI too, but there it's understandable (the page was deleted after the notification was sent); but in e-mail, where we can check if the page exists before sending the notification, it's not.
This was also reported by @MachoCarioca at
https://pt.wikipedia.org/w/index.php?diff=41131641&oldid=41125389&uselang=en
We confirmed the message had that format when I deleted a page where I mentioned the user earlier.
This happened again, according to
https://pt.wikipedia.org/w/index.php?title=Usu%C3%A1rio_Discuss%C3%A3o%3ATeles&type=revision&diff=42563714&oldid=42547431
Checked the fix in betalabs - the current solution is to purge all echo notifications about linking if a page(s) was deleted.
@jmatazzoni please confirm that it's expected behavior.
please confirm that it's expected behavior.
If one of the linked pages no longer exists, then there is no link. So deleting the message makes sense to me. Thanks for asking.
I'm reading @Etonkovidova's message to mean that that solution is currently working, so I'm Resolving this (if that solution is not yet in place or tested, let me know and we can reopen).