User talk:Jack who built the house

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
[edit]

e.g. special:diff/436937248 special:diff/436187300, linking to Commons:User:JWBTH/CD. :) --RZuo (talk) 06:53, 4 August 2020 (UTC)[reply]

@RZuo, thanks, fixed. Right, on Commons itself [[commons:]] links point to the "Commons" namespace, not Commons as the website. Jack who built the house (talk) 08:18, 4 August 2020 (UTC)[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/tr.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['tr'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['tr'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/sv.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['sv'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['sv'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/ru.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['ru'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['ru'] = {
  2. ISSUE: line 216 character 161: This character may get silently deleted by one or more browsers. - Evidence: "sd-removedata-help": "Обратите внимание, что всё, кроме глобальных настроек, удаляется только для текущего домена. Если вы использовали «Удобные обсуждения»‎ на других доменах, вам также придётся удалить данные оттуда. См. <a href=\"https://commons.wikimedia.org/wiki/Special:MyLanguage/User:Jack_who_built_the_house/Convenient_Discussions#Data\" target=\"_blank\">домашнюю страницу скрипта</a> о том, что, почему и как хранит скрипт, а также как удалить каждый элемент отдельно.",
  3. ISSUE: line 275 character 87: This character may get silently deleted by one or more browsers. - Evidence: "msd-error-editconflict-retry": "Просто нажмите «{{int:ooui-dialog-process-retry}}»‎.",
  4. ISSUE: line 315 character 52: This character may get silently deleted by one or more browsers. - Evidence: "footer-enablecd": "Включить «Удобные дискуссии»‎ на этой странице",
  5. ISSUE: line 316 character 54: This character may get silently deleted by one or more browsers. - Evidence: "footer-disablecd": "Выключить «Удобные дискуссии»‎ на этой странице"

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/pms.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['pms'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['pms'] = {
  2. ISSUE: line 39 character 129: This character may get silently deleted by one or more browsers. - Evidence: "section-unwatch-stillwatched": "<strong>Nòta:</strong> A ten ancor sot-euj sta session përchè a l'é contnùa ant la session « $1 » che a ten sot-euj.",
  3. ISSUE: line 61 character 40: This character may get silently deleted by one or more browsers. - Evidence: "thank-success": "La notìfica «Mersì » a l'é stàita mandà.",

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/nl.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['nl'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['nl'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/mk.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['mk'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['mk'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/lb.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['lb'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['lb'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/ko.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['ko'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['ko'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/ja.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['ja'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['ja'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/he.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['he'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['he'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/fr.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['fr'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['fr'] = {
  2. ISSUE: line 272 character 61: This character may get silently deleted by one or more browsers. - Evidence: "msd-error-editconflict-retry": "Cliquer simplement sur « {{int:ooui-dialog-process-retry}} ».",

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/en.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['en'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['en'] = {
  2. ISSUE: line 135 character 26: Duplicate key 'cf-reaction-signature'. - Evidence: "cf-reaction-signature": "No need to enter <kbd>$1</kbd>: the signature will be added automatically.",

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/de.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['de'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['de'] = {

Your CommonsMaintenanceBot (talk) at 10:05, 7 September 2020 (UTC).[reply]

A barnstar for you!

[edit]
The Technical Barnstar
For an excellent discussion gadget! Iniquity (talk) 14:38, 7 September 2020 (UTC)[reply]

A barnstar for you!

[edit]
The Technical Barnstar
Your Convenient Discussions gadget is awesome! Prahlad (talk to me / what I've done) 16:24, 3 November 2020 (UTC)[reply]
Thanks :-) Jack who built the house (talk) 00:30, 4 November 2020 (UTC)[reply]


Hi Jack who built the house, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:Jack who built the house/convenientDiscussions-i18n/fr.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 51 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 27: ['fr'] is better written in dot notation. - Evidence: convenientDiscussions.i18n['fr'] = {
  2. ISSUE: line 42 character 61: This character may get silently deleted by one or more browsers. - Evidence: "section-addsubsection-to": "Ajouter une sous-section à « $1 »",
  3. ISSUE: line 44 character 42: This character may get silently deleted by one or more browsers. - Evidence: "section-watch-success": "La section « $1 » a été ajoutée à votre liste de suivi.",
  4. ISSUE: line 45 character 44: This character may get silently deleted by one or more browsers. - Evidence: "section-unwatch-success": "La section « $1 » a été supprimée de votre liste de suivi.",
  5. ISSUE: line 46 character 49: This character may get silently deleted by one or more browsers. - Evidence: "section-unwatch-stillwatched": "<strong>Note :</strong> vous suivez toujours cette section car elle est incluse dans la section « $1 » que vous suivez.",
  6. ISSUE: line 47 character 49: This character may get silently deleted by one or more browsers. - Evidence: "section-watch-pagenotwatched": "<strong>Note :</strong> vous suivez la section mais pas la page. Afin que les nouveaux commentaires soient mis en évidence dans votre liste de suivi, ajoutez la page à la liste de suivi.",
  7. ISSUE: line 50 character 78: This character may get silently deleted by one or more browsers. - Evidence: "section-watch-error-maxsize": "Impossible de mettre à jour les paramètres : la taille des sections suivies dépasse la taille maximale. <span class=\"cd-notification-editWatchedSections\">Modifier la liste des sections</span> pour corriger cela.",
  8. ISSUE: line 65 character 77: This character may get silently deleted by one or more browsers. - Evidence: "thank-confirm": "Remercier {{gender:$2|}}$1 pour [$3 cette modification] ?",
  9. ISSUE: line 68 character 39: This character may get silently deleted by one or more browsers. - Evidence: "thank-success": "La notification « Merci » a été envoyée.",
  10. ISSUE: line 91 character 66: This character may get silently deleted by one or more browsers. - Evidence: "cf-headline-subsection": "Sujet/titre de la sous-section de « $1 »",
  11. ISSUE: line 92 character 58: This character may get silently deleted by one or more browsers. - Evidence: "cf-comment-placeholder-replytosection": "Répondre à « $1 »",
  12. ISSUE: line 114 character 724: This character may get silently deleted by one or more browsers. - Evidence: "cf-help-content": "<ul>\n<li>Saisissez <kbd>$1</kbd> pour [[mw:Special:MyLanguage/Help:Notifications/Mention|mentionner]] un utilisateur.</li>\n<li>Saisissez <kbd><nowiki>[[# pour insérer un lien vers un commentaire de cette section.
  13. \n
  14. Gardez Maj enfoncée en choisissant un élément de complétion automatique pour modifier le texte affiché (par exemple, [[Article|texte]]).
  15. \n
  16. Gardez Alt enfoncée en choisissant un élément de complétion automatique pour utiliser le texte qui suit comme texte affiché.
  17. \n
  18. Gardez Ctrl enfoncée en choisissant un utilisateur pour ajouter une ponctuation après le nom.
  19. \n\n

    Raccourcis :

    \n
      \n
    • Ctrl+Entrée — publier
    • \n
    • Échap — annuler
    • \n
    • Q (Ctrl+Alt+Q) — citer le texte sélectionné
    • \n
    \n

    Documentation du script

    ",</nowiki>
  20. ISSUE: line 127 character 87: This character may get silently deleted by one or more browsers. - Evidence: "cf-reaction-templateinheadline": "Ne pas utiliser des modèles dans les gros titres : cela casse les liens de section.",
  21. ISSUE: line 128 character 61: This character may get silently deleted by one or more browsers. - Evidence: "cf-reaction-signature": "Inutile de saisir <kbd>$1</kbd> : la signature sera ajoutée automatiquement.",
  22. ISSUE: line 149 character 100: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-noheadline-question": "Êtes-vous sûr{{GENDER:||e}} de vouloir publier le commentaire ?",
  23. ISSUE: line 150 character 91: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-empty": "Êtes-vous sûr{{GENDER:||e}} de vouloir publier un commentaire vide ?",
  24. ISSUE: line 151 character 111: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-long": "Ce commentaire dépasse $1 caractères. Êtes-vous sûr{{GENDER:||e}} de vouloir le publier ?",
  25. ISSUE: line 152 character 204: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-secondlevelheading": "Le commentaire contient le code de la section de second niveau. Si vous déplacez le code source, il vaut mieux utiliser la fonction standard de modification de source ; sinon, il pourrait être modifié de façon imprédictible. Êtes-vous sûr{{GENDER:||e}} de vouloir publier ce commentaire ?",
  26. ISSUE: line 153 character 89: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-delete": "Êtes-vous sûr{{GENDER:||e}} de vouloir supprimer le commentaire ?",
  27. ISSUE: line 156 character 84: This character may get silently deleted by one or more browsers. - Evidence: "cf-confirm-close": "Êtes-vous sûr{{GENDER:||e}} de vouloir fermer ce formulaire ? La saisie sera perdue.",
  28. ISSUE: line 162 character 245: This character may get silently deleted by one or more browsers. - Evidence: "dn-confirm": "Voulez-vous que Discussions pratiques vous envoie des notifications de bureau concernant les nouveaux commentaires sur les pages actuellement ouvertes, si elles vous sont adressées ou publiées dans des sections que vous suivez ? Vous pouvez désactiver cette fonctionnalité dans les paramètres.",
  29. ISSUE: line 171 character 70: This character may get silently deleted by one or more browsers. - Evidence: "deadanchor-searchinarchive": "Voulez-vous chercher dans l’archive ?",
  30. ISSUE: line 192 character 97: This character may get silently deleted by one or more browsers. - Evidence: "notification-toyou-desktop": "$1{{gender:$2|}} a répondu à votre commentaire$3 sur la page « $4 ».",
  31. ISSUE: line 193 character 75: This character may get silently deleted by one or more browsers. - Evidence: "notification-insection": "$1{{gender:$2|}} a répondu dans la section « $3 ».",
  32. ISSUE: line 194 character 83: This character may get silently deleted by one or more browsers. - Evidence: "notification-insection-desktop": "$1{{gender:$2|}} a répondu dans la section « $3 » sur la page « $4 ».",
  33. ISSUE: line 196 character 111: This character may get silently deleted by one or more browsers. - Evidence: "notification-newcomments-desktop": "$1 nouveau{{plural:$1||x}} commentaire{{plural:$1||s}}$2 sur la page « $3 »$4.",
  34. ISSUE: line 200 character 53: This character may get silently deleted by one or more browsers. - Evidence: "notification-part-insection": "dans la section « $1 »",
  35. ISSUE: line 209 character 123: This character may get silently deleted by one or more browsers. - Evidence: "sd-close-confirm": "Les paramètres n’ont pas été enregistrés. Êtes-vous sûr{{GENDER:||e}} de vouloir fermer la fenêtre ?",
  36. ISSUE: line 214 character 92: This character may get silently deleted by one or more browsers. - Evidence: "sd-reset-confirm": "Êtes-vous sûr{{GENDER:||e}} de vouloir réinitialiser les paramètres ? (Cliquez sur « {{int:convenient-discussions-sd-save}} » après la réinitialisation.)",
  37. ISSUE: line 216 character 100: This character may get silently deleted by one or more browsers. - Evidence: "sd-removedata-description": "Supprimer les données que les Discussions pratiques ont collectées : vos paramètres, les pages de discussion dernièrement visitées, les sections suivies et les brouillons de commentaires non envoyés.",
  38. ISSUE: line 218 character 212: This character may get silently deleted by one or more browsers. - Evidence: "sd-removedata-confirm": "Cela supprimera définitivement vos paramètres, vos pages de discussion dernièrement visitées, vos sections suivies et vos brouillons de commentaire non envoyés. Voulez-vous continuer ?",
  39. ISSUE: line 225 character 55: This character may get silently deleted by one or more browsers. - Evidence: "sd-alwaysexpandadvanced": "Développer la section « {{int:convenient-discussions-cf-advanced}} » lors de votre réponse.",
  40. ISSUE: line 226 character 67: This character may get silently deleted by one or more browsers. - Evidence: "sd-autocompletetypes": "Activer la complétion automatique pour :",
  41. ISSUE: line 227 character 50: This character may get silently deleted by one or more browsers. - Evidence: "sd-autocompletetypes-mentions": "les mentions ;",
  42. ISSUE: line 228 character 66: This character may get silently deleted by one or more browsers. - Evidence: "sd-autocompletetypes-commentlinks": "les liens de commentaire ;",
  43. ISSUE: line 229 character 53: This character may get silently deleted by one or more browsers. - Evidence: "sd-autocompletetypes-wikilinks": "les liens wiki ;",
  44. ISSUE: line 230 character 50: This character may get silently deleted by one or more browsers. - Evidence: "sd-autocompletetypes-templates": "les modèles ;",
  45. ISSUE: line 233 character 84: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultcommentlinktype": "Type de lien par défaut à copier en cliquant sur « {{int:convenient-discussions-cm-copylink}} » dans un menu de commentaire",
  46. ISSUE: line 234 character 54: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultcommentlinktype-radio-diff": "lien diff ;",
  47. ISSUE: line 235 character 58: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultcommentlinktype-radio-wikilink": "lien wiki ;",
  48. ISSUE: line 239 character 84: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultsectionlinktype": "Type de lien par défaut à copier en cliquant sur « {{int:convenient-discussions-sm-copylink}} » dans un menu de section",
  49. ISSUE: line 240 character 58: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultsectionlinktype-radio-wikilink": "lien wiki ;",
  50. ISSUE: line 242 character 93: This character may get silently deleted by one or more browsers. - Evidence: "sd-defaultsectionlinktype-help": "Pour copier un lien d’un type différent, cliquer sur « {{int:convenient-discussions-sm-copylink}} » en gardant la touche Maj appuyée.",
  51. ISSUE: line 251 character 138: This character may get silently deleted by one or more browsers. - Evidence: "sd-insertbuttons-help": "Utiliser <code>+</code> pour spécifier un endroit où le curseur devrait être mis après avoir inséré le texte ; par exemple, <code><nowiki>{{+}}. Utiliser ; pour spécifier le texte affiché si vous voulez qu’il soit différent de celui inséré ; par exemple, <code>+</code>;<code />. Utiliser \\ avant les caractères susmentionnés pour les intégrer en l’état ; par exemple, 2\\+2. Les boutons peuvent être glissés et relâchés.",</nowiki>
  52. ISSUE: line 257 character 89: This character may get silently deleted by one or more browsers. - Evidence: "sd-notificationsblacklist": "Ne pas me notifier des commentaires de ces utilisateurs :",
  53. ISSUE: line 260 character 47: This character may get silently deleted by one or more browsers. - Evidence: "sd-signatureprefix": "Préfixe de signature :",
  54. ISSUE: line 272 character 69: This character may get silently deleted by one or more browsers. - Evidence: "ewsd-error-maxsize": "Impossible de mettre à jour les paramètres : la taille de la liste des sections suivies dépasse la taille maximale. Réduire la taille de la liste pour corriger cela.",
  55. ISSUE: line 274 character 124: This character may get silently deleted by one or more browsers. - Evidence: "ewsd-close-confirm": "La liste des sections suivies n’a pas été enregistrée. Êtes-vous sûr de vouloir fermer la fenêtre ?",
  56. ISSUE: line 280 character 96: This character may get silently deleted by one or more browsers. - Evidence: "msd-targetpage": "Saisissez le nom de la page de discussion vers laquelle déplacer le sujet :",
  57. ISSUE: line 282 character 74: This character may get silently deleted by one or more browsers. - Evidence: "msd-summaryending": "Résumé de modification (sera ajouté au standard) :",
  58. ISSUE: line 282 character 74: Too many errors. (85% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 14:41, 7 December 2020 (UTC).[reply]

A barnstar for you!

[edit]
The Brilliant Idea Barnstar
Огромное спасибо! 👍 Не представляю, как бы без него жил в Википедии! (Представляю, конечно, сильно неудобнее!) ·Carn 14:41, 18 December 2020 (UTC)[reply]

A barnstar for you!

[edit]
The Technical Barnstar
Большущее спасибо за скрипт и быстрые ответы на сообщения об ошибках (да и в принципе исправление багов)! 𝟙𝟤𝟯𝟺𝐪𝑤𝒆𝓇𝟷𝟮𝟥𝟜𝓺𝔴𝕖𝖗𝟰 (𝗍𝗮𝘭𝙠) 22:01, 8 March 2021 (UTC)[reply]

Code error

[edit]

I keep getting this error - can you tell me how to stop it? Uncaught TypeError: Cannot read properties of undefined (reading 'map') from https://commons.wikimedia.org/w/index.php?title=User:Jack_who_built_the_house/convenientDiscussions.js&action=raw&ctype=text/javascript at line 7:256531 TypeError: Cannot read properties of undefined (reading 'map') at Comment_Comment.getAdjustedRects (https://commons.wikimedia.org/w/index.php?title=User:Jack_who_built_the_house/convenientDiscussions.js&action=raw&ctype=text/javascript:7:256531) at Comment_Comment.getOffset (https://commons.wikimedia.org/w/index.php?title=User:Jack_who_built_the_house/convenientDiscussions.js&action=raw&ctype=text/javascript:7:258295) at Comment_Comment.setLayersOffsetProperty (https://commons.wikimedia.org/w/index.php?title=User:Jack_who_built_the_house/convenientDiscussions.js&action=raw&ctype=text/javascript:7:259551) at Comment_Comment.configureLayers (https://commons.wikimedia.org/w/index.php?title=User:Jack_who_built_the_house/convenientDiscussions.js&action=raw&ctype=text/javascript:7:261975) at Comment_Comment.highlightHovered (https://commons.wikimedia.org/w/in

Gbawden (talk) 14:41, 23 April 2022 (UTC)[reply]

Про сокращение строки перевода про боковую панель в translatewiki

[edit]

Приветствую, Jack who built the house! Пишу на вашей странице обсуждения здесь, а в translatewiki, по известным причинам. Спасибо за скриншот, иллюстрирующий использование строки, и за внесение исправления!

Обычно я ратую за сохранение глаголов в переводах, но тут случай несколько другой: как вы смотрите на идею обсуждения других вариантов перевода? Исходя из вашего скриншота, вариант «переместить вбок», как мне видится, тоже не влезет в отведённое поле. Я предложил бы что-то из серии:

1) в боковой панели
2) в панели
3) в стороне/в сторону
3) сбоку

Интересно было бы узнать, что вы думаете об этом. — Pacha Tchernof (talk) 20:13, 5 August 2022 (UTC)[reply]

CD

[edit]

Приветствую!

1) https://i.imgur.com/A4pBQoD.png (возможно, связано с @ником без ссылки) -- нет, повторялось многократно с любым сообщением, в тч после перезагрузки страницы.

2) Не баг, но хотелось бы совместимости с ru:u:Jaguar_K/Gadget-CollapsibleSidebar.js и подобным. Проблема в оглавлении, что в левом меню - оно не появляется, если при запуске CD левая панель скрыта, а затем раскрыта. Впрочем, можно оглавление в принципе отвязать от необходимости левой панели.

3) Хотелось бы, чтобы в СН/вкладе/etc CD давал ссылки в стиле инструментов обсуждения, а не в родном формате для того, чтобы не ждать обработки страницы, а сразу перейти к сообщению.

4) Не показывает (сообщение) для переименованных. Так же, непонятно когда показывает (сообщение) во вкладе.

5) AK подпись в t:hide считается за подпись сообщения.

6) Неплохо бы настройку, чтобы "перейти к теме или искать в архиве" можно было вернуть в заголовок страницы. В системном сообщении очень мелко, и ссылки близко друг к другу, легко промахнуться. Jaguar K (talk) 17:05, 4 January 2023 (UTC)[reply]

1) Исправлено ещё в начале января.
2) При случае гляну.
3) Не получится. В СН мы знаем только дату и автора сообщения, а для ссылки в формате DT нужно знать ещё, на что оно отвечает и другие факторы.
4) Не решить. Во вкладе показывает на основе ряда факторов, таких как название страницы, наличине флага малой правки, число добавленных байт, описание правки.
5) Спасибо, посмотрю.
6) Вряд ли. Jack who built the house (talk) 07:12, 13 February 2023 (UTC)[reply]
6) Вряд ли. - почему? И еще: importScript('u:Jack who built the house/proceedToArchive.js'); можно изменить, чтобы работал так же, как CD (сразу давал ссылку на архив, если он найден)?
7) ru:Википедия:Форум/Правила#Википедия:Удаление_страниц:_«администратор»_заменить_на_«участник,_подводящий_итог» раздел Итога.
итог Cantor ru:Special:Diff/129736472 ru:Википедия:Форум/Правила#c-Yellow_Horror-20230409174300-Итог_2
доп. Cantor ru:Special:Diff/129367165 ru:Википедия:Форум/Правила#c-Jaguar_K-20230321213000-Yellow_Horror-20230409174300
Корявое определение (со стороны инструментов википедии, видимо) - заголовки верные, сообщения написаны как обычно (уже здесь неправильно). CD не позволяет ответить. Мб можно поправить (или разработчиками DT сообщить)? Jaguar K (talk) 14:24, 14 April 2023 (UTC)[reply]
6. Скриптом proceedToArchive я уже не буду заниматься. Настройка для места вывода сообщения — странный зверь. Шапка страницы — неудачное место для вывода сообщений от скриптов, там в норме только непосредственный контент страницы. Jack who built the house (talk) 21:44, 19 April 2023 (UTC)[reply]
8) ссылки на разделы ломаются со временем><--Jaguar K (talk) 17:33, 16 April 2023 (UTC)[reply]
Это в движке ломаются. CD сообщение по этой ссылке находит :) Jack who built the house (talk) 21:41, 19 April 2023 (UTC)[reply]
5 исправил. Jack who built the house (talk) 20:56, 30 April 2023 (UTC)[reply]

CD tag on jawiki

[edit]

Hi Jack, I created the convenient-discussions edit tag on the Japanese Wikipedia. I'd appreciate it if you could make the script compatible with it when you have time. Dragoniez (talk) 12:28, 24 September 2023 (UTC)[reply]

@Dragoniez: Thank you! I've created a configuration file for Japanese Wikipedia, ja:利用者:Jack who built the house/convenientDiscussions.js, the tag name is written there. Info about configuration files. If you ever decide to make CD into a gadget, you can use this file as a basis. Jack who built the house (talk) 13:19, 24 September 2023 (UTC)[reply]
Just letting you know, the edit tag has been working like a charm since you generated the config page for us. Thanks! Dragoniez (talk) 13:53, 30 September 2023 (UTC)[reply]
That's great! Too few edits though 😹 Jack who built the house (talk) 14:36, 30 September 2023 (UTC)[reply]

CD on non-Wikimedia wikis

[edit]

Is this supported? I'm running CD on a non-WMF wiki and some of the icons don't show up (even when using a configuration file). Leaderboard (talk) 11:28, 20 October 2023 (UTC)[reply]

@Leaderboard: Oh, good to hear from somebody running CD on a non-WMF wiki. I aim to support it outside of WMF, although my efforts in that direction were limited to this point. Can you show me an example page on the wiki? If you want, we can talk privately. Jack who built the house (talk) 11:37, 20 October 2023 (UTC)[reply]
some of the icons don't show up
Icons are generally loaded as OOUI modules. If some modules are missing, you would generally get an error in the JavaScript console (F12 → Console). Icons can be missing because of an old version of MediaWiki. Jack who built the house (talk) 12:13, 20 October 2023 (UTC)[reply]
@JWBTH: , the website is here (you'll need to create an account on the forum): https://www.betaarchive.com/wiki/ Leaderboard (talk) 18:34, 20 October 2023 (UTC)[reply]
Thanks for the response BTW and fixing the main issue I had. Leaderboard (talk) 13:22, 22 October 2023 (UTC)[reply]
BTW, you could speed up the loading of CD by making it into a gadget loaded by default. See how it is done in azwiki: 1 (+ add |default after ResourceLoader to make the gadget load by default), 2, 3. Jack who built the house (talk) 15:53, 22 October 2023 (UTC)[reply]

A question about the translation of the Convenient Discussions

[edit]

Hello Jack! I'm reviewing the Chinese translation of the tool (the previous translator must have used a machine translation, making the translation very bad), and I'd like to ask if the translation of this message can include Chinese? The Chinese date format is like "2023年12月17日上午10:40" ("17 December 2023, 10:40 AM"), I don't whether the translation "YYYY年M月D日Ah:mm" is correct. Thanks! BlackShadowG (talk) 15:49, 17 December 2023 (UTC)[reply]

@BlackShadowG: Hi, thank you for your contributions! Sorry for the delay. Yes, it can be used!
I went to Chinese Wikipedia and made a screenshot of a comment that uses the message you translated. If the date is correct, then everything is fine. Jack who built the house (talk) 03:51, 25 December 2023 (UTC)[reply]
Oh, it's corrct, thanks for the response! BlackShadowG (talk) 07:37, 5 January 2024 (UTC)[reply]
@JWBTH: Sorry for bothering you again. I have another question: When using this tool on the Chinese Wikipedia, the settings display the message "The current wiki doesn't have an outdent template specified." Could you please guide me on how to specify this template for the Chinese Wikipedia? Thanks again. BlackShadowG (talk) 12:46, 5 January 2024 (UTC)[reply]
@BlackShadowG: You will need to create a configuration file for Chinese Wikipedia using these instructions. You may put it in your user space on zh.wikipedia.org and then contact me, so that I specify it as the configuration file for Chinese Wikipedia. Alternatively, if your community wants to, you may make Convenient Discussions a gadget for everybody (the content of the configuration file will be the content of the gadget). Either way, with a configuration file, the script will run smoother on your wiki. Good luck! Jack who built the house (talk) 16:47, 5 January 2024 (UTC)[reply]
@JWBTH: I've created one on w:zh:User:BlackShadowG/convenientDiscussions.js, could you please specify it as a configuration file for Chinese Wikipedia? I think it will be more persuasive to encourage our community to embrace Convenient Discussions as a gadget once it has been configured for Chinese Wikipedia. Thanks! BlackShadowG (talk) 12:49, 6 January 2024 (UTC)[reply]
@BlackShadowG: could you please specify it as a configuration file for Chinese Wikipedia
Done! Jack who built the house (talk) 13:35, 6 January 2024 (UTC)[reply]


Unwanted pings on en.wikipedia

[edit]

Help!

I received an unnecessary notification with this link over on en.wikipedia. I contacted the author of that page about it, User:Muhandes said it was due to a bug in the Convenient Converations script. So I'm bringing it here.

Why was I pinged, and what is a "TUSC token"? -- Mikeblas (talk) 00:16, 11 November 2024 (UTC)[reply]

Hello. As far as I can see, you were pinged by this edit.
  1. This edit was made by OneClickArchiver, not Convenient Discussions.
  2. I think it's not OneClickArchiver's fault.
  3. The reason you were pinged is that the archiver's signature was in the edit, as well as your nickname. MediaWiki interpreted this as the fact that the archiver wrote the message and pinged you.
Jack who built the house (talk) 01:16, 11 November 2024 (UTC)[reply]
To sort this out, the issue with CD was that from some unknown reason, responses which I made with CD on my talk page went to the top discussion instead of the one I intended. You can see these edits here and here. This resulted in a wrong ping to "TUSC token" which is the top discussion on my talk page. I then had to move them to their correct position (this edit and this) which resulted with the correct ping. This has nothing to do with why using OneClickArchiver results in a ping, which is something new to me but may have always been the case. Muhandes (talk) 07:40, 11 November 2024 (UTC)[reply]
Jack who built the house Thanks for the explanation! Muhandes, it looks like your diagnosis was wrong, and your dismissal of my query was also not productive. Are you able to help me figure out why your edits were pinging me unnecessarily? I still don't know what a "TUSC token" is, or why I should be notified that you (or I?) have one. What bug should OneClickARchiver fix so that other users aren't befuddled by these rapid-fire irrelevant pings? -- Mikeblas (talk) 01:27, 12 November 2024 (UTC)[reply]
@Mikeblas: which part of my diagnosis is wrong? You got pinged because of OneClickArchiver and you got the extra "TUSC token" ping due to a CD irregularity. I didn't see anyone contradicting this so far. I didn't dismiss any of your queries and I told you this exact analysis immediately as you asked. The CD issue does not repeat because I am now using the CD UI differently, replying to messages instead of replying to a topic. I also use OneClickArchiver.quite rarely. Muhandes (talk) 08:00, 12 November 2024 (UTC)[reply]
@Muhandes: By the way, if you try to use "Reply to section" with this topic and press "View changes" instead of "Reply"
– will the diff show the reply in a wrong place? Jack who built the house (talk) 11:58, 12 November 2024 (UTC)[reply]
@JWBTH: Yes, I managed to replicate the bug exactly. It only happens in one section in my page, this one. If I click "Reply to section" and then "view changes", I get the diff on the wrong section. Here is a screen capture, and you can see even the edit summary is /* Better source request for File:Thapar Institute of Engineering and Technology University logo.png */ reply but the diff is on the wrong section
Muhandes (talk) 23:10, 12 November 2024 (UTC)[reply]
That's very helpful! Especially the screenshot. I could reproduce the issue, and now I see the cause: it's the "Comments in Local Time" gadget. It conflicts with CD. You can
Meanwhile, I'll try to figure out why that script causes CD to post in the first section... Jack who built the house (talk) 00:31, 13 November 2024 (UTC)[reply]
(Well, it was kind of funny. Since CD didn't see the comments because of the gadget that changed the format of their signatures, CD assumed that the first section is the right one, because it doesn't have comments as well...) Jack who built the house (talk) 00:51, 13 November 2024 (UTC)[reply]
Disabling the "Comments in Local Time" gadget resolved the issue. Frankly, since the issue did not occur when using "reply to comment", only on "reply to section", I was not even planning to report it. Thanks to Mikeblas for insisting. Muhandes (talk) 07:46, 13 November 2024 (UTC)[reply]
Sorry, I guess I'm misunderstanding the diagnosis and your statements.
Your two edits last week were the only time I've ever been pinged with a "TUSC token" warning, or when an old comment I made was archived. Were this a bug, seems like it might've happened more often, and with more users than just yourself. On your en.talkpage, you said the issue was "failure of the Convenient Discussions script, also beyond my control", but here Jack is saying that the issue wasn't caused by the CD script.
Can either of you clarify the cause of these spurious pings? How can they be eliminated? Nobody wants to get irrelevant pings, and nobody wants to be pinged for comments they made many months ago as they're being archived. -- Mikeblas (talk) 16:18, 12 November 2024 (UTC)[reply]
You've been pinged by the archivation (if you were) because of the archivation edit that by a rare coincidence looked like a legitimate comment pinging you. You couldn't be pinged by two edits posted with CD, because you weren't mentioned in them. Jack who built the house (talk) 17:14, 12 November 2024 (UTC)[reply]
Here's the message I saw, which Muhandes said was due to CD. That's why I've asked about it here. I was also pinged by the archiving of another page, and I linked that screen shot below. -- Mikeblas (talk) 19:52, 13 November 2024 (UTC)[reply]
Ah, ok. Jack who built the house (talk) 20:37, 13 November 2024 (UTC)[reply]
@Mikeblas Two issues were at play:
  • The first was erroneous "TUSC token" pings. This resulted from a well-documented conflict between scripts, which surfaced unexpectedly. I resolved the conflict in my account, so it’s no longer relevant, and I believe JWBTH is looking into a permanent fix.
  • The second, unrelated issue involves pings triggered by archiving with OneClickArchiver. This might be normal behavior if the archiver made the last comment on the thread. Next time I need manual archiving, I'll try asking someone else to do it to see if it prevents the pings.
This should be a satisfactory result. Have fun editing. Muhandes (talk) 07:59, 13 November 2024 (UTC)[reply]
Thanks for the clarification! I'm glad fixes are being made. -- Mikeblas (talk) 19:44, 13 November 2024 (UTC)[reply]
Oh, that's a bug, thanks for the report, I'll look into it! It's a separate issue from pings though. As I understand, Mikeblas is talking about pings, not notifications occurring when someone edits your talk page. Jack who built the house (talk) 10:35, 12 November 2024 (UTC)[reply]
I'm talking about "alerts", like this one. The TUSC token warning showed up in the same list, but I don't think I have a screenshot. -- Mikeblas (talk) 19:42, 13 November 2024 (UTC)[reply]