| Ennomien | |
| Aug 16 2022, 3:45 PM |
| F35467493: image.png | |
| Aug 17 2022, 2:06 PM |
When starting a talk page item using sub-headers (===), the subscribe button is not visible when the signature is below one of the sub-headers. I think it should still show up in that case. For an example, see my sandbox page: here. I hope I've made the problem/request clear.
Ennomien
@Ennomien: Thanks for reporting this. For future reference, please use the bug report form (linked from the top of the task creation page) to create a bug report, and fill in the sections in the template.
Where to see a "Subscribe" button? On https://nl.wikipedia.org/wiki/Speciaal:Voorkeuren?uselang=en#mw-prefsection-betafeatures , do you have Overleghulpmiddelen (Discussion Tools) enabled, maybe?
https://nl.wikipedia.org/w/index.php?title=Gebruiker:Ennomien/Kladblok2&oldid=62621766 shows no "Subscribe" even after enabling that.
Please provide clearer steps to reproduce, as a complete list of steps, plus a screenshot. Thanks!
Thanks. I did not know if this was intentional or not, that's why I didn't choose a bug report.
I indeed should have been clearer. Discussion Tools is enabled. I forgot that the subscribe buttons disappear when viewing an old version of a page, so the perm link did not work correctly. I will retry:
So when viewing this page, there is no subscribe button next to the talk page item (==) when there are sub-headers (===) underneath the item. Discussion Tools must be enabled in order to see this.
When reproducing, don't forget to add "NEWSECTIONLINK" surrounded by __ and make sure you're viewing the current state of a page. Also, add a signature the way I did.
This is what I see (changed to English so it's better understandable):
Thanks for the bug report!
This is a known problem, reported as T298617. We're working on it and it should be fixed soon once we work out some technical details (maybe as early as next week).
This is also a bug :) It's reported as T314260 (reply and subscribe links suffer from the same problem). We already have a fix for this one, and it will be deployed to Wikimedia wikis this week.
Thanks and no problem! I've already searched for duplicates before reporting it myself, but apparently I did not search well enough. Wish you the best.