Help:DiscussionTools/Why can't I reply to this comment?/nb

Diskusjonssider har ingen begrensninger på tilgjengelige formateringsalternativer. Selv om Diskusjonsverktøy er i stand til å gjenkjenne diskusjonsinnlegg i de fleste tilfeller, finnes det situasjoner hvor det er tvetydig, eller umulig, å avgjøre om en del av en side er et innlegg eller hvor svaret burde legges til. Når riktig behandling av et innlegg er uklart vil verktøyet avstå fra å svare heller enn å gjette. På denne siden unngås det å rote til siden enda mer.

Denne siden dokumenterer noen av de feilene du kan komme over, foruten årsaken og løsningen på problemet.

Ingen "svar"-lenke
Dette forekommer når signaturen etter et innlegg ikke oppdages.

Usignert innlegg
Dette er kanskje opplagt, men er tatt med for å behandle situasjonen fullstendig. Hvis en kommentar ikke er signert, vil signaturen ikke bli oppdaget. Diskusjonssider kan inneholde innhold som ikke er diskusjonsinnlegg som ikke lett kan skilles fra usignerte innlegg. (F.eks. forskjellige overskriftsmaler) Å legge til svar-lenker til slikt innhold ville føre til uventede resultater.

Hvis noen andre allerede har svart på innlegget manuelt, vil deres svar og det opprinnelige usignerte innlegget bli behandlet som et innlegg over flere linjer, noe som kan føre til uventede resultater.

Uten dato og tid
Hvis en signatur mangler dato og tid, vil innlegget ikke oppdages. Slike signaturer er ikke mulig å skille fra at noen nevner andre brukere i sine innlegg, og det å legge til svar-lenker vil ofte føre til uventede resultater.

Den vanligste årsaken til dette er når noen legger en signatur til et usignert innlegg uten å legge til dato og tid. Maler som  gjør det mulig å kopiere tid og dato fra sidehistorikken.

Unrecognized namespace
The Reply tool is available in most of the namespaces that are used for discussions, but not in all namespaces. When this is the problem, you will be looking at a page that does not have "talk" in its namespace (e.g., ), and you will not see the "reply" link anywhere on the page.

Usually, it follows your wiki's configuration for the Signature tool in the full-page editor. In particular, it may not be available in the  (also called  ) namespace. It can be enabled in any reasonable namespace. If you need it to work in a different namespace, then ask the Editing team for help.

Ambiguous "unsigned" templates
When a template is used to sign an unsigned comment, the template must output the following:


 * A link to a user's user page, talk page or contributions page
 * A date and time (a "timestamp"), in the same format as in signatures, including the timezone in parentheses
 * The user page, talk page or contributions page link must be before the date and time (like in normal signatures)

Non-standard date or time format
If someone signs their comments with a different date or time format than the default for the wiki, their comments won't be detected.

Sometimes editors may accidentally edit another signature when adding their comments manually, breaking the format.

Another common case is a signature added to an unsigned comment without the timezone indicator (e.g. "(UTC)"), or with a different timezone than the wiki uses.

No link to the user page
Signatures must include a link to the user page, talk page or contributions of a user.

The "reply" link cannot be used to reply to this comment
You'll see this error message when the comment appears to be transcluded from another page, but the tool can't determine from which page, and therefore can't determine where to add your reply. This can be caused by:

Accidental complex transclusion
Parsoid transclusions must be well-formed HTML fragments. When the wikitext of a transcluded page doesn't generate well-formed HTML (e.g. has unclosed tags, or it generates a table row without a table), the transclusion will be extended to cover wikitext belonging to the transcluding page (or other transcluded pages).

For example, if a subpage transcluded earlier on the page has an unclosed tag, all following transcluded subpages will be marked as part of the same transclusion, until the tag is closed (or until the end of the page).

DiscussionTools only supports following simple transclusions (which consist of exactly one transcluded page, and which don't leak to surrounding wikitext).

You can often debug this by opening the page for editing in visual editor (even if visual editor is disabled in that namespace, you can do it by adding  to the URL), clicking in the offending fragment of the page, and looking at the "sidebar" in the template dialog to see if it includes more than one page or "Content" transclusions.

Wrapper templates
When a fragment of a discussion is wrapped in templates like e.g. +, the wrapped comments can't be replied to. DiscussionTools relies on Parsoid to add replies into the HTML document, but contents of transclusions are only editable as wikitext.

Usually wrapper templates are used to archive or end a discussion, so it's rarely a problem that you can't reply to these comments. If someone adds a wrapper template to a comment while you are replying to that comment, you will see an error message and will not be able to post your reply with DiscussionTools.

Sometimes an entire page may be wrapped in a template to add a decorative frame or background. In these cases, plain HTML syntax may be used instead.

Comments in template arguments
Comment which appears in template arguments, for example, can not be replied to.

Nested transclusion or parser function syntax
When a discussion page has separate subpages for e.g. each month, dynamic transclusions depending on the current date are often used to only transclude the latest few subpages, without the need to manually archive them.

When the subpage transclusion is inside a parser function like, DiscussionTools can only see the parser function, and can't determine which page is transcluded within it.

You can fix it by putting the conditional parser functions inside the transclusion syntax instead. See example.

Could not find the comment you're replying to on the page
Usually this error message indicates that someone else removed the comment from the page while you were reading it. It might have been reverted, archived, moved to another discussion page, or the signature might have been changed (e.g. if someone commented while logged out and then corrected the username, or if they expanded their comment and signed it again).

If you can still see the comment after refreshing and purging the page, and you still receive this error, it might indicate a bug in Parsoid causing it to render the page differently from the PHP parser (DiscussionTools uses Parsoid internally to add new comments). Please file a task!

Comments on this page can't be replied to because of an error in the wikitext
You'll see this error message when there is a lint error on the page caused by fostered content. Editing these pages using tools that rely on Parsoid, such as DiscussionTools or VisualEditor, can cause the content to be corrupted (large fragments of the page become duplicated).

To resolve this, you can fix the lint error in the wikitext editor. The error message includes some links that hopefully are helpful.