21:
84:
244:
below the thread → add the person's linked username followed by your signature below the duplicated section header → save the page → likewise immediately undo your edit. In this way, an edit conflict is unlikely to occur, and when the software informs the user of your mention, it will still link to
200:
instead of the requisite four , resulting in only a timestamp), or fail to successfully link the intended pingee's user page in the same edit, they will not receive a ping. Many users try to fix this in the next or a later edit by adding the signature they forgot, fixing their botched signature, or
268:. Be aware that notifications generated using this method will not link the user to the specific section of the page involved, and that you will not be notified as to whether the ping was successful or not.
260:). The edit you invoke to leave such an edit summary can be used to make cosmetic fixes to the botched or missing signature or username mention that resulted in the failed ping (as noted, these repairs will
221:): edit the page → skip a line using a carriage return → add the person's linked username followed by your signature → save the page, and then immediately undo your edit, manually or by a
478:), check the page history to see whether the user attempted to fix a botched ping by any invalid method explained above. If they did, you might point them to this page. The template
354:
If you mis-signed in a thread with the section header "How do I fix my ping?" – at a 'high-traffic page', where your further edits are likely to be interrupted by, or cause, an
256:
ping, an easy workaround, for pinging up to five editors, is to simply mention them in an edit summary while you edit the page involved (by linking to their user page, e.g.,
214:, this time successfully linking the user's user page and signing your post. There are various suggested methods to do so, depending on if the page is high-traffic or not.
446:
To refer the pinged user(s) to a particular section of the page, link it in the same edit summary (this is especially advisable for high volume pages): ]; see ]
420:, instead of fixing the in-text ping itself, an alternative method that provides some (but not all) of the same features, is to notify (up to five) users in an
29:
398:
Immediately click edit for the duplicate section you created, cut it entirely including the section header, and save (alternatively, you can
377:
Copy the existing section header, and paste it below the end of the thread, followed by the "pingee's" linked username and four tildes:
281:
If you mis-signed in a thread at a 'low-traffic page' – where your further edits are unlikely to be interrupted by, or cause, an
465:
349:
336:
Immediately click edit again for the section, cut what you placed in the last edit, and save (alternatively, you can
37:
411:
276:
207:
work – because any change must be parsed as an addition of new lines of text, not a change to existing lines.
517:
475:
511:
92:
Attempting to fix a failed ping in a later edit by adding your signature or fixing a botched username will
549:
504:– for informing users that their attempted fix of a botched ping will not work and links to this page
240:
Alternatively, for high-traffic pages subject to edit conflicts: copy and then paste the existing
507:
305:
301:
109:
421:
363:
271:
470:
Finally, if you see a post in which markup is present for you to have been pinged, but you
429:
371:
294:
125:
117:
59:
438:
Scroll down to the edit summary field and add a link to the user’s page anywhere in it: ]
196:
If you forget to sign your post, fail to sign properly (e.g., you accidentally place five
8:
121:
41:
359:
355:
282:
245:
the correct section of the page because the section header you placed and then removed
218:
51:
498:
481:
435:
Make an edit in the section (such as fixing your failed mention or botched signature)
226:
162:
533:
474:(and you have not turned off the default of receiving notification of "Mentions" at
135:
This can be done by copying and pasting the markup from the user's signature, e.g.,
36:
It explains concepts or processes used by the
Knowledge community. It is not one of
66:
530:– technical details of the MediaWiki software providing the notifications facility
286:
527:
399:
337:
222:
543:
174:
257:
241:
113:
458:
Note that the notification produced by this type of ping will link to the
217:
If not high-traffic (i.e., there is little chance of having or causing an
186:
144:
459:
462:
of the edit you've made instead of the message on the talk page.
310:
265:
211:
225:
from the page history. You might use the following back-to-back
102:
to an edit summary, or use one of the methods described below.
318:
197:
300:
Place your cursor at the end of the existing text and click
289:
that is not in the midst of wide discussion by many users):
139:, or by placing various templates for this purpose, such as
489:
210:
Therefore, to fix the problem, you will have to add a
151:
which links just the user's name, or, for prefixing "
120:
when editing any talk page or page in the
Knowledge
536:– overview of the MediaWiki notifications systems
541:
510:– Knowledge's information page on the system; (
405:(suggested edit summary: "Completing ping fix")
343:(suggested edit summary: "Completing ping fix")
169:, commonly placed with its template shortcuts:
157:" before your post, you might use the template
317:Paste the "pingee's" linked username and four
249:to the one under which you originally posted.
98:work. Instead, reference the user by adding
514:– where feedback and bugs can be reported)
432:link, targeting just the thread involved)
374:link, targeting just the thread involved)
297:link, targeting just the thread involved)
466:Advising users of failed repair attempts
201:by fixing the user name link. This does
518:Special:Preferences#mw-prefsection-echo
476:Special:Preferences#mw-prefsection-echo
441:(suggested edit summary: "Fixing ping")
393:(suggested edit summary: "fixing ping")
331:(suggested edit summary: "fixing ping")
542:
449:suggested edit summary: "Fixing ping")
524:preferences related to notifications
264:fix the ping) or to make some other
78:
40:, and may reflect varying levels of
15:
13:
38:Knowledge's policies or guidelines
14:
561:
108:Pinging another user through the
417:
370:Click edit (we suggest using an
252:Instead of repairing the failed
82:
19:
428:Click edit (we suggest using a
402:your edit in the page history)
340:your edit in the page history)
293:Click edit (we suggest using a
486:may be used for this purpose.
472:did not receive a notification
229:when doing this operation: 1)
1:
308:(or other method to invoke a
7:
380:== How do I fix my ping? ==
10:
566:
49:
350:High-traffic pages method
272:Step-by-step instructions
412:Edit summary alternative
277:Low-traffic pages method
90:This page in a nutshell:
508:Knowledge:Notifications
285:(such as an article's
130:in the same saved edit
28:This help page is a
362:, a section of the
235:Completing ping fix
124:, and successfully
112:system is done by
451:
443:
430:side edit section
407:
395:
345:
333:
295:side edit section
156:
126:signing your post
106:
105:
77:
76:
557:
550:Knowledge how-to
534:mw:Notifications
503:
497:
485:
450:
447:
442:
439:
406:
403:
394:
391:
358:(such as at the
344:
341:
332:
329:
191:
185:
179:
173:
167:
161:
152:
149:
143:
101:
86:
85:
79:
69:
62:
23:
22:
16:
565:
564:
560:
559:
558:
556:
555:
554:
540:
539:
501:
495:
492:
479:
468:
448:
440:
418:described above
414:
404:
392:
385:
352:
342:
330:
324:
307:
303:
279:
274:
236:
232:
192:
189:
183:
180:
177:
171:
168:
165:
159:
155:
150:
147:
141:
138:
99:
83:
73:
72:
65:
58:
54:
46:
45:
20:
12:
11:
5:
563:
553:
552:
538:
537:
531:
528:mw:Manual:Echo
525:
515:
505:
491:
488:
467:
464:
456:
455:
452:
444:
436:
433:
413:
410:
409:
408:
396:
390:Save the page
388:
387:
386:
383:
381:
375:
351:
348:
347:
346:
334:
328:Save the page
326:
322:
315:
298:
278:
275:
273:
270:
242:section header
234:
230:
227:edit summaries
182:
170:
158:
153:
140:
136:
104:
103:
87:
75:
74:
71:
70:
63:
55:
50:
47:
35:
34:
26:
24:
9:
6:
4:
3:
2:
562:
551:
548:
547:
545:
535:
532:
529:
526:
523:
519:
516:
513:
512:its talk page
509:
506:
500:
494:
493:
487:
483:
477:
473:
463:
461:
454:Save the page
453:
445:
437:
434:
431:
427:
426:
425:
423:
419:
401:
397:
389:
382:
379:
378:
376:
373:
369:
368:
367:
365:
361:
357:
356:edit conflict
339:
335:
327:
320:
316:
313:
312:
299:
296:
292:
291:
290:
288:
284:
283:edit conflict
269:
267:
263:
259:
255:
250:
248:
247:was identical
243:
238:
228:
224:
220:
219:edit conflict
215:
213:
208:
206:
205:
199:
194:
188:
176:
164:
146:
133:
131:
127:
123:
119:
115:
111:
110:notifications
97:
96:
91:
88:
81:
80:
68:
64:
61:
57:
56:
53:
48:
43:
39:
33:
31:
25:
18:
17:
521:
471:
469:
457:
422:edit summary
415:
372:edit section
364:Village pump
353:
309:
280:
266:minor change
261:
258:User:Example
253:
251:
246:
239:
216:
209:
203:
202:
195:
134:
129:
107:
94:
93:
89:
30:how-to guide
27:
520:– links to
231:Fixing ping
154:@Username:
60:WP:PINGFIX
366:, etc.):
287:talk page
122:namespace
118:user page
67:H:PINGFIX
52:Shortcuts
42:consensus
544:Category
499:Ping fix
490:See also
482:ping fix
360:Teahouse
311:new line
212:new line
163:Reply to
254:in-text
114:linking
400:revert
384:] ~~~~
338:revert
319:tildes
302:return
223:revert
198:tildes
116:their
306:enter
233:; 2)
522:your
460:diff
323:~~~~
175:Ping
416:As
262:not
237:.
204:not
181:or
132:.
95:not
546::
502:}}
496:{{
484:}}
480:{{
424::
325:):
193:.
190:}}
187:Yo
184:{{
178:}}
172:{{
166:}}
160:{{
148:}}
142:{{
128:,
321:(
314:)
304:/
145:U
137:]
100:]
44:.
32:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.