Last modified: 2014-02-06 03:42:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62834, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60834 - Page information link doesn't work on Flow pages
Page information link doesn't work on Flow pages
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Kunal Mehta (Legoktm)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-04 16:40 UTC by Redrose64
Modified: 2014-02-06 03:42 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Redrose64 2014-02-04 16:40:13 UTC
At [[Wikipedia:WikiProject Hampshire]] there is a link [//en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Hampshire&action=info Page information] which works as it should. But at [[Wikipedia talk:WikiProject Hampshire]], the link [//en.wikipedia.org/w/index.php?title=Wikipedia_talk:WikiProject_Hampshire&action=info Page information] just shows the Flow page, nothing else.
Comment 1 Redrose64 2014-02-04 16:41:36 UTC
Apparently protocol-relative links don't work in bugzilla. [https://en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Hampshire&action=info Page information] [https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:WikiProject_Hampshire&action=info Page information]
Comment 2 Gerrit Notification Bot 2014-02-06 02:30:16 UTC
Change 111707 had a related patch set uploaded by Legoktm:
Whitelist action=info on Flow pages

https://gerrit.wikimedia.org/r/111707
Comment 3 spage 2014-02-06 02:48:11 UTC
Almost all page actions besides the default action=view (and soon, I think action=protect), don't work on a Flow board. A Flow board is no longer a wiki page but a window into a collection of topics made up of posts, and those elements have actions such as edit and delete.

The general issue is whether Flow should silently ignore unrecognized actions or report "Inappropriate action for a Flow board", similar to the error page ?action=BAD  generates on a regular page. I filed bug 60936.

The specific question is whether Flow should have a similar action=flow-info , or reuse action=info to do something quite different. Page watchers and subpages still apply, but edits, authors, and many other items are more applicable to individual topics and posts. I think number of topics on a Flow board is interesting. Perhaps when we have Search/filter for a board, a null search could return "420 topics found".
Comment 4 Kunal Mehta (Legoktm) 2014-02-06 02:54:14 UTC
(In reply to comment #3)
> The specific question is whether Flow should have a similar action=flow-info
> ,
> or reuse action=info to do something quite different. Page watchers and
> subpages still apply, but edits, authors, and many other items are more
> applicable to individual topics and posts. I think number of topics on a Flow
> board is interesting. Perhaps when we have Search/filter for a board, a null
> search could return "420 topics found".

action=info provides enough a good enough hook point that we should just re-use it instead of re-inventing the wheel.

Briefly discussed on IRC with Erik that we should get rid of the "wrong" information that action=info exposes for now, and in the future we can add more Flow-related info.
Comment 5 Gerrit Notification Bot 2014-02-06 03:35:58 UTC
Change 111707 merged by jenkins-bot:
Enable action=info for Flow pages

https://gerrit.wikimedia.org/r/111707
Comment 6 Kunal Mehta (Legoktm) 2014-02-06 03:42:13 UTC
action=info will start to work in 1.23wmf13. Some of the information that articles normally have (last editor, page creator, page length in bytes, etc.) will not be shown because the information would be wrong.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links