Last modified: 2013-12-05 20:51:29 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 T56892, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 54892 - Flow: magic words (e.g., {{PAGENAME}}) don't work in board header and posts
Flow: magic words (e.g., {{PAGENAME}}) don't work in board header and posts
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
master
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://ee-flow.wmflabs.org/wiki/User_...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-02 19:17 UTC by spage
Modified: 2013-12-05 20:51 UTC (History)
5 users (show)

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


Attachments

Description spage 2013-10-02 19:17:05 UTC
For example, {{FULLPAGENAME}} on an occupied talk page displays just Flow on ee-flow (and Special:Flow on my local wiki). I put a sampling of them in http://ee-flow.wmflabs.org/wiki/User_talk:Spage

This is a problem if you want to use templates in the summary to say things like "Previous contents of this talk page have been moved to [[{{FULLPAGENAME}}/Archive|archive]]"

Also referring to a User_talk subpage with [[/Archive]] doesn't work, even though during editing VE thinks the page is there.
Comment 1 spage 2013-10-03 17:21:04 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/278
Comment 2 spage 2013-11-13 02:43:25 UTC
Now on http://ee-flow.wmflabs.org/wiki/User_talk:Spage with latest Parsoid, {{NAMESPACE}}} displays blank and {{FULLPAGENAME}} displays "Main Page" i.e. the default page if no page is specified.

And if I edit my Flow board header containing this text, it displays badly garbled magic word contents:

* FULLPAGENAME={{urrently [[S}}
* PAGENAME={{unning]]}}
* BASEPAGENAME={{ ([[mw:Exten}}
* SUBPAGENAME={{out user-to}}
* TALKPAGENAME={{on the [[San}}
* NAMESPACE={{your talk}}

which may be a different bug with roundtripping HTML in Flow or Parsoid.
Comment 3 spage 2013-11-13 07:41:36 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/448, but people from the community are welcome to contribute here and in Gerrit.
Comment 4 spage 2013-11-14 18:29:35 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/459, but people from the community are welcome to contribute here and in Gerrit.
Comment 5 MZMcBride 2013-11-18 02:28:34 UTC
http://ee-flow.wmflabs.org/w/index.php?title=Talk:Sandbox&workflow=0509a3f95a7b34dffb6efa163e68c4ac&action=view#flow-post-0509a3f95a9334dffb6efa163e68c4ac

This makes Flow pretty difficult to use. I was trying to test Flow's support of magic words.

Input: "{{PAGENAME}} sucks."

Output: "Main Page sucks." (wrong: I was at "Talk:Sandbox", so it should be "Sandbox sucks.", I believe)

When I try to edit the post, I see this, worryingly: "{{is is a }} sucks."

This is not what I input.
Comment 6 MZMcBride 2013-11-18 05:05:32 UTC
This includes {{fullurl:}}.
Comment 7 spage 2013-11-18 08:02:39 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/466, but people from the community are welcome to contribute here and in Gerrit.
Comment 8 spage 2013-11-22 01:08:36 UTC
(In reply to comment #2)\
> And if I edit my Flow board header containing this text, it displays badly
> garbled magic word contents:
> ...
> which may be a different bug with roundtripping HTML in Flow or Parsoid.

it was a different Parsoid bug 56820, and is fixed.

Regarding comment #4 and comment #7 , the Mingle import script would create a new Mingle card whenever the bug title changes. I believe I fixed that.

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


Navigation
Links