Bugzilla – Full Text Bug Listing
| Summary: | Not notified after change to watched wiki page | ||
|---|---|---|---|
| Product: | Community | Reporter: | Dani Megert <daniel_megert> |
| Component: | Wiki | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 298256 | ||
| Bug Blocks: | |||
Wiki only notifies you one after a change, and will not notify you again if you haven't visited the page. I just changed the Development Resources page as webmaster, and my personal account received the email: Dear Denis.roy.eclipse.org, The Eclipsepedia page Development Resources has been changed on 09:21, 5 April 2012 by Webmaster.eclipse.org, see http://wiki.eclipse.org/Development_Resources for the current version. See http://wiki.eclipse.org/index.php?title=Development_Resources&diff=0&oldid=295688 for all changes since your last visit. Editor's summary: /* Committers and The Eclipse.Org Website */ Contact the editor: mail: http://wiki.eclipse.org/Special:Emailuser/Webmaster.eclipse.org wiki: http://wiki.eclipse.org/User:Webmaster.eclipse.org There will be no other notifications in case of further changes unless you visit this page. You could also reset the notification flags for all your watched pages on your watchlist. Your friendly Eclipsepedia notification system Stupid me! Sorry about the noise. This can also happen if you did visit the page, but the server had logged you out (bug 298256). I'm reopening this bug. If the mechanism of notifications relies on being logged in, then it must ask me to logged-in. > I'm reopening this bug. If the mechanism of notifications relies on being
> logged in, then it must ask me to logged-in.
That doesn't really make any sense. To know if you must be notified, we'd have to force everyone to always be logged in.
(In reply to comment #5) > > I'm reopening this bug. If the mechanism of notifications relies on being > > logged in, then it must ask me to logged-in. > > That doesn't really make any sense. I does for me. > To know if you must be notified, we'd > have to force everyone to always be logged in. Yes, exactly, but currently this does not happen! See also bug 298256 why this got worse. Even if I click on the links in the e-mail that notify me, I simply reach the page (not being logged-in) and nothing asks me to log-in. As a result, the page is not marked visited for me and hence I won't get further notifications (this bug). So, at least when I click a link on the notification e-mail, it should ask me to log-in. I continuously loose track of wiki page notifications due to this. I'm also fine closing this bug and fixing bug 298256 as long as I don't get disconnected from notifications. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. (In reply to Eclipse Genie from comment #8) > This bug hasn't had any activity in quite some time. Maybe the problem got > resolved, was a duplicate of something else, or became less pressing for > some reason - or maybe it's still relevant but just hasn't been looked at > yet. > > If you have further information on the current state of the bug, please add > it. The information can be, for example, that the problem still occurs, that > you still want the feature, that more information is needed, or that the bug > is (for whatever reason) no longer relevant. > > -- > The automated Eclipse Genie. Still an issue, but there's hope bug 298256 gets fixed soon. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Still broken. The only reason we don't nag you more often about this is that our hackaround works more or less: https://www.eclipse.org/jdt/ui/scripts/eclipse_wiki.user.js Even with that, the auto-log-outs are still a pain, since they sometimes lose the #fragment in the original link. I still see several cookies from wiki.eclipse.org that are session cookies (bug 298256 comment 26). This bug together with bug 455651 makes tracking of wiki changes impossible without client-side hacks. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/151. |
I noticed this before, but now it happened again. Martin changed http://wiki.eclipse.org/Eclipse/PMC#Meeting_Minutes yesterday. Though I watch this page, I did not get notified.