Page MenuHomePhabricator
Create Task
Maniphest T76120

most LQT conversions put HTML of LQT conversion template in Flow board header, not the template invocation (LQT conversion -- is this a duplicate?)
Closed, ResolvedPublic
Actions

Description

The officewiki LQT conversion, acting as "Flow talk page manager", put {{LQT page converted to Flow}} in some Flow board headers (good), e.g. User_talk:jdavis.

But most got the expanded HTML of the template, as if it had been parsed (bad), e.g. User_talk:BDavis (WMF).

I don't see a pattern to this, the conversions were about the same time.

One other page got a good first board header edit showing a template: Village pump,

but mostly bad first board header edit showing HTML: Talk:Administrative_Services_Suggestion_Box, Talk:Community engagement, Talk:LiquidThreads LQT TestZero, and User_talk:Andrew Garrett (WMF).

Related Objects
Search...

Event Timeline

• Spage created this task.Nov 27 2014, 2:37 AM
• Spage raised the priority of this task from to Medium.
• Spage updated the task description. (Show Details)
• Spage added a project: StructuredDiscussions.
• Spage changed Security from none to None.
• Spage updated the task description. (Show Details)
• Spage added a subscriber: • Spage.
• Spage added a project: Collaboration-Team-Triage.Dec 10 2014, 2:52 AM
• Spage added a subscriber: EBernhardson.

I believe @EBernhardson fixed this, and we cleaned up those board headers by hand.

DannyH renamed this task from most LQT conversions put HTML of LQT conversion template in Flow board header, not the template invocation to most LQT conversions put HTML of LQT conversion template in Flow board header, not the template invocation (LQT conversion -- is this a duplicate?).Jan 12 2015, 6:13 PM
EBernhardson closed this task as Resolved.EditedJan 30 2015, 7:13 PM
EBernhardson claimed this task.

This was caused on officewiki due to some issues talking to parsoid, since then we have adjusted officewiki to appropriately talk to parsoid and removed the fallback from parsoid to wikitext so we don't accidently use the php parser when we expected the parsoid parser.

Specifically the reason the templates didn't round trip here is that the original import was done with the php parser and the HTML from the php parser was stored. When round tripping the HTML from the php parser into parsoid we lose the template information.

Content licensed under Creative Commons Attribution-ShareAlike 3.0 (CC-BY-SA) unless otherwise noted; code licensed under GNU General Public License (GPL) or other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL