Last modified: 2014-10-10 23:24:33 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 T64903, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62903 - Flow: Pages designated for Flow that have no content and have never had content should not have a history tab
Flow: Pages designated for Flow that have no content and have never had conte...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-21 00:19 UTC by Dan Garry
Modified: 2014-10-10 23:24 UTC (History)
5 users (show)

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


Attachments

Description Dan Garry 2014-03-21 00:19:33 UTC
When a page is Flowified, it exists in a state where it has no content and has never had any content. Unlike a talk page in that state, however, the Flow page does actually exist, so the history tab is visible. However, that history page is totally blank because the page has no history... but it is a bit strange to have a button there that takes the user to a page which provides them with no information.

This is only a minor issue right now, but when Flow is more widely deployed then 99% of Flow boards will be pages that have no content and never have had content.

Suggested resolutions:
1) Remove the history tab from any Flow page that has no content and never has had content.
2) Add a message onto the history tab that says "This page has no history." (or something similar) if the Flow page has no content and never has had any content.
Comment 1 Dan Garry 2014-03-21 00:20:24 UTC
Changing severity to minor to reflect problem. Leaving prioritisation up to Flow team.
Comment 2 Matthew Flaschen 2014-10-10 23:22:16 UTC
Flow can be setup for an entire namespace, so you can also see this at e.g. http://ee-flow.wmflabs.org/wiki/User_talk:Testing_123 .

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


Navigation
Links