Help talk:Lint errors/fostered

About this board

Support on translatewiki

4
Amire80 (talkcontribs)

Hi,

I get a DiscussionTools error when I try to click "Reply" on https://translatewiki.net/wiki/Support , specifically this version. This is the main community discussion page of translatewiki.net. I cannot find what is fostered content there. There is one table there, but it seems valid, although it's possible I'm missing something.

Can anyone help, please?

Arlolra (talkcontribs)

The problem seems to have resolved itself, at least there are no more fostered content errors for that page.

It's possible that Parsoid was failing to parse that revision and so the errors were outdated.

Amire80 (talkcontribs)

OK, but for the next time, do you have any tips for debugging it?

Arlolra (talkcontribs)

I don't know too much about how translatewiki is configured. For WMF projects, when an edit is made, changeprop runs so that restbase is populated with a fresh parse of the page. That's when linting generally happens, when parsoid parses the page.

It looks like VE is talking to Parsoid 'direct'ly, rather that through an exposed rest interface ('vrs'). So there's no restbase and I doubt that's configured.

Recently we're switching to populating the parsercache with parsoid output on each edit, much like for the legacy parse. That too would cause linting to happen.

Maybe neither of those are happening. Which leaves the only way for a parse of the page to happen in parsoid being when VE is opened (?veaction=edit). So try that.

If it looks like VE displaying the correct result, maybe it's just a lag between when the parse happens and the lint job is run.

Reply to "Support on translatewiki"
RoySmith (talkcontribs)
Whatamidoing (WMF) (talkcontribs)
Reply to "Reply failure"
Shervin 8564 (talkcontribs)

Hi there! I cant reply messages in my talk page via reply button too

Can anyone help me please?

Whatamidoing (WMF) (talkcontribs)
Reply to "Message reply bug"

Reply tool not working on user talk

3
This post was hidden by Valereee (history)
Valereee (talkcontribs)

At his user talk:

Legoktm (talkcontribs)

Need help fixing wikitext problem

2
Allreet (talkcontribs)

The wikitext error is preventing replies on Wikipedia's Talk:Founding Fathers of the United States page. I'm not sure if this is the cause, but the problem did not exist before the addition of a fairly large table. Of course, we can still respond to comments using "edit" links, but "reply" links no longer work. Thank you.

Arlolra (talkcontribs)
Summary by Legoktm

Filed as phab:T184021.

Ignacio Rodríguez (talkcontribs)

This is giving false positives, particularly on Wikisource, in the case of tables spanning multiple pages. See for example any of the "Page:" results on This result page

Arlolra (talkcontribs)
Summary by Legoktm

Resolved

Vikipolimer (talkcontribs)

Hi there! I cant reply messages in my talk page via reply button, is there any solution with this?

Quiddity (talkcontribs)

Fixed, I think, with this edit. You might want to tell the editor who sent that broken message, that they need to fix it everywhere else.

Vikipolimer (talkcontribs)

@Quiddity Thank you! I'm gonna let they know about this, have a nice Wiki!

Whatamidoing (WMF) (talkcontribs)
Summary by Legoktm

Resolved

Harald the Bard (talkcontribs)

I share the same situation with @Vikipolimer, but I wasn't able to fix it myself. Can someone assist me?

Arlolra (talkcontribs)

False positive with noinclude

1
Bdijkstra (talkcontribs)
<noinclude>{|</noinclude> class="wikitable"<noinclude>
|}</noinclude>

Any table attribute triggers the 'fostered' error on the template page, but nothing is wrong. No error is triggered on transclusions.

Reply to "False positive with noinclude"
Quiddity (WMF) (talkcontribs)

1. Given the current example, should we add a line suggesting the alternatives/fixes, e.g.

If this line is below the opening {|, then you might want to add a ! before the word to turn it into a header row, or a |+ before the word to turn it into a table caption.

2. I think we should also add the second obvious example:

{|
|-
foo
| bar
|}

along with solution:

If this line is below a |- (table row start), then you might want to add a | before the word to turn it into a normal row.

3. What other circumstances might trigger this warning? (We could potentially add examples&solutions for those, too. Or at least point to Help:Tables.)

Arlolra (talkcontribs)

Worth noting that Parsoid currently generates differing output for example 2 there, so wouldn't help in surfacing those errors yet. See phab:T109897

SSastry (WMF) (talkcontribs)

Thanks @Quiddity (WMF) for the suggestion. I've revised the help text. Please check if reads better (and feel free to tweak for clarity).

@Arlolra, I suppose it is time to "fix" that in Parsoid. I'll take a look one of these days. Nick, till such time, your second example cannot be flagged by Linter.

Other examples are where fostering occurs in tables with HTML tags. You can come up with many examples. The scenarios are where content shows up outside <td>, <th>, or <caption> tags. I imagine templates are going to be sources of these markup errors.

Arlolra (talkcontribs)
There are no older topics