diff --git a/dsl/100625_human_info_sample.csv b/dsl/100625_human_info_sample.csv new file mode 100644 index 0000000..980c43e --- /dev/null +++ b/dsl/100625_human_info_sample.csv @@ -0,0 +1,59686 @@ +"id","task_title","comment_text","date_created","AuthorPHID","TaskPHID","comment_type","text_for_analysis","cleaned_messages","priority","priority_score","date_closed","CloserPHID","status","time_flag","source","phase","author_closer","same_author","week_index","http_flag","olmo_cleaned_sentences","resolution_outcome","verification_sample","cleaned_sentences" +37,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","For example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major",1379680980,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_description","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","Unbreak Now!",100,1379977964,NA,"resolved","True","c1",3,"True","False",11,NA,"['VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed.', ""For example, you can't copy/paste in the edit summary box."", '--------------------------\n**Version**: unspecified\n**Severity**: major']",TRUE,0,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed." +37,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","For example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major",1379680980,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_description","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","Unbreak Now!",100,1379977964,NA,"resolved","True","c1",3,"True","False",11,NA,"['VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed.', ""For example, you can't copy/paste in the edit summary box."", '--------------------------\n**Version**: unspecified\n**Severity**: major']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: major" +37,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","For example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major",1379680980,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_description","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed./n/nFor example, you can't copy/paste in the edit summary box. + +-------------------------- +**Version**: unspecified +**Severity**: major","Unbreak Now!",100,1379977964,NA,"resolved","True","c1",3,"True","False",11,NA,"['VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed.', ""For example, you can't copy/paste in the edit summary box."", '--------------------------\n**Version**: unspecified\n**Severity**: major']",TRUE,0,"For example, you can't copy/paste in the edit summary box." +38,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85784 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784",1379977939,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85784 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784","Change 85784 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['Change 85784 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85784 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +39,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85783 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783",1379977741,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85783 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783","Change 85783 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['Change 85783 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85783 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +40,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85784 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784",1379977609,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85784 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85784","Change 85784 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['Change 85784 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85784 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +41,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85783 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783",1379977566,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85783 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85783","Change 85783 had a related patch set uploaded by Catrope: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['Change 85783 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85783 had a related patch set uploaded by Catrope:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +42,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85204 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204",1379702067,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85204 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204","Change 85204 merged by jenkins-bot: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Change 85204 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85204 merged by jenkins-bot:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +43,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Change 85204 had a related patch set uploaded by Esanders: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204",1379684992,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Change 85204 had a related patch set uploaded by Esanders: +Only listen for copy/paste on documentNode and pasteTarget + +https://gerrit.wikimedia.org/r/85204","Change 85204 had a related patch set uploaded by Esanders: +Only listen for copy/paste on documentNode and pasteTarget + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Change 85204 had a related patch set uploaded by Esanders:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL']",NA,0,"Change 85204 had a related patch set uploaded by Esanders:\nOnly listen for copy/paste on documentNode and pasteTarget\n\nGERRIT_URL" +44,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Marking as a regression as this is new behaviour in the latest release (version ""false"")",1379683942,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Marking as a regression as this is new behaviour in the latest release (version ""false"")","Marking as a regression as this is new behaviour in the latest release (version ""false"")",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Marking as a regression as this is new behaviour in the latest release (version ""false"")']",NA,0,"Marking as a regression as this is new behaviour in the latest release (version ""false"")" +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Pasting from an external source into the edit summary box works fine for me." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"To reproduce:\n1." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Load any page in VisualEditor." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"2." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Do any of\n i." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Press the browser back button to exit VE\n ii." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Cancel the edit\n iii." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"make an edit and then save the page\n3." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Select any text anywhere on the page and copy it to the clipboard\n4." +45,"VisualEditor: [Regression] Copy/paste handlers intercept non-surface copy/paste events, even after VE is closed","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",1379683839,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-m5xhygyqlxkvxhsdd6xe","task_subcomment","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted","Pasting from an external source into the edit summary box works fine for me. + +However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE. + +To reproduce: +1. Load any page in VisualEditor. +2. Do any of + i. Press the browser back button to exit VE + ii. Cancel the edit + iii. make an edit and then save the page +3. Select any text anywhere on the page and copy it to the clipboard +4. Try to paste that text anywhere (search box, URL bar, text editor, etc) + +Expected behaviour: Selected text is copied and pasted +Actual behaviour: Selected text is not copied and pasted",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Pasting from an external source into the edit summary box works fine for me.', 'However, once a page has been loaded in VE you cannot copy any text on that page until you reload - even after you have closed VE.', 'To reproduce:\n1.', 'Load any page in VisualEditor.', '2.', 'Do any of\n i.', 'Press the browser back button to exit VE\n ii.', 'Cancel the edit\n iii.', 'make an edit and then save the page\n3.', 'Select any text anywhere on the page and copy it to the clipboard\n4.', 'Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted']",NA,0,"Try to paste that text anywhere (search box, URL bar, text editor, etc)\n\nExpected behaviour: Selected text is copied and pasted\nActual behaviour: Selected text is not copied and pasted" +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)." +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit])." +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"See screenshot." +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"Observed on en.wp (by me and User:KTC) and fr.wp (by me)." +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"KTC used firefox and chrome, and I used firefox 21." +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}" +217,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","screenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}",1372931040,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_description","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)./n/nscreenshot + +As of today, the section edit links seem to have reverted to the old style ([edit]). They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top. See screenshot. + +Observed on en.wp (by me and User:KTC) and fr.wp (by me). KTC used firefox and chrome, and I used firefox 21. + +-------------------------- +**Version**: unspecified +**Severity**: major + +**Attached**: {F11031}","Unbreak Now!",100,1373053892,NA,"resolved","True","c1",3,"False","False",0,NA,"['VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded).', 'screenshot\n\nAs of today, the section edit links seem to have reverted to the old style ([edit]).', ""They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top."", 'See screenshot.', 'Observed on en.wp (by me and User:KTC) and fr.wp (by me).', 'KTC used firefox and chrome, and I used firefox 21.', '--------------------------\n**Version**: unspecified\n**Severity**: major\n\n**Attached**: {F11031}']",TRUE,0,"They don't expand and they open the source editor, even though VE is enabled (the 'Edit' and 'Edit source' tabs are there at the top." +218,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Merged and will hopefully go out soon.",1373053892,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Merged and will hopefully go out soon.","Merged and will hopefully go out soon.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['Merged and will hopefully go out soon.']",NA,0,"Merged and will hopefully go out soon." +219,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Change 72069 merged by jenkins-bot: +mw.ViewPageTarget.init: Move edit section to top init + +https://gerrit.wikimedia.org/r/72069",1373049617,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Change 72069 merged by jenkins-bot: +mw.ViewPageTarget.init: Move edit section to top init + +https://gerrit.wikimedia.org/r/72069","Change 72069 merged by jenkins-bot: +mw.ViewPageTarget.init: Move edit section to top init + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Change 72069 merged by jenkins-bot:\nmw.ViewPageTarget.init: Move edit section to top init\n\nGERRIT_URL']",NA,0,"Change 72069 merged by jenkins-bot:\nmw.ViewPageTarget.init: Move edit section to top init\n\nGERRIT_URL" +220,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",1373016135,"PHID-USER-v3yn5qf233ggnnnmvejc","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Please consider fixing bug 50540 and maybe bug 50405, too.', 'They are directly dependent of this change.', 'Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth.', 'Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.']",NA,0,"Please consider fixing bug 50540 and maybe bug 50405, too." +220,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",1373016135,"PHID-USER-v3yn5qf233ggnnnmvejc","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Please consider fixing bug 50540 and maybe bug 50405, too.', 'They are directly dependent of this change.', 'Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth.', 'Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.']",NA,0,"They are directly dependent of this change." +220,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",1373016135,"PHID-USER-v3yn5qf233ggnnnmvejc","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Please consider fixing bug 50540 and maybe bug 50405, too.', 'They are directly dependent of this change.', 'Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth.', 'Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.']",NA,0,"Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth." +220,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",1373016135,"PHID-USER-v3yn5qf233ggnnnmvejc","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.","Please consider fixing bug 50540 and maybe bug 50405, too. + +They are directly dependent of this change. Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth. + +Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Please consider fixing bug 50540 and maybe bug 50405, too.', 'They are directly dependent of this change.', 'Fixing them now once and for all will prevent further hassle with changing editsection links back-and-forth.', 'Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect.']",NA,0,"Actually fixing bug 50540 would probably simplify code a lot and could therefore resolve bug 50405 as a side effect." +221,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069",1373004125,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Change 72069 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget.init: Move edit section to top init.', 'GERRIT_URL']",NA,0,"Change 72069 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget.init: Move edit section to top init." +221,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069",1373004125,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +https://gerrit.wikimedia.org/r/72069","Change 72069 had a related patch set uploaded by Krinkle: +mw.ViewPageTarget.init: Move edit section to top init. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Change 72069 had a related patch set uploaded by Krinkle:\nmw.ViewPageTarget.init: Move edit section to top init.', 'GERRIT_URL']",NA,0,"GERRIT_URL" +222,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.",1372969315,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.","Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode.']",NA,0,"Bizarrely, the mouseover ""edit source"" links appear briefly when mousing over ""edit"" links while VE is loading a page into edit mode." +223,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.",1372952624,"PHID-USER-gfaq55vdypjmzz6nl2kn","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.","Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"[""Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon.""]",NA,0,"Bug 48429#c35 - basically, visual section editing is a seriously hard problem, and isn't on the agenda any time soon." +224,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",1372952431,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Well, if that\'s the case (I haven\'t heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs.', 'Otherwise, I expect quite a bit of confusion.']",NA,0,"Well, if that\" +224,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",1372952431,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Well, if that\'s the case (I haven\'t heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs.', 'Otherwise, I expect quite a bit of confusion.']",NA,0,"t heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs." +224,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",1372952431,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.","Well, if that's the case (I haven't heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs. Otherwise, I expect quite a bit of confusion.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"['Well, if that\'s the case (I haven\'t heard about it, but I believe you) presumably the link should be renamed to ""edit source"" to be consistent with the naming of the tabs.', 'Otherwise, I expect quite a bit of confusion.']",NA,0,"Otherwise, I expect quite a bit of confusion." +225,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.",1372951540,"PHID-USER-gfaq55vdypjmzz6nl2kn","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"[""I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future."", ""So we now don't have an interface that claims functionality there aren't even plans to implement.""]",NA,0,"I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future." +225,"VisualEditor: [Regression] Section edit links have reverted to the old style (source only, not expanded)","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.",1372951540,"PHID-USER-gfaq55vdypjmzz6nl2kn","PHID-TASK-b5zzf7lh657agk5cdqkw","task_subcomment","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.","I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future. So we now don't have an interface that claims functionality there aren't even plans to implement.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,0,NA,"[""I'd call this NOTABUG, since James has declared that visual section-editing won't be funded for the foreseeable future."", ""So we now don't have an interface that claims functionality there aren't even plans to implement.""]",NA,0,"So we now don't have an interface that claims functionality there aren't even plans to implement." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"1." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Create a page that has a heading at the very beginning\n2." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Open it in VE\n3." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Put the cursor at the beginning of the heading and press Enter\n4." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"An empty heading appears above\n5." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Use arrow keys or mouse to move the cursor into this empty heading\n6." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"See an error in the console\n7." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Type into the heading\n8." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly." +552,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1368667200,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-5refjnnnoyqumq4ge53g","task_description","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox./n/n1. Create a page that has a heading at the very beginning +2. Open it in VE +3. Put the cursor at the beginning of the heading and press Enter +4. An empty heading appears above +5. Use arrow keys or mouse to move the cursor into this empty heading +6. See an error in the console +7. Type into the heading +8. See one error per key press in the console + +In Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Unbreak Now!",100,1371602123,NA,"resolved","True","c1",1,"False","False",-7,NA,"['VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox.', '1.', 'Create a page that has a heading at the very beginning\n2.', 'Open it in VE\n3.', 'Put the cursor at the beginning of the heading and press Enter\n4.', 'An empty heading appears above\n5.', 'Use arrow keys or mouse to move the cursor into this empty heading\n6.', 'See an error in the console\n7.', 'Type into the heading\n8.', 'See one error per key press in the console\n\nIn Chrome, this behaves correctly: it creates a paragraph above the heading, and typing into it works correctly.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +553,"VisualEditor: Pressing Enter in a heading at the beginning breaks in Firefox","This is not an issue anymore.",1371602123,"PHID-USER-s7sn3zjthnxvep34c5ho","PHID-TASK-5refjnnnoyqumq4ge53g","task_subcomment","This is not an issue anymore.","This is not an issue anymore.",NA,NA,NA,NA,NA,"True","c1",2,"False",NA,-2,NA,"['This is not an issue anymore.']",NA,0,"This is not an issue anymore." +640,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821",1366992360,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_description","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +URL","Unbreak Now!",100,1367097148,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest.', ""jQuery have WONTFIX'ed this bug (13821) so we'll have to work around."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']",TRUE,0,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest." +640,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821",1366992360,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_description","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +URL","Unbreak Now!",100,1367097148,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest.', ""jQuery have WONTFIX'ed this bug (13821) so we'll have to work around."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL" +640,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821",1366992360,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_description","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +http://bugs.jquery.com/ticket/13821","VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest./n/njQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +-------------------------- +**Version**: unspecified +**Severity**: major +**See Also**: +URL","Unbreak Now!",100,1367097148,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest.', ""jQuery have WONTFIX'ed this bug (13821) so we'll have to work around."", '--------------------------\n**Version**: unspecified\n**Severity**: major\n**See Also**:\nURL']",TRUE,0,"jQuery have WONTFIX'ed this bug (13821) so we'll have to work around." +641,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","(In reply to comment #5) +> (In reply to comment #0) +> > jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. +> +> Any link? http://bugs.jquery.com/report/13821 returns error. + +http://bugs.jquery.com/ticket/13821 (in the see also field).",1367595136,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","(In reply to comment #5) +> (In reply to comment #0) +> > jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. +> +> Any link? http://bugs.jquery.com/report/13821 returns error. + +http://bugs.jquery.com/ticket/13821 (in the see also field).","(In reply to comment #5) +QUOTE +QUOTE +QUOTE +QUOTE + +URL (in the see also field).",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nURL (in the see also field).']",NA,0,"(In reply to comment #5)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nURL (in the see also field)." +642,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","Another place we had to work around: +https://gerrit.wikimedia.org/r/#/c/62028/",1367577189,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","Another place we had to work around: +https://gerrit.wikimedia.org/r/#/c/62028/","Another place we had to work around: +URL",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['Another place we had to work around:\nURL']",NA,0,"Another place we had to work around:\nURL" +643,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","(In reply to comment #0) +> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +Any link? http://bugs.jquery.com/report/13821 returns error.",1367562927,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","(In reply to comment #0) +> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +Any link? http://bugs.jquery.com/report/13821 returns error.","(In reply to comment #0) +QUOTE + +Any link? URL returns error.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-9,NA,"['(In reply to comment #0)\nQUOTE\n\nAny link?', 'URL returns error.']",NA,0,"(In reply to comment #0)\nQUOTE\n\nAny link?" +643,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","(In reply to comment #0) +> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +Any link? http://bugs.jquery.com/report/13821 returns error.",1367562927,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","(In reply to comment #0) +> jQuery have WONTFIX'ed this bug (13821) so we'll have to work around. + +Any link? http://bugs.jquery.com/report/13821 returns error.","(In reply to comment #0) +QUOTE + +Any link? URL returns error.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-9,NA,"['(In reply to comment #0)\nQUOTE\n\nAny link?', 'URL returns error.']",NA,0,"URL returns error." +644,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","*** Bug 47860 has been marked as a duplicate of this bug. ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","*** Bug 47860 has been marked as a duplicate of this bug. ***","*** Bug 47860 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['*** Bug 47860 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 47860 has been marked as a duplicate of this bug." +644,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","*** Bug 47860 has been marked as a duplicate of this bug. ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","*** Bug 47860 has been marked as a duplicate of this bug. ***","*** Bug 47860 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['*** Bug 47860 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +645,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","Ed's code is merged and will be going out with the regular deployment train on Monday.",1367097148,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","Ed's code is merged and will be going out with the regular deployment train on Monday.","Ed's code is merged and will be going out with the regular deployment train on Monday.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"[""Ed's code is merged and will be going out with the regular deployment train on Monday.""]",NA,0,"Ed's code is merged and will be going out with the regular deployment train on Monday." +646,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","Related URL: https://gerrit.wikimedia.org/r/61180 (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8)",1367066588,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","Related URL: https://gerrit.wikimedia.org/r/61180 (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8)","Related URL: GERRIT_URL (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8)",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-10,NA,"['Related URL: GERRIT_URL (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8)']",NA,0,"Related URL: GERRIT_URL (Gerrit Change I3df8f49b170c31da9610129d53cf8cb65dd5d5f8)" +647,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","*** Bug 47712 has been marked as a duplicate of this bug. ***",1366992520,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","*** Bug 47712 has been marked as a duplicate of this bug. ***","*** Bug 47712 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['*** Bug 47712 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 47712 has been marked as a duplicate of this bug." +647,"VisualEditor: jQuery bug in regex matching causes corruption of data-parsoid on ingest","*** Bug 47712 has been marked as a duplicate of this bug. ***",1366992520,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-5bwy7gci6gdsa3r3m24i","task_subcomment","*** Bug 47712 has been marked as a duplicate of this bug. ***","*** Bug 47712 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['*** Bug 47712 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: (silently) renumbering references." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I was certain to follow the Save Changes procedure, but many different references reverted to the same single reference." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"[...] Same bug today." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"In VE, I placed the cursor in the text, chose ""Reference"" from the ""More"" menu, added a reference, (It appeared as it should with the appropriate numerical superscript), Saved the work, returned to check the page...references disappeared from the list." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"- Window 8, Chrome >>." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"TeamGale adds:\n<> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I only saw it when I saved the article and the number of the references had decreased." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This URL is the change I was doing when it happened." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Could it be related to editing a table with beta?" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"After I re-added the references and the new table, every time I click ""edit beta"" the refs are gone!" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Before I even do any change!" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Just wanted to say that this is happening to other articles as well." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"That would be a problem to a long article with lots of references... Mozilla 21, Windows 8.>>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This time I saved the edit just to post it here." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"URL [...] \nUpdate: Tables were a coincidence." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I didn't realized that it happened while I was editing." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Probably not since I don't see any table on Christopher Thurber's article." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Basically I can't use beta at all on this article!" +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I don't have any issues using the source but, if it's something simple that can be done with beta, I prefer to do it with it." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"But I can't." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"And it's possible to happen and people don't see it." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"It happened to me again in main article's text." +776,"VisualEditor: (silently) renumbering references","Sherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1380214860,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-gjqblxpe4th4o7zcpret","task_description","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, https://en.wikipedia.org/w/index.php?title=Homesickness&diff=573215056&oldid=573214608 : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. https://en.wikipedia.org/w/index.php?title=Dancing_with_the_Stars_%28U.S._season_17%29&diff=prev&oldid=574412488 [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: (silently) renumbering references./n/nSherry describes what happens in this edit, URL : +<<[this edit] is the original problem. It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>> + +The original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce: +<>. + +TeamGale adds: +<> + +TeamGale again: +<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one. This time I saved the edit just to post it here. URL [...] +Update: Tables were a coincidence. It happened to me again in main article's text. I didn't save the edit this time...>> + +I think I saw this renumbering issue at it.wp as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1380220185,NA,"resolved","True","c1",3,"False","False",12,NA,"['VisualEditor: (silently) renumbering references.', 'Sherry describes what happens in this edit, URL :\n<<[this edit] is the original problem.', 'It gave all of those references the same ""name"" (""ref name="":4""""), which convinced the software using for viewing pages that they were all the same ref.>>\n\nThe original reporter, Christopher Thurber, describes the issue, and provides some hints to reproduce:\n<>.', 'TeamGale adds:\n<>\n\nTeamGale again:\n<<[...] every time I am trying to add a reference at a table with VE, it changes it and replaces it with an already existent one.', 'This time I saved the edit just to post it here.', 'URL [...] \nUpdate: Tables were a coincidence.', ""It happened to me again in main article's text."", ""I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I didn't save the edit this time...>>\n\nI think I saw this renumbering issue at it.wp as well." +777,"VisualEditor: (silently) renumbering references","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",1380220185,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gjqblxpe4th4o7zcpret","task_subcomment","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,12,NA,"['Yeah, this was a bad bug - bug 54341.', ""We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!"", '*** This bug has been marked as a duplicate of bug 54341 ***']",NA,0,"Yeah, this was a bad bug - bug 54341." +777,"VisualEditor: (silently) renumbering references","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",1380220185,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gjqblxpe4th4o7zcpret","task_subcomment","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,12,NA,"['Yeah, this was a bad bug - bug 54341.', ""We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!"", '*** This bug has been marked as a duplicate of bug 54341 ***']",NA,0,"*** This bug has been marked as a duplicate of bug 54341 ***" +777,"VisualEditor: (silently) renumbering references","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",1380220185,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gjqblxpe4th4o7zcpret","task_subcomment","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***","Yeah, this was a bad bug - bug 54341. We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry! + +*** This bug has been marked as a duplicate of bug 54341 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,12,NA,"['Yeah, this was a bad bug - bug 54341.', ""We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!"", '*** This bug has been marked as a duplicate of bug 54341 ***']",NA,0,"We fixed it on Tuesday, and back-ported it to production yesterday, so this shouldn't happen again; sorry!" +1197,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","en.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374877200,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-oqjy24dqtbqambra54dm","task_description","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1379848985,NA,"declined","True","c1",3,"False","False",3,NA,"['VisualEditor or Parsoid: Breaks and partially duplicates html tag.', 'en.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading <\n\nPossibly related to bug 51304?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"VisualEditor or Parsoid: Breaks and partially duplicates html tag." +1197,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","en.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374877200,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-oqjy24dqtbqambra54dm","task_description","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1379848985,NA,"declined","True","c1",3,"False","False",3,NA,"['VisualEditor or Parsoid: Breaks and partially duplicates html tag.', 'en.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading <\n\nPossibly related to bug 51304?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"en.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading <\n\nPossibly related to bug 51304?" +1197,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","en.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374877200,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-oqjy24dqtbqambra54dm","task_description","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at https://en.wikipedia.org/w/index.php?title=Axial_precession&diff=next&oldid=565790907 where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor or Parsoid: Breaks and partially duplicates html tag./n/nen.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading < + +Possibly related to bug 51304? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1379848985,NA,"declined","True","c1",3,"False","False",3,NA,"['VisualEditor or Parsoid: Breaks and partially duplicates html tag.', 'en.wp editor DragonsFlight reports a strange diff at URL where a
was duplicated minus the leading <\n\nPossibly related to bug 51304?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +1198,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.",1379848985,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-oqjy24dqtbqambra54dm","task_subcomment","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,11,NA,"[""Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue."", 'Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.']",NA,1,"Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available." +1198,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.",1379848985,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-oqjy24dqtbqambra54dm","task_subcomment","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.","Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue. Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,11,NA,"[""Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue."", 'Marking as ""WORKSFORME"", but please re-open if it recurs or further information is available.']",NA,1,"Can't reproduce; probably a transient Parsoid DSR and off-by-one error, given the issue." +1199,"VisualEditor or Parsoid: Breaks and partially duplicates html tag","Given the proximity of the image, im guessing this is bug 52107.",1375737774,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-oqjy24dqtbqambra54dm","task_subcomment","Given the proximity of the image, im guessing this is bug 52107.","Given the proximity of the image, im guessing this is bug 52107.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,5,NA,"['Given the proximity of the image, im guessing this is bug 52107.']",NA,1,"Given the proximity of the image, im guessing this is bug 52107." +1563,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",1373324220,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_description","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +URL +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","Needs Triage",90,1486157050,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c1",3,"False","False",1,NA,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..).', '1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"VisualEditor should not encourage links of little relevance (e.g." +1563,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",1373324220,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_description","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +URL +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","Needs Triage",90,1486157050,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c1",3,"False","False",1,NA,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..).', '1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"disambiguation pages, already used links, etc..)." +1563,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",1373324220,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_description","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +URL +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","Needs Triage",90,1486157050,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c1",3,"False","False",1,NA,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..).', '1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided." +1563,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",1373324220,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_description","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +URL +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","Needs Triage",90,1486157050,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c1",3,"False","False",1,NA,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..).', '1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g." +1563,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160",1373324220,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_description","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +https://en.wikipedia.org/wiki/Convex_function?veaction=edit +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50160","VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)./n/n1) Open an article such as +URL +2) Click in a non-linked word ""function"" +3) Click in the link button (CTRL+K) + +The list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided. + +Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g. by having a section in the dropdown menu labeled ""Already used links..."") + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","Needs Triage",90,1486157050,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c1",3,"False","False",1,NA,"['VisualEditor should not encourage links of little relevance (e.g.', 'disambiguation pages, already used links, etc..).', '1) Open an article such as\nURL\n2) Click in a non-linked word ""function""\n3) Click in the link button (CTRL+K)\n\nThe list of matching pages will include the disambiguation page ""[[Function]]"", which should actually be avoided.', 'Similarly, if a paragraph already has a link to [[Function]], then it should not appear in a second atempt to add the same link (or there should be some visual indication that this kind of link is not desirable - e.g.', 'by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"by having a section in the dropdown menu labeled ""Already used links..."")\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL" +1564,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***",1373472822,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-atyu2v5fwwehteymmmkf","task_subcomment","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon.', '*** This bug has been marked as a duplicate of bug 50240 ***']",NA,0,"This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon." +1564,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***",1373472822,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-atyu2v5fwwehteymmmkf","task_subcomment","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***","This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon. + +*** This bug has been marked as a duplicate of bug 50240 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['This is a duplicate of bug 50240; yes, this would be a nice enhancement to get done soon.', '*** This bug has been marked as a duplicate of bug 50240 ***']",NA,0,"*** This bug has been marked as a duplicate of bug 50240 ***" +1565,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","See also gerrit change 70564.",1373469016,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_subcomment","See also gerrit change 70564.","See also gerrit change 70564.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['See also gerrit change 70564.']",NA,0,"See also gerrit change 70564." +1566,"VisualEditor should not encourage links of little relevance (e.g. disambiguation pages, already used links, etc..)","PS: this was inspired by the commit message of +https://gerrit.wikimedia.org/r/#/c/72646/",1373325997,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-atyu2v5fwwehteymmmkf","task_subcomment","PS: this was inspired by the commit message of +https://gerrit.wikimedia.org/r/#/c/72646/","PS: this was inspired by the commit message of +URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['PS: this was inspired by the commit message of\nURL']",NA,0,"PS: this was inspired by the commit message of\nURL" +1600,"Keyboard shortcut for editing source","With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1373048100,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_description","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1373077734,NA,"resolved","True","c1",3,"False","False",0,NA,"['Keyboard shortcut for editing source.', 'With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.', 'Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Keyboard shortcut for editing source." +1600,"Keyboard shortcut for editing source","With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1373048100,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_description","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1373077734,NA,"resolved","True","c1",3,"False","False",0,NA,"['Keyboard shortcut for editing source.', 'With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.', 'Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page." +1600,"Keyboard shortcut for editing source","With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1373048100,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_description","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1373077734,NA,"resolved","True","c1",3,"False","False",0,NA,"['Keyboard shortcut for editing source.', 'With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.', 'Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled." +1600,"Keyboard shortcut for editing source","With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1373048100,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_description","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Keyboard shortcut for editing source./n/nWith VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page. Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1373077734,NA,"resolved","True","c1",3,"False","False",0,NA,"['Keyboard shortcut for editing source.', 'With VisualEditor enabled the shortcut alt+shift+e no longer works, which previously opened the ""edit source"" page.', 'Considering many users work without a mouse on a laptop, it would be beneficial to have this enabled.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +1601,"Keyboard shortcut for editing source","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",1373077734,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_subcomment","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['Sorry about this; we fixed this just a few hours ago.', 'Merging with the other report.', '*** This bug has been marked as a duplicate of bug 50725 ***']",NA,0,"Sorry about this; we fixed this just a few hours ago." +1601,"Keyboard shortcut for editing source","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",1373077734,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_subcomment","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['Sorry about this; we fixed this just a few hours ago.', 'Merging with the other report.', '*** This bug has been marked as a duplicate of bug 50725 ***']",NA,0,"Merging with the other report." +1601,"Keyboard shortcut for editing source","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",1373077734,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gqozvzrj5ka3lgyouwvn","task_subcomment","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***","Sorry about this; we fixed this just a few hours ago. Merging with the other report. + +*** This bug has been marked as a duplicate of bug 50725 ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['Sorry about this; we fixed this just a few hours ago.', 'Merging with the other report.', '*** This bug has been marked as a duplicate of bug 50725 ***']",NA,0,"*** This bug has been marked as a duplicate of bug 50725 ***" +1645,"VisualEditor: Still dirty refs?","There seem to be several dirty ref sections in this diff: + +https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132 + +-------------------------- +**Version**: unspecified +**Severity**: normal",1372827600,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-odieilz34gnzoz67vumw","task_description","VisualEditor: Still dirty refs?./n/nThere seem to be several dirty ref sections in this diff: + +https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132 + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Still dirty refs?./n/nThere seem to be several dirty ref sections in this diff: + +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1379613746,NA,"resolved","True","c1",3,"True","False",0,NA,"['VisualEditor: Still dirty refs?.', 'There seem to be several dirty ref sections in this diff:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Still dirty refs?." +1645,"VisualEditor: Still dirty refs?","There seem to be several dirty ref sections in this diff: + +https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132 + +-------------------------- +**Version**: unspecified +**Severity**: normal",1372827600,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-odieilz34gnzoz67vumw","task_description","VisualEditor: Still dirty refs?./n/nThere seem to be several dirty ref sections in this diff: + +https://en.wikipedia.org/w/index.php?title=God_of_War_%28series%29&diff=prev&oldid=562631132 + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Still dirty refs?./n/nThere seem to be several dirty ref sections in this diff: + +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1379613746,NA,"resolved","True","c1",3,"True","False",0,NA,"['VisualEditor: Still dirty refs?.', 'There seem to be several dirty ref sections in this diff:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"There seem to be several dirty ref sections in this diff:\n\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal" +1646,"VisualEditor: Still dirty refs?"," + +*** This bug has been marked as a duplicate of bug 48570 ***",1379613746,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-odieilz34gnzoz67vumw","task_subcomment"," + +*** This bug has been marked as a duplicate of bug 48570 ***"," + +*** This bug has been marked as a duplicate of bug 48570 ***",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['\n\n*** This bug has been marked as a duplicate of bug 48570 ***']",NA,0,"\n\n*** This bug has been marked as a duplicate of bug 48570 ***" +1746,"VisualEditor: Insert media dialog is borked","screenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}",1372595100,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-adbbasada34enlaaq6ns","task_description","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","Needs Triage",90,1372620610,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Insert media dialog is borked.', 'screenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']",TRUE,0,"VisualEditor: Insert media dialog is borked." +1746,"VisualEditor: Insert media dialog is borked","screenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}",1372595100,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-adbbasada34enlaaq6ns","task_description","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","Needs Triage",90,1372620610,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Insert media dialog is borked.', 'screenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']",TRUE,0,"screenshot\n\nIt was working fine previously." +1746,"VisualEditor: Insert media dialog is borked","screenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}",1372595100,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-adbbasada34enlaaq6ns","task_description","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","Needs Triage",90,1372620610,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Insert media dialog is borked.', 'screenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']",TRUE,0,"I can reproduce this on both fr.wp and en.wp." +1746,"VisualEditor: Insert media dialog is borked","screenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}",1372595100,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-adbbasada34enlaaq6ns","task_description","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","Needs Triage",90,1372620610,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Insert media dialog is borked.', 'screenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']",TRUE,0,"See screenshot." +1746,"VisualEditor: Insert media dialog is borked","screenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}",1372595100,"PHID-USER-z6nzrwuaij3spgyg23jt","PHID-TASK-adbbasada34enlaaq6ns","task_description","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","VisualEditor: Insert media dialog is borked./n/nscreenshot + +It was working fine previously. I can reproduce this on both fr.wp and en.wp. See screenshot. + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11359}","Needs Triage",90,1372620610,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Insert media dialog is borked.', 'screenshot\n\nIt was working fine previously.', 'I can reproduce this on both fr.wp and en.wp.', 'See screenshot.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11359}" +1747,"VisualEditor: Insert media dialog is borked"," + +*** This bug has been marked as a duplicate of bug 50471 ***",1372620610,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-adbbasada34enlaaq6ns","task_subcomment"," + +*** This bug has been marked as a duplicate of bug 50471 ***"," + +*** This bug has been marked as a duplicate of bug 50471 ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-1,NA,"['\n\n*** This bug has been marked as a duplicate of bug 50471 ***']",NA,0,"\n\n*** This bug has been marked as a duplicate of bug 50471 ***" +1838,"VisualEditor: Image size parameter with spaces is ignored","See [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1372216200,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-6xivramwe724jwphgukh","task_description","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1372216311,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Image size parameter with spaces is ignored.', 'See [[testwiki:VisualEditor:Little or big]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Image size parameter with spaces is ignored." +1838,"VisualEditor: Image size parameter with spaces is ignored","See [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1372216200,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-6xivramwe724jwphgukh","task_description","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1372216311,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Image size parameter with spaces is ignored.', 'See [[testwiki:VisualEditor:Little or big]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"See [[testwiki:VisualEditor:Little or big]]." +1838,"VisualEditor: Image size parameter with spaces is ignored","See [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1372216200,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-6xivramwe724jwphgukh","task_description","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Image size parameter with spaces is ignored./n/nSee [[testwiki:VisualEditor:Little or big]]. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1372216311,NA,"resolved","True","c1",2,"False","False",-1,NA,"['VisualEditor: Image size parameter with spaces is ignored.', 'See [[testwiki:VisualEditor:Little or big]].', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +1839,"VisualEditor: Image size parameter with spaces is ignored"," + +*** This bug has been marked as a duplicate of bug 49696 ***",1372216311,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-6xivramwe724jwphgukh","task_subcomment"," + +*** This bug has been marked as a duplicate of bug 49696 ***"," + +*** This bug has been marked as a duplicate of bug 49696 ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-1,NA,"['\n\n*** This bug has been marked as a duplicate of bug 49696 ***']",NA,0,"\n\n*** This bug has been marked as a duplicate of bug 49696 ***" +1971,"VisualEditor: visual representation of template breaks on 'apply changes'","Screenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}",1371532800,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-xfgiug37am4goz3ewbs4","task_description","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","Needs Triage",90,1372015399,NA,"resolved","True","c1",2,"False","False",-2,NA,"[""VisualEditor: visual representation of template breaks on 'apply changes'."", 'Screenshot\n\nSee associated screenshot.', 'This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11624}']",TRUE,0,"Screenshot\n\nSee associated screenshot." +1971,"VisualEditor: visual representation of template breaks on 'apply changes'","Screenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}",1371532800,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-xfgiug37am4goz3ewbs4","task_description","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","Needs Triage",90,1372015399,NA,"resolved","True","c1",2,"False","False",-2,NA,"[""VisualEditor: visual representation of template breaks on 'apply changes'."", 'Screenshot\n\nSee associated screenshot.', 'This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11624}']",TRUE,0,"This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11624}" +1971,"VisualEditor: visual representation of template breaks on 'apply changes'","Screenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}",1371532800,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-xfgiug37am4goz3ewbs4","task_description","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on https://www.mediawiki.org/wiki/VisualEditor:Template_test + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","VisualEditor: visual representation of template breaks on 'apply changes'./n/nScreenshot + +See associated screenshot. This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11624}","Needs Triage",90,1372015399,NA,"resolved","True","c1",2,"False","False",-2,NA,"[""VisualEditor: visual representation of template breaks on 'apply changes'."", 'Screenshot\n\nSee associated screenshot.', 'This was an attempt to include ""foo"" in a string-based parameter in the infobox on URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11624}']",TRUE,0,"VisualEditor: visual representation of template breaks on 'apply changes'." +1972,"VisualEditor: visual representation of template breaks on 'apply changes'","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***",1372015399,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-xfgiug37am4goz3ewbs4","task_subcomment","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['This is a dupe of bug 49854.', '*** This bug has been marked as a duplicate of bug 49854 ***']",NA,0,"This is a dupe of bug 49854." +1972,"VisualEditor: visual representation of template breaks on 'apply changes'","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***",1372015399,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-xfgiug37am4goz3ewbs4","task_subcomment","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***","This is a dupe of bug 49854. + +*** This bug has been marked as a duplicate of bug 49854 ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['This is a dupe of bug 49854.', '*** This bug has been marked as a duplicate of bug 49854 ***']",NA,0,"*** This bug has been marked as a duplicate of bug 49854 ***" +2108,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","https://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1367290980,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-slnchzhtiw4uoxg47vla","task_description","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nhttps://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nURL + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1367545048,NA,"resolved","True","c1",1,"False","False",-9,NA,"['VisualEditor: Extra tags got inserted causing infobox layout to be broken.', 'URL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically.', 'Where\'s that ""partial serialization"" mentioned before?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"VisualEditor: Extra tags got inserted causing infobox layout to be broken." +2108,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","https://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1367290980,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-slnchzhtiw4uoxg47vla","task_description","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nhttps://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nURL + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1367545048,NA,"resolved","True","c1",1,"False","False",-9,NA,"['VisualEditor: Extra tags got inserted causing infobox layout to be broken.', 'URL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically.', 'Where\'s that ""partial serialization"" mentioned before?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"URL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically." +2108,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","https://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1367290980,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-slnchzhtiw4uoxg47vla","task_description","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nhttps://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nURL + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1367545048,NA,"resolved","True","c1",1,"False","False",-9,NA,"['VisualEditor: Extra tags got inserted causing infobox layout to be broken.', 'URL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically.', 'Where\'s that ""partial serialization"" mentioned before?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"Where\" +2108,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","https://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal",1367290980,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-slnchzhtiw4uoxg47vla","task_description","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nhttps://zh.wikipedia.org/w/index.php?title=Team_A_6th_Stage%E3%80%8C%E7%9B%AE%E6%93%8A%E8%80%85%E3%80%8D&diff=26390481&oldid=25589213 + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Extra tags got inserted causing infobox layout to be broken./n/nURL + +All change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically. + +Where's that ""partial serialization"" mentioned before? + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1367545048,NA,"resolved","True","c1",1,"False","False",-9,NA,"['VisualEditor: Extra tags got inserted causing infobox layout to be broken.', 'URL\n\nAll change done manually is the insertion of ""编辑器测试"" at the first diff, then those extra and got added automatically.', 'Where\'s that ""partial serialization"" mentioned before?', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"partial serialization" +2109,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-slnchzhtiw4uoxg47vla","task_subcomment","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"[""The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May."", 'The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor).', 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 47737 ***']",NA,1,"The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor)." +2109,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-slnchzhtiw4uoxg47vla","task_subcomment","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"[""The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May."", 'The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor).', 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 47737 ***']",NA,1,"Marking as a dupe." +2109,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-slnchzhtiw4uoxg47vla","task_subcomment","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"[""The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May."", 'The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor).', 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 47737 ***']",NA,1,"*** This bug has been marked as a duplicate of bug 47737 ***" +2109,"VisualEditor: Extra tags got inserted causing infobox layout to be broken","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",1367545048,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-slnchzhtiw4uoxg47vla","task_subcomment","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***","The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May. + +The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor). + +Marking as a dupe. + +*** This bug has been marked as a duplicate of bug 47737 ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"[""The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May."", 'The whitespace changes look to be bug 47712 in Parsoid (but possibly actually a fault in VisualEditor).', 'Marking as a dupe.', '*** This bug has been marked as a duplicate of bug 47737 ***']",NA,1,"The main part of this bug (the extra and ) look like they're duplicates of bug 47737 - this is fixed, but the new code won't get to zhwiki until 8 May." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"See the URL for a demo." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"In the output page it is shown as ""1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"A""." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"In the VE it is shown as\n1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"1." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"A\n\nThis is an edge case but it should should probably be identical in any case." +2121,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","See the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes",1367008080,"PHID-USER-xfe43w2lb5gpvglf4coa","PHID-TASK-exyn4bfiq2igip2xy6r4","task_description","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://www.mediawiki.org/wiki/VisualEditor:Multiple_hashes","A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page./n/nSee the URL for a demo. + +The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning. + +In the output page it is shown as ""1. 1. 1. 1. 1. 1. 1. A"". + +In the VE it is shown as +1. + 1. + 1. + 1. + 1. + 1. + 1. A + +This is an edge case but it should should probably be identical in any case. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Needs Triage",90,1367009441,NA,"declined","True","c1",1,"False","False",-10,NA,"['A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page.', 'See the URL for a demo.', 'The last line in the source of the demo page has an empty paragraph before it and several hash marks in the beginning.', 'In the output page it is shown as ""1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A"".', 'In the VE it is shown as\n1.', '1.', '1.', '1.', '1.', '1.', '1.', 'A\n\nThis is an edge case but it should should probably be identical in any case.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL" +2122,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.",1367019704,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-exyn4bfiq2igip2xy6r4","task_subcomment","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['Confirm that this is intentional behaviour.', ""There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.""]",NA,0,"Confirm that this is intentional behaviour." +2122,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.",1367019704,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-exyn4bfiq2igip2xy6r4","task_subcomment","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.","Confirm that this is intentional behaviour. There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['Confirm that this is intentional behaviour.', ""There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing.""]",NA,0,"There are a number of ways in which VisualEditor is deliberately not merely a WYSIWYG editor, and we should probably explain them so it's less confusing." +2123,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).",1367009441,"PHID-USER-s7sn3zjthnxvep34c5ho","PHID-TASK-exyn4bfiq2igip2xy6r4","task_subcomment","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-10,NA,"[""As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level."", ""James - please confirm (and reopen if I'm wrong).""]",NA,0,"As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level." +2123,"A paragraph with multiple hash marks in the beginning is shown differently in VE and in output page","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).",1367009441,"PHID-USER-s7sn3zjthnxvep34c5ho","PHID-TASK-exyn4bfiq2igip2xy6r4","task_subcomment","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).","As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level. James - please confirm (and reopen if I'm wrong).",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-10,NA,"[""As far as I know it is supposed to be that way - otherwise you wouldn't be able to add content to list item at each level."", ""James - please confirm (and reopen if I'm wrong).""]",NA,0,"James - please confirm (and reopen if I'm wrong)." +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,"**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,", 2500 );\n define( \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,", 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,";\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,";\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,"] = 1;\n $wgHiddenPrefs[] = \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,";\n $wgVisualEditorParsoidURL = \" +2207,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html",1359038700,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_description","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** `mail` + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'http://parsoid.wmflabs.org/'; + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html","Parsoid should support passing on an authenticated user's read right (when MW API supports that)./n/n**Author:** CODE + +**Description:** +Hi, + +when I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error: + + {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}} + +My config is as following: + + require_once(""$IP/extensions/VisualEditor/VisualEditor.php""); + define( 'NS_VISUALEDITOR', 2500 ); + define( 'NS_VISUALEDITOR_TALK', 2501 ); + $wgExtraNamespaces[NS_VISUALEDITOR] = 'VisualEditor'; + $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = 'VisualEditor_talk'; + $wgVisualEditorNamespaces = array( NS_MAIN ); + $wgVisualEditorNamespaces = array(); + $wgVisualEditorNamespaces[] = NS_VISUALEDITOR; + $wgDefaultUserOptions['visualeditor-enable'] = 1; + $wgHiddenPrefs[] = 'visualeditor-enable'; + $wgVisualEditorParsoidURL = 'URL + +I installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013). + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC +**URL**: URL","Needs Triage",90,1360207511,NA,"resolved","True","c1",1,"False","False",-23,NA,"[""Parsoid should support passing on an authenticated user's read right (when MW API supports that)."", '**Author:** CODE\n\n**Description:**\nHi,\n\nwhen I click on the WYSIWYG button on /w/VisualEditor:Sandbox (existsting page), I only get an error:\n\n {""error"":{""code"":""parsoidserver"",""info"":""Error contacting the Parsoid server""}}\n\nMy config is as following:\n\n require_once(""$IP/extensions/VisualEditor/VisualEditor.php"");\n define( \'NS_VISUALEDITOR\', 2500 );\n define( \'NS_VISUALEDITOR_TALK\', 2501 );\n $wgExtraNamespaces[NS_VISUALEDITOR] = \'VisualEditor\';\n $wgExtraNamespaces[NS_VISUALEDITOR_TALK] = \'VisualEditor_talk\';\n $wgVisualEditorNamespaces = array( NS_MAIN );\n $wgVisualEditorNamespaces = array();\n $wgVisualEditorNamespaces[] = NS_VISUALEDITOR;\n $wgDefaultUserOptions[\'visualeditor-enable\'] = 1;\n $wgHiddenPrefs[] = \'visualeditor-enable\';\n $wgVisualEditorParsoidURL = \'URL\n\nI installed the current git masters from mediawiki and visualeditor as of today (24 Jan 2013).', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n**URL**: URL']",TRUE,0,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)." +2208,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)"," + +*** This bug has been marked as a duplicate of bug 44483 ***",1360207511,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gf44zknlabktvyuiobnc","task_subcomment"," + +*** This bug has been marked as a duplicate of bug 44483 ***"," + +*** This bug has been marked as a duplicate of bug 44483 ***",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-21,NA,"['\n\n*** This bug has been marked as a duplicate of bug 44483 ***']",NA,0,"\n\n*** This bug has been marked as a duplicate of bug 44483 ***" +2209,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**mail** wrote: + +http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)",1359450666,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_subcomment","**mail** wrote: + +http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)","**mail** wrote: + +URL + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-22,NA,"[""**mail** wrote:\n\nURL\n\nSolved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE."", 'I hope there will be the possibility to have it FALSE in the future :)']",NA,0,"I hope there will be the possibility to have it FALSE in the future :)" +2209,"Parsoid should support passing on an authenticated user's read right (when MW API supports that)","**mail** wrote: + +http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)",1359450666,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gf44zknlabktvyuiobnc","task_subcomment","**mail** wrote: + +http://lists.wikimedia.org/pipermail/wikitext-l/2013-January/000750.html + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)","**mail** wrote: + +URL + +Solved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE. +I hope there will be the possibility to have it FALSE in the future :)",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-22,NA,"[""**mail** wrote:\n\nURL\n\nSolved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE."", 'I hope there will be the possibility to have it FALSE in the future :)']",NA,0,"**mail** wrote:\n\nURL\n\nSolved by setting $wgGroupPermissions['*']['read'] from FALSE to TRUE." +2684,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal",1377700800,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_description","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +URL + +Example course page: +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1397705810,NA,"resolved","True","c1",3,"False","False",8,NA,"['VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages.', 'For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"".', '(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)', 'Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages." +2684,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal",1377700800,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_description","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +URL + +Example course page: +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1397705810,NA,"resolved","True","c1",3,"False","False",8,NA,"['VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages.', 'For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"".', '(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)', 'Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source""." +2684,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal",1377700800,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_description","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +URL + +Example course page: +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1397705810,NA,"resolved","True","c1",3,"False","False",8,NA,"['VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages.', 'For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"".', '(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)', 'Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)" +2684,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal",1377700800,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_description","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma + +Example course page: +http://en.wikipedia.org/wiki/Education_Program:University_of_Oklahoma/History_of_Science_from_Antiquity_to_Newton_(Fall_2013) + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages./n/nFor those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"". (VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".) + +Example institution page: +URL + +Example course page: +URL + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1397705810,NA,"resolved","True","c1",3,"False","False",8,NA,"['VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages.', 'For those with the rights to edit such pages (admins and those with EducationProgram-specific userrights), the Edit button on course pages and institution pages is mislabeled ""Create source"".', '(VE is not enabled in the Education Program: namespace, so it should remain simply ""Edit"".)', 'Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Example institution page:\nURL\n\nExample course page:\nURL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal" +2685,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +https://github.com/wikimedia/operations-mediawiki-config/blob/master/wmf-config/InitialiseSettings.php#L9292-9349 + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...",1397734119,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +https://github.com/wikimedia/operations-mediawiki-config/blob/master/wmf-config/InitialiseSettings.php#L9292-9349 + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +URL + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nP.S.', ""Go to a production wiki and try this in a js console:\n\nmw.config.get('wgContentNamespaces')\n\nThe results coincide:\n\nURL\n\nI lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...""]",NA,0,"**andrew.green.df** wrote:\n\nP.S." +2685,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +https://github.com/wikimedia/operations-mediawiki-config/blob/master/wmf-config/InitialiseSettings.php#L9292-9349 + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...",1397734119,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +https://github.com/wikimedia/operations-mediawiki-config/blob/master/wmf-config/InitialiseSettings.php#L9292-9349 + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...","**andrew.green.df** wrote: + +P.S. Go to a production wiki and try this in a js console: + +mw.config.get('wgContentNamespaces') + +The results coincide: + +URL + +I lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nP.S.', ""Go to a production wiki and try this in a js console:\n\nmw.config.get('wgContentNamespaces')\n\nThe results coincide:\n\nURL\n\nI lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though...""]",NA,0,"Go to a production wiki and try this in a js console:\n\nmw.config.get('wgContentNamespaces')\n\nThe results coincide:\n\nURL\n\nI lost the scent of $wgVisualEditorNamespaces following a brief pursuit, though..." +2686,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",1397732911,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change.', 'tl;dr: Is $wgContentNamespaces getting checked?', ""I don't see how EP_NS could be there, and checking it in js seems to fix the issue."", 'Thanks!']",NA,0,"**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change." +2686,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",1397732911,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change.', 'tl;dr: Is $wgContentNamespaces getting checked?', ""I don't see how EP_NS could be there, and checking it in js seems to fix the issue."", 'Thanks!']",NA,0,"tl;dr: Is $wgContentNamespaces getting checked?" +2686,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",1397732911,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change.', 'tl;dr: Is $wgContentNamespaces getting checked?', ""I don't see how EP_NS could be there, and checking it in js seems to fix the issue."", 'Thanks!']",NA,0,"Thanks!" +2686,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",1397732911,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!","**andrew.green.df** wrote: + +Added a comment on the Gerrit change. tl;dr: Is $wgContentNamespaces getting checked? I don't see how EP_NS could be there, and checking it in js seems to fix the issue. Thanks!",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['**andrew.green.df** wrote:\n\nAdded a comment on the Gerrit change.', 'tl;dr: Is $wgContentNamespaces getting checked?', ""I don't see how EP_NS could be there, and checking it in js seems to fix the issue."", 'Thanks!']",NA,0,"I don't see how EP_NS could be there, and checking it in js seems to fix the issue." +2687,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Change 125233 merged by jenkins-bot: +Don't change tabs on Education Program pages + +https://gerrit.wikimedia.org/r/125233",1397705933,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","Change 125233 merged by jenkins-bot: +Don't change tabs on Education Program pages + +https://gerrit.wikimedia.org/r/125233","Change 125233 merged by jenkins-bot: +Don't change tabs on Education Program pages + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"[""Change 125233 merged by jenkins-bot:\nDon't change tabs on Education Program pages\n\nGERRIT_URL""]",NA,0,"Change 125233 merged by jenkins-bot:\nDon't change tabs on Education Program pages\n\nGERRIT_URL" +2688,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…",1397246077,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…","(In reply to Andrew Green from comment #9) +QUOTE +QUOTE + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +QUOTE +QUOTE + +Understood. + + +QUOTE + +Alex's patch is necessarily a horrible hack, but yeah…",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['(In reply to Andrew Green from comment #9)\nQUOTE\nQUOTE\n\nIdeally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely.', ':-)\n\n\nQUOTE\nQUOTE\n\nUnderstood.', ""QUOTE\n\nAlex's patch is necessarily a horrible hack, but yeah…""]",NA,0,"(In reply to Andrew Green from comment #9)\nQUOTE\nQUOTE\n\nIdeally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely." +2688,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…",1397246077,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…","(In reply to Andrew Green from comment #9) +QUOTE +QUOTE + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +QUOTE +QUOTE + +Understood. + + +QUOTE + +Alex's patch is necessarily a horrible hack, but yeah…",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['(In reply to Andrew Green from comment #9)\nQUOTE\nQUOTE\n\nIdeally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely.', ':-)\n\n\nQUOTE\nQUOTE\n\nUnderstood.', ""QUOTE\n\nAlex's patch is necessarily a horrible hack, but yeah…""]",NA,0,":-)\n\n\nQUOTE\nQUOTE\n\nUnderstood." +2688,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…",1397246077,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","(In reply to Andrew Green from comment #9) +> I can look into making the EP extension warn VE through some generic +> mechanism. + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +> BTW, I wouldn't recommend that anyone try to make major changes to the EP +> extension, as the plan is just to rewrite it. + +Understood. + + +> Alex's patch also looks like a fine temporary solution. :) + +Alex's patch is necessarily a horrible hack, but yeah…","(In reply to Andrew Green from comment #9) +QUOTE +QUOTE + +Ideally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely. :-) + + +QUOTE +QUOTE + +Understood. + + +QUOTE + +Alex's patch is necessarily a horrible hack, but yeah…",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['(In reply to Andrew Green from comment #9)\nQUOTE\nQUOTE\n\nIdeally EP would warn VE through the existing generic mechanisms that Krinkle suggested; this would avoid VE having to have EP-specific code in it entirely.', ':-)\n\n\nQUOTE\nQUOTE\n\nUnderstood.', ""QUOTE\n\nAlex's patch is necessarily a horrible hack, but yeah…""]",NA,0,"QUOTE\n\nAlex's patch is necessarily a horrible hack, but yeah…" +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,"**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism." +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,"The issues Krinkle mentions are certainly valid." +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,":)" +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,"The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes." +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,"BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it." +2689,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",1397245474,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)","**andrew.green.df** wrote: + +I can look into making the EP extension warn VE through some generic mechanism. The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes. + +BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it. + +The issues Krinkle mentions are certainly valid. Alex's patch also looks like a fine temporary solution. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['**andrew.green.df** wrote:\n\nI can look into making the EP extension warn VE through some generic mechanism.', ""The bug is moderately important for users of the extension, and I imagine there's some way to do this without making major changes."", ""BTW, I wouldn't recommend that anyone try to make major changes to the EP extension, as the plan is just to rewrite it."", 'The issues Krinkle mentions are certainly valid.', ""Alex's patch also looks like a fine temporary solution."", ':)']",NA,0,"Alex's patch also looks like a fine temporary solution." +2690,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","(In reply to Krinkle from comment #7) +> I'd say EP should either let us know how to generically detect it without +> being EP specific, or it should implement support to at least do one thing +> right. Possibly we could do the latter ourselves (maybe Alex is interested +> in patching EP). + +I don't really think this bug is important enough to VE to justify making big changes to how another extension works...",1397243067,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","(In reply to Krinkle from comment #7) +> I'd say EP should either let us know how to generically detect it without +> being EP specific, or it should implement support to at least do one thing +> right. Possibly we could do the latter ourselves (maybe Alex is interested +> in patching EP). + +I don't really think this bug is important enough to VE to justify making big changes to how another extension works...","(In reply to Krinkle from comment #7) +QUOTE +QUOTE +QUOTE +QUOTE + +I don't really think this bug is important enough to VE to justify making big changes to how another extension works...",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"[""(In reply to Krinkle from comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't really think this bug is important enough to VE to justify making big changes to how another extension works...""]",NA,0,"(In reply to Krinkle from comment #7)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't really think this bug is important enough to VE to justify making big changes to how another extension works..." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Not one of them is being used by EP right now." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"* Generally this is something we have Special pages for." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"), it should be a Special page." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Or at least a custom namespace with a negative namespace id." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Right now they take over move, delete, edit and view." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails)." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"For example ""View history"" (action=history) is quite useless right now." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Not to mention API actions, none of those are working as expected." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"3) Existence check impossible." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Possibly we could do the latter ourselves (maybe Alex is interested in patching EP)." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"2) It doesn't scale." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"And action=edit doesn't work as expected." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"Because they aren't actually wiki pages with page and revision ids, existence check isn't possible." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"ContentModel can't be overridden because it doesn't use wikipage content." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them." +2691,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",1397241093,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).","From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage. + +Not one of them is being used by EP right now. + +* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page). + +* Generally this is something we have Special pages for. If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.), it should be a Special page. Or at least a custom namespace with a negative namespace id. + +* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage. So inherently this is going to cause trouble because: + 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=). + 2) It doesn't scale. Right now they take over move, delete, edit and view. But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails). For example ""View history"" (action=history) is quite useless right now. And action=edit doesn't work as expected. Not to mention API actions, none of those are working as expected. + 3) Existence check impossible. Because they aren't actually wiki pages with page and revision ids, existence check isn't possible. ContentModel can't be overridden because it doesn't use wikipage content. All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases. + +There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them. + +I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right. Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['From a quick investigation it looks like there are about a dozen different ways in which VisualEditor can reasonably find out that the page is not a real wikipage.', 'Not one of them is being used by EP right now.', ""* It's pretending to be a wiki page (by having its own namespace and using action=view, albeit overridden, to render the dynamically constructed page)."", '* Generally this is something we have Special pages for.', 'If the rendering is completely taken over (as in, there is no page table entry, no revisions table entries etc.', '), it should be a Special page.', 'Or at least a custom namespace with a negative namespace id.', ""* It abuses existing WikiPage action queries (action=edit, action=delete), which doesn't make sense because it isn't a WikiPage."", ""So inherently this is going to cause trouble because:\n 1) They aren't compatible (the query string parameters Action pages take aren't supported, other than title=)."", ""2) It doesn't scale."", 'Right now they take over move, delete, edit and view.', 'But there are more page actions, and by design they will not support all of them (they override the ones they re-implement and the rest just fails).', 'For example ""View history"" (action=history) is quite useless right now.', ""And action=edit doesn't work as expected."", 'Not to mention API actions, none of those are working as expected.', '3) Existence check impossible.', ""Because they aren't actually wiki pages with page and revision ids, existence check isn't possible."", ""ContentModel can't be overridden because it doesn't use wikipage content."", 'All pages are considered inexistent pages in a custom namespace, and then overridden to exist in some cases.', ""There are many different ways in which EP could indicate in a standard / reliable way that doesn't require other code to hardcode for EP specifically, and it doesn't seem to be using any of them."", ""I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right."", 'Possibly we could do the latter ourselves (maybe Alex is interested in patching EP).']",NA,0,"I'd say EP should either let us know how to generically detect it without being EP specific, or it should implement support to at least do one thing right." +2692,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Change 125233 had a related patch set uploaded by Alex Monk: +Only make tab changes on articles + +https://gerrit.wikimedia.org/r/125233",1397151063,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","Change 125233 had a related patch set uploaded by Alex Monk: +Only make tab changes on articles + +https://gerrit.wikimedia.org/r/125233","Change 125233 had a related patch set uploaded by Alex Monk: +Only make tab changes on articles + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['Change 125233 had a related patch set uploaded by Alex Monk:\nOnly make tab changes on articles\n\nGERRIT_URL']",NA,0,"Change 125233 had a related patch set uploaded by Alex Monk:\nOnly make tab changes on articles\n\nGERRIT_URL" +2693,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).",1396995419,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).","I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"[""I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything).""]",NA,0,"I think VE shouldn't be modifying tabs on pages which aren't articles (check wgIsArticle is true before doing anything)." +2694,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?",1396986708,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?","Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,40,NA,"['Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?']",NA,0,"Slinging to Alex – not sure what the fix here would be (it feels like overriding the semantics of a tab is something that should involve a class change, really) – thoughts?" +2695,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)",1396986438,"PHID-USER-brn4v5ta45bnw4f5as3h","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it.', ':)']",NA,0,"Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it." +2695,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)",1396986438,"PHID-USER-brn4v5ta45bnw4f5as3h","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)","Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it. :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,40,NA,"['Hi James, just noting for the record that this is still quite problematic, and we very much appreciate any efforts to fix it.', ':)']",NA,0,":)" +2696,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","*** Bug 56844 has been marked as a duplicate of this bug. ***",1384096303,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","*** Bug 56844 has been marked as a duplicate of this bug. ***","*** Bug 56844 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,18,NA,"['*** Bug 56844 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 56844 has been marked as a duplicate of this bug." +2696,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","*** Bug 56844 has been marked as a duplicate of this bug. ***",1384096303,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","*** Bug 56844 has been marked as a duplicate of this bug. ***","*** Bug 56844 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,18,NA,"['*** Bug 56844 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +2697,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","@James: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.",1378409168,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","@James: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.","SCREEN_NAME: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,9,NA,"['SCREEN_NAME: Any chance of getting this fixed soon?', 'Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.']",NA,0,"SCREEN_NAME: Any chance of getting this fixed soon?" +2697,"VisualEditor: Edit tab replaced with ""Create source"" for Education Program pages","@James: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.",1378409168,"PHID-USER-nyv6rqxnzdy3oe323a3d","PHID-TASK-4lk6qpiuan7kbk6fch54","task_subcomment","@James: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.","SCREEN_NAME: Any chance of getting this fixed soon? Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,9,NA,"['SCREEN_NAME: Any chance of getting this fixed soon?', 'Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse.']",NA,0,"Now is when many instructors who are new to Wikipedia will be trying to set up their course pages, and the mislabeled tab is likely to confuse." +2831,"VisualEditor: Inspector fails to render correctly for embedded buttons","Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1376488380,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_description","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1376511662,NA,"resolved","True","c1",3,"True","False",6,NA,"['VisualEditor: Inspector fails to render correctly for embedded buttons.', ""Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g."", 'Math) we need it to work in block mode as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Inspector fails to render correctly for embedded buttons." +2831,"VisualEditor: Inspector fails to render correctly for embedded buttons","Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1376488380,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_description","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1376511662,NA,"resolved","True","c1",3,"True","False",6,NA,"['VisualEditor: Inspector fails to render correctly for embedded buttons.', ""Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g."", 'Math) we need it to work in block mode as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Math) we need it to work in block mode as well." +2831,"VisualEditor: Inspector fails to render correctly for embedded buttons","Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1376488380,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_description","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1376511662,NA,"resolved","True","c1",3,"True","False",6,NA,"['VisualEditor: Inspector fails to render correctly for embedded buttons.', ""Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g."", 'Math) we need it to work in block mode as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +2831,"VisualEditor: Inspector fails to render correctly for embedded buttons","Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1376488380,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_description","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Inspector fails to render correctly for embedded buttons./n/nHasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g. Math) we need it to work in block mode as well. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1376511662,NA,"resolved","True","c1",3,"True","False",6,NA,"['VisualEditor: Inspector fails to render correctly for embedded buttons.', ""Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g."", 'Math) we need it to work in block mode as well.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Hasn't been an issue until now as we've only used inspectors on text, but now we have inspectors for MW extensions (e.g." +2832,"VisualEditor: Inspector fails to render correctly for embedded buttons","Change 79055 merged by jenkins-bot: +Fix rendering of inspector for embedded buttons + +https://gerrit.wikimedia.org/r/79055",1376509523,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_subcomment","Change 79055 merged by jenkins-bot: +Fix rendering of inspector for embedded buttons + +https://gerrit.wikimedia.org/r/79055","Change 79055 merged by jenkins-bot: +Fix rendering of inspector for embedded buttons + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,6,NA,"['Change 79055 merged by jenkins-bot:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL']",NA,0,"Change 79055 merged by jenkins-bot:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL" +2833,"VisualEditor: Inspector fails to render correctly for embedded buttons","Change 79055 had a related patch set uploaded by Esanders: +Fix rendering of inspector for embedded buttons + +https://gerrit.wikimedia.org/r/79055",1376491490,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-4hkjv2ath5m5txk2nfy2","task_subcomment","Change 79055 had a related patch set uploaded by Esanders: +Fix rendering of inspector for embedded buttons + +https://gerrit.wikimedia.org/r/79055","Change 79055 had a related patch set uploaded by Esanders: +Fix rendering of inspector for embedded buttons + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,6,NA,"['Change 79055 had a related patch set uploaded by Esanders:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL']",NA,0,"Change 79055 had a related patch set uploaded by Esanders:\nFix rendering of inspector for embedded buttons\n\nGERRIT_URL" +3265,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374604560,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_description","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under URL you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1374779912,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog.', 'If you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog." +3265,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374604560,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_description","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under URL you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1374779912,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog.', 'If you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"If you look at page settings under URL you\" +3265,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374604560,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_description","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under URL you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1374779912,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog.', 'If you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,", ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn" +3265,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374604560,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_description","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under URL you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1374779912,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog.', 'If you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +3265,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","If you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1374604560,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_description","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under https://sv.wikipedia.org/wiki/Violin?veaction=edit you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog./n/nIf you look at page settings under URL you'll see the category ""Wikipedia"". This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1374779912,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog.', 'If you look at page settings under URL you\'ll see the category ""Wikipedia"".', ""This is actually Kategori:Wikipedia:Basartiklar if you look at the page source; it seems the VE isn't including category elements that are preceded by a colon."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Wikipedia" +3266,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","Now fixed in master.",1374779912,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jxtza5wxkt3lvc2yga75","task_subcomment","Now fixed in master.","Now fixed in master.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,3,NA,"['Now fixed in master.']",NA,0,"Now fixed in master." +3267,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","Change 75859 merged by jenkins-bot: +Parse category names correctly + +https://gerrit.wikimedia.org/r/75859",1374776211,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jxtza5wxkt3lvc2yga75","task_subcomment","Change 75859 merged by jenkins-bot: +Parse category names correctly + +https://gerrit.wikimedia.org/r/75859","Change 75859 merged by jenkins-bot: +Parse category names correctly + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Change 75859 merged by jenkins-bot:\nParse category names correctly\n\nGERRIT_URL']",NA,0,"Change 75859 merged by jenkins-bot:\nParse category names correctly\n\nGERRIT_URL" +3268,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","Change 75859 had a related patch set uploaded by Esanders: +Parse category names correctly + +https://gerrit.wikimedia.org/r/75859",1374756861,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jxtza5wxkt3lvc2yga75","task_subcomment","Change 75859 had a related patch set uploaded by Esanders: +Parse category names correctly + +https://gerrit.wikimedia.org/r/75859","Change 75859 had a related patch set uploaded by Esanders: +Parse category names correctly + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Change 75859 had a related patch set uploaded by Esanders:\nParse category names correctly\n\nGERRIT_URL']",NA,0,"Change 75859 had a related patch set uploaded by Esanders:\nParse category names correctly\n\nGERRIT_URL" +3269,"VisualEditor: Categories with colons in their name do not display properly in the meta-data dialog","This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].",1374683040,"PHID-USER-uf3buojo4ceizjywvyn5","PHID-TASK-jxtza5wxkt3lvc2yga75","task_subcomment","This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].","This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]].']",NA,0,"This style of category name also appears at de.wikipedia, e.g., [[:de:Kategorie:Wikipedia:Schnelllöschen]]." +3795,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358",1372947300,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_description","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","High",80,1410982793,NA,"resolved","True","c1",3,"True","False",0,NA,"['VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters.', ""TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters." +3795,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358",1372947300,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_description","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","High",80,1410982793,NA,"resolved","True","c1",3,"True","False",0,NA,"['VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters.', ""TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL" +3795,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358",1372947300,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_description","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60358","VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters./n/nTemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL","High",80,1410982793,NA,"resolved","True","c1",3,"True","False",0,NA,"['VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters.', ""TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL']",FALSE,0,"TemplateData makes it possible to have 'required' parameters, but not using these parameters in the Template editor, does not alert you of the fact that these parameters are required." +3796,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Verified the fix in production",1411682658,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Verified the fix in production","Verified the fix in production",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,64,NA,"['Verified the fix in production']",NA,0,"Verified the fix in production" +3797,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Verified the fix in test2",1411081594,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Verified the fix in test2","Verified the fix in test2",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,63,NA,"['Verified the fix in test2']",NA,0,"Verified the fix in test2" +3798,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters",1410991738,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters","Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,63,NA,"['Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters']",NA,0,"Verified the fix to show confirmation dialog when trying to insert/edit a template with one or more missing required parameters" +3799,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","There are still some remaining improvements (as always), but the thrust of this bug is now done.",1410982793,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","There are still some remaining improvements (as always), but the thrust of this bug is now done.","There are still some remaining improvements (as always), but the thrust of this bug is now done.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,63,NA,"['There are still some remaining improvements (as always), but the thrust of this bug is now done.']",NA,0,"There are still some remaining improvements (as always), but the thrust of this bug is now done." +3800,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Change 156559 merged by jenkins-bot: +Get confirmation when trying to insert/edit template/citation with required parameters missing + +https://gerrit.wikimedia.org/r/156559",1410982430,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Change 156559 merged by jenkins-bot: +Get confirmation when trying to insert/edit template/citation with required parameters missing + +https://gerrit.wikimedia.org/r/156559","Change 156559 merged by jenkins-bot: +Get confirmation when trying to insert/edit template/citation with required parameters missing + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,63,NA,"['Change 156559 merged by jenkins-bot:\nGet confirmation when trying to insert/edit template/citation with required parameters missing\n\nGERRIT_URL']",NA,0,"Change 156559 merged by jenkins-bot:\nGet confirmation when trying to insert/edit template/citation with required parameters missing\n\nGERRIT_URL" +3801,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Change 156559 had a related patch set uploaded by Alex Monk: +Get confirmation when trying to insert template with required parameters missing + +https://gerrit.wikimedia.org/r/156559",1409154385,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Change 156559 had a related patch set uploaded by Alex Monk: +Get confirmation when trying to insert template with required parameters missing + +https://gerrit.wikimedia.org/r/156559","Change 156559 had a related patch set uploaded by Alex Monk: +Get confirmation when trying to insert template with required parameters missing + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,60,NA,"['Change 156559 had a related patch set uploaded by Alex Monk:\nGet confirmation when trying to insert template with required parameters missing\n\nGERRIT_URL']",NA,0,"Change 156559 had a related patch set uploaded by Alex Monk:\nGet confirmation when trying to insert template with required parameters missing\n\nGERRIT_URL" +3802,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","We're also going to require the user to confirm when they try to insert a template with required parameters missing.",1409154296,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","We're also going to require the user to confirm when they try to insert a template with required parameters missing.","We're also going to require the user to confirm when they try to insert a template with required parameters missing.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,60,NA,"[""We're also going to require the user to confirm when they try to insert a template with required parameters missing.""]",NA,0,"We're also going to require the user to confirm when they try to insert a template with required parameters missing." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"I just used the Cite news template in VE, via the mini-editor." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"That template has a number of ""required"" parameters." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"I also tested the Infobox person template, which uses the regular Template dialog." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"That template has one required parameter, ""Name""." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"And the inserted template did *not* have a value for the one required parameter." +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"So not only are ""required"" parameters not enforced by VE, but VE doesn\" +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,", ""That is quite unhelpful; it" +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"t one of the goals of the VE team.)"", " +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,", '(I note, in passing, that the marking of " +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0," fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', " +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"One or more required parameters is missing" +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"return to dialog" +3803,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",1408766440,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.","I just used the Cite news template in VE, via the mini-editor. That template has a number of ""required"" parameters. I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page. + +I also tested the Infobox person template, which uses the regular Template dialog. That template has one required parameter, ""Name"". I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed. And the inserted template did *not* have a value for the one required parameter. + +So not only are ""required"" parameters not enforced by VE, but VE doesn't even *warn* the user that one or more required parameters are missing. That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor. + +(I note, in passing, that the marking of ""required"" fields is, let's say, *subtle* - an uncolored asterisk that doesn't have a tooltip. I hope that subtlety isn't one of the goals of the VE team.) + +At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"". Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog. + +And NO, Bug 60358 does not address *anything* about the templates creation process (as described above). Bug 60358 is about *editing* an existing template, which is a different thing.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['I just used the Cite news template in VE, via the mini-editor.', 'That template has a number of ""required"" parameters.', 'I added just a url (a non-required field), clicked ""Insert citation"", and the dialog closed, posting the citation to the main page.', 'I also tested the Infobox person template, which uses the regular Template dialog.', 'That template has one required parameter, ""Name"".', 'I ignored that parameter, added another one, filled in the second one, and clicked ""Insert template""; the dialog box closed.', 'And the inserted template did *not* have a value for the one required parameter.', 'So not only are ""required"" parameters not enforced by VE, but VE doesn\'t even *warn* the user that one or more required parameters are missing.', ""That is quite unhelpful; it's a missed opportunity for VE to be *better* than the wikitext editor."", '(I note, in passing, that the marking of ""required"" fields is, let\'s say, *subtle* - an uncolored asterisk that doesn\'t have a tooltip.', ""I hope that subtlety isn't one of the goals of the VE team.)"", 'At minimum, VE should display a warning (pop-up box) that says ""One or more required parameters is missing"".', 'Then the user could choose either to click on ""return to dialog"" or click on ""insert citation""; the latter would finish the dialog.', 'And NO, Bug 60358 does not address *anything* about the templates creation process (as described above).', 'Bug 60358 is about *editing* an existing template, which is a different thing.']",NA,0,"insert citation" +3804,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to Alex Monk from comment #14) +> Is there anything left here to do that isn't bug 60358? + +I believe that that will complete this.",1408762442,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to Alex Monk from comment #14) +> Is there anything left here to do that isn't bug 60358? + +I believe that that will complete this.","(In reply to Alex Monk from comment #14) +QUOTE + +I believe that that will complete this.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,59,NA,"['(In reply to Alex Monk from comment #14)\nQUOTE\n\nI believe that that will complete this.']",NA,0,"(In reply to Alex Monk from comment #14)\nQUOTE\n\nI believe that that will complete this." +3805,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Is there anything left here to do that isn't bug 60358?",1408757255,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Is there anything left here to do that isn't bug 60358?","Is there anything left here to do that isn't bug 60358?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,59,NA,"[""Is there anything left here to do that isn't bug 60358?""]",NA,0,"Is there anything left here to do that isn't bug 60358?" +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"The required can be seen in a left column, while the optional are in the ""body""." +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?" +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"), but you get the idea after filling the first templates." +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required..." +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently." +3806,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",1386641485,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...","I haven't tested required/optional fields in depth, but some casual tests suggest that currently + +* Required and optional parameters are presented differently. The required can be seen in a left column, while the optional are in the ""body"". Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?), but you get the idea after filling the first templates. + +* Required field aren't still enforced, nor there is any warning when they are left empty. + +My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,23,NA,"[""I haven't tested required/optional fields in depth, but some casual tests suggest that currently\n\n* Required and optional parameters are presented differently."", 'The required can be seen in a left column, while the optional are in the ""body"".', 'Not the most self-evident UX if you ask me (why not adding labels ""Required"" / ""Optional""?', '), but you get the idea after filling the first templates.', ""* Required field aren't still enforced, nor there is any warning when they are left empty."", 'My expectation as an editor is that a field marked as ""required"" in the documentation it is actually required...']",NA,0,"* Required field aren't still enforced, nor there is any warning when they are left empty." +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters." +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\" +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters." +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"required" +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"recommended" +3807,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",1374454542,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.","I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters. The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters. + +It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that's not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"". + +As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""I don't see why Wikipedia communities can't be trusted to decide what is *mandatory* and what is not, for template parameters."", 'The communities are, after all, the ones who will live with the consequences of over-specifying or under-specifying such parameters.', 'It seems a bit paternalistic for the WMF to tell these communities that whether or not they want the software to help ensure that ""required"" parameters are non-blank, that\'s not going to happen - that WMF considers anything ""required"" to actually be just ""recommended"".', 'As an absolute minimum, VE should issue a warning when a ""required"" parameter is left blank.']",NA,0,"required" +3808,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Not enforcing mandatory params is a bug in either design or implementation.",1374447401,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Not enforcing mandatory params is a bug in either design or implementation.","Not enforcing mandatory params is a bug in either design or implementation.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Not enforcing mandatory params is a bug in either design or implementation.']",NA,0,"Not enforcing mandatory params is a bug in either design or implementation." +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"Should there be ""not recommended"" parameters (I\" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,", ""More generally, I don" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"t need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", " +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"for experts only" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"not recommended" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"required" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"suggested" +3809,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",1374079148,"PHID-USER-hirrhium5ibrtof34lwa","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.","Should there be ""not recommended"" parameters (I'd suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?) should be marked as such by a label, when listed as parameters that *could* be added. + +More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates. We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis. + +In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Should there be ""not recommended"" parameters (I\'d suggest something like ""for experts only"" as a label; if something is ""not recommended"", why have it at all?)', 'should be marked as such by a label, when listed as parameters that *could* be added.', ""More generally, I don't think we need to worry much about really complex templates, if (as suggested elsewhere) the template dialog box includes a link to the documentation page for such templates."", ""We don't need to worry much because only editors who are really interested - and motivated to understand the template - are likely to go beyond the parameters that are required and suggested, with the possible exception of editors who (idiosyncratically) use a less common parameter on a regular basis."", 'In short, a ""required"" and a ""suggested"" list (AND enforcing that the ""required"" list be filled in) would be a huge win for the occasional user of templates.']",NA,0,"required" +3810,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Indeed, I gave up doing this for the Portuguese version for now: +https://pt.wikipedia.org/wiki/Template:Info/Taxonomia?uselang=en",1373922302,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Indeed, I gave up doing this for the Portuguese version for now: +https://pt.wikipedia.org/wiki/Template:Info/Taxonomia?uselang=en","Indeed, I gave up doing this for the Portuguese version for now: +URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Indeed, I gave up doing this for the Portuguese version for now:\nURL']",NA,0,"Indeed, I gave up doing this for the Portuguese version for now:\nURL" +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional""." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"I\" +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"t want the user to enter, the color parameter in the Taxobox is such a case." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"BTW Taxobox URL is a nice torture test." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"It has over 100 parameter, most will not need to be used, but there will be an article using each." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested""." +3811,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",1373921757,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","This topic came up in http://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Duplicate_parameters_in_a_template +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox http://en.wikipedia.org/wiki/Taxobox is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".","This topic came up in URL +and John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"". + +I'd possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don't want the user to enter, the color parameter in the Taxobox is such a case. Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented. + +BTW Taxobox URL is a nice torture test. It has over 100 parameter, most will not need to be used, but there will be an article using each. Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['This topic came up in URL\nand John Broughton came up with the idea that you really want more types of status: ""required"" - must be set, ""suggested"" - appears automatically on the lhs, and ""optional"".', 'I\'d possibly add a ""not recommended"" for parameters which are there to cover corner cases but you really don\'t want the user to enter, the color parameter in the Taxobox is such a case.', 'Its only useful for subtemplate calling taxobox and should almost never be used in an article, but it needs to be documented.', 'BTW Taxobox URL is a nice torture test.', 'It has over 100 parameter, most will not need to be used, but there will be an article using each.', 'Perhaphs 10 of these are the most likely to be used which could be marked as ""suggested"".']",NA,0,"not recommended" +3812,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.",1373565271,"PHID-USER-joqqkabmjmvxeucx4ni2","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.","English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk.']",NA,0,"English Wikipedian Joe Decker recommends indicating required parameters perhaps with the standard red asterisk." +3813,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%",1373565194,"PHID-USER-joqqkabmjmvxeucx4ni2","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['%%%*** Bug 51186 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"%%%*** Bug 51186 has been marked as a duplicate of this bug." +3813,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%",1373565194,"PHID-USER-joqqkabmjmvxeucx4ni2","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%","%%%*** Bug 51186 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['%%%*** Bug 51186 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"***%%%" +3814,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Change 73136 merged by jenkins-bot: +Auto-add required params for user added templates + +https://gerrit.wikimedia.org/r/73136",1373560433,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Change 73136 merged by jenkins-bot: +Auto-add required params for user added templates + +https://gerrit.wikimedia.org/r/73136","Change 73136 merged by jenkins-bot: +Auto-add required params for user added templates + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['Change 73136 merged by jenkins-bot:\nAuto-add required params for user added templates\n\nGERRIT_URL']",NA,0,"Change 73136 merged by jenkins-bot:\nAuto-add required params for user added templates\n\nGERRIT_URL" +3815,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Leaving at ""recommend"" for now since we can't fully ensure that requiring all parameters is consistently the desired behavior.",1373507848,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Leaving at ""recommend"" for now since we can't fully ensure that requiring all parameters is consistently the desired behavior.","Leaving at ""recommend"" for now since we can't fully ensure that requiring all parameters is consistently the desired behavior.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['Leaving at ""recommend"" for now since we can\'t fully ensure that requiring all parameters is consistently the desired behavior.']",NA,0,"Leaving at ""recommend"" for now since we can\" +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence." +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"Not sure if we should do that (or let users do what they want)." +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template." +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"(Put them at the top?" +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"Highlight them?" +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"Icon?" +3816,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",1373503365,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","(In reply to comment #2) +> Change 73136 had a related patch set uploaded by Jforrester: +> Auto-add required params for user added templates +> +> https://gerrit.wikimedia.org/r/73136 + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE + +This just adds the parameters, not ""enforcing"" their presence. Not sure if we should do that (or let users do what they want). + +Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template. (Put them at the top? Highlight them? Icon? …)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,1,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis just adds the parameters, not ""enforcing"" their presence.', 'Not sure if we should do that (or let users do what they want).', 'Another improvement under this bug will be to indicate mandatory ones in the list of available parameters on the template.', '(Put them at the top?', 'Highlight them?', 'Icon?', '…)']",NA,0,"…)" +3817,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Change 73136 had a related patch set uploaded by Jforrester: +Auto-add required params for user added templates + +https://gerrit.wikimedia.org/r/73136",1373503236,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Change 73136 had a related patch set uploaded by Jforrester: +Auto-add required params for user added templates + +https://gerrit.wikimedia.org/r/73136","Change 73136 had a related patch set uploaded by Jforrester: +Auto-add required params for user added templates + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['Change 73136 had a related patch set uploaded by Jforrester:\nAuto-add required params for user added templates\n\nGERRIT_URL']",NA,0,"Change 73136 had a related patch set uploaded by Jforrester:\nAuto-add required params for user added templates\n\nGERRIT_URL" +3818,"VisualEditor: Transclusion dialog should recommend TemplateData-hinted mandatory parameters","Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.",1373354062,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-ob2d5ffvdmtamrwpb4u7","task_subcomment","Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.","Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,1,NA,"['Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion.']",NA,0,"Indeed, this seems like a low hanging fruit improvement - when inserting a new template, having all the required fields immediately be ready for use would significantly speed up template completion." +5445,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1366932300,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_description","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","High",80,1369409008,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page.', 'EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,1,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page." +5445,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1366932300,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_description","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","High",80,1369409008,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page.', 'EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,1,"EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality." +5445,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1366932300,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_description","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page./n/nEditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","High",80,1369409008,NA,"resolved","True","c1",1,"True","False",-10,NA,"['VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page.', 'EditPage.php has a prominent notice that users are editing an oldid page; VE should have something similar, probably in the ""notices"" functionality.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,1,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +5446,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","Merged and will go out with wmf5 on 27 May.",1369409008,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","Merged and will go out with wmf5 on 27 May.","Merged and will go out with wmf5 on 27 May.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['Merged and will go out with wmf5 on 27 May.']",NA,1,"Merged and will go out with wmf5 on 27 May." +5447,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","Related URL: https://gerrit.wikimedia.org/r/65291 (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead)",1369406998,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","Related URL: https://gerrit.wikimedia.org/r/65291 (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead)","Related URL: GERRIT_URL (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead)",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['Related URL: GERRIT_URL (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead)']",NA,1,"Related URL: GERRIT_URL (Gerrit Change I216cdd68014173aa65cad42ddd3d870334be9ead)" +5448,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","(In reply to comment #2) +> EditPage uses msg: editingold[1]. +> +> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en + +Ah, yes, whoops. Good catch.",1369256829,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","(In reply to comment #2) +> EditPage uses msg: editingold[1]. +> +> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en + +Ah, yes, whoops. Good catch.","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +Ah, yes, whoops. Good catch.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, yes, whoops.', 'Good catch.']",NA,1,"(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, yes, whoops." +5448,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","(In reply to comment #2) +> EditPage uses msg: editingold[1]. +> +> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en + +Ah, yes, whoops. Good catch.",1369256829,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","(In reply to comment #2) +> EditPage uses msg: editingold[1]. +> +> [1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en + +Ah, yes, whoops. Good catch.","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +Ah, yes, whoops. Good catch.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, yes, whoops.', 'Good catch.']",NA,1,"Good catch." +5449,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","EditPage uses msg: editingold[1]. + +[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en",1369244923,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","EditPage uses msg: editingold[1]. + +[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en","EditPage uses msg: editingold[1]. + +[1] URL",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['EditPage uses msg: editingold[1].', '[1] URL']",NA,1,"EditPage uses msg: editingold[1]." +5449,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","EditPage uses msg: editingold[1]. + +[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en",1369244923,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","EditPage uses msg: editingold[1]. + +[1] https://www.mediawiki.org/wiki/MediaWiki:Editingold/en","EditPage uses msg: editingold[1]. + +[1] URL",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['EditPage uses msg: editingold[1].', '[1] URL']",NA,1,"[1] URL" +5450,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","This looks to be . :-)",1367275878,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","This looks to be . :-)","This looks to be . :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['This looks to be .', ':-)']",NA,1,"This looks to be ." +5450,"VisualEditor: Warn the user more prominently that they are editing an out-dated version of the page","This looks to be . :-)",1367275878,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-hmeryxjc5h5ucj6zkjj7","task_subcomment","This looks to be . :-)","This looks to be . :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-9,NA,"['This looks to be .', ':-)']",NA,1,":-)" +5505,"VisualEditor: Round-tripping failure - Extra newline added at end of body","When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1366312920,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_description","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1368557767,NA,"resolved","True","c1",1,"True","False",-11,NA,"['VisualEditor: Round-tripping failure - Extra newline added at end of body.', 'When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end.', 'This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Round-tripping failure - Extra newline added at end of body." +5505,"VisualEditor: Round-tripping failure - Extra newline added at end of body","When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1366312920,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_description","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1368557767,NA,"resolved","True","c1",1,"True","False",-11,NA,"['VisualEditor: Round-tripping failure - Extra newline added at end of body.', 'When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end.', 'This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end." +5505,"VisualEditor: Round-tripping failure - Extra newline added at end of body","When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1366312920,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_description","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1368557767,NA,"resolved","True","c1",1,"True","False",-11,NA,"['VisualEditor: Round-tripping failure - Extra newline added at end of body.', 'When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end.', 'This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext." +5505,"VisualEditor: Round-tripping failure - Extra newline added at end of body","When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1366312920,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_description","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Round-tripping failure - Extra newline added at end of body./n/nWhen loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end. This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1368557767,NA,"resolved","True","c1",1,"True","False",-11,NA,"['VisualEditor: Round-tripping failure - Extra newline added at end of body.', 'When loading a page into VE and exporting it again with a minor edit, an extra newline is added at the end.', 'This shows up as a diff in the DOM, and will result in an extra newline in the serialized wikitext.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +5506,"VisualEditor: Round-tripping failure - Extra newline added at end of body","(In reply to comment #3) +> This might be fixed by bug 48344. +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",1368557767,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-akpipntp36njlfgkew56","task_subcomment","(In reply to comment #3) +> This might be fixed by bug 48344. +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.","(In reply to comment #3) +QUOTE +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-7,NA,"[""(In reply to comment #3)\nQUOTE\nIt most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine)."", 'Closing this bug unless and until someone can get a newline to show up again.']",NA,0,"Closing this bug unless and until someone can get a newline to show up again." +5506,"VisualEditor: Round-tripping failure - Extra newline added at end of body","(In reply to comment #3) +> This might be fixed by bug 48344. +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",1368557767,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-akpipntp36njlfgkew56","task_subcomment","(In reply to comment #3) +> This might be fixed by bug 48344. +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.","(In reply to comment #3) +QUOTE +It most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine). Closing this bug unless and until someone can get a newline to show up again.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-7,NA,"[""(In reply to comment #3)\nQUOTE\nIt most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine)."", 'Closing this bug unless and until someone can get a newline to show up again.']",NA,0,"(In reply to comment #3)\nQUOTE\nIt most probably is, yes (bug 48344 is only fixed when selser is on, but it's on in production so that's fine)." +5507,"VisualEditor: Round-tripping failure - Extra newline added at end of body","This might be fixed by bug 48344.",1368552325,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_subcomment","This might be fixed by bug 48344.","This might be fixed by bug 48344.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-7,NA,"['This might be fixed by bug 48344.']",NA,0,"This might be fixed by bug 48344." +5508,"VisualEditor: Round-tripping failure - Extra newline added at end of body","Eh, disregard that link- belongs to bug 47419.",1366388820,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_subcomment","Eh, disregard that link- belongs to bug 47419.","Eh, disregard that link- belongs to bug 47419.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-11,NA,"['Eh, disregard that link- belongs to bug 47419.']",NA,0,"Eh, disregard that link- belongs to bug 47419." +5509,"VisualEditor: Round-tripping failure - Extra newline added at end of body","Example edit: https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&curid=37842561&diff=551148728&oldid=551148307",1366388778,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-akpipntp36njlfgkew56","task_subcomment","Example edit: https://en.wikipedia.org/w/index.php?title=User:Fluffernutter/Kinne&curid=37842561&diff=551148728&oldid=551148307","Example edit: URL",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-11,NA,"['Example edit: URL']",NA,0,"Example edit: URL" +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"VisualEditor: Text duplication when using jquery.IME on existing pages." +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)" +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is." +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph." +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"So effectively the text is duplicated at the beginning of the page." +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"This means that first the caret moves to the beginning of the page, then the text is duplicated." +6148,"VisualEditor: Text duplication when using jquery.IME on existing pages","Screenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}",1379764980,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_description","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from https://bugzilla.wikimedia.org/show_bug.cgi?id=53706#c3 + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +https://www.mediawiki.org/wiki/User:Siddhartha_Ghai/sandbox?veaction=edit + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","VisualEditor: Text duplication when using jquery.IME on existing pages./n/nScreenshot showing text duplication + +This bug was observed when continuing testing from URL + +The entire test procedure is as follows: + +System Environment: +Windows7 X64 SP1 +Google Chrome 29.0.1547.66 m + +Test Url: +URL + +Steps: +Enable ULS IME hindi transliteration +Take a caret to the end of the first paragraph using the mouse (i.e click at +the end of the first paragraph to take the caret there.) +Input ag +Output will be अग् as expected but with incorrect selection as reported in the comment linked above +Further input a +This causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is. + +What should have happened: +The original output अग् should have been changed to अग at the end of the first paragraph. + +So effectively the text is duplicated at the beginning of the page. This means that first the caret moves to the beginning of the page, then the text is duplicated. + +Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711 + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F11824}","Medium",50,1453749177,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",11,NA,"['VisualEditor: Text duplication when using jquery.IME on existing pages.', 'Screenshot showing text duplication\n\nThis bug was observed when continuing testing from URL\n\nThe entire test procedure is as follows:\n\nSystem Environment:\nWindows7 X64 SP1\nGoogle Chrome 29.0.1547.66 m\n\nTest Url:\nURL\n\nSteps:\nEnable ULS IME hindi transliteration\nTake a caret to the end of the first paragraph using the mouse (i.e click at\nthe end of the first paragraph to take the caret there.)', 'Input ag\nOutput will be अग् as expected but with incorrect selection as reported in the comment linked above\nFurther input a\nThis causes the text अग to show up at the beginning of the page with the text अग् at the end of the first paragraph remaining as it is.', 'What should have happened:\nThe original output अग् should have been changed to अग at the end of the first paragraph.', 'So effectively the text is duplicated at the beginning of the page.', 'This means that first the caret moves to the beginning of the page, then the text is duplicated.', 'Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}']",FALSE,1,"Note: The text is navigable and removable, so this is different from Bug 53708 and Bug 53711\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F11824}" +6149,"VisualEditor: Text duplication when using jquery.IME on existing pages","As of https://gerrit.wikimedia.org/r/#/c/264577/ in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.",1453749108,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-qb2engnawhn3el2wqyzm","task_subcomment","As of https://gerrit.wikimedia.org/r/#/c/264577/ in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.","As of URL in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,134,NA,"['As of URL in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow.']",NA,1,"As of URL in #jquery.ime this should now be resolved and working for all users, and will be part of the wmf.12 release starting tomorrow." +6150,"VisualEditor: Text duplication when using jquery.IME on existing pages","Automatic Incorrect caret movement has been reported separately as Bug 54424",1379768763,"PHID-USER-4bjsher5mqcoikeqnnec","PHID-TASK-qb2engnawhn3el2wqyzm","task_subcomment","Automatic Incorrect caret movement has been reported separately as Bug 54424","Automatic Incorrect caret movement has been reported separately as Bug 54424",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,11,NA,"['Automatic Incorrect caret movement has been reported separately as Bug 54424']",NA,1,"Automatic Incorrect caret movement has been reported separately as Bug 54424" +6308,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","For example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1378834020,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-wh766os42bllzvmszxya","task_description","VisualEditor: Investigate where we can replace setTimeouts with EventSequencer./n/nFor example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Investigate where we can replace setTimeouts with EventSequencer./n/nFor example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"True","False",10,NA,"['VisualEditor: Investigate where we can replace setTimeouts with EventSequencer.', 'For example, onBeforePaste/onAfterPaste in ve.ce.Surface\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer." +6308,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","For example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1378834020,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-wh766os42bllzvmszxya","task_description","VisualEditor: Investigate where we can replace setTimeouts with EventSequencer./n/nFor example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Investigate where we can replace setTimeouts with EventSequencer./n/nFor example, onBeforePaste/onAfterPaste in ve.ce.Surface + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"True","False",10,NA,"['VisualEditor: Investigate where we can replace setTimeouts with EventSequencer.', 'For example, onBeforePaste/onAfterPaste in ve.ce.Surface\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"For example, onBeforePaste/onAfterPaste in ve.ce.Surface\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +6309,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","Thanks, looks like I hadn't properly updated my copy of VE to master. :P",1378839634,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-wh766os42bllzvmszxya","task_subcomment","Thanks, looks like I hadn't properly updated my copy of VE to master. :P","Thanks, looks like I hadn't properly updated my copy of VE to master. :P",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"[""Thanks, looks like I hadn't properly updated my copy of VE to master."", ':P']",NA,1,":P" +6309,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","Thanks, looks like I hadn't properly updated my copy of VE to master. :P",1378839634,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-wh766os42bllzvmszxya","task_subcomment","Thanks, looks like I hadn't properly updated my copy of VE to master. :P","Thanks, looks like I hadn't properly updated my copy of VE to master. :P",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"[""Thanks, looks like I hadn't properly updated my copy of VE to master."", ':P']",NA,1,"Thanks, looks like I hadn't properly updated my copy of VE to master." +6310,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","(In reply to comment #1) +> Got a reference doc for EventSequencer? + +https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.EventSequencer",1378839518,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-wh766os42bllzvmszxya","task_subcomment","(In reply to comment #1) +> Got a reference doc for EventSequencer? + +https://doc.wikimedia.org/VisualEditor/master/#!/api/ve.EventSequencer","(In reply to comment #1) +QUOTE + +URL",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['(In reply to comment #1)\nQUOTE\n\nURL']",NA,1,"(In reply to comment #1)\nQUOTE\n\nURL" +6311,"VisualEditor: Investigate where we can replace setTimeouts with EventSequencer","Got a reference doc for EventSequencer?",1378839441,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-wh766os42bllzvmszxya","task_subcomment","Got a reference doc for EventSequencer?","Got a reference doc for EventSequencer?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"['Got a reference doc for EventSequencer?']",NA,1,"Got a reference doc for EventSequencer?" +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"User preferences are inconsistently stored (bool/int as default, string for overrides)." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"Just look at my mw.user.options table added below." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"1 vs true vs ""1""." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"Worse yet, check the inconsistency in Gadgets." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"Gadgets enabled by default return 1 and gadgets enabled by the user return ""1""." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed." +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"``CODE``\n--------------------------\n**See Also**:\n{T29471}" +7068,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Just look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}",1375702860,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-yfjwr3je2btidmhmuccx","task_description","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``` +aftv5-last-filter: null +ccmeonemails: 0 +cols: ""120"" +date: ""mdy"" +diffonly: ""1"" +disablemail: 0 +disablesuggest: 0 +echo-email-format: ""html"" +echo-email-frequency: 0 +echo-notify-show-link: true +echo-show-alert: true +echo-subscriptions-email-article-linked: false +echo-subscriptions-email-edit-thank: false +echo-subscriptions-email-edit-user-talk: 1 +echo-subscriptions-email-mention: false +echo-subscriptions-email-other: false +echo-subscriptions-email-page-review: false +echo-subscriptions-email-reverted: false +echo-subscriptions-email-system: true +echo-subscriptions-web-article-linked: ""1"" +echo-subscriptions-web-edit-thank: true +echo-subscriptions-web-edit-user-talk: true +echo-subscriptions-web-mention: true +echo-subscriptions-web-other: true +echo-subscriptions-web-page-review: true +echo-subscriptions-web-reverted: true +echo-subscriptions-web-system: true +editfont: ""default"" +editondblclick: 0 +editsection: 1 +editsectiononrightclick: 0 +enotifminoredits: 0 +enotifrevealaddr: 0 +enotifusertalkpages: 1 +enotifwatchlistpages: 0 +ep_bulkdelcourses: true +ep_bulkdelorgs: false +ep_showdyk: true +ep_showtoplink: false +extendwatchlist: 0 +fancysig: ""1"" +flaggedrevseditdiffs: true +flaggedrevssimpleui: 1 +flaggedrevsstable: 0 +flaggedrevsviewdiffs: false +forceeditsummary: ""1"" +gadget-BugStatusUpdate: ""1"" +gadget-DRN-wizard: 1 +gadget-HotCat: ""1"" +gadget-Navigation_popups: ""1"" +gadget-NoAnimations: ""1"" +gadget-PrintOptions: ""1"" +gadget-ReferenceTooltips: 1 +gadget-UTCLiveClock: ""1"" +gadget-addsection-plus: ""1"" +gadget-charinsert: 1 +gadget-contribsrange: ""1"" +gadget-edittop: ""1"" +gadget-exlinks: ""1"" +gadget-metadata: ""1"" +gadget-mySandbox: 1 +gadget-purgetab: ""1"" +gadget-teahouse: 1 +gadget-widensearch: ""1"" +gadget-wikEd: ""1"" +gadget-wikEdDiff: ""1"" +gender: ""male"" +gettingstarted-task-toolbar-show-intro: """" +hideminor: 0 +hidepatrolled: 0 +imagesize: 2 +justify: 0 +language: ""en"" +math: ""6"" +mfWatchlistFilter: ""all"" +mfWatchlistView: ""feed"" +minordefault: 0 +newpageshidepatrolled: 0 +nocache: 0 +noconvertlink: 0 +norollbackdiff: 0 +numberheadings: 0 +previewonfirst: 0 +previewontop: 1 +rcdays: 7 +rclimit: 50 +rcshowwikidata: ""1"" +rememberpassword: 0 +rows: ""30"" +searchNs0: true +searchNs1: false +searchNs2: false +searchNs3: false +searchNs4: false +searchNs5: false +searchNs6: false +searchNs7: false +searchNs8: false +searchNs9: false +searchNs10: false +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +searchNs15: false +searchNs100: false +searchNs101: false +searchNs108: false +searchNs109: false +searchNs446: false +searchNs447: false +searchNs710: false +searchNs711: false +searchNs828: false +searchNs829: false +searchlimit: 20 +showhiddencats: ""1"" +showjumplinks: 1 +shownumberswatching: 1 +showtoc: 1 +showtoolbar: 1 +skin: ""vector"" +stubthreshold: ""2000"" +thumbsize: 4 +timecorrection: ""ZoneInfo|120|Europe/Amsterdam"" +uls-preferences: """" +underline: 2 +usebetatoolbar: 1 +usebetatoolbar-cgd: 1 +useeditwarning: 1 +uselivepreview: 0 +usenewrc: ""1"" +userjs-curationtoolbar: ""hidden"" +variant: ""en"" +vector-collapsiblenav: 1 +vector-simplesearch: 1 +visualeditor-betatempdisable: 0 +visualeditor-enable: 1 +watchcreations: 1 +watchdefault: 0 +watchdeletion: 0 +watchlistdays: 3 +watchlisthideanons: 0 +watchlisthidebots: 0 +watchlisthideliu: 0 +watchlisthideminor: 0 +watchlisthideown: 0 +watchlisthidepatrolled: 0 +watchmoves: 0 +wikilove-enabled: 1 +wllimit: 250 +wlshowwikibase: ""1"" +``` +-------------------------- +**See Also**: +{T29471}","User preferences are inconsistently stored (bool/int as default, string for overrides)./n/nJust look at my mw.user.options table added below. 1 vs true vs ""1"". I'm in favor of using numbers over booleans here, but why do we have string values for numbers ? + +Worse yet, check the inconsistency in Gadgets. Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"". + +We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed. + +``CODE`` +-------------------------- +**See Also**: +{T29471}","Medium",50,NA,NA,"open","True","c1",3,"True","False",5,NA,"['User preferences are inconsistently stored (bool/int as default, string for overrides).', 'Just look at my mw.user.options table added below.', '1 vs true vs ""1"".', ""I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?"", 'Worse yet, check the inconsistency in Gadgets.', 'Gadgets enabled by default return 1 and gadgets enabled by the user return ""1"".', 'We should really do a bit of clean up here, and possibly even cleanup the existing values in tables, this makes coding JS against these pages more fragile than needed.', '``CODE``\n--------------------------\n**See Also**:\n{T29471}']",FALSE,0,"I'm in favor of using numbers over booleans here, but why do we have string values for numbers ?" +7069,"User preferences are inconsistently stored (bool/int as default, string for overrides)","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",1519100508,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).","SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"[""SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies."", 'This task is about inconsistencies within a single key.', 'Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).']",NA,0,"This task is about inconsistencies within a single key." +7069,"User preferences are inconsistently stored (bool/int as default, string for overrides)","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",1519100508,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).","SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"[""SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies."", 'This task is about inconsistencies within a single key.', 'Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).']",NA,0,"Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row)." +7069,"User preferences are inconsistently stored (bool/int as default, string for overrides)","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",1519100508,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","@Samwilson I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).","SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies. + +This task is about inconsistencies within a single key. Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"[""SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies."", 'This task is about inconsistencies within a single key.', 'Where the same logical value of the same preference key can be int, int-ish string, or boolean, depending on how/if it got normalised, and where it came from (PHP default or MySQL row).']",NA,0,"SCREEN_NAME I'd recommend tracking that as a separate task because it involves explicitly changing the format of a preference key, and none of the array-like use cases you mentioned are subject to normalisation inconsistencies." +7070,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Also, just to note that `email-blacklist` is another outlier and is actually an array.",1519099509,"PHID-USER-hlhhe6qw6qfkl7wyfhxk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Also, just to note that `email-blacklist` is another outlier and is actually an array.","Also, just to note that CODE is another outlier and is actually an array.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,242,NA,"['Also, just to note that CODE is another outlier and is actually an array.']",NA,0,"Also, just to note that CODE is another outlier and is actually an array." +7071,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",1519098837,"PHID-USER-hlhhe6qw6qfkl7wyfhxk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,242,NA,"['Is it in scope for this task to tackle the storing of arrays in options?', 'e.g.', 'the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?']",NA,0,"Is it in scope for this task to tackle the storing of arrays in options?" +7071,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",1519098837,"PHID-USER-hlhhe6qw6qfkl7wyfhxk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,242,NA,"['Is it in scope for this task to tackle the storing of arrays in options?', 'e.g.', 'the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?']",NA,0,"e.g." +7071,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",1519098837,"PHID-USER-hlhhe6qw6qfkl7wyfhxk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?","Is it in scope for this task to tackle the storing of arrays in options? e.g. the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,242,NA,"['Is it in scope for this task to tackle the storing of arrays in options?', 'e.g.', 'the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?']",NA,0,"the differences between JSON strings (rcfilters-saved-queries), pipe-delimited (timecorrection), newline-delimited (email-blacklist), and what these should be exposed as?" +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE." +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"I have no idea why this task\" +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High""." +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce." +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code." +7072,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479716929,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which had borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Low" +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE." +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"I have no idea why this task\" +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High""." +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce." +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Other wikis which borrowed code from us had the issue too, and they most probably won't update the code." +7073,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",1479715550,"PHID-USER-p6gpvwnc6ske65oxuoof","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first `compact-language-links` user option was set to `""""` when switched off, but after some change switching it on and off turns it to `""0""`. (Was finally fixed [[https://ru.wikipedia.org/w/index.php?title=MediaWiki:Interwiki-links.js&diff=81404746&oldid=79892976|here]].) Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".","Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE. (Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce. Other wikis which borrowed code from us had the issue too, and they most probably won't update the code. + +I have no idea why this task's priority is set to ""Low"". I don't know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,177,NA,"['Hello, we at Russian Wikipedia had **months** of interwiki gadgets not working for some users, because at first CODE user option was set to CODE when switched off, but after some change switching it on and off turns it to CODE.', ""(Was finally fixed [[URL Those who switched the option off after that change had gadget not working, but the project engineers weren't able to reproduce."", ""Other wikis which borrowed code from us had the issue too, and they most probably won't update the code."", 'I have no idea why this task\'s priority is set to ""Low"".', 'I don\'t know the site policy regarding changing priorities, I will try change to ""Normal"" at least, maybe needs ""High"".']",NA,0,"Low" +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"Preferences has a filter for some values." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"The search preferences, for example, are normalised to booleans." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"A few other are casted to integers." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"However the filters are only applied on the way into the database." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"On the way out they become strings regardless and nothing takes care of that." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)." +7074,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1519100319,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the way into the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,242,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the way into the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"Preferences has a filter for some values." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"The search preferences, for example, are normalised to booleans." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"A few other are casted to integers." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"However the filters are only applied on the in to the database." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"On the way out they become strings regardless and nothing takes care of that." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)." +7075,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",1423877781,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``` +rclimit: 50 +rows: ""30"" +searchNs0: true +searchNs1: false +.. +searchNs10: ""1"" +searchNs11: false +searchNs12: false +searchNs13: false +searchNs14: ""1"" +``` + +Quite the mix up. + +Few thoughts: Applying it on the way out would be a good start. Though it's not a a great system to use for extensions. We could extend the preference descriptor array with a `kind` property (for int, bool or str). Or perhaps something we can derive from the `type` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ","Preferences has a filter for some values. The search preferences, for example, are normalised to booleans. A few other are casted to integers. + +However the filters are only applied on the in to the database. On the way out they become strings regardless and nothing takes care of that. + +So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out: + +``CODE`CODEkindCODEtype` property (for HTMLForm field type). Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types. ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,84,NA,"['Preferences has a filter for some values.', 'The search preferences, for example, are normalised to booleans.', 'A few other are casted to integers.', 'However the filters are only applied on the in to the database.', 'On the way out they become strings regardless and nothing takes care of that.', ""So aside from the filters not being available to extension-provided preferences (it's a hardcoded privilege for core's own handling), even for the core ones, there's no normalisation on the way out:\n\n``CODE`CODEkindCODEtype` property (for HTMLForm field type)."", ""Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types.""]",NA,0,"Though the latter is extendable so we'd need to put it in the HTMLFormField class instead of simply having Preferences map the shortcuts to native types." +7076,"User preferences are inconsistently stored (bool/int as default, string for overrides)","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",1423875937,"PHID-USER-qgqq35kbi5wss2tlgmhg","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,84,NA,"['I have had similar difficulties and personally prefer booleans wherever possible.', ""They're more reliable and less likely to be unpredictable."", ""They are either true or false or they're invalid.""]",NA,0,"I have had similar difficulties and personally prefer booleans wherever possible." +7076,"User preferences are inconsistently stored (bool/int as default, string for overrides)","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",1423875937,"PHID-USER-qgqq35kbi5wss2tlgmhg","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,84,NA,"['I have had similar difficulties and personally prefer booleans wherever possible.', ""They're more reliable and less likely to be unpredictable."", ""They are either true or false or they're invalid.""]",NA,0,"They're more reliable and less likely to be unpredictable." +7076,"User preferences are inconsistently stored (bool/int as default, string for overrides)","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",1423875937,"PHID-USER-qgqq35kbi5wss2tlgmhg","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.","I have had similar difficulties and personally prefer booleans wherever possible. They're more reliable and less likely to be unpredictable. They are either true or false or they're invalid.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,84,NA,"['I have had similar difficulties and personally prefer booleans wherever possible.', ""They're more reliable and less likely to be unpredictable."", ""They are either true or false or they're invalid.""]",NA,0,"They are either true or false or they're invalid." +7077,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set CODE +(i.e., if I use WikiEditor's default): + - If I don't change the preference + CODE + - If I enable the preference + CODE +* If I set CODE (as in WMF cluster[1]): + - If I don't change the preference + CODE + - If I disable the preference + CODE (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + CODE + - If I disable the preference + CODE (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', ""The current behavior is ***very*** inconvenient:\n* If I do not set CODE\n(i.e., if I use WikiEditor's default):\n - If I don't change the preference\n CODE\n - If I enable the preference\n CODE\n* If I set CODE (as in WMF cluster[1]):\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (non-empty string == true!)"", ""* On English Wikipedia\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (empty string!)"", '[1] URL']",NA,0,"(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else." +7077,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set CODE +(i.e., if I use WikiEditor's default): + - If I don't change the preference + CODE + - If I enable the preference + CODE +* If I set CODE (as in WMF cluster[1]): + - If I don't change the preference + CODE + - If I disable the preference + CODE (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + CODE + - If I disable the preference + CODE (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', ""The current behavior is ***very*** inconvenient:\n* If I do not set CODE\n(i.e., if I use WikiEditor's default):\n - If I don't change the preference\n CODE\n - If I enable the preference\n CODE\n* If I set CODE (as in WMF cluster[1]):\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (non-empty string == true!)"", ""* On English Wikipedia\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (empty string!)"", '[1] URL']",NA,0,"[1] URL" +7077,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set CODE +(i.e., if I use WikiEditor's default): + - If I don't change the preference + CODE + - If I enable the preference + CODE +* If I set CODE (as in WMF cluster[1]): + - If I don't change the preference + CODE + - If I disable the preference + CODE (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + CODE + - If I disable the preference + CODE (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', ""The current behavior is ***very*** inconvenient:\n* If I do not set CODE\n(i.e., if I use WikiEditor's default):\n - If I don't change the preference\n CODE\n - If I enable the preference\n CODE\n* If I set CODE (as in WMF cluster[1]):\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (non-empty string == true!)"", ""* On English Wikipedia\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (empty string!)"", '[1] URL']",NA,0,"The current behavior is ***very*** inconvenient:\n* If I do not set CODE\n(i.e., if I use WikiEditor's default):\n - If I don't change the preference\n CODE\n - If I enable the preference\n CODE\n* If I set CODE (as in WMF cluster[1]):\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (non-empty string == true!)" +7077,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1466864706,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> `mw.user.options.get( 'anyBooleanPreference' ) === true` +> `mw.user.options.get( 'anyBooleanPreference' ) === false` +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set `$wgDefaultUserOptions['usebetatoolbar']` +(i.e., if I use WikiEditor's default): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === null` + - If I enable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""1""` +* If I set `$wgDefaultUserOptions['usebetatoolbar'] = 1` (as in WMF cluster[1]): + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === ""0""` (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + `mw.user.options.get( 'usebetatoolbar' ) === 1` + - If I disable the preference + `mw.user.options.get( 'usebetatoolbar' ) === """"` (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set CODE +(i.e., if I use WikiEditor's default): + - If I don't change the preference + CODE + - If I enable the preference + CODE +* If I set CODE (as in WMF cluster[1]): + - If I don't change the preference + CODE + - If I disable the preference + CODE (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + CODE + - If I disable the preference + CODE (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', ""The current behavior is ***very*** inconvenient:\n* If I do not set CODE\n(i.e., if I use WikiEditor's default):\n - If I don't change the preference\n CODE\n - If I enable the preference\n CODE\n* If I set CODE (as in WMF cluster[1]):\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (non-empty string == true!)"", ""* On English Wikipedia\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (empty string!)"", '[1] URL']",NA,0,"* On English Wikipedia\n - If I don't change the preference\n CODE\n - If I disable the preference\n CODE (empty string!)" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else." +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"]\n(i.e., if I use WikiEditor\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"t change the preference\n mw.user.options.get( \" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0," ) === null\n - If I enable the preference\n mw.user.options.get( \" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0," ) === ""1""\n* If I set $wgDefaultUserOptions[\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"] = 1 (as in WMF cluster[1]):\n - If I don\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"usebetatoolbar\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"usebetatoolbar\" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"t change the preference\n mw.user.options.get( \" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0," ) === 1\n - If I disable the preference\n mw.user.options.get( \" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0," ) === """" (empty string!)" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"[1] URL" +7078,"User preferences are inconsistently stored (bool/int as default, string for overrides)","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641",1408812707,"PHID-USER-sryrz6tgcfnnsiddx32p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","(In reply to Bartosz Dziewoński from comment #1) +> ... +> normalizing values of boolean prefs to true/false just before building this +> list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way. + ++1 for normalizing boolean preferences so that either +> mw.user.options.get( 'anyBooleanPreference' ) === true +> mw.user.options.get( 'anyBooleanPreference' ) === false +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] https://github.com/wikimedia/operations-mediawiki-config/blob/8178a4994c0137f5171798f3e831c0492c8cbc06/wmf-config/CommonSettings.php#L1641","(In reply to Bartosz Dziewoński from comment #1) +QUOTE +QUOTE +QUOTE + ++1 for normalizing boolean preferences so that either +QUOTE +QUOTE +and nothing else. + +The current behavior is ***very*** inconvenient: +* If I do not set $wgDefaultUserOptions['usebetatoolbar'] +(i.e., if I use WikiEditor's default): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === null + - If I enable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""1"" +* If I set $wgDefaultUserOptions['usebetatoolbar'] = 1 (as in WMF cluster[1]): + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === ""0"" (non-empty string == true!) +* On English Wikipedia + - If I don't change the preference + mw.user.options.get( 'usebetatoolbar' ) === 1 + - If I disable the preference + mw.user.options.get( 'usebetatoolbar' ) === """" (empty string!) + +[1] URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,59,NA,"['(In reply to Bartosz Dziewoński from comment #1)\nQUOTE\nQUOTE\nQUOTE\n\n+1 for normalizing boolean preferences so that either\nQUOTE\nQUOTE\nand nothing else.', 'The current behavior is ***very*** inconvenient:\n* If I do not set $wgDefaultUserOptions[\'usebetatoolbar\']\n(i.e., if I use WikiEditor\'s default):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === null\n - If I enable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""1""\n* If I set $wgDefaultUserOptions[\'usebetatoolbar\'] = 1 (as in WMF cluster[1]):\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === ""0"" (non-empty string == true!)', '* On English Wikipedia\n - If I don\'t change the preference\n mw.user.options.get( \'usebetatoolbar\' ) === 1\n - If I disable the preference\n mw.user.options.get( \'usebetatoolbar\' ) === """" (empty string!)', '[1] URL']",NA,0,"0" +7079,"User preferences are inconsistently stored (bool/int as default, string for overrides)","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",1375735877,"PHID-USER-a6jwrurphpx6yl4coupk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,5,NA,"['The integer came from $wgDefaultSettings.', 'Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.']",NA,0,"The integer came from $wgDefaultSettings." +7079,"User preferences are inconsistently stored (bool/int as default, string for overrides)","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",1375735877,"PHID-USER-a6jwrurphpx6yl4coupk","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.","The integer came from $wgDefaultSettings. Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,5,NA,"['The integer came from $wgDefaultSettings.', 'Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings.']",NA,0,"Set it to string there and it should work, except gadget and maybe the searchNs, because that are dynamically preferences, where the default is not stored in $wgDefaultSettings." +7080,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,5,NA,"['Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).', 'Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null.', 'You should just check for truthiness in this case.', ""I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.""]",NA,0,"Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them)." +7080,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,5,NA,"['Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).', 'Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null.', 'You should just check for truthiness in this case.', ""I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.""]",NA,0,"Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null." +7080,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,5,NA,"['Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).', 'Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null.', 'You should just check for truthiness in this case.', ""I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.""]",NA,0,"You should just check for truthiness in this case." +7080,"User preferences are inconsistently stored (bool/int as default, string for overrides)","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",1375703425,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yfjwr3je2btidmhmuccx","task_subcomment","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.","Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them). + +Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null. You should just check for truthiness in this case. + +I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,5,NA,"['Values that are actually saved in the database (ie, non-default ones) are always strings, and apparently usually equal to ""1"" (but for boolean prefs any truthy value is technically possible, especially if one uses the API to set them).', 'Values that are default ones are equal to whatever the programmer decided, and as you can see they might be 1/0, true/false, ""1""/""0"" or null.', 'You should just check for truthiness in this case.', ""I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way.""]",NA,0,"I'm not sure how to solve this, or whether we actually want to solve this; normalizing values of boolean prefs to true/false just before building this list (in ResourceLoaderUserOptionsModule#getScript) seems like the best way." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"He asks whether this should be offered to VE users while it does not support redirects." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"In other cases the different display formats (e.g." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact." +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +7092,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1375469280,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_description","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors./n/nen.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to. He asks whether this should be offered to VE users while it does not support redirects. + +However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors. There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided. + +There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant. In other cases the different display formats (e.g. generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact. + +As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response. Sort of a: +IF editor=""VisualEditor"" THEN do X ELSE do Y + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Medium",50,NA,NA,"open","True","c1",3,"False","False",4,NA,"['VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors.', 'en.wp user Andrew Gray notes that on creating a page in VE he is given several alternatives to writing a new article, one of which is to search for an existing page to redirect the title to.', 'He asks whether this should be offered to VE users while it does not support redirects.', 'However, the message is provided by [[MediaWiki:Newarticletext]] and the text is served identically in the source and visual editors.', 'There is no current mechanism to detect in which editor it is being displayed so different content cannot be provided.', 'There will be occasions where such messages and also edit notices are only relevant to either source or visual editor users or are differently relevant.', 'In other cases the different display formats (e.g.', 'generally horizontal in source, generally vertical in visual) may lead to different presentation choices for optimum impact.', ""As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response."", 'Sort of a:\nIF editor=""VisualEditor"" THEN do X ELSE do Y\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,0,"As it is not inconceivable that there will in future be other editors (developed by WMF or others) there should be some way for the editor to uniquely declare itself to such messages and for them to be able to determine what they do if they don't recognise the response." +7093,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",1378320091,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,9,NA,"[""I don't think there should be a control for separate interface messages."", 'However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.']",NA,0,"However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces." +7093,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",1378320091,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.","I don't think there should be a control for separate interface messages. + +However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,9,NA,"[""I don't think there should be a control for separate interface messages."", 'However either way, meanwhile a workaround is to use a CSS selector (.ve-available or .ve-not-available) to hide or display certain pieces.']",NA,0,"I don't think there should be a control for separate interface messages." +7094,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",1375472876,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,4,NA,"['Yes, that does sound far simpler to implement!', ""More difficult to keep the two in synch, but I suppose you can't have everything.""]",NA,0,"Yes, that does sound far simpler to implement!" +7094,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",1375472876,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.","Yes, that does sound far simpler to implement! More difficult to keep the two in synch, but I suppose you can't have everything.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,4,NA,"['Yes, that does sound far simpler to implement!', ""More difficult to keep the two in synch, but I suppose you can't have everything.""]",NA,0,"More difficult to keep the two in synch, but I suppose you can't have everything." +7095,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",1375470158,"PHID-USER-jnta3z3spxto3vbxdngm","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,4,NA,"['One possible way to do this is using a different interface message for VE in such cases.', 'MediaWiki:Newarticletext-VE for example.', 'This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)']",NA,0,"One possible way to do this is using a different interface message for VE in such cases." +7095,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",1375470158,"PHID-USER-jnta3z3spxto3vbxdngm","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,4,NA,"['One possible way to do this is using a different interface message for VE in such cases.', 'MediaWiki:Newarticletext-VE for example.', 'This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)']",NA,0,"MediaWiki:Newarticletext-VE for example." +7095,"VisualEditor: Provide a way for interface messages, edit notices, etc to display different content to Visual and Source editors","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",1375470158,"PHID-USER-jnta3z3spxto3vbxdngm","PHID-TASK-lusyegvtclbce7nfsesb","task_subcomment","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)","One possible way to do this is using a different interface message for VE in such cases. MediaWiki:Newarticletext-VE for example. + +This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,4,NA,"['One possible way to do this is using a different interface message for VE in such cases.', 'MediaWiki:Newarticletext-VE for example.', 'This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)']",NA,0,"This looks apparently more simple to do than creating yet another programming language to control such logic on the message itself ;)" +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Goto URL\n2." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Position the cursor at the start of the page directly before the bold ""T""." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"3." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Hit Backspace (to delete infobox)\n4." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Hit Ctrl+Z (undo)\n5." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Hit Backspace again\n6." +7247,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal",1375008900,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_description","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** `jonathan_haas` + +**Description:** +Steps to reproduce: + +1. Goto http://de.wikipedia.org/wiki/The_Binding_of_Isaac?veaction=edit +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph./n/n**Author:** CODE + +**Description:** +Steps to reproduce: + +1. Goto URL +2. Position the cursor at the start of the page directly before the bold ""T"". +3. Hit Backspace (to delete infobox) +4. Hit Ctrl+Z (undo) +5. Hit Backspace again +6. Hit Ctrl+Z again +Repeat as long as you want + +Actual result: + +On each Ctrl+Z a paragraph more is selected + +Expected result: + +Selection stays the same, undo should undo the action and not change the selection + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1394503778,NA,"resolved","True","c1",3,"False","False",3,NA,"['VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph.', '**Author:** CODE\n\n**Description:**\nSteps to reproduce:\n\n1.', 'Goto URL\n2.', 'Position the cursor at the start of the page directly before the bold ""T"".', '3.', 'Hit Backspace (to delete infobox)\n4.', 'Hit Ctrl+Z (undo)\n5.', 'Hit Backspace again\n6.', 'Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Hit Ctrl+Z again\nRepeat as long as you want\n\nActual result:\n\nOn each Ctrl+Z a paragraph more is selected\n\nExpected result:\n\nSelection stays the same, undo should undo the action and not change the selection\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal" +7248,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","This was fixed in gerrit 115759 as part of fixing bug 57552.",1394503778,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_subcomment","This was fixed in gerrit 115759 as part of fixing bug 57552.","This was fixed in gerrit 115759 as part of fixing bug 57552.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,36,NA,"['This was fixed in gerrit 115759 as part of fixing bug 57552.']",NA,0,"This was fixed in gerrit 115759 as part of fixing bug 57552." +7249,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.",1382445971,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_subcomment","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,16,NA,"['**jonathan_haas** wrote:\n\nDeleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2.', 'In short: The problem is more hidden, but the underlying issue has not been fixed.']",NA,0,"**jonathan_haas** wrote:\n\nDeleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2." +7249,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.",1382445971,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_subcomment","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.","**jonathan_haas** wrote: + +Deleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2. + +In short: The problem is more hidden, but the underlying issue has not been fixed.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,16,NA,"['**jonathan_haas** wrote:\n\nDeleting infoboxes with a simple backspace has been disabled, but this is still somewhat reproducible, if you select an area (for example the infobox _and_ the bold T) in step 2.', 'In short: The problem is more hidden, but the underlying issue has not been fixed.']",NA,0,"In short: The problem is more hidden, but the underlying issue has not been fixed." +7250,"VisualEditor: Selection expanded on undoing a deletion to cover the whole paragraph","Reproduced.",1375050421,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-3wvoqjxuqinfi7bgkax4","task_subcomment","Reproduced.","Reproduced.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Reproduced.']",NA,0,"Reproduced." +7678,"Template search results list should contain each template's descripton","**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1373980800,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_description","Template search results list should contain each template's descripton./n/n**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774","Template search results list should contain each template's descripton./n/n**Author:** CODE + +**Description:** +See this feedback trhead: [ URL ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1429285347,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",2,NA,"[""Template search results list should contain each template's descripton."", ""**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"So, add the template description to the search results list." +7678,"Template search results list should contain each template's descripton","**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1373980800,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_description","Template search results list should contain each template's descripton./n/n**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774","Template search results list should contain each template's descripton./n/n**Author:** CODE + +**Description:** +See this feedback trhead: [ URL ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1429285347,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",2,NA,"[""Template search results list should contain each template's descripton."", ""**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL" +7678,"Template search results list should contain each template's descripton","**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1373980800,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_description","Template search results list should contain each template's descripton./n/n**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774","Template search results list should contain each template's descripton./n/n**Author:** CODE + +**Description:** +See this feedback trhead: [ URL ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1429285347,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",2,NA,"[""Template search results list should contain each template's descripton."", ""**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"Template search results list should contain each template's descripton." +7678,"Template search results list should contain each template's descripton","**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1373980800,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_description","Template search results list should contain each template's descripton./n/n**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774","Template search results list should contain each template's descripton./n/n**Author:** CODE + +**Description:** +See this feedback trhead: [ URL ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1429285347,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",2,NA,"[""Template search results list should contain each template's descripton."", ""**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one." +7678,"Template search results list should contain each template's descripton","**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774",1373980800,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_description","Template search results list should contain each template's descripton./n/n**Author:** `turingt` + +**Description:** +See this feedback trhead: [ https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Feedback#Observation_-_Template_Editor_behavior_improved ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=51774","Template search results list should contain each template's descripton./n/n**Author:** CODE + +**Description:** +See this feedback trhead: [ URL ] + +The search results for parameters include each parameter's description, making it easy to select the right one. + +But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template). + +So, add the template description to the search results list. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1429285347,"PHID-USER-ydswvwhh5pm4lshahjje","resolved","True","c1",3,"False","False",2,NA,"[""Template search results list should contain each template's descripton."", ""**Author:** CODE\n\n**Description:**\nSee this feedback trhead: [ URL ]\n\nThe search results for parameters include each parameter's description, making it easy to select the right one."", ""But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)."", 'So, add the template description to the search results list.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"But the templates list result contains only the template name, even though the template description is available (it's shown right 'after' a template is selected, so it doesn't help in choosing the right template)." +7679,"Template search results list should contain each template's descripton","Verified the fix in Betalabs",1429568922,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","Verified the fix in Betalabs","Verified the fix in Betalabs",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,94,NA,"['Verified the fix in Betalabs']",NA,0,"Verified the fix in Betalabs" +7680,"Template search results list should contain each template's descripton","Change 203459 merged by jenkins-bot: +Show template description in the template search + +[[https://gerrit.wikimedia.org/r/203459]]",1429262905,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","Change 203459 merged by jenkins-bot: +Show template description in the template search + +[[https://gerrit.wikimedia.org/r/203459]]","Change 203459 merged by jenkins-bot: +Show template description in the template search + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,93,NA,"['Change 203459 merged by jenkins-bot:\nShow template description in the template search\n\n[[GERRIT_URL]]']",NA,0,"Change 203459 merged by jenkins-bot:\nShow template description in the template search\n\n[[GERRIT_URL]]" +7681,"Template search results list should contain each template's descripton","Change 203459 had a related patch set uploaded (by Mooeypoo): +Show template description in the template search + +[[https://gerrit.wikimedia.org/r/203459]] +",1428697842,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","Change 203459 had a related patch set uploaded (by Mooeypoo): +Show template description in the template search + +[[https://gerrit.wikimedia.org/r/203459]] +","Change 203459 had a related patch set uploaded (by Mooeypoo): +Show template description in the template search + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,92,NA,"['Change 203459 had a related patch set uploaded (by Mooeypoo):\nShow template description in the template search\n\n[[GERRIT_URL]]']",NA,0,"Change 203459 had a related patch set uploaded (by Mooeypoo):\nShow template description in the template search\n\n[[GERRIT_URL]]" +7682,"Template search results list should contain each template's descripton","Thanks for the explanation, I've now reported it as bug 51822.",1374511823,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","Thanks for the explanation, I've now reported it as bug 51822.","Thanks for the explanation, I've now reported it as bug 51822.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""Thanks for the explanation, I've now reported it as bug 51822.""]",NA,0,"Thanks for the explanation, I've now reported it as bug 51822." +7683,"Template search results list should contain each template's descripton","(In reply to comment #4) +> (In reply to comment #3) +> > > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > > functionality to be useful only for people who already know template names +> > > (i.e. those who don't need it). +> > +> > That is a distinct enhancement request; please open a new bug for it. +> +> Is it distinct or is it part of bug 51670? + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.",1374509714,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","(In reply to comment #4) +> (In reply to comment #3) +> > > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > > functionality to be useful only for people who already know template names +> > > (i.e. those who don't need it). +> > +> > That is a distinct enhancement request; please open a new bug for it. +> +> Is it distinct or is it part of bug 51670? + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.","(In reply to comment #4) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,3,NA,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt's distinct."", ""This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.""]",NA,0,"(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt's distinct." +7683,"Template search results list should contain each template's descripton","(In reply to comment #4) +> (In reply to comment #3) +> > > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > > functionality to be useful only for people who already know template names +> > > (i.e. those who don't need it). +> > +> > That is a distinct enhancement request; please open a new bug for it. +> +> Is it distinct or is it part of bug 51670? + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.",1374509714,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","(In reply to comment #4) +> (In reply to comment #3) +> > > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > > functionality to be useful only for people who already know template names +> > > (i.e. those who don't need it). +> > +> > That is a distinct enhancement request; please open a new bug for it. +> +> Is it distinct or is it part of bug 51670? + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.","(In reply to comment #4) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +It's distinct. This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,3,NA,"[""(In reply to comment #4)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIt's distinct."", ""This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion.""]",NA,0,"This is asking for VisualEditor when searching pages (for links), categories (for the category dialog) and templates (for the transclusion dialog) to use an entirely different (and slower) part of MediaWiki's search infrastructure so we can do in-string searching rather than left-string completion." +7684,"Template search results list should contain each template's descripton","(In reply to comment #3) +> > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > functionality to be useful only for people who already know template names +> > (i.e. those who don't need it). +> +> That is a distinct enhancement request; please open a new bug for it. + +Is it distinct or is it part of bug 51670?",1374508615,"PHID-USER-ysftv67jxeaxdwcakvwo","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","(In reply to comment #3) +> > If I type ""book"", template ""Cite book"" is not shown, which limits the search +> > functionality to be useful only for people who already know template names +> > (i.e. those who don't need it). +> +> That is a distinct enhancement request; please open a new bug for it. + +Is it distinct or is it part of bug 51670?","(In reply to comment #3) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Is it distinct or is it part of bug 51670?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIs it distinct or is it part of bug 51670?']",NA,0,"(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nIs it distinct or is it part of bug 51670?" +7685,"Template search results list should contain each template's descripton","(In reply to comment #2) +> Also typing a word only shows template names starting with that word, not +> containing it, which is a weird search behavior. +> +> If I type ""book"", template ""Cite book"" is not shown, which limits the search +> functionality to be useful only for people who already know template names +> (i.e. those who don't need it). + +That is a distinct enhancement request; please open a new bug for it.",1374507636,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","(In reply to comment #2) +> Also typing a word only shows template names starting with that word, not +> containing it, which is a weird search behavior. +> +> If I type ""book"", template ""Cite book"" is not shown, which limits the search +> functionality to be useful only for people who already know template names +> (i.e. those who don't need it). + +That is a distinct enhancement request; please open a new bug for it.","(In reply to comment #2) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +That is a distinct enhancement request; please open a new bug for it.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,3,NA,"['(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat is a distinct enhancement request; please open a new bug for it.']",NA,0,"(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThat is a distinct enhancement request; please open a new bug for it." +7686,"Template search results list should contain each template's descripton","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",1374502086,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['**turingt** wrote:\n\nAlso typing a word only shows template names starting with that word, not containing it, which is a weird search behavior.', 'If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e.', ""those who don't need it).""]",NA,0,"**turingt** wrote:\n\nAlso typing a word only shows template names starting with that word, not containing it, which is a weird search behavior." +7686,"Template search results list should contain each template's descripton","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",1374502086,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['**turingt** wrote:\n\nAlso typing a word only shows template names starting with that word, not containing it, which is a weird search behavior.', 'If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e.', ""those who don't need it).""]",NA,0,"If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e." +7686,"Template search results list should contain each template's descripton","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",1374502086,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).","**turingt** wrote: + +Also typing a word only shows template names starting with that word, not containing it, which is a weird search behavior. + +If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e. those who don't need it).",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['**turingt** wrote:\n\nAlso typing a word only shows template names starting with that word, not containing it, which is a weird search behavior.', 'If I type ""book"", template ""Cite book"" is not shown, which limits the search functionality to be useful only for people who already know template names (i.e.', ""those who don't need it).""]",NA,0,"those who don't need it)." +7687,"Template search results list should contain each template's descripton","Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New' + +https://en.wikipedia.org/wiki/Special:PrefixIndex/Template:New + +More practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.",1374462543,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-3es7m4cbr63gg2w4l5or","task_subcomment","Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New' + +https://en.wikipedia.org/wiki/Special:PrefixIndex/Template:New + +More practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.","Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New' + +URL + +More practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"[""Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New'\n\nURL\n\nMore practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results.""]",NA,0,"Also typing in 'new' into the New template box returns a list of 10 templates starting with 'new', with no way to scroll through the longer list of templates starting/containing with 'New'\n\nURL\n\nMore practical, 'New Zealand' or 'New York' only returns 10, and the user may not know the right keyword needed to return better results." +8483,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","Try editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50551 +https://bugzilla.wikimedia.org/show_bug.cgi?id=50910 +https://bugzilla.wikimedia.org/show_bug.cgi?id=51708",1372453440,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_description","VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it./n/nTry editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50551 +https://bugzilla.wikimedia.org/show_bug.cgi?id=50910 +https://bugzilla.wikimedia.org/show_bug.cgi?id=51708","VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it./n/nTry editing the professional ratings template in URL + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL +URL +URL","Medium",50,1554826913,"PHID-USER-wkpnidxoctuhawexig5p","duplicate","True","c1",2,"False","False",-1,NA,"[""VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it."", 'Try editing the professional ratings template in URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL']",FALSE,0,"Try editing the professional ratings template in URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL" +8483,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","Try editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50551 +https://bugzilla.wikimedia.org/show_bug.cgi?id=50910 +https://bugzilla.wikimedia.org/show_bug.cgi?id=51708",1372453440,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_description","VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it./n/nTry editing the professional ratings template in https://en.wikipedia.org/wiki/All_6%27s_and_7%27s?veaction=edit + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50551 +https://bugzilla.wikimedia.org/show_bug.cgi?id=50910 +https://bugzilla.wikimedia.org/show_bug.cgi?id=51708","VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it./n/nTry editing the professional ratings template in URL + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +URL +URL +URL","Medium",50,1554826913,"PHID-USER-wkpnidxoctuhawexig5p","duplicate","True","c1",2,"False","False",-1,NA,"[""VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it."", 'Try editing the professional ratings template in URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nURL\nURL\nURL']",FALSE,0,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it." +8484,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","This issue also occurs for the following case: + +1.Add an image +2.Add a gallery +3.Change the position of the image to the left +4.Select the gallery +5.Try to select the image + +Observed Result: +Since the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.",1396302080,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","This issue also occurs for the following case: + +1.Add an image +2.Add a gallery +3.Change the position of the image to the left +4.Select the gallery +5.Try to select the image + +Observed Result: +Since the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.","This issue also occurs for the following case: + +1.Add an image +2.Add a gallery +3.Change the position of the image to the left +4.Select the gallery +5.Try to select the image + +Observed Result: +Since the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,39,NA,"['This issue also occurs for the following case:\n\n1.Add an image\n2.Add a gallery \n3.Change the position of the image to the left \n4.Select the gallery\n5.Try to select the image \n\nObserved Result:\nSince the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that.']",NA,0,"This issue also occurs for the following case:\n\n1.Add an image\n2.Add a gallery \n3.Change the position of the image to the left \n4.Select the gallery\n5.Try to select the image \n\nObserved Result:\nSince the width of the phantom for the gallery is 100% , it is overlapping with the image and it becomes difficult to select the image after that." +8485,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 51048 has been marked as a duplicate of this bug. ***",1385381652,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 51048 has been marked as a duplicate of this bug. ***","*** Bug 51048 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,21,NA,"['*** Bug 51048 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 51048 has been marked as a duplicate of this bug." +8485,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 51048 has been marked as a duplicate of this bug. ***",1385381652,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 51048 has been marked as a duplicate of this bug. ***","*** Bug 51048 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,21,NA,"['*** Bug 51048 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +8486,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 50443 has been marked as a duplicate of this bug. ***",1377830806,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 50443 has been marked as a duplicate of this bug. ***","*** Bug 50443 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,8,NA,"['*** Bug 50443 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 50443 has been marked as a duplicate of this bug." +8486,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 50443 has been marked as a duplicate of this bug. ***",1377830806,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 50443 has been marked as a duplicate of this bug. ***","*** Bug 50443 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,8,NA,"['*** Bug 50443 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +8487,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 50211 has been marked as a duplicate of this bug. ***",1373164008,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 50211 has been marked as a duplicate of this bug. ***","*** Bug 50211 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['*** Bug 50211 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 50211 has been marked as a duplicate of this bug." +8487,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","*** Bug 50211 has been marked as a duplicate of this bug. ***",1373164008,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","*** Bug 50211 has been marked as a duplicate of this bug. ***","*** Bug 50211 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['*** Bug 50211 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +8488,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.",1372456631,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-1,NA,"['Changed title to ""Phantoms can be width:100% when the object they\'re meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play.', 'This can make it impossible to edit the floated item.']",NA,0,"Changed title to ""Phantoms can be width:100% when the object they\" +8488,"VisualEditor: Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.",1372456631,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-2r6x4q4bt3fqtg3es4ps","task_subcomment","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.","Changed title to ""Phantoms can be width:100% when the object they're meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play. This can make it impossible to edit the floated item.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-1,NA,"['Changed title to ""Phantoms can be width:100% when the object they\'re meant to cover has a floated element alongside it""; looks like the phantom is generated to be as wide as its target ""should"" be, before the floats come into play.', 'This can make it impossible to edit the floated item.']",NA,0,"; looks like the phantom is generated to be as wide as its target " +8763,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830",1371995700,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_description","VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff./n/n...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830","VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff./n/n...and quite dramatically - take a look at URL + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830","Medium",50,1642380969,"PHID-USER-wkpnidxoctuhawexig5p","resolved","True","c1",2,"False","False",-2,NA,"['VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff.', '...and quite dramatically - take a look at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nT50830']",FALSE,1,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff." +8763,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830",1371995700,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_description","VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff./n/n...and quite dramatically - take a look at https://en.wikipedia.org/w/index.php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830","VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff./n/n...and quite dramatically - take a look at URL + +-------------------------- +**Version**: unspecified +**Severity**: normal +**See Also**: +T50830","Medium",50,1642380969,"PHID-USER-wkpnidxoctuhawexig5p","resolved","True","c1",2,"False","False",-2,NA,"['VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff.', '...and quite dramatically - take a look at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nT50830']",FALSE,1,"...and quite dramatically - take a look at URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**See Also**:\nT50830" +8764,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",1642380969,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,446,NA,"['Parsoid\'s ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit.', 'Please re-open if you run into similar dirty diffs that happened within the last year or so.']",NA,1,"Parsoid\" +8764,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",1642380969,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.","Parsoid's ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit. Please re-open if you run into similar dirty diffs that happened within the last year or so.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,446,NA,"['Parsoid\'s ""selective serialization"" has been improved greatly since 2013 and this should not be occurring any more, unless content in the same paragraph was changed in the edit.', 'Please re-open if you run into similar dirty diffs that happened within the last year or so.']",NA,1,"selective serialization" +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh." +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,":-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause." +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\" +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully." +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement." +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these." +8765,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",1372000762,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","(In reply to comment #0) +> ...and quite dramatically - take a look at +> https://en.wikipedia.org/w/index. +> php?title=Modified_discrete_cosine_transform&diff=561051085&oldid=558725133 + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +> Brad also has a suggestion (along with a bug report) for a workflow to make +> these easier to identify: + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.","(In reply to comment #0) +QUOTE +QUOTE +QUOTE + +Eurgh. I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement. + +Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these. Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen. :-( + +Punting to Roan for thoughts, but I think this is probably a lost cause. + +(In reply to comment #1) +QUOTE +QUOTE + +That's going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can't objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-2,NA,"['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\n\nEurgh.', ""I hate being proven wrong; each of those changes fixes the (entirely-broken, but masked for users by MediaWiki) wikitext; these are the kinds of errors it's not really possible for us to re-implement."", ""Specifically, Foo Bar Baz is definitely broken HTML (mis-nested annotations), and I don't think it's necessarily a bad thing that we fix these."", ""Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen."", ':-(\n\nPunting to Roan for thoughts, but I think this is probably a lost cause.', '(In reply to comment #1)\nQUOTE\nQUOTE\n\nThat\'s going to be done in VisualEditor as part of bug 49761 (well, not that way, because VE can\'t objectively know what bits of the DOM it ""should"" have just altered unless we have a local copy of MediaWiki :-)) but yes, coming very soon, hopefully.']",NA,1,"Obviously it'd be much better if we had a bot do a massive run over the corpus and fix these for users now, rather than have them blame VE, but that's not going to happen." +8766,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",1371996216,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",NA,NA,NA,NA,NA,"True","c1",2,"False",NA,-2,NA,"['Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff.', ""If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team."", '(Please don\'t try to use this idea as an error concealment technique: these errors shouldn\'t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""']",NA,1,"Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff." +8766,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",1371996216,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",NA,NA,NA,NA,NA,"True","c1",2,"False",NA,-2,NA,"['Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff.', ""If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team."", '(Please don\'t try to use this idea as an error concealment technique: these errors shouldn\'t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""']",NA,1,"(Please don\" +8766,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",1371996216,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",NA,NA,NA,NA,NA,"True","c1",2,"False",NA,-2,NA,"['Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff.', ""If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team."", '(Please don\'t try to use this idea as an error concealment technique: these errors shouldn\'t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""']",NA,1,"t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""" +8766,"VisualEditor: Mis-nested annotations are cleaned up, leading to a dirty diff","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",1371996216,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-vrnyctiie6ntzdrqt77a","task_subcomment","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""","Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify: + +""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff. If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team. (Please don't try to use this idea as an error concealment technique: these errors shouldn't occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""",NA,NA,NA,NA,NA,"True","c1",2,"False",NA,-2,NA,"['Brad also has a suggestion (along with a bug report) for a workflow to make these easier to identify:\n\n""One way to catch this for debugging purposes would be for the VisualEditor to make a note at tuntime of which sections of the article have been edited visually, for the JS code to report this to the server at save time, and then to check on the server side which sections of the article have changed in the wikitext diff.', ""If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team."", '(Please don\'t try to use this idea as an error concealment technique: these errors shouldn\'t occur, as every one of them reveals some sort of bug, either in the code or the data model, and hiding them would make the software more, rather than less brittle.)""']",NA,1,"If (a) the section structure of the article remains unchanged from before the edit, and (b) there are wikitext differences in sections that have not been changed by the editor in visual mode, then something's clearly gone wrong, and the edit session should be auto-reported to the programming team." +9354,"Parsoid should support and natively as they are not normal parser tags","screenshot + +Example: https://www.mediawiki.org/wiki/Communication + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50284 + +**Attached**: {F10855}",1369744440,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_description","Parsoid should support and natively as they are not normal parser tags./n/nscreenshot + +Example: https://www.mediawiki.org/wiki/Communication + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50284 + +**Attached**: {F10855}","Parsoid should support and natively as they are not normal parser tags./n/nscreenshot + +Example: URL + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: URL +**See Also**: +URL + +**Attached**: {F10855}","Medium",50,1451432369,"PHID-USER-gxcjmjpejlhfnrquksm2","resolved","True","c1",1,"True","False",-5,NA,"['Parsoid should support and natively as they are not normal parser tags.', 'screenshot\n\nExample: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL\n**See Also**:\nURL\n\n**Attached**: {F10855}']",FALSE,0,"Parsoid should support and natively as they are not normal parser tags." +9354,"Parsoid should support and natively as they are not normal parser tags","screenshot + +Example: https://www.mediawiki.org/wiki/Communication + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50284 + +**Attached**: {F10855}",1369744440,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_description","Parsoid should support and natively as they are not normal parser tags./n/nscreenshot + +Example: https://www.mediawiki.org/wiki/Communication + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=50284 + +**Attached**: {F10855}","Parsoid should support and natively as they are not normal parser tags./n/nscreenshot + +Example: URL + +-------------------------- +**Version**: unspecified +**Severity**: major +**URL**: URL +**See Also**: +URL + +**Attached**: {F10855}","Medium",50,1451432369,"PHID-USER-gxcjmjpejlhfnrquksm2","resolved","True","c1",1,"True","False",-5,NA,"['Parsoid should support and natively as they are not normal parser tags.', 'screenshot\n\nExample: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL\n**See Also**:\nURL\n\n**Attached**: {F10855}']",FALSE,0,"screenshot\n\nExample: URL\n\n--------------------------\n**Version**: unspecified\n**Severity**: major\n**URL**: URL\n**See Also**:\nURL\n\n**Attached**: {F10855}" +9355,"Parsoid should support and natively as they are not normal parser tags","Parsoid will now wrap these appropriately with the proper typeof `mw:Extension/translate` and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.",1451432369,"PHID-USER-gxcjmjpejlhfnrquksm2","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid will now wrap these appropriately with the proper typeof `mw:Extension/translate` and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.","Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,130,NA,"['Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot.', 'Support for the Translate extension in VE is still needed, but a separate task.']",NA,0,"Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot." +9355,"Parsoid should support and natively as they are not normal parser tags","Parsoid will now wrap these appropriately with the proper typeof `mw:Extension/translate` and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.",1451432369,"PHID-USER-gxcjmjpejlhfnrquksm2","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid will now wrap these appropriately with the proper typeof `mw:Extension/translate` and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.","Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot. + +Support for the Translate extension in VE is still needed, but a separate task.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,130,NA,"['Parsoid will now wrap these appropriately with the proper typeof CODE and whatnot.', 'Support for the Translate extension in VE is still needed, but a separate task.']",NA,0,"Support for the Translate extension in VE is still needed, but a separate task." +9356,"Parsoid should support and natively as they are not normal parser tags","Change 261293 merged by jenkins-bot: +T50891: Register and natively + +[[https://gerrit.wikimedia.org/r/261293]]",1451423865,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 261293 merged by jenkins-bot: +T50891: Register and natively + +[[https://gerrit.wikimedia.org/r/261293]]","Change 261293 merged by jenkins-bot: +T50891: Register and natively + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,130,NA,"['Change 261293 merged by jenkins-bot:\nT50891: Register and natively\n\n[[GERRIT_URL]]']",NA,0,"Change 261293 merged by jenkins-bot:\nT50891: Register and natively\n\n[[GERRIT_URL]]" +9357,"Parsoid should support and natively as they are not normal parser tags","Change 261293 had a related patch set uploaded (by Arlolra): +T50891: Register and natively + +[[https://gerrit.wikimedia.org/r/261293]] +",1451345650,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 261293 had a related patch set uploaded (by Arlolra): +T50891: Register and natively + +[[https://gerrit.wikimedia.org/r/261293]] +","Change 261293 had a related patch set uploaded (by Arlolra): +T50891: Register and natively + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,130,NA,"['Change 261293 had a related patch set uploaded (by Arlolra):\nT50891: Register and natively\n\n[[GERRIT_URL]]']",NA,0,"Change 261293 had a related patch set uploaded (by Arlolra):\nT50891: Register and natively\n\n[[GERRIT_URL]]" +9358,"Parsoid should support and natively as they are not normal parser tags",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",1449004296,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.","QUOTE +QUOTE + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,126,NA,"['QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions.', 'As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated.', 'VE and other tools can then use this to provide translation support by querying the API to manage translations.', 'I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.']",NA,0,"QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions." +9358,"Parsoid should support and natively as they are not normal parser tags",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",1449004296,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.","QUOTE +QUOTE + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,126,NA,"['QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions.', 'As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated.', 'VE and other tools can then use this to provide translation support by querying the API to manage translations.', 'I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.']",NA,0,"As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated." +9358,"Parsoid should support and natively as they are not normal parser tags",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",1449004296,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.","QUOTE +QUOTE + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,126,NA,"['QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions.', 'As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated.', 'VE and other tools can then use this to provide translation support by querying the API to manage translations.', 'I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.']",NA,0,"VE and other tools can then use this to provide translation support by querying the API to manage translations." +9358,"Parsoid should support and natively as they are not normal parser tags",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",1449004296,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment",">>! In T50891#1840365, @kaldari wrote: +> Any update on this? + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.","QUOTE +QUOTE + +A generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions. As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated. VE and other tools can then use this to provide translation support by querying the API to manage translations. + +I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,126,NA,"['QUOTE\nQUOTE\n\nA generic extension registration mechanism in Parsoid is one of our (parsing team) goals for this quarter and once that is done, we should be able to work on specific extensions.', 'As noted in T50891#1002436, I think we can implement a parsoid-native version of this which adds annotations to the DOM that marks trees that need to be translated.', 'VE and other tools can then use this to provide translation support by querying the API to manage translations.', 'I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on.']",NA,0,"I think we can get the extension part done within the next month or so, but the tools to build on top of that is something for VE and language team to work on." +9359,"Parsoid should support and natively as they are not normal parser tags","Any update on this?",1448940120,"PHID-USER-a5pveeqqwaddgfjiv2fq","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Any update on this?","Any update on this?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,126,NA,"['Any update on this?']",NA,0,"Any update on this?" +9360,"Parsoid should support and natively as they are not normal parser tags","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",1422567418,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"[""Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']",NA,0,"This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation." +9360,"Parsoid should support and natively as they are not normal parser tags","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",1422567418,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"[""Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']",NA,0,"In addition, it would also have to register a html2wt handler for serializing it back to wikitext." +9360,"Parsoid should support and natively as they are not normal parser tags","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",1422567418,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"[""Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']",NA,0,"This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does." +9360,"Parsoid should support and natively as they are not normal parser tags","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",1422567418,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"[""Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']",NA,0,"Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months." +9360,"Parsoid should support and natively as they are not normal parser tags","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",1422567418,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.","Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension). + +This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation. In addition, it would also have to register a html2wt handler for serializing it back to wikitext. + +This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does. Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"[""Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)."", 'This native translate will be relatively straightforward and will not do anything special beyond recognizing the and associated tags and marking up DOM fragments with a special typeof that clients like VE or gadgets or anyone could use to enable translation.', 'In addition, it would also have to register a html2wt handler for serializing it back to wikitext.', 'This should not be a lot of work -- most of it will be in figuring out if there are any tricky things that the translate extension does.', 'Talking to Niklas, we figured this is not high priority, but something worth tackling over the next 6 months.']",NA,0,"Since is a special extension that hooks into the parser pipeline in a way that is not visible to Parsoid, and also since it doesn't render anything new, but marks DOM fragments for translation, the ideal way to deal with this in the short term (till translation goes with a VE based approach) is to implement a native version of translate in Parsoid (just like Cite and planned Gallery extension)." +9361,"Parsoid should support and natively as they are not normal parser tags","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",1422482506,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']",NA,0,"I had a chat with Subbu about this." +9361,"Parsoid should support and natively as they are not normal parser tags","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",1422482506,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']",NA,0,"In the short tem (this year) we could add configurable support for tags in parsoid." +9361,"Parsoid should support and natively as they are not normal parser tags","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",1422482506,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']",NA,0,"That support will preserve the tags and comments when pages are edited with VE." +9361,"Parsoid should support and natively as they are not normal parser tags","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",1422482506,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']",NA,0,"In the long term we will implement support for translatable pages without any kind of markup." +9361,"Parsoid should support and natively as they are not normal parser tags","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",1422482506,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.","I had a chat with Subbu about this. In the short tem (this year) we could add configurable support for tags in parsoid. That support will preserve the tags and comments when pages are edited with VE. In the long term we will implement support for translatable pages without any kind of markup. Marking those pages for translation would only work with VE and it needs special page translation module in VE.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,82,NA,"['I had a chat with Subbu about this.', 'In the short tem (this year) we could add configurable support for tags in parsoid.', 'That support will preserve the tags and comments when pages are edited with VE.', 'In the long term we will implement support for translatable pages without any kind of markup.', 'Marking those pages for translation would only work with VE and it needs special page translation module in VE.']",NA,0,"Marking those pages for translation would only work with VE and it needs special page translation module in VE." +9362,"Parsoid should support and natively as they are not normal parser tags","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",1422112321,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.","Kabhi2104 asked on #mediawiki-i18n: +QUOTE + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[URL list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,81,NA,"['Kabhi2104 asked on #mediawiki-i18n:\nQUOTE\n\nExplained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn\'t know"" it.', 'A symptom is the absence from [[URL list on Special:Version]].', 'Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894.', ""But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]."", ""More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.""]",NA,0,"Kabhi2104 asked on #mediawiki-i18n:\nQUOTE\n\nExplained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn\" +9362,"Parsoid should support and natively as they are not normal parser tags","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",1422112321,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.","Kabhi2104 asked on #mediawiki-i18n: +QUOTE + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[URL list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,81,NA,"['Kabhi2104 asked on #mediawiki-i18n:\nQUOTE\n\nExplained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn\'t know"" it.', 'A symptom is the absence from [[URL list on Special:Version]].', 'Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894.', ""But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]."", ""More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.""]",NA,0,"t be required]]."", ""More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don" +9362,"Parsoid should support and natively as they are not normal parser tags","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",1422112321,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Kabhi2104 asked on #mediawiki-i18n: +> Nemo_bis: i had one doubt, what does normal parser tags mean ? + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[https://www.mediawiki.org/wiki/Special:Version|the list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[https://meta.wikimedia.org/wiki/Help_talk:List#List-agnostic_markup_insertions|is meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.","Kabhi2104 asked on #mediawiki-i18n: +QUOTE + +Explained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn't know"" it. A symptom is the absence from [[URL list on Special:Version]]. + +Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894. But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]. + +More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,81,NA,"['Kabhi2104 asked on #mediawiki-i18n:\nQUOTE\n\nExplained briefly from a non-technical perspective, this means that is a ""tag"" for the Translate extension, but the parser ""doesn\'t know"" it.', 'A symptom is the absence from [[URL list on Special:Version]].', 'Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894.', ""But even in the current situation there are some limitations, especially for the newline, which [[URL meaningful for the parser and perhaps shouldn't be required]]."", ""More broadly, one could speculate that most wikitext markup is meant to add or modify the HTML of the resulting page, or properties of the page in the database: while translate tags don't do either and are properties of the wikitext itself.""]",NA,0," it.', 'A symptom is the absence from [[URL list on Special:Version]].', 'Concretely, the parser deals with tags in ways that interfere with the Translate syntax, with some consequences identified in T50891#524894.', " +9363,"Parsoid should support and natively as they are not normal parser tags","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.",1412577526,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,66,NA,"[""To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself."", 'I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.']",NA,0,"I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid." +9363,"Parsoid should support and natively as they are not normal parser tags","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.",1412577526,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.","To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself. I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,66,NA,"[""To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself."", 'I cannot continue with this patch/bug until I get help from other people to modify parser/parsoid.']",NA,0,"To be clear: there is nothing wrong with that patch itself, it just doesn't work due to limitations in the parser itself." +9364,"Parsoid should support and natively as they are not normal parser tags","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.",1399802210,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.","(In reply to Nemo from comment #43) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +No. There is no patch to review for merge. There is patch to re-*do*.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['(In reply to Nemo from comment #43)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'There is no patch to review for merge.', 'There is patch to re-*do*.']",NA,0,"(In reply to Nemo from comment #43)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo." +9364,"Parsoid should support and natively as they are not normal parser tags","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.",1399802210,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.","(In reply to Nemo from comment #43) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +No. There is no patch to review for merge. There is patch to re-*do*.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['(In reply to Nemo from comment #43)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'There is no patch to review for merge.', 'There is patch to re-*do*.']",NA,0,"There is no patch to review for merge." +9364,"Parsoid should support and natively as they are not normal parser tags","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.",1399802210,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to Nemo from comment #43) +> (In reply to James Forrester from comment #42) +> > No patch any more. :-( +> +> Hmm I'm not sure that's what ""Can be re-activated if there is outlook on +> getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible +> way to tag such stale patches in need of TLC. + +No. There is no patch to review for merge. There is patch to re-*do*.","(In reply to Nemo from comment #43) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +No. There is no patch to review for merge. There is patch to re-*do*.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['(In reply to Nemo from comment #43)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nNo.', 'There is no patch to review for merge.', 'There is patch to re-*do*.']",NA,0,"There is patch to re-*do*." +9365,"Parsoid should support and natively as they are not normal parser tags","(In reply to James Forrester from comment #42) +> No patch any more. :-( + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.",1399802137,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to James Forrester from comment #42) +> No patch any more. :-( + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.","(In reply to James Forrester from comment #42) +QUOTE + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['(In reply to James Forrester from comment #42)\nQUOTE\n\nHmm I\'m not sure that\'s what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.']",NA,0,"(In reply to James Forrester from comment #42)\nQUOTE\n\nHmm I\" +9365,"Parsoid should support and natively as they are not normal parser tags","(In reply to James Forrester from comment #42) +> No patch any more. :-( + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.",1399802137,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to James Forrester from comment #42) +> No patch any more. :-( + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.","(In reply to James Forrester from comment #42) +QUOTE + +Hmm I'm not sure that's what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['(In reply to James Forrester from comment #42)\nQUOTE\n\nHmm I\'m not sure that\'s what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC.']",NA,0,"s what ""Can be re-activated if there is outlook on getting this in a mergable state"" means, PATCH_TO_REVIEW seems a sensible way to tag such stale patches in need of TLC." +9366,"Parsoid should support and natively as they are not normal parser tags","No patch any more. :-(",1399715908,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","No patch any more. :-(","No patch any more. :-(",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['No patch any more.', ':-(']",NA,0,"No patch any more." +9366,"Parsoid should support and natively as they are not normal parser tags","No patch any more. :-(",1399715908,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","No patch any more. :-(","No patch any more. :-(",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,44,NA,"['No patch any more.', ':-(']",NA,0,":-(" +9367,"Parsoid should support and natively as they are not normal parser tags","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583",1397663477,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['Change 91583 abandoned by Siebrand:\nAdd $wgTranslatePageTranslationUseParserHook\n\nReason:\nAbandoned as there is no progress on this patch set.', 'Can be re-activated if there is outlook on getting this in a mergable state.', 'GERRIT_URL']",NA,0,"Change 91583 abandoned by Siebrand:\nAdd $wgTranslatePageTranslationUseParserHook\n\nReason:\nAbandoned as there is no progress on this patch set." +9367,"Parsoid should support and natively as they are not normal parser tags","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583",1397663477,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['Change 91583 abandoned by Siebrand:\nAdd $wgTranslatePageTranslationUseParserHook\n\nReason:\nAbandoned as there is no progress on this patch set.', 'Can be re-activated if there is outlook on getting this in a mergable state.', 'GERRIT_URL']",NA,0,"Can be re-activated if there is outlook on getting this in a mergable state." +9367,"Parsoid should support and natively as they are not normal parser tags","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583",1397663477,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +https://gerrit.wikimedia.org/r/91583","Change 91583 abandoned by Siebrand: +Add $wgTranslatePageTranslationUseParserHook + +Reason: +Abandoned as there is no progress on this patch set. Can be re-activated if there is outlook on getting this in a mergable state. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,41,NA,"['Change 91583 abandoned by Siebrand:\nAdd $wgTranslatePageTranslationUseParserHook\n\nReason:\nAbandoned as there is no progress on this patch set.', 'Can be re-activated if there is outlook on getting this in a mergable state.', 'GERRIT_URL']",NA,0,"GERRIT_URL" +9368,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?",1382781712,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?","(In reply to comment #39) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This causes (lack of) whitespace issues and breaks all lists. + +QUOTE +QUOTE + +It doesn't. + +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +QUOTE +QUOTE +QUOTE +QUOTE + +Any changes for interim solutions?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']",NA,0,"(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists." +9368,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?",1382781712,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?","(In reply to comment #39) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This causes (lack of) whitespace issues and breaks all lists. + +QUOTE +QUOTE + +It doesn't. + +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +QUOTE +QUOTE +QUOTE +QUOTE + +Any changes for interim solutions?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\" +9368,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?",1382781712,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?","(In reply to comment #39) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This causes (lack of) whitespace issues and breaks all lists. + +QUOTE +QUOTE + +It doesn't. + +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +QUOTE +QUOTE +QUOTE +QUOTE + +Any changes for interim solutions?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']",NA,0,"m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not." +9368,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?",1382781712,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?","(In reply to comment #39) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This causes (lack of) whitespace issues and breaks all lists. + +QUOTE +QUOTE + +It doesn't. + +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +QUOTE +QUOTE +QUOTE +QUOTE + +Any changes for interim solutions?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?" +9368,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?",1382781712,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #39) +> (In reply to comment #36) +> > Issues I have found: +> > +> > * [MAJOR] Disabling edit section links does not work for headings inside +> > tags +> +> You could try marking your output as HTML according to +> https://www.mediawiki.org/wiki/Manual: +> Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output. +> 3F + +This causes (lack of) whitespace issues and breaks all lists. + +> I'm not sure whether that suppresses section edit links too, but worth a try +> IMO. + +It doesn't. + +> +> > * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> > fix. Above issue make this a bigger issue. +> > * [BLOCKER] Table of contents does not include links +> +> Can you check whether your headings are matched by the formatHeadings regexp? + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +> +> Ideally we'd move both TOC and section edit links to JS / CSS. That is our +> plan +> for Parsoid output, but not going to happen over night. + +Any changes for interim solutions?","(In reply to comment #39) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This causes (lack of) whitespace issues and breaks all lists. + +QUOTE +QUOTE + +It doesn't. + +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'm assuming it processes the html I'm returning, which is: +

CultureCulture

+ +Not sure whether that matches or not. + +QUOTE +QUOTE +QUOTE +QUOTE + +Any changes for interim solutions?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['(In reply to comment #39)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis causes (lack of) whitespace issues and breaks all lists.', ""QUOTE\nQUOTE\n\nIt doesn't."", 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI\'m assuming it processes the html I\'m returning, which is:\n

CultureCulture

\n\nNot sure whether that matches or not.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAny changes for interim solutions?']",NA,0,"QUOTE\nQUOTE\n\nIt doesn't." +9369,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",1382742193,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.","(In reply to comment #36) +QUOTE +QUOTE +QUOTE +QUOTE + +You could try marking your output as HTML according to URL + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +QUOTE +QUOTE +QUOTE + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO."", 'QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?', ""Ideally we'd move both TOC and section edit links to JS / CSS."", 'That is our plan for Parsoid output, but not going to happen over night.']",NA,0,"QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?" +9369,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",1382742193,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.","(In reply to comment #36) +QUOTE +QUOTE +QUOTE +QUOTE + +You could try marking your output as HTML according to URL + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +QUOTE +QUOTE +QUOTE + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO."", 'QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?', ""Ideally we'd move both TOC and section edit links to JS / CSS."", 'That is our plan for Parsoid output, but not going to happen over night.']",NA,0,"That is our plan for Parsoid output, but not going to happen over night." +9369,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",1382742193,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.","(In reply to comment #36) +QUOTE +QUOTE +QUOTE +QUOTE + +You could try marking your output as HTML according to URL + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +QUOTE +QUOTE +QUOTE + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO."", 'QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?', ""Ideally we'd move both TOC and section edit links to JS / CSS."", 'That is our plan for Parsoid output, but not going to happen over night.']",NA,0,"(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO." +9369,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",1382742193,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #36) +> Issues I have found: +> +> * [MAJOR] Disabling edit section links does not work for headings inside +> tags + +You could try marking your output as HTML according to https://www.mediawiki.org/wiki/Manual:Tag_extensions#How_can_I_avoid_modification_of_my_extension.27s_HTML_output.3F + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +> * [NORMAL] Edit section links don't work. Not a regression, but would be nice +> fix. Above issue make this a bigger issue. +> * [BLOCKER] Table of contents does not include links + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.","(In reply to comment #36) +QUOTE +QUOTE +QUOTE +QUOTE + +You could try marking your output as HTML according to URL + +I'm not sure whether that suppresses section edit links too, but worth a try IMO. + +QUOTE +QUOTE +QUOTE + +Can you check whether your headings are matched by the formatHeadings regexp? + +Ideally we'd move both TOC and section edit links to JS / CSS. That is our plan for Parsoid output, but not going to happen over night.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""(In reply to comment #36)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYou could try marking your output as HTML according to URL\n\nI'm not sure whether that suppresses section edit links too, but worth a try IMO."", 'QUOTE\nQUOTE\nQUOTE\n\nCan you check whether your headings are matched by the formatHeadings regexp?', ""Ideally we'd move both TOC and section edit links to JS / CSS."", 'That is our plan for Parsoid output, but not going to happen over night.']",NA,0,"Ideally we'd move both TOC and section edit links to JS / CSS." +9370,"Parsoid should support and natively as they are not normal parser tags","Editing translatable pages via API seems to work now.",1382609272,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Editing translatable pages via API seems to work now.","Editing translatable pages via API seems to work now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Editing translatable pages via API seems to work now.']",NA,0,"Editing translatable pages via API seems to work now." +9371,"Parsoid should support and natively as they are not normal parser tags","Also, please test the patch if you can to see if you find any other changes in behavior.",1382609061,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Also, please test the patch if you can to see if you find any other changes in behavior.","Also, please test the patch if you can to see if you find any other changes in behavior.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Also, please test the patch if you can to see if you find any other changes in behavior.']",NA,0,"Also, please test the patch if you can to see if you find any other changes in behavior." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"Not a regression, but would be nice fix." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"Above issue make this a bigger issue." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"The original logic cannot be implemented with information provided for the parser hook." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"You can see the buildup at bottom of URL compare with URL ." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"This is annoying and would be nice to fix, but the workaround is to edit page source." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"Documentation about whitespace before has to be update if this way is chosen." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"Please help me solve the remaining issues." +9372,"Parsoid should support and natively as they are not normal parser tags","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",1382608843,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of http://dev.translatewiki.net/wiki/Extension:Translate compare with http://www.mediawiki.org/wiki/Help:Extension:Translate . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.","Issues I have found: + +* [MAJOR] Disabling edit section links does not work for headings inside tags +* [NORMAL] Edit section links don't work. Not a regression, but would be nice fix. Above issue make this a bigger issue. +* [BLOCKER] Table of contents does not include links +* [MINOR] White space trimming behavior has changed. The original logic cannot be implemented with information provided for the parser hook. You can see the buildup at bottom of URL compare with URL . This is annoying and would be nice to fix, but the workaround is to edit page source. Documentation about whitespace before has to be update if this way is chosen. + +Please help me solve the remaining issues.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"[""Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work."", 'Not a regression, but would be nice fix.', 'Above issue make this a bigger issue.', '* [BLOCKER] Table of contents does not include links\n* [MINOR] White space trimming behavior has changed.', 'The original logic cannot be implemented with information provided for the parser hook.', 'You can see the buildup at bottom of URL compare with URL .', 'This is annoying and would be nice to fix, but the workaround is to edit page source.', 'Documentation about whitespace before has to be update if this way is chosen.', 'Please help me solve the remaining issues.']",NA,0,"Issues I have found:\n\n* [MAJOR] Disabling edit section links does not work for headings inside tags\n* [NORMAL] Edit section links don't work." +9373,"Parsoid should support and natively as they are not normal parser tags","Change 91583 had a related patch set uploaded by Nikerabbit: +Add $wgTranslatePageTranslationUseParserHook + +https://gerrit.wikimedia.org/r/91583",1382608576,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 91583 had a related patch set uploaded by Nikerabbit: +Add $wgTranslatePageTranslationUseParserHook + +https://gerrit.wikimedia.org/r/91583","Change 91583 had a related patch set uploaded by Nikerabbit: +Add $wgTranslatePageTranslationUseParserHook + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,16,NA,"['Change 91583 had a related patch set uploaded by Nikerabbit:\nAdd $wgTranslatePageTranslationUseParserHook\n\nGERRIT_URL']",NA,0,"Change 91583 had a related patch set uploaded by Nikerabbit:\nAdd $wgTranslatePageTranslationUseParserHook\n\nGERRIT_URL" +9374,"Parsoid should support and natively as they are not normal parser tags","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",1382602468,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Trying the parser hook solution now.', ""I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?"", "")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links."", ""I'm still trying with more complex pages with templates as well extensions and our tutorial.""]",NA,0,"Trying the parser hook solution now." +9374,"Parsoid should support and natively as they are not normal parser tags","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",1382602468,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Trying the parser hook solution now.', ""I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?"", "")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links."", ""I'm still trying with more complex pages with templates as well extensions and our tutorial.""]",NA,0,"I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?" +9374,"Parsoid should support and natively as they are not normal parser tags","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",1382602468,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Trying the parser hook solution now.', ""I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?"", "")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links."", ""I'm still trying with more complex pages with templates as well extensions and our tutorial.""]",NA,0,")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links." +9374,"Parsoid should support and natively as they are not normal parser tags","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",1382602468,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.","Trying the parser hook solution now. I have code like: + + $parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) { + $re = '~]+)>(.*?)~u'; + $output = preg_replace( $re, '\2', $input ); + + $output = $parser->recursiveTagParse( $output, $frame ); + $output = trim( $output ); + return $output; + } ); + +This seems to work okay on simple text, with the exception of section edit links. + +I'm still trying with more complex pages with templates as well extensions and our tutorial.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,16,NA,"['Trying the parser hook solution now.', ""I have code like:\n\n\t\t$parser->setHook( 'translate', function ( $input, $params, $parser, $frame ) {\n\t\t\t$re = '~]+)>(.*?"", "")~u';\n\t\t\t$output = preg_replace( $re, '\\2', $input );\n\n\t\t\t$output = $parser->recursiveTagParse( $output, $frame );\n\t\t\t$output = trim( $output );\n\t\t\treturn $output;\n\t\t} );\n\nThis seems to work okay on simple text, with the exception of section edit links."", ""I'm still trying with more complex pages with templates as well extensions and our tutorial.""]",NA,0,"I'm still trying with more complex pages with templates as well extensions and our tutorial." +9375,"Parsoid should support and natively as they are not normal parser tags","**gmaruzz** wrote: + +bump",1382525422,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","**gmaruzz** wrote: + +bump","**gmaruzz** wrote: + +bump",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,16,NA,"['**gmaruzz** wrote:\n\nbump']",NA,0,"**gmaruzz** wrote:\n\nbump" +9376,"Parsoid should support and natively as they are not normal parser tags","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",1382026260,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.","Niklas: So, here is what I found: + +URL works and does not crash. + +URL throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']",NA,0,"Niklas: So, here is what I found:\n\nURL works and does not crash." +9376,"Parsoid should support and natively as they are not normal parser tags","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",1382026260,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.","Niklas: So, here is what I found: + +URL works and does not crash. + +URL throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']",NA,0,"URL throws the exception." +9376,"Parsoid should support and natively as they are not normal parser tags","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",1382026260,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.","Niklas: So, here is what I found: + +URL works and does not crash. + +URL throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']",NA,0,"I am a bit baffled why the comment in the extension content should change what hook is called." +9376,"Parsoid should support and natively as they are not normal parser tags","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",1382026260,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.","Niklas: So, here is what I found: + +URL works and does not crash. + +URL throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']",NA,0,"It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you." +9376,"Parsoid should support and natively as they are not normal parser tags","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",1382026260,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: So, here is what I found: + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo works and does not crash. + +https://meta.wikimedia.org/w/api.php?action=parse&text=foo throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.","Niklas: So, here is what I found: + +URL works and does not crash. + +URL throws the exception. + +I am a bit baffled why the comment in the extension content should change what hook is called. I'll let you investigate from here. It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: So, here is what I found:\n\nURL works and does not crash.', 'URL throws the exception.', 'I am a bit baffled why the comment in the extension content should change what hook is called.', ""I'll let you investigate from here."", 'It might be worth using this opportunity to use a regular extension hook (rather than the ParserBeforeStrip hook), if that might work for you.']",NA,0,"I'll let you investigate from here." +9377,"Parsoid should support and natively as they are not normal parser tags","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",1382022809,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: To me, it looks like an existing bug got exposed.', 'Can you provide more details?', 'Maybe full url of the API call?', 'And/or, if you hop onto #mediawiki-parsoid, we could investigate.']",NA,0,"Niklas: To me, it looks like an existing bug got exposed." +9377,"Parsoid should support and natively as they are not normal parser tags","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",1382022809,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: To me, it looks like an existing bug got exposed.', 'Can you provide more details?', 'Maybe full url of the API call?', 'And/or, if you hop onto #mediawiki-parsoid, we could investigate.']",NA,0,"Can you provide more details?" +9377,"Parsoid should support and natively as they are not normal parser tags","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",1382022809,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: To me, it looks like an existing bug got exposed.', 'Can you provide more details?', 'Maybe full url of the API call?', 'And/or, if you hop onto #mediawiki-parsoid, we could investigate.']",NA,0,"Maybe full url of the API call?" +9377,"Parsoid should support and natively as they are not normal parser tags","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",1382022809,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.","Niklas: To me, it looks like an existing bug got exposed. Can you provide more details? Maybe full url of the API call? And/or, if you hop onto #mediawiki-parsoid, we could investigate.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['Niklas: To me, it looks like an existing bug got exposed.', 'Can you provide more details?', 'Maybe full url of the API call?', 'And/or, if you hop onto #mediawiki-parsoid, we could investigate.']",NA,0,"And/or, if you hop onto #mediawiki-parsoid, we could investigate." +9378,"Parsoid should support and natively as they are not normal parser tags","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?",1381997259,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown.', 'Does anybody have an idea why?']",NA,0,"I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown." +9378,"Parsoid should support and natively as they are not normal parser tags","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?",1381997259,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?","I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown. Does anybody have an idea why?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,15,NA,"['I just found out that if edit is made via API, the ParserBeforeStrip hook I am using does not get called and the exception is shown.', 'Does anybody have an idea why?']",NA,0,"Does anybody have an idea why?" +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag." +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"This is quite expensive as you can imagine." +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"* This lets the translate hack work for now." +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"* The translate extension will crash once we actually call the registered tag hook." +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"So there is some time to fix this up, but we should not pretend that it is fixed right now." +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"Can you provide more information on what stops you from using the actual tag hook?" +9379,"Parsoid should support and natively as they are not normal parser tags","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",1381334518,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?","To summarize: + +* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag. This is quite expensive as you can imagine. +* This lets the translate hack work for now. At least it won't crash. +* The translate extension will crash once we actually call the registered tag hook. + +So there is some time to fix this up, but we should not pretend that it is fixed right now. + +Can you provide more information on what stops you from using the actual tag hook?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['To summarize:\n\n* We currently work around the missing tag hook API by calling the full action=parse pipeline for each extension tag.', 'This is quite expensive as you can imagine.', '* This lets the translate hack work for now.', ""At least it won't crash."", '* The translate extension will crash once we actually call the registered tag hook.', 'So there is some time to fix this up, but we should not pretend that it is fixed right now.', 'Can you provide more information on what stops you from using the actual tag hook?']",NA,0,"At least it won't crash." +9380,"Parsoid should support and natively as they are not normal parser tags","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",1381334222,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Okay, we tested and all is good for now.', 'You can ignore #c27 :-).', 'As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).']",NA,0,"Okay, we tested and all is good for now." +9380,"Parsoid should support and natively as they are not normal parser tags","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",1381334222,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Okay, we tested and all is good for now.', 'You can ignore #c27 :-).', 'As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).']",NA,0,"You can ignore #c27 :-)." +9380,"Parsoid should support and natively as they are not normal parser tags","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",1381334222,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).","Okay, we tested and all is good for now. You can ignore #c27 :-). + +As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Okay, we tested and all is good for now.', 'You can ignore #c27 :-).', 'As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly).']",NA,0,"As I indicated in #c26, this is a problem for when we start updating Parsoid code to call extensions directly rather than go through the full parse pipeline (which was meant to be a temporary hack while we figured out how to call extensions directly)." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"Actually, now that I wrote that, I might have misspoken about whether it will work now as well." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"Niklas is right." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"Parsoid will recognize the hooks because of the registration." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb." +9381,"Parsoid should support and natively as they are not normal parser tags","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",1381332394,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.","Actually, now that I wrote that, I might have misspoken about whether it will work now as well. Niklas is right. For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work. + +Parsoid will recognize the hooks because of the registration. In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb. + +One of us (Gabriel or me) will experiment with the updated code locally and update this bug.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Actually, now that I wrote that, I might have misspoken about whether it will work now as well.', 'Niklas is right.', 'For and tags found in top-level pages, since we never go through PHP parser at all, this may still not work.', 'Parsoid will recognize the hooks because of the registration.', 'In turn, it will call the PHP parser to translate the extension content, which in turn may callback into the translate extension rather than the ParserBeforeStrip callback (which is what and relies on), and that will bomb.', 'One of us (Gabriel or me) will experiment with the updated code locally and update this bug.']",NA,0,"One of us (Gabriel or me) will experiment with the updated code locally and update this bug." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook)." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"Anything this is something we could discuss more." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"Hope this summarizes where we stand now." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point." +9382,"Parsoid should support and natively as they are not normal parser tags","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",1381331649,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.","The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks. But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly. + +Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook). So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them. + +If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work. However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point. + +So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser. + +I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms. We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline. Anything this is something we could discuss more. + +Hope this summarizes where we stand now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['The patch will work with Parsoid right now, because Parsoid always goes through the PHP parser when dealing with extensions and tag hooks.', 'But, there are plans for Parsoid to bypass the PHP parser and call the extensions/hooks directly.', 'Right now, The translate code preprocesses the page by stripping the and tags before the PHP parser actually parses the page source (by registering for ParserBeforeStrip hook).', 'So, even though the tag hooks are registered (with a callback that bombs if called), the PHP parser never gets to calling them.', 'If Parsoid is able to mimic the behavior (by calling all hooks, not just extension callback hooks), the existing code will continue to work.', ""However, if Parsoid only supports tag extensions directly, then, the ParserBeforeStrip code won't be invoked by Parsoid at that time and this will be a problem at that point."", 'So, this is not an issue *right now*, but could be at a later point depending on what functionality Parsoid will implement natively and what it will continue to defer to the PHP parser.', ""I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms."", 'We could streamline extensions to go through narrow interfaces rather than continuing to use all sort of hooks into various points of the parsing timeline.', 'Anything this is something we could discuss more.', 'Hope this summarizes where we stand now.']",NA,0,"I think Gabriel was responding to that future concern and also hoping that we can use the opportunity of Parsoid's ongoing development to cleanup some of these interfaces and mechanisms." +9383,"Parsoid should support and natively as they are not normal parser tags","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",1381311581,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Misunderstanding or miscommunication about the actual requirements is not scope creep.', 'The patch which was made does not add value.', 'I changed the title to reflect the issue with my understanding of it.']",NA,0,"Misunderstanding or miscommunication about the actual requirements is not scope creep." +9383,"Parsoid should support and natively as they are not normal parser tags","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",1381311581,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Misunderstanding or miscommunication about the actual requirements is not scope creep.', 'The patch which was made does not add value.', 'I changed the title to reflect the issue with my understanding of it.']",NA,0,"The patch which was made does not add value." +9383,"Parsoid should support and natively as they are not normal parser tags","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",1381311581,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.","Misunderstanding or miscommunication about the actual requirements is not scope creep. The patch which was made does not add value. I changed the title to reflect the issue with my understanding of it.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"['Misunderstanding or miscommunication about the actual requirements is not scope creep.', 'The patch which was made does not add value.', 'I changed the title to reflect the issue with my understanding of it.']",NA,0,"I changed the title to reflect the issue with my understanding of it." +9384,"Parsoid should support and natively as they are not normal parser tags","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and """,1381308196,"PHID-USER-w5a723w3wes6jd5wskgg","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and ""","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See URL Section ""Parser extension tags"" now shows "" and """,NA,NA,NA,NA,NA,"True","c1",3,"False",NA,14,NA,"['This issue appears to suffer from scope creep.', 'The requirements of the current summary have been met.', 'See URL Section ""Parser extension tags"" now shows "" and ""']",NA,0,"This issue appears to suffer from scope creep." +9384,"Parsoid should support and natively as they are not normal parser tags","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and """,1381308196,"PHID-USER-w5a723w3wes6jd5wskgg","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and ""","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See URL Section ""Parser extension tags"" now shows "" and """,NA,NA,NA,NA,NA,"True","c1",3,"False",NA,14,NA,"['This issue appears to suffer from scope creep.', 'The requirements of the current summary have been met.', 'See URL Section ""Parser extension tags"" now shows "" and ""']",NA,0,"The requirements of the current summary have been met." +9384,"Parsoid should support and natively as they are not normal parser tags","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and """,1381308196,"PHID-USER-w5a723w3wes6jd5wskgg","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See https://translatewiki.net/wiki/Special:Version?uselang=en: Section ""Parser extension tags"" now shows "" and ""","This issue appears to suffer from scope creep. The requirements of the current summary have been met. See URL Section ""Parser extension tags"" now shows "" and """,NA,NA,NA,NA,NA,"True","c1",3,"False",NA,14,NA,"['This issue appears to suffer from scope creep.', 'The requirements of the current summary have been met.', 'See URL Section ""Parser extension tags"" now shows "" and ""']",NA,0,"See URL Section ""Parser extension tags"" now shows "" and """ +9385,"Parsoid should support and natively as they are not normal parser tags","That patch won't work well with Parsoid, see the comment in the patch set.",1381173268,"PHID-USER-hbtlbu4zftxnz4i6f7yf","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","That patch won't work well with Parsoid, see the comment in the patch set.","That patch won't work well with Parsoid, see the comment in the patch set.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"[""That patch won't work well with Parsoid, see the comment in the patch set.""]",NA,0,"That patch won't work well with Parsoid, see the comment in the patch set." +9386,"Parsoid should support and natively as they are not normal parser tags","I don't deserve the credit for Niklas's fix. :-)",1381161087,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I don't deserve the credit for Niklas's fix. :-)","I don't deserve the credit for Niklas's fix. :-)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"[""I don't deserve the credit for Niklas's fix."", ':-)']",NA,0,":-)" +9386,"Parsoid should support and natively as they are not normal parser tags","I don't deserve the credit for Niklas's fix. :-)",1381161087,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I don't deserve the credit for Niklas's fix. :-)","I don't deserve the credit for Niklas's fix. :-)",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,14,NA,"[""I don't deserve the credit for Niklas's fix."", ':-)']",NA,0,"I don't deserve the credit for Niklas's fix." +9387,"Parsoid should support and natively as they are not normal parser tags","Change 83427 merged by jenkins-bot: +Register translate and tvar to the parser + +https://gerrit.wikimedia.org/r/83427",1380976648,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 83427 merged by jenkins-bot: +Register translate and tvar to the parser + +https://gerrit.wikimedia.org/r/83427","Change 83427 merged by jenkins-bot: +Register translate and tvar to the parser + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Change 83427 merged by jenkins-bot:\nRegister translate and tvar to the parser\n\nGERRIT_URL']",NA,0,"Change 83427 merged by jenkins-bot:\nRegister translate and tvar to the parser\n\nGERRIT_URL" +9388,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #19) +> I think I already did it yesterday. + +There is a comment, but now a followup question requires addresssing",1380973744,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #19) +> I think I already did it yesterday. + +There is a comment, but now a followup question requires addresssing","(In reply to comment #19) +QUOTE + +There is a comment, but now a followup question requires addresssing",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['(In reply to comment #19)\nQUOTE\n\nThere is a comment, but now a followup question requires addresssing']",NA,0,"(In reply to comment #19)\nQUOTE\n\nThere is a comment, but now a followup question requires addresssing" +9389,"Parsoid should support and natively as they are not normal parser tags","I think I already did it yesterday.",1380972312,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I think I already did it yesterday.","I think I already did it yesterday.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I think I already did it yesterday.']",NA,0,"I think I already did it yesterday." +9390,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",1380903233,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.","(In reply to comment #17) +QUOTE +QUOTE + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['(In reply to comment #17)\nQUOTE\nQUOTE\n\nOh.', ""We've been patiently waiting for you to merge it."", ':-(\n\nWill ping the team.']",NA,0,"(In reply to comment #17)\nQUOTE\nQUOTE\n\nOh." +9390,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",1380903233,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.","(In reply to comment #17) +QUOTE +QUOTE + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['(In reply to comment #17)\nQUOTE\nQUOTE\n\nOh.', ""We've been patiently waiting for you to merge it."", ':-(\n\nWill ping the team.']",NA,0,":-(\n\nWill ping the team." +9390,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",1380903233,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #17) +> Assigning to James, hoping this may get a parsoid person to review the patch +> that's been available for nearly a month now. + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.","(In reply to comment #17) +QUOTE +QUOTE + +Oh. We've been patiently waiting for you to merge it. :-( + +Will ping the team.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['(In reply to comment #17)\nQUOTE\nQUOTE\n\nOh.', ""We've been patiently waiting for you to merge it."", ':-(\n\nWill ping the team.']",NA,0,"We've been patiently waiting for you to merge it." +9391,"Parsoid should support and natively as they are not normal parser tags","Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.",1380870838,"PHID-USER-w5a723w3wes6jd5wskgg","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.","Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"[""Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now.""]",NA,0,"Assigning to James, hoping this may get a parsoid person to review the patch that's been available for nearly a month now." +9392,"Parsoid should support and natively as they are not normal parser tags","fwiw this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29 + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.",1380324098,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","fwiw this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29 + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.","fwiw this bug has been mentioned at URL + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['fwiw this bug has been mentioned at URL\n\nI have also seen this problem here and there while editing at mediawiki.org.', 'Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.']",NA,0,"fwiw this bug has been mentioned at URL\n\nI have also seen this problem here and there while editing at mediawiki.org." +9392,"Parsoid should support and natively as they are not normal parser tags","fwiw this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29 + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.",1380324098,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","fwiw this bug has been mentioned at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#VisualEditor_weekly_update_-_2013-09-26_.28MW_1.22wmf19.29 + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.","fwiw this bug has been mentioned at URL + +I have also seen this problem here and there while editing at mediawiki.org. Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,12,NA,"['fwiw this bug has been mentioned at URL\n\nI have also seen this problem here and there while editing at mediawiki.org.', 'Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough.']",NA,0,"Then again these tags are not used in most Wikimedia projects or MediaWikis there so fair enough." +9393,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",1378773198,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.","(In reply to comment #14) +QUOTE +QUOTE + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['(In reply to comment #14)\nQUOTE\nQUOTE\n\nYes.', ""On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE."", ""However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.""]",NA,0,"(In reply to comment #14)\nQUOTE\nQUOTE\n\nYes." +9393,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",1378773198,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.","(In reply to comment #14) +QUOTE +QUOTE + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['(In reply to comment #14)\nQUOTE\nQUOTE\n\nYes.', ""On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE."", ""However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.""]",NA,0,"On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE." +9393,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",1378773198,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #14) +> In the long term yes, but wont this render VE useless on translatable pages +> in the short them? + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.","(In reply to comment #14) +QUOTE +QUOTE + +Yes. On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE. + +However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['(In reply to comment #14)\nQUOTE\nQUOTE\n\nYes.', ""On MW.org you can use the alien node editor to edit any extension node's contents (but they won't be rich), but on other wikis it will make them un-editable in VE."", ""However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs.""]",NA,0,"However, making a Translation extension editor in VE shouldn't be hard at all - I've created that as bug 53974 along the lines of other bugs." +9394,"Parsoid should support and natively as they are not normal parser tags","In the long term yes, but wont this render VE useless on translatable pages in the short them?",1378772376,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","In the long term yes, but wont this render VE useless on translatable pages in the short them?","In the long term yes, but wont this render VE useless on translatable pages in the short them?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['In the long term yes, but wont this render VE useless on translatable pages in the short them?']",NA,0,"In the long term yes, but wont this render VE useless on translatable pages in the short them?" +9395,"Parsoid should support and natively as they are not normal parser tags","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",1378754413,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['Niklas: If VE has to support editing for , , etc.', 'tags, Parsoid has to know about those tags.', 'Parsoid finds out about installed tags by querying mediawiki API.', 'So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.']",NA,0,"Niklas: If VE has to support editing for , , etc." +9395,"Parsoid should support and natively as they are not normal parser tags","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",1378754413,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['Niklas: If VE has to support editing for , , etc.', 'tags, Parsoid has to know about those tags.', 'Parsoid finds out about installed tags by querying mediawiki API.', 'So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.']",NA,0,"tags, Parsoid has to know about those tags." +9395,"Parsoid should support and natively as they are not normal parser tags","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",1378754413,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['Niklas: If VE has to support editing for , , etc.', 'tags, Parsoid has to know about those tags.', 'Parsoid finds out about installed tags by querying mediawiki API.', 'So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.']",NA,0,"Parsoid finds out about installed tags by querying mediawiki API." +9395,"Parsoid should support and natively as they are not normal parser tags","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",1378754413,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.","Niklas: If VE has to support editing for , , etc. tags, Parsoid has to know about those tags. Parsoid finds out about installed tags by querying mediawiki API. So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['Niklas: If VE has to support editing for , , etc.', 'tags, Parsoid has to know about those tags.', 'Parsoid finds out about installed tags by querying mediawiki API.', 'So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them.']",NA,0,"So, either MW API should expose this information for hooks automatically or we need a different API endpoint, or you have to register them." +9396,"Parsoid should support and natively as they are not normal parser tags","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",1378751046,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['See the above commit.', 'It is not thoroughly tested.', ""I still don't understand what would the benefit.""]",NA,0,"See the above commit." +9396,"Parsoid should support and natively as they are not normal parser tags","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",1378751046,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['See the above commit.', 'It is not thoroughly tested.', ""I still don't understand what would the benefit.""]",NA,0,"It is not thoroughly tested." +9396,"Parsoid should support and natively as they are not normal parser tags","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",1378751046,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.","See the above commit. It is not thoroughly tested. I still don't understand what would the benefit.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,10,NA,"['See the above commit.', 'It is not thoroughly tested.', ""I still don't understand what would the benefit.""]",NA,0,"I still don't understand what would the benefit." +9397,"Parsoid should support and natively as they are not normal parser tags","Change 83427 had a related patch set uploaded by Nikerabbit: +Register translate and tvar to the parser + +https://gerrit.wikimedia.org/r/83427",1378750854,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Change 83427 had a related patch set uploaded by Nikerabbit: +Register translate and tvar to the parser + +https://gerrit.wikimedia.org/r/83427","Change 83427 had a related patch set uploaded by Nikerabbit: +Register translate and tvar to the parser + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"['Change 83427 had a related patch set uploaded by Nikerabbit:\nRegister translate and tvar to the parser\n\nGERRIT_URL']",NA,0,"Change 83427 had a related patch set uploaded by Nikerabbit:\nRegister translate and tvar to the parser\n\nGERRIT_URL" +9398,"Parsoid should support and natively as they are not normal parser tags","Ping.",1377214396,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Ping.","Ping.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,7,NA,"['Ping.']",NA,0,"Ping." +9399,"Parsoid should support and natively as they are not normal parser tags","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.",1375385299,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Does someone want to try registering them and see what happens?', ""I probably don't have time before Wikimania.""]",NA,0,"Does someone want to try registering them and see what happens?" +9399,"Parsoid should support and natively as they are not normal parser tags","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.",1375385299,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.","Does someone want to try registering them and see what happens? I probably don't have time before Wikimania.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Does someone want to try registering them and see what happens?', ""I probably don't have time before Wikimania.""]",NA,0,"I probably don't have time before Wikimania." +9400,"Parsoid should support and natively as they are not normal parser tags","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.",1375380363,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"[""I don't know."", 'Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.']",NA,0,"Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality." +9400,"Parsoid should support and natively as they are not normal parser tags","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.",1375380363,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.","I don't know. Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"[""I don't know."", 'Either the registration would just be symbolic without any side effects, or it could also interfere with the current functionality.']",NA,0,"I don't know." +9401,"Parsoid should support and natively as they are not normal parser tags","@Niklas are there issues with registering them?",1375380132,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","@Niklas are there issues with registering them?","SCREEN_NAME are there issues with registering them?",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['SCREEN_NAME are there issues with registering them?']",NA,0,"SCREEN_NAME are there issues with registering them?" +9402,"Parsoid should support and natively as they are not normal parser tags","*** Bug 52408 has been marked as a duplicate of this bug. ***",1375378489,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","*** Bug 52408 has been marked as a duplicate of this bug. ***","*** Bug 52408 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['*** Bug 52408 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 52408 has been marked as a duplicate of this bug." +9402,"Parsoid should support and natively as they are not normal parser tags","*** Bug 52408 has been marked as a duplicate of this bug. ***",1375378489,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","*** Bug 52408 has been marked as a duplicate of this bug. ***","*** Bug 52408 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['*** Bug 52408 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +9403,"Parsoid should support and natively as they are not normal parser tags","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",1375378361,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , , are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]",NA,0,"Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text." +9403,"Parsoid should support and natively as they are not normal parser tags","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",1375378361,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , , are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]",NA,0,"This will also let VE support them in the future and protect them from being modified right now." +9403,"Parsoid should support and natively as they are not normal parser tags","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",1375378361,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , , are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]",NA,0,"Is there any other way to discover that , , are valid tags on the wiki, i.e." +9403,"Parsoid should support and natively as they are not normal parser tags","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",1375378361,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , , are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]",NA,0,"what is the mediawiki api endpoint?" +9403,"Parsoid should support and natively as they are not normal parser tags","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",1375378361,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.","Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text. This will also let VE support them in the future and protect them from being modified right now. + +Is there any other way to discover that , , are valid tags on the wiki, i.e. what is the mediawiki api endpoint? So far we've been using siprop and fetching installed extension tags and use that to detect these.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,4,NA,"['Parsoid needs to know if something is a valid extension tag so that it can process them rather than escape them to literal text.', 'This will also let VE support them in the future and protect them from being modified right now.', 'Is there any other way to discover that , , are valid tags on the wiki, i.e.', 'what is the mediawiki api endpoint?', ""So far we've been using siprop and fetching installed extension tags and use that to detect these.""]",NA,0,"So far we've been using siprop and fetching installed extension tags and use that to detect these." +9404,"Parsoid should support and natively as they are not normal parser tags"," and are not a normal extension tags. Please explain why I should register them.",1369809699,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment"," and are not a normal extension tags. Please explain why I should register them."," and are not a normal extension tags. Please explain why I should register them.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"[' and are not a normal extension tags.', 'Please explain why I should register them.']",NA,0," and are not a normal extension tags." +9404,"Parsoid should support and natively as they are not normal parser tags"," and are not a normal extension tags. Please explain why I should register them.",1369809699,"PHID-USER-732lqsmz4v6bss3kln2v","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment"," and are not a normal extension tags. Please explain why I should register them."," and are not a normal extension tags. Please explain why I should register them.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"[' and are not a normal extension tags.', 'Please explain why I should register them.']",NA,0,"Please explain why I should register them." +9405,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #2) +> Parsoid does fetch a list of registered extensions from the config and uses +> that to wrap the block with mw:Object/Extension/ type. All +> other unknown tags are pass through as plain text. + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.",1369765885,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #2) +> Parsoid does fetch a list of registered extensions from the config and uses +> that to wrap the block with mw:Object/Extension/ type. All +> other unknown tags are pass through as plain text. + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this."", 'Re-filing.']",NA,0,"Re-filing." +9405,"Parsoid should support and natively as they are not normal parser tags","(In reply to comment #2) +> Parsoid does fetch a list of registered extensions from the config and uses +> that to wrap the block with mw:Object/Extension/ type. All +> other unknown tags are pass through as plain text. + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.",1369765885,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","(In reply to comment #2) +> Parsoid does fetch a list of registered extensions from the config and uses +> that to wrap the block with mw:Object/Extension/ type. All +> other unknown tags are pass through as plain text. + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +Ah, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this. Re-filing.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this."", 'Re-filing.']",NA,0,"(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\nAh, my apologies; I thought you were doing this, but it didn't even occur to me that the Translate extension might fail to do this." +9406,"Parsoid should support and natively as they are not normal parser tags","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?",1369761569,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check URL + +Any idea why mw.org is not reporting as a registered extension?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type.', 'All other unknown tags are pass through as plain text.', 'The problem is that mediawiki does not report as an installed extension.', 'Check URL\n\nAny idea why mw.org is not reporting as a registered extension?']",NA,0,"Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type." +9406,"Parsoid should support and natively as they are not normal parser tags","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?",1369761569,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check URL + +Any idea why mw.org is not reporting as a registered extension?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type.', 'All other unknown tags are pass through as plain text.', 'The problem is that mediawiki does not report as an installed extension.', 'Check URL\n\nAny idea why mw.org is not reporting as a registered extension?']",NA,0,"All other unknown tags are pass through as plain text." +9406,"Parsoid should support and natively as they are not normal parser tags","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?",1369761569,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check URL + +Any idea why mw.org is not reporting as a registered extension?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type.', 'All other unknown tags are pass through as plain text.', 'The problem is that mediawiki does not report as an installed extension.', 'Check URL\n\nAny idea why mw.org is not reporting as a registered extension?']",NA,0,"The problem is that mediawiki does not report as an installed extension." +9406,"Parsoid should support and natively as they are not normal parser tags","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?",1369761569,"PHID-USER-slccyo5rqasgpljxny7g","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check http://www.mediawiki.org/w/api.php?action=query&meta=siteinfo&format=jsonfm&siprop=extensiontags + +Any idea why mw.org is not reporting as a registered extension?","Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type. All other unknown tags are pass through as plain text. + +The problem is that mediawiki does not report as an installed extension. Check URL + +Any idea why mw.org is not reporting as a registered extension?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Parsoid does fetch a list of registered extensions from the config and uses that to wrap the block with mw:Object/Extension/ type.', 'All other unknown tags are pass through as plain text.', 'The problem is that mediawiki does not report as an installed extension.', 'Check URL\n\nAny idea why mw.org is not reporting as a registered extension?']",NA,0,"Check URL\n\nAny idea why mw.org is not reporting as a registered extension?" +9407,"Parsoid should support and natively as they are not normal parser tags","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?",1369745248,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn\'t recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn\'t been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?']",NA,0,"Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn\" +9407,"Parsoid should support and natively as they are not normal parser tags","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?",1369745248,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-jpmjmzcf4crsjhqwquzp","task_subcomment","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?","Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn't recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn't been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-5,NA,"['Yes, the Translate extension needs to be extended to support VisualEditor editing, but the core issue is that Parsoid doesn\'t recognise as an extension block; should it take the local list of registered extensions, and for ones it hasn\'t been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?']",NA,0,"t been told how to deal with just wrap it as a typeof=""mw:Object/Unknown"" or something similar?" +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"VisualEditor: Data model needs characters, not code points." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"For instance, U+282E2 (\" +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0," in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2""." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"In a plain textarea, this behaves like a single character from the point of view of the user." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates)." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"2) Combining accents can be used in sequences to build up abstract characters." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent)." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent)." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Then we can refine splitCharacters as needed." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \" +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0," can still detect the simple cases." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This sounds like a big change for a small issue, but I think it would avoid problems in the future." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!" +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character." +9509,"VisualEditor: Data model needs characters, not code points","At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1369029300,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_description","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","VisualEditor: Data model needs characters, not code points./n/nAt present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters. Here are two cases where this causes bugs: + +1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF. For instance, U+282E2 ('elevator' in Cantonese) is a single character represented in Javascript as ""\uD860\uDEE2"". In a plain textarea, this behaves like a single character from the point of view of the user. However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16. (see The Unicode Standard, Version 6.2, Section 3.8, Surrogates). + +2) Combining accents can be used in sequences to build up abstract characters. For example, the Javascript string ""m\u0300"" represents a single abstract character (m with grave accent). In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent). However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent. + +These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\uD860', '\uDEE2', ..., 'm', '\u0300']). My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\uD860\uDEE2', ..., 'm\u0300'], where each element represents a whole character. + +A good start would be to abstract out away calls to string.split( '' ) into a single function like this: + + ve.splitCharacters = function ( value ) { + return value.split( /(?![\uDC00-\uDFFF])/ ); // don't split surrogate pairs + }; + +The rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character. Then we can refine splitCharacters as needed. + +Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that 'typeof data[i] === ""string""' can still detect the simple cases. + +This sounds like a big change for a small issue, but I think it would avoid problems in the future. With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1370532382,NA,"resolved","True","c1",1,"False","False",-6,NA,"['VisualEditor: Data model needs characters, not code points.', 'At present, the VisualEditor treats UTF-16 code points as if they were synonymous with abstract characters.', 'Here are two cases where this causes bugs:\n\n1) UTF-16 uses a surrogate pair to represent each Unicode character above U+FFFF.', 'For instance, U+282E2 (\'elevator\' in Cantonese) is a single character represented in Javascript as ""\\uD860\\uDEE2"".', 'In a plain textarea, this behaves like a single character from the point of view of the user.', 'However in the VisualEditor, cursoring and backspacing requires two presses; and after cursoring once, any text typed will go in the middle of the surrogate pair, creating invalid UTF-16.', '(see The Unicode Standard, Version 6.2, Section 3.8, Surrogates).', '2) Combining accents can be used in sequences to build up abstract characters.', 'For example, the Javascript string ""m\\u0300"" represents a single abstract character (m with grave accent).', 'In a plain textarea, this behaves like a single character when cursoring, but like two characters when backspacing (so the first backspace just removes the accent).', 'However in the VisualEditor, cursoring requires two presses; and after cursoring once, any typed text will go between the letter and the accent, creating an inappropriate dangling combining accent.', ""These kinds of issues occur because the DataModel uses Arrays with code point elements, say ['\\uD860', '\\uDEE2', ..., 'm', '\\u0300'])."", ""My hunch is that this is slightly too low level, and it should instead use abstract character elements, say ['\\uD860\\uDEE2', ..., 'm\\u0300'], where each element represents a whole character."", ""A good start would be to abstract out away calls to string.split( '' ) into a single function like this:\n\n ve.splitCharacters = function ( value ) {\n return value.split( /(?!"", ""[\\uDC00-\\uDFFF])/ ); // don't split surrogate pairs\n };\n\nThe rest of the codebase should call this function to perform splits, and then not assume that data[i] is a single character."", 'Then we can refine splitCharacters as needed.', 'Alternatively, since the overwhelming majority of characters will in fact be single code points, perhaps the DataModel structure could ""encode"" the exceptional multi-code point characters as objects, so that \'typeof data[i] === ""string""\' can still detect the simple cases.', 'This sounds like a big change for a small issue, but I think it would avoid problems in the future.', 'With a character representation, you can safely perform useful operations like splicing and truncating without having to check the surrounding context very carefully every time.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"string" +9510,"VisualEditor: Data model needs characters, not code points","Marking this as merged; follow-up in bug 49257.",1370532382,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Marking this as merged; follow-up in bug 49257.","Marking this as merged; follow-up in bug 49257.",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-4,NA,"['Marking this as merged; follow-up in bug 49257.']",NA,0,"Marking this as merged; follow-up in bug 49257." +9511,"VisualEditor: Data model needs characters, not code points","*** Bug 49233 has been marked as a duplicate of this bug. ***",1370531722,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","*** Bug 49233 has been marked as a duplicate of this bug. ***","*** Bug 49233 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-4,NA,"['*** Bug 49233 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 49233 has been marked as a duplicate of this bug." +9511,"VisualEditor: Data model needs characters, not code points","*** Bug 49233 has been marked as a duplicate of this bug. ***",1370531722,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","*** Bug 49233 has been marked as a duplicate of this bug. ***","*** Bug 49233 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",2,"True",NA,-4,NA,"['*** Bug 49233 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +9512,"VisualEditor: Data model needs characters, not code points","Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.",1369497594,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.","Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"[""Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow.""]",NA,0,"Ed's main block of code is merged and will go out with wmf5; keeping this open for follow-up, and removing milestone of tomorrow." +9513,"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL .', ""We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes."", 'The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct.', 'Then we can get the splitting rules right in isolation.']",NA,0,"To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL ." +9513,"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL .', ""We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes."", 'The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct.', 'Then we can get the splitting rules right in isolation.']",NA,0,"The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct." +9513,"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL .', ""We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes."", 'The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct.', 'Then we can get the splitting rules right in isolation.']",NA,0,"Then we can get the splitting rules right in isolation." +9513,"VisualEditor: Data model needs characters, not code points","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",1369309137,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (http://unicode.org/reports/tr29/) . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.","To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL . We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes. + +The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct. Then we can get the splitting rules right in isolation.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['To be precise about what should constitute a character, see Grapheme Cluster Boundary Rules from TR29 (URL .', ""We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes."", 'The important thing right now is to abstract the code away from assuming single-codepoint characters, so the structure is correct.', 'Then we can get the splitting rules right in isolation.']",NA,0,"We probably want to implement these, except insofar as it differs from the browsers' implementations of what constitutes a character for cursoring purposes." +9514,"VisualEditor: Data model needs characters, not code points","Related URL: https://gerrit.wikimedia.org/r/64965 (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55)",1369248049,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Related URL: https://gerrit.wikimedia.org/r/64965 (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55)","Related URL: GERRIT_URL (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55)",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['Related URL: GERRIT_URL (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55)']",NA,0,"Related URL: GERRIT_URL (Gerrit Change I8d936fb15d82f73cd45fac142c540a7950850d55)" +9515,"VisualEditor: Data model needs characters, not code points","(In reply to comment #3) +> Another major issue is that window.getSelection (which is what we use to get +> cursor position, via Rangy) calculates using number of codepoints, not +> characters, so this would need to be translated. + +Which would be done in ve.ce.getOffsetFromTextNode",1369049395,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","(In reply to comment #3) +> Another major issue is that window.getSelection (which is what we use to get +> cursor position, via Rangy) calculates using number of codepoints, not +> characters, so this would need to be translated. + +Which would be done in ve.ce.getOffsetFromTextNode","(In reply to comment #3) +QUOTE +QUOTE +QUOTE + +Which would be done in ve.ce.getOffsetFromTextNode",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nWhich would be done in ve.ce.getOffsetFromTextNode']",NA,0,"(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nWhich would be done in ve.ce.getOffsetFromTextNode" +9516,"VisualEditor: Data model needs characters, not code points","Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.",1369048633,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.","Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated.']",NA,0,"Another major issue is that window.getSelection (which is what we use to get cursor position, via Rangy) calculates using number of codepoints, not characters, so this would need to be translated." +9517,"VisualEditor: Data model needs characters, not code points","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",1369046846,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['Ideally merging would be done at the transaction level (e.g.', 'in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g.', ""Data: ['F','o','o']\n\nTransaction:\n Retain: 3\n Replace:\n Remove: ''\n Insert: ''\n\nWould become:\n\nTransaction:\n Retain: 2\n Replace:\n Remove: 'o'\n Insert: 'o'""]",NA,0,"Ideally merging would be done at the transaction level (e.g." +9517,"VisualEditor: Data model needs characters, not code points","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",1369046846,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['Ideally merging would be done at the transaction level (e.g.', 'in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g.', ""Data: ['F','o','o']\n\nTransaction:\n Retain: 3\n Replace:\n Remove: ''\n Insert: ''\n\nWould become:\n\nTransaction:\n Retain: 2\n Replace:\n Remove: 'o'\n Insert: 'o'""]",NA,0,"in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g." +9517,"VisualEditor: Data model needs characters, not code points","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",1369046846,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'","Ideally merging would be done at the transaction level (e.g. in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g. + +Data: ['F','o','o'] + +Transaction: + Retain: 3 + Replace: + Remove: '' + Insert: '' + +Would become: + +Transaction: + Retain: 2 + Replace: + Remove: 'o' + Insert: 'o'",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-6,NA,"['Ideally merging would be done at the transaction level (e.g.', 'in fixupInsertion), although we would need to extend that method to be allowed to modify the remove part of a transaction, e.g.', ""Data: ['F','o','o']\n\nTransaction:\n Retain: 3\n Replace:\n Remove: ''\n Insert: ''\n\nWould become:\n\nTransaction:\n Retain: 2\n Replace:\n Remove: 'o'\n Insert: 'o'""]",NA,0,"Data: ['F','o','o']\n\nTransaction:\n Retain: 3\n Replace:\n Remove: ''\n Insert: ''\n\nWould become:\n\nTransaction:\n Retain: 2\n Replace:\n Remove: 'o'\n Insert: 'o'" +9518,"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['A related question is when invalid UTF-16 is checked and how errors are handled.', ""I don't know enough to suggest where in the system the checks should be."", 'But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function.', 'Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.']",NA,0,"A related question is when invalid UTF-16 is checked and how errors are handled." +9518,"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['A related question is when invalid UTF-16 is checked and how errors are handled.', ""I don't know enough to suggest where in the system the checks should be."", 'But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function.', 'Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.']",NA,0,"But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function." +9518,"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['A related question is when invalid UTF-16 is checked and how errors are handled.', ""I don't know enough to suggest where in the system the checks should be."", 'But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function.', 'Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.']",NA,0,"Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk." +9518,"VisualEditor: Data model needs characters, not code points","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",1369029854,"PHID-USER-lliyevigiycjbybglftk","PHID-TASK-vqj7c3uh5ndu4ic45odq","task_subcomment","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.","A related question is when invalid UTF-16 is checked and how errors are handled. + +I don't know enough to suggest where in the system the checks should be. But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function. Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-6,NA,"['A related question is when invalid UTF-16 is checked and how errors are handled.', ""I don't know enough to suggest where in the system the checks should be."", 'But it obviously relates to the parts of ve.dm.Converter and ve.ce.Surface (for paste) which would call this new splitCharacters function.', 'Note that two chunks of invalid UTF-16 can concatenate into one valid but unexpected chunk.']",NA,0,"I don't know enough to suggest where in the system the checks should be." +9929,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Simple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1367166420,"PHID-USER-3uecblbxq24ycewm2cog","PHID-TASK-v7tsixpel4mikkpah73h","task_description","VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines./n/nSimple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60535","VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines./n/nSimple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL +**See Also**: +URL","Medium",50,1394077374,NA,"resolved","True","c1",1,"False","False",-10,NA,"['VisualEditor: Slugs should be more obvious to the user that they\'re not ""really"" blank lines.', 'Simple test case, see URL:\n\n* foo\n: bar\n\nadds a newline in edit mode.', 'When removing this newline in edit mode the : is killed by the parser.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL']",FALSE,0,"VisualEditor: Slugs should be more obvious to the user that they\" +9929,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Simple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60535",1367166420,"PHID-USER-3uecblbxq24ycewm2cog","PHID-TASK-v7tsixpel4mikkpah73h","task_description","VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines./n/nSimple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://de.wikipedia.org/wiki/Benutzer:Raymond/Finissage +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=60535","VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines./n/nSimple test case, see URL: + +* foo +: bar + +adds a newline in edit mode. When removing this newline in edit mode the : is killed by the parser. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL +**See Also**: +URL","Medium",50,1394077374,NA,"resolved","True","c1",1,"False","False",-10,NA,"['VisualEditor: Slugs should be more obvious to the user that they\'re not ""really"" blank lines.', 'Simple test case, see URL:\n\n* foo\n: bar\n\nadds a newline in edit mode.', 'When removing this newline in edit mode the : is killed by the parser.', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL\n**See Also**:\nURL']",FALSE,0,"really" +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"On nl.wp a discussion has started to turn on VE." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"In the process feedback has been collected on VE." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"Some users commented on ""white lines"" as a blocking issue for turning VE on as default." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"On mouse over the white line turns blue." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"Some users fear that newcomers others will delete those white lines and carriage returns." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"However, after deletion of those lines images are accidently deleted from the page." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"This discussion started on bug 49806." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"James Forrester pointed me to this bug to continue the discussion." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)" +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"I will also copy to bug 55336." +9930,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",1405114275,"PHID-USER-mcyovqjor52nj3se4lq7","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* https://nl.wikipedia.org/wiki/Bali_%28eiland%29?veaction=edit +* https://nl.wikipedia.org/wiki/Justine_Henin?veaction=edit +* https://nl.wikipedia.org/wiki/Rijn?veaction=edit +* https://nl.wikipedia.org/wiki/Brussels_Hoofdstedelijk_Gewest?veaction=edit +* https://nl.wikipedia.org/wiki/Antwerpen_%28stad%29?veaction=edit +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.","On nl.wp a discussion has started to turn on VE. In the process feedback has been collected on VE. Some users commented on ""white lines"" as a blocking issue for turning VE on as default. +On top of pages like: +* URL +* URL +* URL +* URL +* URL +as well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode. On mouse over the white line turns blue. + +Some users fear that newcomers others will delete those white lines and carriage returns. However, after deletion of those lines images are accidently deleted from the page. + +This discussion started on bug 49806. James Forrester pointed me to this bug to continue the discussion. + +(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.) + +How can I help to resolve this 'bug'? I will also copy to bug 55336.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,53,NA,"['On nl.wp a discussion has started to turn on VE.', 'In the process feedback has been collected on VE.', 'Some users commented on ""white lines"" as a blocking issue for turning VE on as default.', 'On top of pages like:\n* URL\n* URL\n* URL\n* URL\n* URL\nas well as on other places on the page ""white lines"" or carriage returns appear in VE edit mode which do not appear in read mode.', 'On mouse over the white line turns blue.', 'Some users fear that newcomers others will delete those white lines and carriage returns.', 'However, after deletion of those lines images are accidently deleted from the page.', 'This discussion started on bug 49806.', 'James Forrester pointed me to this bug to continue the discussion.', '(Deleting white space at the bottom of a page might also delete accidently categories and other metadata.)', ""How can I help to resolve this 'bug'?"", 'I will also copy to bug 55336.']",NA,0,"How can I help to resolve this 'bug'?" +9931,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",1394077374,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,35,NA,"['Initial version of this now merged and being deployed tomorrow.', ""I think we'll want to revisit the styling and behaviour, but this will do for now.""]",NA,0,"Initial version of this now merged and being deployed tomorrow." +9931,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",1394077374,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.","Initial version of this now merged and being deployed tomorrow. I think we'll want to revisit the styling and behaviour, but this will do for now.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,35,NA,"['Initial version of this now merged and being deployed tomorrow.', ""I think we'll want to revisit the styling and behaviour, but this will do for now.""]",NA,0,"I think we'll want to revisit the styling and behaviour, but this will do for now." +9932,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 abandoned by Esanders: +Vector style tweaks for collapsible slugs + +https://gerrit.wikimedia.org/r/116742",1394042895,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Change 116742 abandoned by Esanders: +Vector style tweaks for collapsible slugs + +https://gerrit.wikimedia.org/r/116742","Change 116742 abandoned by Esanders: +Vector style tweaks for collapsible slugs + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,35,NA,"['Change 116742 abandoned by Esanders:\nVector style tweaks for collapsible slugs\n\nGERRIT_URL']",NA,0,"Change 116742 abandoned by Esanders:\nVector style tweaks for collapsible slugs\n\nGERRIT_URL" +9933,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 merged by jenkins-bot: +Collapse block slugs and expand on hover/focus + +https://gerrit.wikimedia.org/r/109307",1394040062,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Change 109307 merged by jenkins-bot: +Collapse block slugs and expand on hover/focus + +https://gerrit.wikimedia.org/r/109307","Change 109307 merged by jenkins-bot: +Collapse block slugs and expand on hover/focus + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,35,NA,"['Change 109307 merged by jenkins-bot:\nCollapse block slugs and expand on hover/focus\n\nGERRIT_URL']",NA,0,"Change 109307 merged by jenkins-bot:\nCollapse block slugs and expand on hover/focus\n\nGERRIT_URL" +9934,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 116742 had a related patch set uploaded by Esanders: +Vector style tweaks for collapsible slugs + +https://gerrit.wikimedia.org/r/116742",1393942167,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Change 116742 had a related patch set uploaded by Esanders: +Vector style tweaks for collapsible slugs + +https://gerrit.wikimedia.org/r/116742","Change 116742 had a related patch set uploaded by Esanders: +Vector style tweaks for collapsible slugs + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,35,NA,"['Change 116742 had a related patch set uploaded by Esanders:\nVector style tweaks for collapsible slugs\n\nGERRIT_URL']",NA,0,"Change 116742 had a related patch set uploaded by Esanders:\nVector style tweaks for collapsible slugs\n\nGERRIT_URL" +9935,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Change 109307 had a related patch set uploaded by Esanders: +Collapse block slugs, and expand on hover/focus + +https://gerrit.wikimedia.org/r/109307",1390581550,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Change 109307 had a related patch set uploaded by Esanders: +Collapse block slugs, and expand on hover/focus + +https://gerrit.wikimedia.org/r/109307","Change 109307 had a related patch set uploaded by Esanders: +Collapse block slugs, and expand on hover/focus + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,29,NA,"['Change 109307 had a related patch set uploaded by Esanders:\nCollapse block slugs, and expand on hover/focus\n\nGERRIT_URL']",NA,0,"Change 109307 had a related patch set uploaded by Esanders:\nCollapse block slugs, and expand on hover/focus\n\nGERRIT_URL" +9936,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Thanks, Ed, for splitting the issue and working on a patch for bug 55336.', ""Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation."", 'I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.', ""I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative."", 'In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.']",NA,0,"Thanks, Ed, for splitting the issue and working on a patch for bug 55336." +9936,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Thanks, Ed, for splitting the issue and working on a patch for bug 55336.', ""Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation."", 'I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.', ""I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative."", 'In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.']",NA,0,"I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall." +9936,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Thanks, Ed, for splitting the issue and working on a patch for bug 55336.', ""Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation."", 'I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.', ""I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative."", 'In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.']",NA,0,"In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page." +9936,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Thanks, Ed, for splitting the issue and working on a patch for bug 55336.', ""Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation."", 'I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.', ""I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative."", 'In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.']",NA,0,"Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation." +9936,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",1381008272,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.","Thanks, Ed, for splitting the issue and working on a patch for bug 55336. + +Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation. I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall. + +I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative. In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['Thanks, Ed, for splitting the issue and working on a patch for bug 55336.', ""Accordingly, I've set that bug to High/Major and this one to Normal, as the overall UX for slugs is important, but not as significant as the accidental deletion of content with the current implementation."", 'I also suspect that we would want to alter the delete behavior even if we end up altering the slug appearance overall.', ""I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative."", 'In addition to offering an affordance on hover, we might also expand the slugs as the user moves her cursor through the page.']",NA,0,"I do agree that the accidental whitespace is confusing (it's often the most immediate and obvious difference from read mode) and it would be good to find an alternative." +9937,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**jonathan_haas** wrote: + +(In reply to comment #15) +> Why don't we just suppress the delete key when pressing it would delete the +> object the slug is associated with? + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",1380964477,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**jonathan_haas** wrote: + +(In reply to comment #15) +> Why don't we just suppress the delete key when pressing it would delete the +> object the slug is associated with? + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.","**jonathan_haas** wrote: + +(In reply to comment #15) +QUOTE +QUOTE + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['**jonathan_haas** wrote:\n\n(In reply to comment #15)\nQUOTE\nQUOTE\n\nThis would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout.', 'I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.']",NA,0,"**jonathan_haas** wrote:\n\n(In reply to comment #15)\nQUOTE\nQUOTE\n\nThis would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout." +9937,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**jonathan_haas** wrote: + +(In reply to comment #15) +> Why don't we just suppress the delete key when pressing it would delete the +> object the slug is associated with? + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",1380964477,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**jonathan_haas** wrote: + +(In reply to comment #15) +> Why don't we just suppress the delete key when pressing it would delete the +> object the slug is associated with? + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.","**jonathan_haas** wrote: + +(In reply to comment #15) +QUOTE +QUOTE + +This would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout. + +I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['**jonathan_haas** wrote:\n\n(In reply to comment #15)\nQUOTE\nQUOTE\n\nThis would still leave the user with a superfluous empty line, which might be confusing and/or destroying the page layout.', 'I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one.']",NA,0,"I like the idea in attachment 12988, but I think it would be better, if slugs would have had an effective default height of 0 (for example height: 4px, margin-top: -2px, margin-bottom:-2px), so the article layout would match the real one." +9938,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",1380963747,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes.', 'Here is the latter: bug 55336']",NA,0,"I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes." +9938,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",1380963747,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336","I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes. Here is the latter: bug 55336",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,13,NA,"['I think we should split this bug in two: Slugs, and accidental deletion of FocusableNodes.', 'Here is the latter: bug 55336']",NA,0,"Here is the latter: bug 55336" +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"This is very surprising and counter-intuitive behavior." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"That seems like the simplest solution to me and does not require a redesign of the slugs." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions." +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?" +9939,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",1380953506,"PHID-USER-766idcqt4jkngnnuhnrj","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.","I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such. I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions. + +Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout. A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears. This is very surprising and counter-intuitive behavior. + +Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with? In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects. I've never had any problems as a result. + +That seems like the simplest solution to me and does not require a redesign of the slugs.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,13,NA,"['I agree with previous commenters that this is likely to be at the cause of a lot of the accidental infobox deletions and such.', ""I understand it's a tricky issue, but the current behavior is extremely confusing from the user's point of view, so we need to look at some viable solutions."", 'Recapping the simple case: User is on what they perceive to be an unnecessary newline, presses delete to make the visual layout match the expected layout.', 'A separate object (in the case of the infobox, right-aligned on the other side of the screen) suddenly disappears.', 'This is very surprising and counter-intuitive behavior.', ""Why don't we just suppress the delete key when pressing it would delete the object the slug is associated with?"", 'In some alternative editors like Google Docs, it is actually not possible to nuke the entire document by just pressing down the delete key at the top of the page -- it will stop before certain objects.', ""I've never had any problems as a result."", 'That seems like the simplest solution to me and does not require a redesign of the slugs.']",NA,0,"I've never had any problems as a result." +9940,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 . +Hoping this gets some love soon :)",1379004776,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 . +Hoping this gets some love soon :)","Today JohnCD asked again about this and I got another report from fr.wp, URL . +Hoping this gets some love soon :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"['Today JohnCD asked again about this and I got another report from fr.wp, URL .', 'Hoping this gets some love soon :)']",NA,0,"Today JohnCD asked again about this and I got another report from fr.wp, URL ." +9940,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 . +Hoping this gets some love soon :)",1379004776,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Today JohnCD asked again about this and I got another report from fr.wp, https://fr.wikipedia.org/w/index.php?title=Osmium&diff=96605232&oldid=93301425 . +Hoping this gets some love soon :)","Today JohnCD asked again about this and I got another report from fr.wp, URL . +Hoping this gets some love soon :)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,10,NA,"['Today JohnCD asked again about this and I got another report from fr.wp, URL .', 'Hoping this gets some love soon :)']",NA,0,"Hoping this gets some love soon :)" +9941,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 52172 has been marked as a duplicate of this bug. ***",1375047891,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 52172 has been marked as a duplicate of this bug. ***","*** Bug 52172 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['*** Bug 52172 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 52172 has been marked as a duplicate of this bug." +9941,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 52172 has been marked as a duplicate of this bug. ***",1375047891,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 52172 has been marked as a duplicate of this bug. ***","*** Bug 52172 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['*** Bug 52172 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +9942,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",1374960319,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}","Created attachment 12988 +Copy of URL + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Created attachment 12988\nCopy of URL\n\nPlease upload attachments to Bugzilla.', 'imgur periodically prunes images; Bugzilla does not.', ':-)\n\n**Attached**: {F10355}']",NA,0,"Created attachment 12988\nCopy of URL\n\nPlease upload attachments to Bugzilla." +9942,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",1374960319,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}","Created attachment 12988 +Copy of URL + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Created attachment 12988\nCopy of URL\n\nPlease upload attachments to Bugzilla.', 'imgur periodically prunes images; Bugzilla does not.', ':-)\n\n**Attached**: {F10355}']",NA,0,"imgur periodically prunes images; Bugzilla does not." +9942,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",1374960319,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Created attachment 12988 +Copy of http://i.imgur.com/39QQi8U.png + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}","Created attachment 12988 +Copy of URL + +Please upload attachments to Bugzilla. imgur periodically prunes images; Bugzilla does not. :-) + +**Attached**: {F10355}",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,3,NA,"['Created attachment 12988\nCopy of URL\n\nPlease upload attachments to Bugzilla.', 'imgur periodically prunes images; Bugzilla does not.', ':-)\n\n**Attached**: {F10355}']",NA,0,":-)\n\n**Attached**: {F10355}" +9943,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Suggestion: +http://i.imgur.com/39QQi8U.png",1374926957,"PHID-USER-it53o2f2kyryqyj33uzt","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Suggestion: +http://i.imgur.com/39QQi8U.png","Suggestion: +URL",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,3,NA,"['Suggestion:\nURL']",NA,0,"Suggestion:\nURL" +9944,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g.', 'a PROD) from the top of a page which has an infobox.', 'Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top.', 'The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box.', '(Win7, FF22.0)']",NA,0,"**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g." +9944,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g.', 'a PROD) from the top of a page which has an infobox.', 'Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top.', 'The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box.', '(Win7, FF22.0)']",NA,0,"a PROD) from the top of a page which has an infobox." +9944,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g.', 'a PROD) from the top of a page which has an infobox.', 'Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top.', 'The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box.', '(Win7, FF22.0)']",NA,0,"Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top." +9944,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g.', 'a PROD) from the top of a page which has an infobox.', 'Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top.', 'The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box.', '(Win7, FF22.0)']",NA,0,"The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box." +9944,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",1374396945,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)","**JohnCD67** wrote: + +This causes trouble in the fairly common operation of removing a template (e.g. a PROD) from the top of a page which has an infobox. Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top. The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box. (Win7, FF22.0)",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**JohnCD67** wrote:\n\nThis causes trouble in the fairly common operation of removing a template (e.g.', 'a PROD) from the top of a page which has an infobox.', 'Click the template to select it, press ""Delete"" and it goes, leaving apparently a spare blank line at the top.', 'The natural reaction is press ""Delete"" again to remove the blank line, and that takes out the info box.', '(Win7, FF22.0)']",NA,0,"(Win7, FF22.0)" +9945,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",1374361883,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**joedecker** wrote:\n\nI suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused.', 'As a separate question, can you undo deletion of slugs?', 'If not, I think that would explain another set of problems others and I have observed.']",NA,0,"**joedecker** wrote:\n\nI suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused." +9945,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",1374361883,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**joedecker** wrote:\n\nI suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused.', 'As a separate question, can you undo deletion of slugs?', 'If not, I think that would explain another set of problems others and I have observed.']",NA,0,"As a separate question, can you undo deletion of slugs?" +9945,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",1374361883,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.","**joedecker** wrote: + +I suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused. + +As a separate question, can you undo deletion of slugs? If not, I think that would explain another set of problems others and I have observed.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['**joedecker** wrote:\n\nI suspect this is behind a few of the reports (on the ENWIKI feedback page, some of them mine) in which unexpected deletions are caused.', 'As a separate question, can you undo deletion of slugs?', 'If not, I think that would explain another set of problems others and I have observed.']",NA,0,"If not, I think that would explain another set of problems others and I have observed." +9946,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).",1373913566,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Gotcha.', ""A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).""]",NA,0,"Gotcha." +9946,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).",1373913566,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).","Gotcha. A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Gotcha.', ""A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :).""]",NA,0,"A user was confused as to why they couldn't add a template to the top of an article without it appearing on the same line :)." +9947,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #4) +> Does this include the line of whitespace right at the start of articles? + +Yes.",1373913377,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","(In reply to comment #4) +> Does this include the line of whitespace right at the start of articles? + +Yes.","(In reply to comment #4) +QUOTE + +Yes.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,2,NA,"['(In reply to comment #4)\nQUOTE\n\nYes.']",NA,0,"(In reply to comment #4)\nQUOTE\n\nYes." +9948,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","(In reply to comment #5) +> It looks like this bug was fixed somehow. I cannot longer reproduce it on +> dewiki. + +Yes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.",1373913366,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","(In reply to comment #5) +> It looks like this bug was fixed somehow. I cannot longer reproduce it on +> dewiki. + +Yes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.","(In reply to comment #5) +QUOTE +QUOTE + +Yes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,2,NA,"['(In reply to comment #5)\nQUOTE\nQUOTE\n\nYes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely.']",NA,0,"(In reply to comment #5)\nQUOTE\nQUOTE\n\nYes, we removed the slugs between lists because we felt they were no longer needed given the new editing tools, but they remain more widely." +9949,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.",1373909882,"PHID-USER-3uecblbxq24ycewm2cog","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['It looks like this bug was fixed somehow.', 'I cannot longer reproduce it on dewiki.']",NA,0,"It looks like this bug was fixed somehow." +9949,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.",1373909882,"PHID-USER-3uecblbxq24ycewm2cog","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.","It looks like this bug was fixed somehow. I cannot longer reproduce it on dewiki.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['It looks like this bug was fixed somehow.', 'I cannot longer reproduce it on dewiki.']",NA,0,"I cannot longer reproduce it on dewiki." +9950,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","Does this include the line of whitespace right at the start of articles?",1373879923,"PHID-USER-j5ma2nageni56xp567v5","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","Does this include the line of whitespace right at the start of articles?","Does this include the line of whitespace right at the start of articles?",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,2,NA,"['Does this include the line of whitespace right at the start of articles?']",NA,0,"Does this include the line of whitespace right at the start of articles?" +9951,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 50295 has been marked as a duplicate of this bug. ***",1373854867,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 50295 has been marked as a duplicate of this bug. ***","*** Bug 50295 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,2,NA,"['*** Bug 50295 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 50295 has been marked as a duplicate of this bug." +9951,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 50295 has been marked as a duplicate of this bug. ***",1373854867,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 50295 has been marked as a duplicate of this bug. ***","*** Bug 50295 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,2,NA,"['*** Bug 50295 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +9952,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 50797 has been marked as a duplicate of this bug. ***",1373046915,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 50797 has been marked as a duplicate of this bug. ***","*** Bug 50797 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['*** Bug 50797 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 50797 has been marked as a duplicate of this bug." +9952,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","*** Bug 50797 has been marked as a duplicate of this bug. ***",1373046915,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","*** Bug 50797 has been marked as a duplicate of this bug. ***","*** Bug 50797 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,0,NA,"['*** Bug 50797 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,"This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph." +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,"so it\" +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,"re not really ""there"" and are just places items can go." +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,"Re-purposing this bug to talk about that." +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,":-)" +9953,"VisualEditor: Slugs should be more obvious to the user that they're not ""really"" blank lines","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",1367169998,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-v7tsixpel4mikkpah73h","task_subcomment","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)","This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph. We've been thinking about putting a little icon in slugs and making them a different height/etc. so it's obvious that they're not really ""there"" and are just places items can go. + +Re-purposing this bug to talk about that. :-)",NA,NA,NA,NA,NA,"True","c1",1,"True",NA,-10,NA,"['This is deliberate - the line is a ""slug"", allowing the user to insert text between the UL and the DL without creating a bullet and then down-converting it into a paragraph.', ""We've been thinking about putting a little icon in slugs and making them a different height/etc."", 'so it\'s obvious that they\'re not really ""there"" and are just places items can go.', 'Re-purposing this bug to talk about that.', ':-)']",NA,0,"We've been thinking about putting a little icon in slugs and making them a different height/etc." +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"VisualEditor: Suggestion lists (of templates/links/categories/etc.)" +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"differ over time with the same input (e.g." +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"between browsers/users)." +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \" +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0," into input box." +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect." +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL" +10782,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","In Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406",1377199800,"PHID-USER-kqibbfgfpgocyzwe32lv","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_description","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in https://test2.wikipedia.org + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=58406","VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)./n/nIn Chrome, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub"" + +In Firefox, edit any page in URL + +Click Transclusion, type 's' into input box. +Result is a list of suggestions that begin with ""Succession box"" and ""South America"" + +This suggests that at least one list of Template suggestions is absolutely incorrect. + +-------------------------- +**Version**: unspecified +**Severity**: minor +**See Also**: +URL","Low",25,1429301547,"PHID-USER-ydswvwhh5pm4lshahjje","declined","True","c1",3,"False","False",7,NA,"['VisualEditor: Suggestion lists (of templates/links/categories/etc.)', 'differ over time with the same input (e.g.', 'between browsers/users).', ""In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box."", 'Result is a list of suggestions that begin with ""Smaller"" and ""Sectstub""\n\nIn Firefox, edit any page in URL\n\nClick Transclusion, type \'s\' into input box.', 'Result is a list of suggestions that begin with ""Succession box"" and ""South America""\n\nThis suggests that at least one list of Template suggestions is absolutely incorrect.', '--------------------------\n**Version**: unspecified\n**Severity**: minor\n**See Also**:\nURL']",FALSE,0,"In Chrome, edit any page in URL\n\nClick Transclusion, type 's' into input box." +10783,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","*** Bug 70219 has been marked as a duplicate of this bug. ***",1416339245,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_subcomment","*** Bug 70219 has been marked as a duplicate of this bug. ***","*** Bug 70219 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,72,NA,"['*** Bug 70219 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 70219 has been marked as a duplicate of this bug." +10783,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","*** Bug 70219 has been marked as a duplicate of this bug. ***",1416339245,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_subcomment","*** Bug 70219 has been marked as a duplicate of this bug. ***","*** Bug 70219 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,72,NA,"['*** Bug 70219 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +10784,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",1387245600,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_subcomment","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,24,NA,"[""This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit)."", 'Not sure if this is a ""bug"" per se…']",NA,0,"Not sure if this is a ""bug"" per se…" +10784,"VisualEditor: Suggestion lists (of templates/links/categories/etc.) differ over time with the same input (e.g. between browsers/users)","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",1387245600,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-gi6xthiyrxw7c2mnmgvl","task_subcomment","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…","This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit). Not sure if this is a ""bug"" per se…",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,24,NA,"[""This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit)."", 'Not sure if this is a ""bug"" per se…']",NA,0,"This is caused by the search back end that supplies the suggestions; I don't think it alters by user/browser so much as over time (though it's cached after the first request for a bit)." +12293,"Add tracking category to pages with errors in ","An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1365503760,"PHID-USER-tyjmn7xcw6s2b6rqagj7","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_description","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","resolved","True","c1",1,"False","False",-12,NA,"['Add tracking category to pages with errors in .', 'An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"Add tracking category to pages with errors in ." +12293,"Add tracking category to pages with errors in ","An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1365503760,"PHID-USER-tyjmn7xcw6s2b6rqagj7","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_description","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","resolved","True","c1",1,"False","False",-12,NA,"['Add tracking category to pages with errors in .', 'An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors." +12293,"Add tracking category to pages with errors in ","An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1365503760,"PHID-USER-tyjmn7xcw6s2b6rqagj7","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_description","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Add tracking category to pages with errors in ./n/nAn automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","resolved","True","c1",1,"False","False",-12,NA,"['Add tracking category to pages with errors in .', 'An automatic tracking category for pages with errors in (when parsed by texvc) would help finding these pages and fixing the errors.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +12294,"Add tracking category to pages with errors in ","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[GERRIT_URL]].",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['I see nobody answers.', 'I am closing the task by myself.', 'If there is a problem, reopen it.', 'Closed as resolved by [[GERRIT_URL]].']",NA,1,"I see nobody answers." +12294,"Add tracking category to pages with errors in ","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[GERRIT_URL]].",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['I see nobody answers.', 'I am closing the task by myself.', 'If there is a problem, reopen it.', 'Closed as resolved by [[GERRIT_URL]].']",NA,1,"I am closing the task by myself." +12294,"Add tracking category to pages with errors in ","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[GERRIT_URL]].",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['I see nobody answers.', 'I am closing the task by myself.', 'If there is a problem, reopen it.', 'Closed as resolved by [[GERRIT_URL]].']",NA,1,"If there is a problem, reopen it." +12294,"Add tracking category to pages with errors in ","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].",1467323599,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[https://gerrit.wikimedia.org/r/292576]].","I see nobody answers. I am closing the task by myself. If there is a problem, reopen it. + +Closed as resolved by [[GERRIT_URL]].",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['I see nobody answers.', 'I am closing the task by myself.', 'If there is a problem, reopen it.', 'Closed as resolved by [[GERRIT_URL]].']",NA,1,"Closed as resolved by [[GERRIT_URL]]." +12295,"Add tracking category to pages with errors in ","The discussion was moved to [[https://en.wikipedia.org/wiki/MediaWiki_talk:Math-tracking-category-error|here]]. +",1467219463,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","The discussion was moved to [[https://en.wikipedia.org/wiki/MediaWiki_talk:Math-tracking-category-error|here]]. +","The discussion was moved to [[URL +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['The discussion was moved to [[URL']",NA,1,"The discussion was moved to [[URL" +12296,"Add tracking category to pages with errors in ","No problem. +",1467218718,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","No problem. +","No problem. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['No problem.']",NA,1,"No problem." +12297,"Add tracking category to pages with errors in ","Thank you. I have posted an edit request at that page on en.wiki.",1467210767,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","Thank you. I have posted an edit request at that page on en.wiki.","Thank you. I have posted an edit request at that page on en.wiki.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['Thank you.', 'I have posted an edit request at that page on en.wiki.']",NA,1,"Thank you." +12297,"Add tracking category to pages with errors in ","Thank you. I have posted an edit request at that page on en.wiki.",1467210767,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","Thank you. I have posted an edit request at that page on en.wiki.","Thank you. I have posted an edit request at that page on en.wiki.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['Thank you.', 'I have posted an edit request at that page on en.wiki.']",NA,1,"I have posted an edit request at that page on en.wiki." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"We are talking about removing pages from category, so it can be done for your entire wiki and nothing else." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"1." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"2." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"4." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"5." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Save the page." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"6." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Open one page with a math error in good namespace for editing." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Make sure the category is there." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"7." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Open one page with a math error in bad namespace for editing." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Make sure the category is not there." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"8." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"If there is a problem, replace "":"" with ""-"" in the code and try again." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"9." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"When you are sure it works, run a nulledit bot on the current category content." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"10." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Done." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"First of all,SCREEN_NAME, you can't do it only in vector or only in your account." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Second of all, there is no link for this case help, because it's too obvious." +12298,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467195164,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace for editing. Make sure the category is there. +7. Open one page with a math error in bad namespace for editing. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace for editing.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace for editing.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"And the last parameter is the category name (you'll see it in the wiki editor in the page creation moment)." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"We are talking about removing pages from category, so it can be done for your entire wiki and nothing else." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"1." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"2." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"4." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"5." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Save the page." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"6." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Open one page with a math error in good namespace." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Make sure the category is there." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"7." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Open one page with a math error in bad namespace." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Make sure the category is not there." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"8." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"If there is a problem, replace "":"" with ""-"" in the code and try again." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"9." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"When you are sure it works, run a nulledit bot on the current category content." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"10." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Done." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"First of all,SCREEN_NAME, you can't do it only in vector or only in your account." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"Second of all, there is no link for this case help, because it's too obvious." +12299,"Add tracking category to pages with errors in ","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",1467194961,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","First of all, @Jonesey95, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ","First of all,SCREEN_NAME, you can't do it only in vector or only in your account. We are talking about removing pages from category, so it can be done for your entire wiki and nothing else. +Second of all, there is no link for this case help, because it's too obvious. +1. Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki. +2. Put there for example a code: +{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}] +3. Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow. +4. And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment). +5. Save the page. +6. Open one page with a math error in good namespace. Make sure the category is there. +7. Open one page with a math error in bad namespace. Make sure the category is not there. +8. If there is a problem, replace "":"" with ""-"" in the code and try again. +9. When you are sure it works, run a nulledit bot on the current category content. +10. Done. + ",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"[""First of all,SCREEN_NAME, you can't do it only in vector or only in your account."", 'We are talking about removing pages from category, so it can be done for your entire wiki and nothing else.', ""Second of all, there is no link for this case help, because it's too obvious."", '1.', 'Create a new page [[{{ns:8}}:math-tracking-category-error]] in your wiki.', '2.', 'Put there for example a code:\n{{#switch:{{NAMESPACENUMBER}]|1|2|3|118|2600=:|Pages with math errors}]\n3.', 'Where the numbers list is all namespace numbers where you want just a message, not a category - here, for example, talk, user, user talk, draft and flow.', '4.', ""And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)."", '5.', 'Save the page.', '6.', 'Open one page with a math error in good namespace.', 'Make sure the category is there.', '7.', 'Open one page with a math error in bad namespace.', 'Make sure the category is not there.', '8.', 'If there is a problem, replace "":"" with ""-"" in the code and try again.', '9.', 'When you are sure it works, run a nulledit bot on the current category content.', '10.', 'Done.']",NA,1,"And the last parameter is the current name (you'll see it in the wiki editor in the page creation moment)." +12300,"Add tracking category to pages with errors in ","I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",1467177192,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.","I would love to do it myself (for everyone, not just in my own vector.js).SCREEN_NAME, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['I would love to do it myself (for everyone, not just in my own vector.js).SCREEN_NAME, do you have a link to instructions on how to take care of it on en.wiki?', 'Thanks.']",NA,1,"I would love to do it myself (for everyone, not just in my own vector.js).SCREEN_NAME, do you have a link to instructions on how to take care of it on en.wiki?" +12300,"Add tracking category to pages with errors in ","I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",1467177192,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I would love to do it myself (for everyone, not just in my own vector.js). @IKhitron, do you have a link to instructions on how to take care of it on en.wiki? Thanks.","I would love to do it myself (for everyone, not just in my own vector.js).SCREEN_NAME, do you have a link to instructions on how to take care of it on en.wiki? Thanks.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['I would love to do it myself (for everyone, not just in my own vector.js).SCREEN_NAME, do you have a link to instructions on how to take care of it on en.wiki?', 'Thanks.']",NA,1,"Thanks." +12301,"Add tracking category to pages with errors in ","I meant one line in wiki code, @SalixAlba and @Jonesey95, not jawascript. +",1467148543,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I meant one line in wiki code, @SalixAlba and @Jonesey95, not jawascript. +","I meant one line in wiki code,SCREEN_NAME andSCREEN_NAME, not jawascript. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['I meant one line in wiki code,SCREEN_NAME andSCREEN_NAME, not jawascript.']",NA,1,"I meant one line in wiki code,SCREEN_NAME andSCREEN_NAME, not jawascript." +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"It is a little annoying." +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"In time the number of false positives will go down and each page is re-rendered." +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"Some talk pages which discuss rendering errors will remain." +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"If its really a problem this bit of javascript in your vector.js will hide most of the talk pages." +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }" +12302,"Add tracking category to pages with errors in ","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",1467141776,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }","It is a little annoying. But I'm convinced it is worth the extra effort. In time the number of false positives will go down and each page is re-rendered. Some talk pages which discuss rendering errors will remain. + +If its really a problem this bit of javascript in your vector.js will hide most of the talk pages. + + jQuery( document ).ready( function( $ ) { + if( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") { + $("".mw-category-group a"").each(function(ind,ele) { + var title = ele.innerHTML; + if(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") + || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) { + root = ele.parentElement; + $(root).css({""display"":""none""}); + console.log(ele.innerHTML); + } + }) + } + }",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['It is a little annoying.', ""But I'm convinced it is worth the extra effort."", 'In time the number of false positives will go down and each page is re-rendered.', 'Some talk pages which discuss rendering errors will remain.', 'If its really a problem this bit of javascript in your vector.js will hide most of the talk pages.', 'jQuery( document ).ready( function( $ ) {\t\n \tif( document.title == ""Category:Pages with math errors - Wikipedia, the free encyclopedia"") {\n\t\t$("".mw-category-group a"").each(function(ind,ele) {\n\t\t\tvar title = ele.innerHTML;\n\t\t\tif(title.startsWith(""User:"") || title.startsWith(""Talk:"") || title.startsWith(""User talk:"") \n\t\t\t || title.startsWith(""Wikipedia:"") || title.startsWith(""Wikipedia talk:"") ) {\n\t\t\t\troot = ele.parentElement;\n\t\t\t\t$(root).css({""display"":""none""});\n\t\t\t\tconsole.log(ele.innerHTML);\n\t\t\t}\n\t\t})\n\t }\n }']",NA,1,"But I'm convinced it is worth the extra effort." +12303,"Add tracking category to pages with errors in ","But @Jonesey95, you can do it in a minute by yourself. +",1467135776,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","But @Jonesey95, you can do it in a minute by yourself. +","ButSCREEN_NAME, you can do it in a minute by yourself. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,156,NA,"['ButSCREEN_NAME, you can do it in a minute by yourself.']",NA,1,"ButSCREEN_NAME, you can do it in a minute by yourself." +12304,"Add tracking category to pages with errors in ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['If possible, it might be a good idea to limit the namespaces to which this category applies.', 'For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g.', '""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""', 'The error message still shows on these pages, but they are not categorized.', ""There is little point in categorizing someone's User sandbox page; it clutters the category with false positives.""]",NA,1,"If possible, it might be a good idea to limit the namespaces to which this category applies." +12304,"Add tracking category to pages with errors in ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['If possible, it might be a good idea to limit the namespaces to which this category applies.', 'For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g.', '""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""', 'The error message still shows on these pages, but they are not categorized.', ""There is little point in categorizing someone's User sandbox page; it clutters the category with false positives.""]",NA,1,"For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g." +12304,"Add tracking category to pages with errors in ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['If possible, it might be a good idea to limit the namespaces to which this category applies.', 'For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g.', '""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""', 'The error message still shows on these pages, but they are not categorized.', ""There is little point in categorizing someone's User sandbox page; it clutters the category with false positives.""]",NA,1,"""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""" +12304,"Add tracking category to pages with errors in ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['If possible, it might be a good idea to limit the namespaces to which this category applies.', 'For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g.', '""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""', 'The error message still shows on these pages, but they are not categorized.', ""There is little point in categorizing someone's User sandbox page; it clutters the category with false positives.""]",NA,1,"The error message still shows on these pages, but they are not categorized." +12304,"Add tracking category to pages with errors in ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",1467130992,"PHID-USER-7cpk77uy2iq7bxf6hac6","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ","If possible, it might be a good idea to limit the namespaces to which this category applies. For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g. ""Category:Pages with archiveurl citation errors"": + +""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories."" + +The error message still shows on these pages, but they are not categorized. There is little point in categorizing someone's User sandbox page; it clutters the category with false positives. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,156,NA,"['If possible, it might be a good idea to limit the namespaces to which this category applies.', 'For an example, see the Citation Style 1 error messages and categories on en.wiki, e.g.', '""Category:Pages with archiveurl citation errors"":\n\n""Pages in the Book talk, Category talk, Draft, Draft talk, Education Program talk, File talk, Help talk, MediaWiki talk, Module talk, Portal talk, Talk, Template talk, TimedText talk, User, User talk, and Wikipedia talk namespaces are not included in the error tracking categories.""', 'The error message still shows on these pages, but they are not categorized.', ""There is little point in categorizing someone's User sandbox page; it clutters the category with false positives.""]",NA,1,"There is little point in categorizing someone's User sandbox page; it clutters the category with false positives." +12305,"Add tracking category to pages with errors in ","@Aklapper? Or maybe @Quiddity? Thanks. +",1466776616,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","@Aklapper? Or maybe @Quiddity? Thanks. +","SCREEN_NAME? Or maybeSCREEN_NAME? Thanks. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['SCREEN_NAME?', 'Or maybeSCREEN_NAME?', 'Thanks.']",NA,1,"SCREEN_NAME?" +12305,"Add tracking category to pages with errors in ","@Aklapper? Or maybe @Quiddity? Thanks. +",1466776616,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","@Aklapper? Or maybe @Quiddity? Thanks. +","SCREEN_NAME? Or maybeSCREEN_NAME? Thanks. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['SCREEN_NAME?', 'Or maybeSCREEN_NAME?', 'Thanks.']",NA,1,"Or maybeSCREEN_NAME?" +12305,"Add tracking category to pages with errors in ","@Aklapper? Or maybe @Quiddity? Thanks. +",1466776616,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","@Aklapper? Or maybe @Quiddity? Thanks. +","SCREEN_NAME? Or maybeSCREEN_NAME? Thanks. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['SCREEN_NAME?', 'Or maybeSCREEN_NAME?', 'Thanks.']",NA,1,"Thanks." +12306,"Add tracking category to pages with errors in ","It looks like this is fixed in T134872 by https://gerrit.wikimedia.org/r/292576 We can probably close this as a duplicate. ",1466691225,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","It looks like this is fixed in T134872 by https://gerrit.wikimedia.org/r/292576 We can probably close this as a duplicate. ","It looks like this is fixed in T134872 by GERRIT_URL We can probably close this as a duplicate. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['It looks like this is fixed in T134872 by GERRIT_URL We can probably close this as a duplicate.']",NA,1,"It looks like this is fixed in T134872 by GERRIT_URL We can probably close this as a duplicate." +12307,"Add tracking category to pages with errors in ","So we now seem to have [[Category:Pages with math errors]] on en wiki at least. ",1466630074,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","So we now seem to have [[Category:Pages with math errors]] on en wiki at least. ","So we now seem to have [[Category:Pages with math errors]] on en wiki at least. ",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,155,NA,"['So we now seem to have [[Category:Pages with math errors]] on en wiki at least.']",NA,1,"So we now seem to have [[Category:Pages with math errors]] on en wiki at least." +12308,"Add tracking category to pages with errors in ","Hello, @Aklapper. It works. I think you need close this task as resolved. +",1466629083,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","Hello, @Aklapper. It works. I think you need close this task as resolved. +","Hello,SCREEN_NAME. It works. I think you need close this task as resolved. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['Hello,SCREEN_NAME.', 'It works.', 'I think you need close this task as resolved.']",NA,1,"Hello,SCREEN_NAME." +12308,"Add tracking category to pages with errors in ","Hello, @Aklapper. It works. I think you need close this task as resolved. +",1466629083,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","Hello, @Aklapper. It works. I think you need close this task as resolved. +","Hello,SCREEN_NAME. It works. I think you need close this task as resolved. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['Hello,SCREEN_NAME.', 'It works.', 'I think you need close this task as resolved.']",NA,1,"It works." +12308,"Add tracking category to pages with errors in ","Hello, @Aklapper. It works. I think you need close this task as resolved. +",1466629083,"PHID-USER-t7ue4j3fnqznjjs4z5ef","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","Hello, @Aklapper. It works. I think you need close this task as resolved. +","Hello,SCREEN_NAME. It works. I think you need close this task as resolved. +",NA,NA,NA,NA,NA,"True","c1",3,"True",NA,155,NA,"['Hello,SCREEN_NAME.', 'It works.', 'I think you need close this task as resolved.']",NA,1,"I think you need close this task as resolved." +12309,"Add tracking category to pages with errors in ","I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.",1437662084,"PHID-USER-4sfm3grxdo6hnogm4iqe","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.","I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,107,NA,"[""I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept.""]",NA,1,"I think we would need comunity consensus for enabling the MathSearch extension in production... and a lot of cleanup work... sinc it's currently more desinged as demo/proof of concept." +12310,"Add tracking category to pages with errors in ","**physik** wrote: + +(In reply to Richard Morris from comment #2) +> This error is made worse by the difference between the syntax used in +> MathJax and texvc. In +> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/ +> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +> a unicode character was used in a formula, the editor was probably using +> MathJax so the error did not show up. There seem to be a few such errors. A +> google search +> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia. +> org+-Talk%3A +> can be used to find some. + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",1413745226,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","**physik** wrote: + +(In reply to Richard Morris from comment #2) +> This error is made worse by the difference between the syntax used in +> MathJax and texvc. In +> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/ +> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +> a unicode character was used in a formula, the editor was probably using +> MathJax so the error did not show up. There seem to be a few such errors. A +> google search +> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia. +> org+-Talk%3A +> can be used to find some. + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.","**physik** wrote: + +(In reply to Richard Morris from comment #2) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,67,NA,"['**physik** wrote:\n\n(In reply to Richard Morris from comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBug 72240 will make it better again.', ""I'll try to migrate this feature from MathSearch to the Math extension.""]",NA,1,"**physik** wrote:\n\n(In reply to Richard Morris from comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBug 72240 will make it better again." +12310,"Add tracking category to pages with errors in ","**physik** wrote: + +(In reply to Richard Morris from comment #2) +> This error is made worse by the difference between the syntax used in +> MathJax and texvc. In +> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/ +> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +> a unicode character was used in a formula, the editor was probably using +> MathJax so the error did not show up. There seem to be a few such errors. A +> google search +> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia. +> org+-Talk%3A +> can be used to find some. + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",1413745226,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","**physik** wrote: + +(In reply to Richard Morris from comment #2) +> This error is made worse by the difference between the syntax used in +> MathJax and texvc. In +> http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/ +> Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +> a unicode character was used in a formula, the editor was probably using +> MathJax so the error did not show up. There seem to be a few such errors. A +> google search +> https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia. +> org+-Talk%3A +> can be used to find some. + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.","**physik** wrote: + +(In reply to Richard Morris from comment #2) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Bug 72240 will make it better again. I'll try to migrate this feature from MathSearch to the Math extension.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,67,NA,"['**physik** wrote:\n\n(In reply to Richard Morris from comment #2)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nBug 72240 will make it better again.', ""I'll try to migrate this feature from MathSearch to the Math extension.""]",NA,1,"I'll try to migrate this feature from MathSearch to the Math extension." +12311,"Add tracking category to pages with errors in ","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.",1376979625,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.","This error is made worse by the difference between the syntax used in MathJax and texvc. In +URL +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search URL +can be used to find some.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,7,NA,"['This error is made worse by the difference between the syntax used in MathJax and texvc.', 'In\nURL\na unicode character was used in a formula, the editor was probably using MathJax so the error did not show up.', 'There seem to be a few such errors.', 'A google search URL\ncan be used to find some.']",NA,1,"This error is made worse by the difference between the syntax used in MathJax and texvc." +12311,"Add tracking category to pages with errors in ","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.",1376979625,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.","This error is made worse by the difference between the syntax used in MathJax and texvc. In +URL +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search URL +can be used to find some.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,7,NA,"['This error is made worse by the difference between the syntax used in MathJax and texvc.', 'In\nURL\na unicode character was used in a formula, the editor was probably using MathJax so the error did not show up.', 'There seem to be a few such errors.', 'A google search URL\ncan be used to find some.']",NA,1,"In\nURL\na unicode character was used in a formula, the editor was probably using MathJax so the error did not show up." +12311,"Add tracking category to pages with errors in ","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.",1376979625,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.","This error is made worse by the difference between the syntax used in MathJax and texvc. In +URL +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search URL +can be used to find some.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,7,NA,"['This error is made worse by the difference between the syntax used in MathJax and texvc.', 'In\nURL\na unicode character was used in a formula, the editor was probably using MathJax so the error did not show up.', 'There seem to be a few such errors.', 'A google search URL\ncan be used to find some.']",NA,1,"There seem to be a few such errors." +12311,"Add tracking category to pages with errors in ","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.",1376979625,"PHID-USER-7hrs7wwclcldf7mm6a7o","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","This error is made worse by the difference between the syntax used in MathJax and texvc. In +http://en.wikipedia.org/w/index.php?title=Wikipedia:VisualEditor/Feedback&oldid=569279227#Math_text_that_doesn.27t_parse_when_in_VE +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search https://www.google.co.uk/search?q=%22Failed+to+parse%22+site:en.wikipedia.org+-Talk%3A +can be used to find some.","This error is made worse by the difference between the syntax used in MathJax and texvc. In +URL +a unicode character was used in a formula, the editor was probably using MathJax so the error did not show up. There seem to be a few such errors. A google search URL +can be used to find some.",NA,NA,NA,NA,NA,"True","c1",3,"False",NA,7,NA,"['This error is made worse by the difference between the syntax used in MathJax and texvc.', 'In\nURL\na unicode character was used in a formula, the editor was probably using MathJax so the error did not show up.', 'There seem to be a few such errors.', 'A google search URL\ncan be used to find some.']",NA,1,"A google search URL\ncan be used to find some." +12312,"Add tracking category to pages with errors in ","**physik** wrote: + +This is already a feature of the MathSearch extension.",1365506334,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-fr22j5swh5wt5gmpgdnh","task_subcomment","**physik** wrote: + +This is already a feature of the MathSearch extension.","**physik** wrote: + +This is already a feature of the MathSearch extension.",NA,NA,NA,NA,NA,"True","c1",1,"False",NA,-12,NA,"['**physik** wrote:\n\nThis is already a feature of the MathSearch extension.']",NA,1,"**physik** wrote:\n\nThis is already a feature of the MathSearch extension." +13574,"Create a ""zen mode""/""Distraction free mode"" MediaWiki extension","Perhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a ""zen mode"" capability from ?action=edit. + +GitHub and it seems like the Cloud9 IDE both have this mode. It's demonstrated here: . + +In short, in the case of GitHub, it appears to be a bit of JavaScript that adds a ""zen mode"" button to the UI. When the user clicks this button, the non-essential page elements are hidden from the page, allowing the user to focus on the textarea (or other central input area) alone. Basically it reduces the amount of noise on the page in order to increase the signal. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=14501",1361595420,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-edwajw6htxppl743yg5e","task_description","Create a ""zen mode""/""Distraction free mode"" MediaWiki extension./n/nPerhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a ""zen mode"" capability from ?action=edit. + +GitHub and it seems like the Cloud9 IDE both have this mode. It's demonstrated here: . + +In short, in the case of GitHub, it appears to be a bit of JavaScript that adds a ""zen mode"" button to the UI. When the user clicks this button, the non-essential page elements are hidden from the page, allowing the user to focus on the textarea (or other central input area) alone. Basically it reduces the amount of noise on the page in order to increase the signal. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=14501","Create a ""zen mode""/""Distraction free mode"" MediaWiki extension./n/nPerhaps might be nice in MediaWiki core, but would definitely be nice as at least a MediaWiki extension, we should implement a ""zen mode"" capability from ?action=edit. + +GitHub and it seems like the Cloud9 IDE both have this mode. It's demonstrated here: +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"// Returning avoids breakage of scripts like dumpBackup.php." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor." +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +16740,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Having FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1320866820,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_description","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See http://dev.ckeditor.com/ticket/6279 + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts./n/nHaving FCKeditor installed, I get the following notice when I run the maintenance scripts: + +Notice: Undefined index: HTTP_USER_AGENT in extensions\FCKeditor\fckeditor\fckeditor_php5.php on line 37 + +The file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode. + +People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue. See URL + +I see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance. +I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode: + +At the beginning of FCKeditor\FCKeditor.php: + +// There is no reason for FCKeditor to run in commandline mode. +// Returning avoids breakage of scripts like dumpBackup.php. +if ( isset($wgCommandLineMode) && $wgCommandLineMode ) +{ + return; // Simply return from the include, so no FCKeditor code is run +} + + +I am running MediaWiki 1.17 and the according released version of FCKeditor. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1323819001,NA,"resolved","True","c2",1,"False","False",-94,"True","['Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts.', ""Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode."", 'People have already asked for a fix in CKEditor itself, however the CKEditor guys say they will not fix this issue.', 'See URL\n\nI see no reason for FCKeditor to be loaded when running command line php scripts for mediawiki maintenance.', 'I propose to fix the issue in the MediaWiki extension by adding an early return, if we are in command line mode:\n\nAt the beginning of FCKeditor\\FCKeditor.php:\n\n// There is no reason for FCKeditor to run in commandline mode.', '// Returning avoids breakage of scripts like dumpBackup.php.', 'if ( isset($wgCommandLineMode) && $wgCommandLineMode )\n{\n return; // Simply return from the include, so no FCKeditor code is run\n}\n\n\nI am running MediaWiki 1.17 and the according released version of FCKeditor.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Having FCKeditor installed, I get the following notice when I run the maintenance scripts:\n\nNotice: Undefined index: HTTP_USER_AGENT in extensions\\FCKeditor\\fckeditor\\fckeditor_php5.php on line 37\n\nThe file in question attempts to access $_SERVER['HTTP_USER_AGENT'] which is not set in command line mode." +16741,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",1323869954,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-89,"True","['Hi Brion,\n\nyes, your patch solves the issue as well!', 'Thank you!', ':-)']",NA,0,"Hi Brion,\n\nyes, your patch solves the issue as well!" +16741,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",1323869954,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-89,"True","['Hi Brion,\n\nyes, your patch solves the issue as well!', 'Thank you!', ':-)']",NA,0,"Thank you!" +16741,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",1323869954,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)","Hi Brion, + +yes, your patch solves the issue as well! Thank you! :-)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-89,"True","['Hi Brion,\n\nyes, your patch solves the issue as well!', 'Thank you!', ':-)']",NA,0,":-)" +16742,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",1323819001,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Ok looks like the loader code is doing this:\n\n // Initialize FCKeditor and the MediaWiki extension\n $fckeditor = new FCKeditor('fake');\n $wgFCKEditorIsCompatible = $fckeditor->IsCompatible();\n\nso...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work."", ';)\n\nLemme see if we can disable that....\n\nr106129 should do the job, seems to work for my testing.', 'Joerg, can you confirm?']",NA,0,";)\n\nLemme see if we can disable that....\n\nr106129 should do the job, seems to work for my testing." +16742,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",1323819001,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Ok looks like the loader code is doing this:\n\n // Initialize FCKeditor and the MediaWiki extension\n $fckeditor = new FCKeditor('fake');\n $wgFCKEditorIsCompatible = $fckeditor->IsCompatible();\n\nso...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work."", ';)\n\nLemme see if we can disable that....\n\nr106129 should do the job, seems to work for my testing.', 'Joerg, can you confirm?']",NA,0,"Joerg, can you confirm?" +16742,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",1323819001,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?","Ok looks like the loader code is doing this: + + // Initialize FCKeditor and the MediaWiki extension + $fckeditor = new FCKeditor('fake'); + $wgFCKEditorIsCompatible = $fckeditor->IsCompatible(); + +so...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work. ;) + +Lemme see if we can disable that.... + +r106129 should do the job, seems to work for my testing. Joerg, can you confirm?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Ok looks like the loader code is doing this:\n\n // Initialize FCKeditor and the MediaWiki extension\n $fckeditor = new FCKeditor('fake');\n $wgFCKEditorIsCompatible = $fckeditor->IsCompatible();\n\nso...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work."", ';)\n\nLemme see if we can disable that....\n\nr106129 should do the job, seems to work for my testing.', 'Joerg, can you confirm?']",NA,0,"Ok looks like the loader code is doing this:\n\n // Initialize FCKeditor and the MediaWiki extension\n $fckeditor = new FCKeditor('fake');\n $wgFCKEditorIsCompatible = $fckeditor->IsCompatible();\n\nso...... that kinda defeats the purpose of a loader script not being supposed to execute stuff that might not work." +16743,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",1323818630,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like."", ""These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals."", ';)']",NA,0,";)" +16743,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",1323818630,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like."", ""These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals."", ';)']",NA,0,"Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like." +16743,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",1323818630,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)","Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like. + +These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals. ;)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-90,"True","[""Shouldn't make a difference between 1.18 and earlier since it's a bug in the FCKEditor low-level classes, it looks like."", ""These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals."", ';)']",NA,0,"These really shouldn't be getting invoked unless the editor is in use, though.... but I don't really want to mess around with its internals." +16744,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",1323613139,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-90,"True","['Hi sumanah,\n\nthanks for the question.', 'I was not yet able to install 1.18 to test this.', 'I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend.', 'I will definitely keep you updated here.']",NA,0,"Hi sumanah,\n\nthanks for the question." +16744,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",1323613139,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-90,"True","['Hi sumanah,\n\nthanks for the question.', 'I was not yet able to install 1.18 to test this.', 'I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend.', 'I will definitely keep you updated here.']",NA,0,"I was not yet able to install 1.18 to test this." +16744,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",1323613139,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-90,"True","['Hi sumanah,\n\nthanks for the question.', 'I was not yet able to install 1.18 to test this.', 'I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend.', 'I will definitely keep you updated here.']",NA,0,"I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend." +16744,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",1323613139,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.","Hi sumanah, + +thanks for the question. I was not yet able to install 1.18 to test this. I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend. I will definitely keep you updated here.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-90,"True","['Hi sumanah,\n\nthanks for the question.', 'I was not yet able to install 1.18 to test this.', 'I hope that other work in my wiki is completed during this week and that I can install 1.18 next weekend.', 'I will definitely keep you updated here.']",NA,0,"I will definitely keep you updated here." +16745,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","**sumanah** wrote: + +Joerg, just a quick question, does the problem still happen with MediaWiki 1.18?",1322776202,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","**sumanah** wrote: + +Joerg, just a quick question, does the problem still happen with MediaWiki 1.18?","**sumanah** wrote: + +Joerg, just a quick question, does the problem still happen with MediaWiki 1.18?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-91,"True","['**sumanah** wrote:\n\nJoerg, just a quick question, does the problem still happen with MediaWiki 1.18?']",NA,0,"**sumanah** wrote:\n\nJoerg, just a quick question, does the problem still happen with MediaWiki 1.18?" +16746,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}",1320866932,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-94,"True","['Created attachment 9404\nPatch for the issue\n\nI attached the patch.', '**Attached**: {F8381}']",NA,0,"Created attachment 9404\nPatch for the issue\n\nI attached the patch." +16746,"Undefined index ""HTTP_USER_AGENT"" causes PHP notice in maintenance scripts","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}",1320866932,"PHID-USER-lcqy7fyefr42fd2lpdne","PHID-TASK-ynjvd2pb6u52k7kwgzgh","task_subcomment","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}","Created attachment 9404 +Patch for the issue + +I attached the patch. + +**Attached**: {F8381}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-94,"True","['Created attachment 9404\nPatch for the issue\n\nI attached the patch.', '**Attached**: {F8381}']",NA,0,"**Attached**: {F8381}" +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"NewUserMessage extensions breaks login." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"I installed this extension and it works fine for a new user signing up, but it breaks login for existing users." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"Disabling the extension resolved the issue for me." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"This is using MediaWiki 1.18.0." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"Nothing showed up in the error log." +16857,"NewUserMessage extensions breaks login","I installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker",1326123000,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_description","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","NewUserMessage extensions breaks login./n/nI installed this extension and it works fine for a new user signing up, but it breaks login for existing users. Logging in as an existing user generates the error: + +Login error +You have not specified a valid username. + +Disabling the extension resolved the issue for me. This is using MediaWiki 1.18.0. Nothing showed up in the error log. + +-------------------------- +**Version**: unspecified +**Severity**: blocker","High",80,1350964208,NA,"declined","True","c2",1,"False","False",-86,"True","['NewUserMessage extensions breaks login.', 'I installed this extension and it works fine for a new user signing up, but it breaks login for existing users.', 'Logging in as an existing user generates the error:\n\nLogin error\nYou have not specified a valid username.', 'Disabling the extension resolved the issue for me.', 'This is using MediaWiki 1.18.0.', 'Nothing showed up in the error log.', '--------------------------\n**Version**: unspecified\n**Severity**: blocker']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: blocker" +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"Sorry to go silent on this thread." +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated." +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"If I deactivate it I can login." +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception." +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"I'm not going to reopen this, I'll try to debug further." +16858,"NewUserMessage extensions breaks login","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",1358809691,"PHID-USER-m4lc24apros2wn24aqyu","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.","Sorry to go silent on this thread. I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception. For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated. If I deactivate it I can login. I'm not going to reopen this, I'll try to debug further. I'm very confused about what is happening.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['Sorry to go silent on this thread.', ""I'm now using NewUserMessage on a number of wikis and indeed it works fine, with one exception."", 'For some reason I have one instance where my user account (and seemingly no others) cannot log in if NewUserMessage is activated.', 'If I deactivate it I can login.', ""I'm not going to reopen this, I'll try to debug further."", ""I'm very confused about what is happening.""]",NA,0,"I'm very confused about what is happening." +16859,"NewUserMessage extensions breaks login","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!",1350964208,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ). Thanks!",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-45,"True","['Unfortunately closing this report as no further information has been provided.', 'Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ).', 'Thanks!']",NA,0,"Unfortunately closing this report as no further information has been provided." +16859,"NewUserMessage extensions breaks login","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!",1350964208,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ). Thanks!",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-45,"True","['Unfortunately closing this report as no further information has been provided.', 'Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ).', 'Thanks!']",NA,0,"Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL )." +16859,"NewUserMessage extensions breaks login","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!",1350964208,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see http://www.mediawiki.org/wiki/Version_lifecycle ). Thanks!","Unfortunately closing this report as no further information has been provided. + +Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ). Thanks!",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-45,"True","['Unfortunately closing this report as no further information has been provided.', 'Jamie: Please feel free to reopen this report if you can provide the information asked for and if this still happens in a recent supported version (see URL ).', 'Thanks!']",NA,0,"Thanks!" +16860,"NewUserMessage extensions breaks login","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?",1337632645,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['**AzianAlex** wrote:\n\nWorks fine for me too.', 'Have you tried clearing your cache?']",NA,0,"**AzianAlex** wrote:\n\nWorks fine for me too." +16860,"NewUserMessage extensions breaks login","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?",1337632645,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?","**AzianAlex** wrote: + +Works fine for me too. Have you tried clearing your cache?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['**AzianAlex** wrote:\n\nWorks fine for me too.', 'Have you tried clearing your cache?']",NA,0,"Have you tried clearing your cache?" +16861,"NewUserMessage extensions breaks login","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",1335110687,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-71,"True","['**vivekee047** wrote:\n\nThis works fine for me.', 'Can you check it once again please.', 'Thanks']",NA,0,"**vivekee047** wrote:\n\nThis works fine for me." +16861,"NewUserMessage extensions breaks login","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",1335110687,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-71,"True","['**vivekee047** wrote:\n\nThis works fine for me.', 'Can you check it once again please.', 'Thanks']",NA,0,"Can you check it once again please." +16861,"NewUserMessage extensions breaks login","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",1335110687,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-ses3qd5xfsiawguaqdlu","task_subcomment","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks","**vivekee047** wrote: + +This works fine for me. Can you check it once again please. +Thanks",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-71,"True","['**vivekee047** wrote:\n\nThis works fine for me.', 'Can you check it once again please.', 'Thanks']",NA,0,"Thanks" +17045,"No way to do logins without user surrendering their password to software","There is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348",1331645520,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_description","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1416907981,"PHID-USER-ppytiem7rcsbnstfsrvq","declined","True","c2",1,"True","True",-77,"True","['No way to do logins without user surrendering their password to software.', 'There is currently no way to login to SUL on production.', ""Regular login which asks for password isn't possible because of restrictions set by wmf."", 'This blocks the development of app, until any kind of login is enabled by wmf operation team.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"No way to do logins without user surrendering their password to software." +17045,"No way to do logins without user surrendering their password to software","There is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348",1331645520,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_description","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1416907981,"PHID-USER-ppytiem7rcsbnstfsrvq","declined","True","c2",1,"True","True",-77,"True","['No way to do logins without user surrendering their password to software.', 'There is currently no way to login to SUL on production.', ""Regular login which asks for password isn't possible because of restrictions set by wmf."", 'This blocks the development of app, until any kind of login is enabled by wmf operation team.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"There is currently no way to login to SUL on production." +17045,"No way to do logins without user surrendering their password to software","There is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348",1331645520,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_description","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1416907981,"PHID-USER-ppytiem7rcsbnstfsrvq","declined","True","c2",1,"True","True",-77,"True","['No way to do logins without user surrendering their password to software.', 'There is currently no way to login to SUL on production.', ""Regular login which asks for password isn't possible because of restrictions set by wmf."", 'This blocks the development of app, until any kind of login is enabled by wmf operation team.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"This blocks the development of app, until any kind of login is enabled by wmf operation team." +17045,"No way to do logins without user surrendering their password to software","There is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348",1331645520,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_description","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1416907981,"PHID-USER-ppytiem7rcsbnstfsrvq","declined","True","c2",1,"True","True",-77,"True","['No way to do logins without user surrendering their password to software.', 'There is currently no way to login to SUL on production.', ""Regular login which asks for password isn't possible because of restrictions set by wmf."", 'This blocks the development of app, until any kind of login is enabled by wmf operation team.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL" +17045,"No way to do logins without user surrendering their password to software","There is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348",1331645520,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_description","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +https://bugzilla.wikimedia.org/show_bug.cgi?id=30348","No way to do logins without user surrendering their password to software./n/nThere is currently no way to login to SUL on production. Regular login which asks for password isn't possible because of restrictions set by wmf. This blocks the development of app, until any kind of login is enabled by wmf operation team. + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +URL","Medium",50,1416907981,"PHID-USER-ppytiem7rcsbnstfsrvq","declined","True","c2",1,"True","True",-77,"True","['No way to do logins without user surrendering their password to software.', 'There is currently no way to login to SUL on production.', ""Regular login which asks for password isn't possible because of restrictions set by wmf."", 'This blocks the development of app, until any kind of login is enabled by wmf operation team.', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\nURL']",FALSE,0,"Regular login which asks for password isn't possible because of restrictions set by wmf." +17046,"No way to do logins without user surrendering their password to software","BTW the app in my comment from 2013 you responded to was the C++ application for which OAuth is still not useable, only web-based app's are now supported",1416910649,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","BTW the app in my comment from 2013 you responded to was the C++ application for which OAuth is still not useable, only web-based app's are now supported","BTW the app in my comment from 2013 you responded to was the C++ application for which OAuth is still not useable, only web-based app's are now supported",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,64,"True","[""BTW the app in my comment from 2013 you responded to was the C++ application for which OAuth is still not useable, only web-based app's are now supported""]",NA,0,"BTW the app in my comment from 2013 you responded to was the C++ application for which OAuth is still not useable, only web-based app's are now supported" +17047,"No way to do logins without user surrendering their password to software","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.",1416910556,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,64,"True","['this is irrelevant, whole huggle-wa project is closed now.', ""bug is closed as it's no longer valid.""]",NA,0,"this is irrelevant, whole huggle-wa project is closed now." +17047,"No way to do logins without user surrendering their password to software","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.",1416910556,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.","this is irrelevant, whole huggle-wa project is closed now. bug is closed as it's no longer valid.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,64,"True","['this is irrelevant, whole huggle-wa project is closed now.', ""bug is closed as it's no longer valid.""]",NA,0,"bug is closed as it's no longer valid." +17048,"No way to do logins without user surrendering their password to software",">>! In T37199#400227, @Petrb wrote: +> ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work + +""for app it doesn't work"" which app doesnt it work for? + +Is there a ticket open for why oauth doesnt work? +",1416909680,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment",">>! In T37199#400227, @Petrb wrote: +> ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work + +""for app it doesn't work"" which app doesnt it work for? + +Is there a ticket open for why oauth doesnt work? +","QUOTE +QUOTE + +""for app it doesn't work"" which app doesnt it work for? + +Is there a ticket open for why oauth doesnt work? +",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,64,"True","['QUOTE\nQUOTE\n\n""for app it doesn\'t work"" which app doesnt it work for?', 'Is there a ticket open for why oauth doesnt work?']",NA,0,"QUOTE\nQUOTE\n\n""for app it doesn\" +17049,"No way to do logins without user surrendering their password to software","ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work",1379754742,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work","ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,3,"True","[""ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work""]",NA,0,"ok so oauth is partially available for webapp's so this is no longer a blocker, but for app it doesn't work" +17050,"No way to do logins without user surrendering their password to software","(In reply to comment #13) +> Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.",1376789843,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #13) +> Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.",1376789843,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #13) +> Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.",1376789843,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #13) +> Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.",1376789843,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #13) +> Is it possible to provide users with an edit token that is visible via +> preferences (like the watchlist token), and is expired frequently; e.g. daily +> reset, with an age of 24 hrs after first use of the token. + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to , OAuth is going into testing on Monday, August 19.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE + +Possible? Sure. But it's unlikely to be implemented on Wikimedia wikis. According to What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +thread here: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/59502",1331774322,"PHID-USER-ogbcrxm45oo3n3xe5q25","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #3) +> What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +thread here: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/59502","(In reply to comment #3) +QUOTE +QUOTE +QUOTE + +thread here: URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-76,"True","['(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nthread here: URL']",NA,0,"(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nthread here: URL" +17059,"No way to do logins without user surrendering their password to software","yes but that is allowed by wmf, while doing it on server is not",1331667950,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","yes but that is allowed by wmf, while doing it on server is not","yes but that is allowed by wmf, while doing it on server is not",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","['yes but that is allowed by wmf, while doing it on server is not']",NA,0,"yes but that is allowed by wmf, while doing it on server is not" +17060,"No way to do logins without user surrendering their password to software","(In reply to comment #2) +> Ryan Lane is going to discuss some alternative options which are possible, +> however until then the development is kind of blocked, so I created this ticket +> so other devs of huggle wa can see the reason + +(In reply to comment #3) +> What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...",1331661018,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #2) +> Ryan Lane is going to discuss some alternative options which are possible, +> however until then the development is kind of blocked, so I created this ticket +> so other devs of huggle wa can see the reason + +(In reply to comment #3) +> What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +(In reply to comment #3) +QUOTE +QUOTE +QUOTE + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\n(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nEssentially that's no different to how the Windows app works - You still enter your username and password into the application."", ""Just for the web app, you're giving a remote server your details too...""]",NA,0,"(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\n(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nEssentially that's no different to how the Windows app works - You still enter your username and password into the application." +17060,"No way to do logins without user surrendering their password to software","(In reply to comment #2) +> Ryan Lane is going to discuss some alternative options which are possible, +> however until then the development is kind of blocked, so I created this ticket +> so other devs of huggle wa can see the reason + +(In reply to comment #3) +> What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...",1331661018,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #2) +> Ryan Lane is going to discuss some alternative options which are possible, +> however until then the development is kind of blocked, so I created this ticket +> so other devs of huggle wa can see the reason + +(In reply to comment #3) +> What he's saying is that the web version of huggle needs to log users in as +> themselves, which means it needs to ask for their username/password. Obviously +> this sucks a little, but there's no alternative because we don't support OAuth. + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...","(In reply to comment #2) +QUOTE +QUOTE +QUOTE + +(In reply to comment #3) +QUOTE +QUOTE +QUOTE + +Essentially that's no different to how the Windows app works - You still enter your username and password into the application. Just for the web app, you're giving a remote server your details too...",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","[""(In reply to comment #2)\nQUOTE\nQUOTE\nQUOTE\n\n(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\n\nEssentially that's no different to how the Windows app works - You still enter your username and password into the application."", ""Just for the web app, you're giving a remote server your details too...""]",NA,0,"Just for the web app, you're giving a remote server your details too..." +17061,"No way to do logins without user surrendering their password to software","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.",1331660724,"PHID-USER-xs3vxsmgivmm2tuyxsrb","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-77,"True","[""What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password."", ""Obviously this sucks a little, but there's no alternative because we don't support OAuth.""]",NA,0,"What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password." +17061,"No way to do logins without user surrendering their password to software","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.",1331660724,"PHID-USER-xs3vxsmgivmm2tuyxsrb","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.","What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password. Obviously this sucks a little, but there's no alternative because we don't support OAuth.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-77,"True","[""What he's saying is that the web version of huggle needs to log users in as themselves, which means it needs to ask for their username/password."", ""Obviously this sucks a little, but there's no alternative because we don't support OAuth.""]",NA,0,"Obviously this sucks a little, but there's no alternative because we don't support OAuth." +17062,"No way to do logins without user surrendering their password to software","Ryan Lane is going to discuss some alternative options which are possible, however until then the development is kind of blocked, so I created this ticket so other devs of huggle wa can see the reason",1331660199,"PHID-USER-ppytiem7rcsbnstfsrvq","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","Ryan Lane is going to discuss some alternative options which are possible, however until then the development is kind of blocked, so I created this ticket so other devs of huggle wa can see the reason","Ryan Lane is going to discuss some alternative options which are possible, however until then the development is kind of blocked, so I created this ticket so other devs of huggle wa can see the reason",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","['Ryan Lane is going to discuss some alternative options which are possible, however until then the development is kind of blocked, so I created this ticket so other devs of huggle wa can see the reason']",NA,0,"Ryan Lane is going to discuss some alternative options which are possible, however until then the development is kind of blocked, so I created this ticket so other devs of huggle wa can see the reason" +17063,"No way to do logins without user surrendering their password to software","(In reply to comment #0) +> There is currently no way to login to SUL on production. Regular login which +> asks for password isn't possible because of restrictions set by wmf. This +> blocks the development of app, until any kind of login is enabled by wmf +> operation team. + +Eh, what?",1331659506,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-hygsocxkypuho4yqoprw","task_subcomment","(In reply to comment #0) +> There is currently no way to login to SUL on production. Regular login which +> asks for password isn't possible because of restrictions set by wmf. This +> blocks the development of app, until any kind of login is enabled by wmf +> operation team. + +Eh, what?","(In reply to comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +Eh, what?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","['(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nEh, what?']",NA,0,"(In reply to comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nEh, what?" +17081,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Try visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1330507020,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_description","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting URL - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1363804433,NA,"resolved","True","c2",1,"False","False",-78,"True","[""Non-Wikipedia mobile domains use Wikipedia's SSL certificate."", ""Try visiting URL - you'll get warning that host does not match certificate."", 'The cert is issued to Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"The cert is issued to Wikipedia." +17081,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Try visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1330507020,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_description","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting URL - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1363804433,NA,"resolved","True","c2",1,"False","False",-78,"True","[""Non-Wikipedia mobile domains use Wikipedia's SSL certificate."", ""Try visiting URL - you'll get warning that host does not match certificate."", 'The cert is issued to Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +17081,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Try visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1330507020,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_description","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting URL - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1363804433,NA,"resolved","True","c2",1,"False","False",-78,"True","[""Non-Wikipedia mobile domains use Wikipedia's SSL certificate."", ""Try visiting URL - you'll get warning that host does not match certificate."", 'The cert is issued to Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate." +17081,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Try visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1330507020,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_description","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting https://en.m.wiktionary.org/wiki/Wiktionary:Main_Page - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Non-Wikipedia mobile domains use Wikipedia's SSL certificate./n/nTry visiting URL - you'll get warning that host does not match certificate. The cert is issued to Wikipedia. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1363804433,NA,"resolved","True","c2",1,"False","False",-78,"True","[""Non-Wikipedia mobile domains use Wikipedia's SSL certificate."", ""Try visiting URL - you'll get warning that host does not match certificate."", 'The cert is issued to Wikipedia.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Try visiting URL - you'll get warning that host does not match certificate." +17082,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.",1363804433,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-23,"True","['According to RobH ""This was done and pushed out awhile ago, all done!""', 'Closing as FIXED.']",NA,0,"According to RobH ""This was done and pushed out awhile ago, all done!""" +17082,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.",1363804433,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.","According to RobH ""This was done and pushed out awhile ago, all done!"" + +Closing as FIXED.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-23,"True","['According to RobH ""This was done and pushed out awhile ago, all done!""', 'Closing as FIXED.']",NA,0,"Closing as FIXED." +17083,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Note that m.wikipedia.org was also accidentally left off, so the unified cert is being rolled back.",1363133763,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Note that m.wikipedia.org was also accidentally left off, so the unified cert is being rolled back.","Note that m.wikipedia.org was also accidentally left off, so the unified cert is being rolled back.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-24,"True","['Note that m.wikipedia.org was also accidentally left off, so the unified cert is being rolled back.']",NA,0,"Note that m.wikipedia.org was also accidentally left off, so the unified cert is being rolled back." +17084,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.",1363127826,"PHID-USER-xs3vxsmgivmm2tuyxsrb","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['mediawiki.org was accidentally left out of the unified certificate.', ""We'll be ordering a new one soon.""]",NA,0,"mediawiki.org was accidentally left out of the unified certificate." +17084,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.",1363127826,"PHID-USER-xs3vxsmgivmm2tuyxsrb","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.","mediawiki.org was accidentally left out of the unified certificate. We'll be ordering a new one soon.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['mediawiki.org was accidentally left out of the unified certificate.', ""We'll be ordering a new one soon.""]",NA,0,"We'll be ordering a new one soon." +17085,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Done for all except for mediawiki.org",1363127766,"PHID-USER-xs3vxsmgivmm2tuyxsrb","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Done for all except for mediawiki.org","Done for all except for mediawiki.org",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['Done for all except for mediawiki.org']",NA,0,"Done for all except for mediawiki.org" +17086,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Created attachment 11918 +Windows Phone 7.5 error screen on wikivoyage + +**Attached**: {F8836}",1363115566,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Created attachment 11918 +Windows Phone 7.5 error screen on wikivoyage + +**Attached**: {F8836}","Created attachment 11918 +Windows Phone 7.5 error screen on wikivoyage + +**Attached**: {F8836}",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-25,"True","['Created attachment 11918\nWindows Phone 7.5 error screen on wikivoyage\n\n**Attached**: {F8836}']",NA,0,"Created attachment 11918\nWindows Phone 7.5 error screen on wikivoyage\n\n**Attached**: {F8836}" +17087,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Created attachment 11917 +Errors on m.wikivoyage in Firefox + +**Attached**: {F8835}",1363115509,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Created attachment 11917 +Errors on m.wikivoyage in Firefox + +**Attached**: {F8835}","Created attachment 11917 +Errors on m.wikivoyage in Firefox + +**Attached**: {F8835}",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-25,"True","['Created attachment 11917\nErrors on m.wikivoyage in Firefox\n\n**Attached**: {F8835}']",NA,0,"Created attachment 11917\nErrors on m.wikivoyage in Firefox\n\n**Attached**: {F8835}" +17088,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 46037 has been marked as a duplicate of this bug. ***",1363115475,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 46037 has been marked as a duplicate of this bug. ***","*** Bug 46037 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-25,"True","['*** Bug 46037 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 46037 has been marked as a duplicate of this bug." +17088,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 46037 has been marked as a duplicate of this bug. ***",1363115475,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 46037 has been marked as a duplicate of this bug. ***","*** Bug 46037 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-25,"True","['*** Bug 46037 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +17089,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Just in case it's related: I just logged in to English Wikipedia from my mobile device and a dialog showed up saying that wikivoyage.org certificate is untrusted.",1361921653,"PHID-USER-lluzkul4z7us4sxkayss","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Just in case it's related: I just logged in to English Wikipedia from my mobile device and a dialog showed up saying that wikivoyage.org certificate is untrusted.","Just in case it's related: I just logged in to English Wikipedia from my mobile device and a dialog showed up saying that wikivoyage.org certificate is untrusted.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-27,"True","[""Just in case it's related: I just logged in to English Wikipedia from my mobile device and a dialog showed up saying that wikivoyage.org certificate is untrusted.""]",NA,0,"Just in case it's related: I just logged in to English Wikipedia from my mobile device and a dialog showed up saying that wikivoyage.org certificate is untrusted." +17090,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%",1361358978,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-27,"True","['**inbox** wrote:\n\n%%%*** Bug 38412 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"**inbox** wrote:\n\n%%%*** Bug 38412 has been marked as a duplicate of this bug." +17090,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%",1361358978,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%","**inbox** wrote: + +%%%*** Bug 38412 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-27,"True","['**inbox** wrote:\n\n%%%*** Bug 38412 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"***%%%" +17091,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%",1361358864,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-27,"True","['**inbox** wrote:\n\n%%%*** Bug 37650 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"**inbox** wrote:\n\n%%%*** Bug 37650 has been marked as a duplicate of this bug." +17091,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%",1361358864,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%","**inbox** wrote: + +%%%*** Bug 37650 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-27,"True","['**inbox** wrote:\n\n%%%*** Bug 37650 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"***%%%" +17092,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #15) +> This was posted over a month ago. Any updates? + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.",1361038878,"PHID-USER-7ey733eainlhx5xqp4d3","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #15) +> This was posted over a month ago. Any updates? + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.","(In reply to comment #15) +QUOTE + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-28,"True","[""(In reply to comment #15)\nQUOTE\n\nThe RT ticket's had very recent progress."", ""I wouldn't expect any further news at least until after the weekend.""]",NA,0,"(In reply to comment #15)\nQUOTE\n\nThe RT ticket's had very recent progress." +17092,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #15) +> This was posted over a month ago. Any updates? + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.",1361038878,"PHID-USER-7ey733eainlhx5xqp4d3","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #15) +> This was posted over a month ago. Any updates? + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.","(In reply to comment #15) +QUOTE + +The RT ticket's had very recent progress. I wouldn't expect any further news at least until after the weekend.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-28,"True","[""(In reply to comment #15)\nQUOTE\n\nThe RT ticket's had very recent progress."", ""I wouldn't expect any further news at least until after the weekend.""]",NA,0,"I wouldn't expect any further news at least until after the weekend." +17093,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.",1361038211,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-28,"True","['(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis was posted over a month ago.', 'Any updates?', 'Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.']",NA,0,"(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis was posted over a month ago." +17093,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.",1361038211,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-28,"True","['(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis was posted over a month ago.', 'Any updates?', 'Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.']",NA,0,"Any updates?" +17093,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.",1361038211,"PHID-USER-x7ti5ksby4ubsabntlxa","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #13) +> > The problem is that mobile is served by Varnish, whereas the main projects +> > are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> > two in this new setup. +> +> As for the current status, RobHa ""emailed digicert to attempt to get ALL our +> domains as SANS on a single root level wikimedia.org certificate."" + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about https://uk.m.wikinews.org using a wikipedia cert.","(In reply to comment #13) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +This was posted over a month ago. Any updates? Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-28,"True","['(In reply to comment #13)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThis was posted over a month ago.', 'Any updates?', 'Just had a user in #wikimedia-tech asking about URL using a wikipedia cert.']",NA,0,"Just had a user in #wikimedia-tech asking about URL using a wikipedia cert." +17094,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","Created attachment 11757 +ugly error message in Firefox android + +**Attached**: {F8834}",1360344072,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","Created attachment 11757 +ugly error message in Firefox android + +**Attached**: {F8834}","Created attachment 11757 +ugly error message in Firefox android + +**Attached**: {F8834}",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-29,"True","['Created attachment 11757\nugly error message in Firefox android\n\n**Attached**: {F8834}']",NA,0,"Created attachment 11757\nugly error message in Firefox android\n\n**Attached**: {F8834}" +17095,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",1358158691,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""","DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL . That's not the case here. + +With regard to the problems and the current status of this: + +QUOTE +QUOTE +QUOTE + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-33,"True","['DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL .', ""That's not the case here."", 'With regard to the problems and the current status of this:\n\nQUOTE\nQUOTE\nQUOTE\n\nAs for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""']",NA,0,"DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL ." +17095,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",1358158691,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""","DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL . That's not the case here. + +With regard to the problems and the current status of this: + +QUOTE +QUOTE +QUOTE + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-33,"True","['DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL .', ""That's not the case here."", 'With regard to the problems and the current status of this:\n\nQUOTE\nQUOTE\nQUOTE\n\nAs for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""']",NA,0,"With regard to the problems and the current status of this:\n\nQUOTE\nQUOTE\nQUOTE\n\nAs for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""" +17095,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",1358158691,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","DavidL: ""Critical"" means ""Crashes, loss of data"" as per http://www.mediawiki.org/wiki/Bugzilla/Fields#Severity . That's not the case here. + +With regard to the problems and the current status of this: + +> The problem is that mobile is served by Varnish, whereas the main projects +> are still on Squid, and NGINX (HTTPS) will need to distinguish between the +> two in this new setup. + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""","DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL . That's not the case here. + +With regard to the problems and the current status of this: + +QUOTE +QUOTE +QUOTE + +As for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-33,"True","['DavidL: ""Critical"" means ""Crashes, loss of data"" as per URL .', ""That's not the case here."", 'With regard to the problems and the current status of this:\n\nQUOTE\nQUOTE\nQUOTE\n\nAs for the current status, RobHa ""emailed digicert to attempt to get ALL our domains as SANS on a single root level wikimedia.org certificate.""']",NA,0,"That's not the case here." +17096,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**lambdav** wrote: + +Critical problems do not seems to be high priority for wikimedia...",1357951678,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**lambdav** wrote: + +Critical problems do not seems to be high priority for wikimedia...","**lambdav** wrote: + +Critical problems do not seems to be high priority for wikimedia...",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-33,"True","['**lambdav** wrote:\n\nCritical problems do not seems to be high priority for wikimedia...']",NA,0,"**lambdav** wrote:\n\nCritical problems do not seems to be high priority for wikimedia..." +17097,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.",1352636537,"PHID-USER-pwsgofaoir7tnszvfzqi","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-42,"True","['...or remove the ""Mobile view"" link altogether when in https.', ""Seriously - this really should be dealt with, even if we don't get good certificates.""]",NA,0,"...or remove the ""Mobile view"" link altogether when in https." +17097,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.",1352636537,"PHID-USER-pwsgofaoir7tnszvfzqi","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.","...or remove the ""Mobile view"" link altogether when in https. Seriously - this really should be dealt with, even if we don't get good certificates.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-42,"True","['...or remove the ""Mobile view"" link altogether when in https.', ""Seriously - this really should be dealt with, even if we don't get good certificates.""]",NA,0,"Seriously - this really should be dealt with, even if we don't get good certificates." +17098,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",1350160634,"PHID-USER-5paybpgtxjrhikdos3p5","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-46,"True","['If the good certificates won\'t be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?']",NA,0,"If the good certificates won\" +17098,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",1350160634,"PHID-USER-5paybpgtxjrhikdos3p5","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-46,"True","['If the good certificates won\'t be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?']",NA,0,"normal" +17098,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",1350160634,"PHID-USER-5paybpgtxjrhikdos3p5","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?","If the good certificates won't be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-46,"True","['If the good certificates won\'t be added, is there a way to redirect users, that used ""normal"" website in https and click on ""Mobile view"" link, to mobile website using http ?']",NA,0,"Mobile view" +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"If it were, it would have been fixed already, right?" +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998." +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then." +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it." +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"It used to be that the mobile site was completely read-only, but maybe that's changed?" +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"I'm not sure what the critical or high priority parts would be here." +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"I think you're really asking for a status update from RT #2541." +17099,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.",1350101462,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","(In reply to comment #6) +> (In reply to comment #1) +>> RT #2541 +> +> This site has private access only. +> +> How many years to solve a Critical problem with High priority ? No one is +> assigned to this bug, and no solution is proposed. + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +> On a related note, if you go to .com addresses (like https://en.wikipedia.com/) +> using HTTPS protocol, before you get forwarded to the .org address, you will +> get an error message regarding the SSL key. That is because the .com addresses +> use the SSL key that is for *.wikipedia.org + +I split this out to bug 40998.","(In reply to comment #6) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Well, it's obviously not a critical problem with high priority, then. If it were, it would have been fixed already, right? :-) + +I'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it. It used to be that the mobile site was completely read-only, but maybe that's changed? I'm not sure what the critical or high priority parts would be here. + +I think you're really asking for a status update from RT #2541. I'll CC a few a people on this bug who may be able to help with that. + +(In reply to comment #8) +QUOTE +QUOTE +QUOTE +QUOTE + +I split this out to bug 40998.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-46,"True","[""(In reply to comment #6)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWell, it's obviously not a critical problem with high priority, then."", 'If it were, it would have been fixed already, right?', "":-)\n\nI'm gonna bump the priority down a bit, as the mobile sites not properly handling SSL isn't that critical, as I read it."", ""It used to be that the mobile site was completely read-only, but maybe that's changed?"", ""I'm not sure what the critical or high priority parts would be here."", ""I think you're really asking for a status update from RT #2541."", ""I'll CC a few a people on this bug who may be able to help with that."", '(In reply to comment #8)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI split this out to bug 40998.']",NA,0,"I'll CC a few a people on this bug who may be able to help with that." +17100,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","On a related note, if you go to .com addresses (like https://en.wikipedia.com/) using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org",1350098036,"PHID-USER-p2ebbrj45wupyi25othr","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","On a related note, if you go to .com addresses (like https://en.wikipedia.com/) using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org","On a related note, if you go to .com addresses (like URL using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-46,"True","['On a related note, if you go to .com addresses (like URL using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key.', 'That is because the .com addresses use the SSL key that is for *.wikipedia.org']",NA,0,"On a related note, if you go to .com addresses (like URL using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key." +17100,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","On a related note, if you go to .com addresses (like https://en.wikipedia.com/) using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org",1350098036,"PHID-USER-p2ebbrj45wupyi25othr","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","On a related note, if you go to .com addresses (like https://en.wikipedia.com/) using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org","On a related note, if you go to .com addresses (like URL using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key. That is because the .com addresses use the SSL key that is for *.wikipedia.org",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-46,"True","['On a related note, if you go to .com addresses (like URL using HTTPS protocol, before you get forwarded to the .org address, you will get an error message regarding the SSL key.', 'That is because the .com addresses use the SSL key that is for *.wikipedia.org']",NA,0,"That is because the .com addresses use the SSL key that is for *.wikipedia.org" +17101,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**headerfuturetree** wrote: + +//**content hidden as private in Bugzilla**//",1348146930,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**headerfuturetree** wrote: + +//**content hidden as private in Bugzilla**//","**headerfuturetree** wrote: + +//**content hidden as private in Bugzilla**//",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-49,"True","['**headerfuturetree** wrote:\n\n//**content hidden as private in Bugzilla**//']",NA,0,"**headerfuturetree** wrote:\n\n//**content hidden as private in Bugzilla**//" +17102,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",1342358249,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.","**lambdav** wrote: + +(In reply to comment #1) +QUOTE + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-59,"True","['**lambdav** wrote:\n\n(In reply to comment #1)\nQUOTE\n\nThis site has private access only.', 'How many years to solve a Critical problem with High priority ?', 'No one is assigned to this bug, and no solution is proposed.']",NA,0,"**lambdav** wrote:\n\n(In reply to comment #1)\nQUOTE\n\nThis site has private access only." +17102,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",1342358249,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.","**lambdav** wrote: + +(In reply to comment #1) +QUOTE + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-59,"True","['**lambdav** wrote:\n\n(In reply to comment #1)\nQUOTE\n\nThis site has private access only.', 'How many years to solve a Critical problem with High priority ?', 'No one is assigned to this bug, and no solution is proposed.']",NA,0,"How many years to solve a Critical problem with High priority ?" +17102,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",1342358249,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**lambdav** wrote: + +(In reply to comment #1) +> RT #2541 + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.","**lambdav** wrote: + +(In reply to comment #1) +QUOTE + +This site has private access only. + +How many years to solve a Critical problem with High priority ? No one is assigned to this bug, and no solution is proposed.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-59,"True","['**lambdav** wrote:\n\n(In reply to comment #1)\nQUOTE\n\nThis site has private access only.', 'How many years to solve a Critical problem with High priority ?', 'No one is assigned to this bug, and no solution is proposed.']",NA,0,"No one is assigned to this bug, and no solution is proposed." +17103,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**lambdav** wrote: + +How many months to resolve a Critical bug with High priority ?",1339593996,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**lambdav** wrote: + +How many months to resolve a Critical bug with High priority ?","**lambdav** wrote: + +How many months to resolve a Critical bug with High priority ?",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-63,"True","['**lambdav** wrote:\n\nHow many months to resolve a Critical bug with High priority ?']",NA,0,"**lambdav** wrote:\n\nHow many months to resolve a Critical bug with High priority ?" +17104,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 37024 has been marked as a duplicate of this bug. ***",1337704981,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 37024 has been marked as a duplicate of this bug. ***","*** Bug 37024 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['*** Bug 37024 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 37024 has been marked as a duplicate of this bug." +17104,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 37024 has been marked as a duplicate of this bug. ***",1337704981,"PHID-USER-aasrweh54ew7py3agvg2","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 37024 has been marked as a duplicate of this bug. ***","*** Bug 37024 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['*** Bug 37024 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +17105,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%",1331835104,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-76,"True","['**pfhayes** wrote:\n\n%%%*** Bug 34833 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"**pfhayes** wrote:\n\n%%%*** Bug 34833 has been marked as a duplicate of this bug." +17105,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%",1331835104,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%","**pfhayes** wrote: + +%%%*** Bug 34833 has been marked as a duplicate of this bug. ***%%%",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-76,"True","['**pfhayes** wrote:\n\n%%%*** Bug 34833 has been marked as a duplicate of this bug.', '***%%%']",NA,0,"***%%%" +17106,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 35096 has been marked as a duplicate of this bug. ***",1331326730,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 35096 has been marked as a duplicate of this bug. ***","*** Bug 35096 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","['*** Bug 35096 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 35096 has been marked as a duplicate of this bug." +17106,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","*** Bug 35096 has been marked as a duplicate of this bug. ***",1331326730,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","*** Bug 35096 has been marked as a duplicate of this bug. ***","*** Bug 35096 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-77,"True","['*** Bug 35096 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +17107,"Non-Wikipedia mobile domains use Wikipedia's SSL certificate","RT #2541",1330523778,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-pumiywpy6qmi7nito5hn","task_subcomment","RT #2541","RT #2541",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-78,"True","['RT #2541']",NA,0,"RT #2541" +17198,"Bad SSL cert at integration.mediawiki.org","Split out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/",1324490280,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_description","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1324564550,NA,"resolved","True","c2",1,"True","False",-88,"True","['Bad SSL cert at integration.mediawiki.org.', 'Split out from bug 29550:\n\n\n integration.mediawiki.org uses an invalid security certificate.', 'The certificate is only valid for the following names:\n *.wikimedia.org , wikimedia.org \n\n(Error code: ssl_error_bad_cert_domain)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"Bad SSL cert at integration.mediawiki.org." +17198,"Bad SSL cert at integration.mediawiki.org","Split out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/",1324490280,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_description","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1324564550,NA,"resolved","True","c2",1,"True","False",-88,"True","['Bad SSL cert at integration.mediawiki.org.', 'Split out from bug 29550:\n\n\n integration.mediawiki.org uses an invalid security certificate.', 'The certificate is only valid for the following names:\n *.wikimedia.org , wikimedia.org \n\n(Error code: ssl_error_bad_cert_domain)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"Split out from bug 29550:\n\n\n integration.mediawiki.org uses an invalid security certificate." +17198,"Bad SSL cert at integration.mediawiki.org","Split out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/",1324490280,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_description","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://integration.mediawiki.org/testswarm/","Bad SSL cert at integration.mediawiki.org./n/nSplit out from bug 29550: + + + integration.mediawiki.org uses an invalid security certificate. + +The certificate is only valid for the following names: + *.wikimedia.org , wikimedia.org + +(Error code: ssl_error_bad_cert_domain) + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1324564550,NA,"resolved","True","c2",1,"True","False",-88,"True","['Bad SSL cert at integration.mediawiki.org.', 'Split out from bug 29550:\n\n\n integration.mediawiki.org uses an invalid security certificate.', 'The certificate is only valid for the following names:\n *.wikimedia.org , wikimedia.org \n\n(Error code: ssl_error_bad_cert_domain)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"The certificate is only valid for the following names:\n *.wikimedia.org , wikimedia.org \n\n(Error code: ssl_error_bad_cert_domain)\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL" +17199,"Bad SSL cert at integration.mediawiki.org","(merging Continuous Integration into Testing Infrastructure)",1325631155,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_subcomment","(merging Continuous Integration into Testing Infrastructure)","(merging Continuous Integration into Testing Infrastructure)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-87,"True","['(merging Continuous Integration into Testing Infrastructure)']",NA,0,"(merging Continuous Integration into Testing Infrastructure)" +17200,"Bad SSL cert at integration.mediawiki.org","And https://gerrit.wikimedia.org/r/1732 which adds SSLCACertificateFile to fix cert verification",1325093594,"PHID-USER-orzyp3dswemhdgdznro5","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_subcomment","And https://gerrit.wikimedia.org/r/1732 which adds SSLCACertificateFile to fix cert verification","And GERRIT_URL which adds SSLCACertificateFile to fix cert verification",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-87,"True","['And GERRIT_URL which adds SSLCACertificateFile to fix cert verification']",NA,0,"And GERRIT_URL which adds SSLCACertificateFile to fix cert verification" +17201,"Bad SSL cert at integration.mediawiki.org","Change deployed.",1324564550,"PHID-USER-orzyp3dswemhdgdznro5","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_subcomment","Change deployed.","Change deployed.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Change deployed.']",NA,0,"Change deployed." +17202,"Bad SSL cert at integration.mediawiki.org","Well spotted! +Ops change is https://gerrit.wikimedia.org/r/1669 , pending review, merge ...",1324492963,"PHID-USER-orzyp3dswemhdgdznro5","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_subcomment","Well spotted! +Ops change is https://gerrit.wikimedia.org/r/1669 , pending review, merge ...","Well spotted! +Ops change is GERRIT_URL , pending review, merge ...",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Well spotted!', 'Ops change is GERRIT_URL , pending review, merge ...']",NA,0,"Well spotted!" +17202,"Bad SSL cert at integration.mediawiki.org","Well spotted! +Ops change is https://gerrit.wikimedia.org/r/1669 , pending review, merge ...",1324492963,"PHID-USER-orzyp3dswemhdgdznro5","PHID-TASK-o7qu5nvtew2u5is7oyl5","task_subcomment","Well spotted! +Ops change is https://gerrit.wikimedia.org/r/1669 , pending review, merge ...","Well spotted! +Ops change is GERRIT_URL , pending review, merge ...",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Well spotted!', 'Ops change is GERRIT_URL , pending review, merge ...']",NA,0,"Ops change is GERRIT_URL , pending review, merge ..." +17246,"Link to switch to http/https version of current page","It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1322506800,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_description","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1325052259,NA,"resolved","True","c2",1,"False","False",-92,"True","['Link to switch to http/https version of current page.', 'It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around.', 'E.g.', 'a footer link like the one we have for going to the page on the mobile site.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Link to switch to http/https version of current page." +17246,"Link to switch to http/https version of current page","It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1322506800,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_description","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1325052259,NA,"resolved","True","c2",1,"False","False",-92,"True","['Link to switch to http/https version of current page.', 'It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around.', 'E.g.', 'a footer link like the one we have for going to the page on the mobile site.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around." +17246,"Link to switch to http/https version of current page","It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1322506800,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_description","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1325052259,NA,"resolved","True","c2",1,"False","False",-92,"True","['Link to switch to http/https version of current page.', 'It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around.', 'E.g.', 'a footer link like the one we have for going to the page on the mobile site.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"E.g." +17246,"Link to switch to http/https version of current page","It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1322506800,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_description","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1325052259,NA,"resolved","True","c2",1,"False","False",-92,"True","['Link to switch to http/https version of current page.', 'It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around.', 'E.g.', 'a footer link like the one we have for going to the page on the mobile site.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"a footer link like the one we have for going to the page on the mobile site." +17246,"Link to switch to http/https version of current page","It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1322506800,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_description","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Link to switch to http/https version of current page./n/nIt would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around. E.g. a footer link like the one we have for going to the page on the mobile site. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1325052259,NA,"resolved","True","c2",1,"False","False",-92,"True","['Link to switch to http/https version of current page.', 'It would be nice if there was an easy way to go from http to the same page on the secure site, and the other way around.', 'E.g.', 'a footer link like the one we have for going to the page on the mobile site.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +17247,"Link to switch to http/https version of current page","I'd internatiolaise the http/https as secure/insecure instead of showing the raw protocols in the message.",1325460348,"PHID-USER-izojihzr4ja3jsgzn5wv","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","I'd internatiolaise the http/https as secure/insecure instead of showing the raw protocols in the message.","I'd internatiolaise the http/https as secure/insecure instead of showing the raw protocols in the message.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-87,"True","[""I'd internatiolaise the http/https as secure/insecure instead of showing the raw protocols in the message.""]",NA,0,"I'd internatiolaise the http/https as secure/insecure instead of showing the raw protocols in the message." +17248,"Link to switch to http/https version of current page","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",1325052259,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)","(In reply to comment #2) +QUOTE + +I understand.. I don't know much javascript but this was simple enough to make myself :) URL + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-87,"True","['(In reply to comment #2)\nQUOTE\n\nI understand..', ""I don't know much javascript but this was simple enough to make myself :) URL\n\nI will still have to wait for the shared gadget repository to be able to use it easily on all wikis."", ""(Marking as fixed, as I'm happy now :p.)""]",NA,0,"(In reply to comment #2)\nQUOTE\n\nI understand.." +17248,"Link to switch to http/https version of current page","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",1325052259,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)","(In reply to comment #2) +QUOTE + +I understand.. I don't know much javascript but this was simple enough to make myself :) URL + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-87,"True","['(In reply to comment #2)\nQUOTE\n\nI understand..', ""I don't know much javascript but this was simple enough to make myself :) URL\n\nI will still have to wait for the shared gadget repository to be able to use it easily on all wikis."", ""(Marking as fixed, as I'm happy now :p.)""]",NA,0,"I don't know much javascript but this was simple enough to make myself :) URL\n\nI will still have to wait for the shared gadget repository to be able to use it easily on all wikis." +17248,"Link to switch to http/https version of current page","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",1325052259,"PHID-USER-th6xijvyee7wqsk7bc67","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","(In reply to comment #2) +> That would completely ruin caching, unless implemented as a gadget. + +I understand.. I don't know much javascript but this was simple enough to make myself :) https://incubator.wikimedia.org/wiki/MediaWiki:Gadget-otherProtocol.js + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)","(In reply to comment #2) +QUOTE + +I understand.. I don't know much javascript but this was simple enough to make myself :) URL + +I will still have to wait for the shared gadget repository to be able to use it easily on all wikis. + +(Marking as fixed, as I'm happy now :p.)",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-87,"True","['(In reply to comment #2)\nQUOTE\n\nI understand..', ""I don't know much javascript but this was simple enough to make myself :) URL\n\nI will still have to wait for the shared gadget repository to be able to use it easily on all wikis."", ""(Marking as fixed, as I'm happy now :p.)""]",NA,0,"(Marking as fixed, as I'm happy now :p.)" +17249,"Link to switch to http/https version of current page","That's trivial to add. I had never seen that mobile link, btw.",1322604406,"PHID-USER-izojihzr4ja3jsgzn5wv","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","That's trivial to add. I had never seen that mobile link, btw.","That's trivial to add. I had never seen that mobile link, btw.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","[""That's trivial to add."", 'I had never seen that mobile link, btw.']",NA,0,"I had never seen that mobile link, btw." +17249,"Link to switch to http/https version of current page","That's trivial to add. I had never seen that mobile link, btw.",1322604406,"PHID-USER-izojihzr4ja3jsgzn5wv","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","That's trivial to add. I had never seen that mobile link, btw.","That's trivial to add. I had never seen that mobile link, btw.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","[""That's trivial to add."", 'I had never seen that mobile link, btw.']",NA,0,"That's trivial to add." +17250,"Link to switch to http/https version of current page","**john** wrote: + +That would completely ruin caching, unless implemented as a gadget.",1322604325,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","**john** wrote: + +That would completely ruin caching, unless implemented as a gadget.","**john** wrote: + +That would completely ruin caching, unless implemented as a gadget.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**john** wrote:\n\nThat would completely ruin caching, unless implemented as a gadget.']",NA,0,"**john** wrote:\n\nThat would completely ruin caching, unless implemented as a gadget." +17251,"Link to switch to http/https version of current page","'Switch to secure site' 'Switch to OMG ALL YOUR COOKIES BELONG TO ME site' :P :)",1322604301,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-hfdhnp2k7kcjo2mblxaz","task_subcomment","'Switch to secure site' 'Switch to OMG ALL YOUR COOKIES BELONG TO ME site' :P :)","'Switch to secure site' 'Switch to OMG ALL YOUR COOKIES BELONG TO ME site' :P :)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-92,"True","[""'Switch to secure site' 'Switch to OMG ALL YOUR COOKIES BELONG TO ME site' :P :)""]",NA,0,"'Switch to secure site' 'Switch to OMG ALL YOUR COOKIES BELONG TO ME site' :P :)" +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"upload.wikimedia.org provides wrong certificate via IPv6." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"See below." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Key encipherment." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Key Purpose (not critical):\n TLS WWW Server." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"TLS WWW Client." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Please let me know If you need any additional information." +17310,"upload.wikimedia.org provides wrong certificate via IPv6","**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1318956120,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_description","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** `maxi` + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: http://rapidssl-crl.geotrust.com/crls/rapidssl.crl + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-http://rapidssl-aia.geotrust.com/rapidssl.crt + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","upload.wikimedia.org provides wrong certificate via IPv6./n/n**Author:** CODE + +**Description:** +When connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown. + +The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org. See below. + + - Certificate[0] info: + - X.509 Certificate Information: + Version: 3 + Serial Number (hex): 027a5f + Issuer: C=US,O=GeoTrust\, Inc.,CN=RapidSSL CA + Validity: + Not Before: Mon Jul 18 07:19:38 UTC 2011 + Not After: Tue Jul 19 16:14:20 UTC 2016 + Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org + Subject Public Key Algorithm: RSA + Certificate Security Level: Low + Modulus (bits 2048): + 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55 + ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae + fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a + 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9 + 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79 + 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18 + 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58 + 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82 + fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df + 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16 + 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70 + 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e + 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d + 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d + cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd + 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa + bb + Exponent (bits 24): + 01:00:01 + Extensions: + Authority Key Identifier (not critical): + 6b693d6a18424add8f026539fd35248678911630 + Key Usage (critical): + Digital signature. + Key encipherment. + Key Purpose (not critical): + TLS WWW Server. + TLS WWW Client. + Subject Alternative Name (not critical): + DNSname: *.wikimediafoundation.org + DNSname: wikimediafoundation.org + CRL Distribution points (not critical): + URI: URL + Subject Key Identifier (not critical): + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + Basic Constraints (critical): + Certificate Authority (CA): FALSE + Unknown extension 1.3.6.1.5.5.7.1.1 (not critical): + ASCII: 0;09..+.....0..-URL + Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274 + Signature Algorithm: RSA-SHA1 + Signature: + 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c + 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c + 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d + d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82 + 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad + 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8 + e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10 + 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec + a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3 + f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2 + 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee + 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41 + ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62 + e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d + e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79 + 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89 +Other Information: + MD5 fingerprint: + 272480c41a073648db7fedd9066e96be + SHA-1 fingerprint: + 70616f43e39edd64c5aedaa3f79372e654d0e30c + Public Key Id: + 16f250574f6b2250a9caa67c53a7b59b9eefbc5c + + +-----BEGIN CERTIFICATE----- +MIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT +MRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew +HhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44 +NERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD +VQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0 +NzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz +IChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp +ZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw +DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8 +DXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY +i0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi +ugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX +sPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg +bAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA +AaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud +DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R +BDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh +dGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n +ZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ +qcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG +AQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz +bC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix +kSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW +WjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC +/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz +BHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI +boWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok= +-----END CERTIFICATE----- + +$ host upload.wikimedia.org +upload.wikimedia.org is an alias for upload.esams.wikimedia.org. +upload.esams.wikimedia.org has address 91.198.174.234 +upload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2 + + +When using the IPv4 address a valid certificate is provided. + +This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https. + +Please let me know If you need any additional information. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Medium",50,1337009170,NA,"resolved","True","c2",1,"False","False",-98,"True","['upload.wikimedia.org provides wrong certificate via IPv6.', '**Author:** CODE\n\n**Description:**\nWhen connectiong via IPv6 to upload.wikimedia.org a wrong certificate is shown.', 'The certificate is issued for ""*.wikimediafoundation.org"" and ""wikimediafoundation.org"" which does not match upload.wikimedia.org.', 'See below.', '- Certificate[0] info:\n - X.509 Certificate Information:\n Version: 3\n Serial Number (hex): 027a5f\n Issuer: C=US,O=GeoTrust\\, Inc.,CN=RapidSSL CA\n Validity:\n Not Before: Mon Jul 18 07:19:38 UTC 2011\n Not After: Tue Jul 19 16:14:20 UTC 2016\n Subject: serialNumber=DN84DBlZKsoLji7PlLHE4Pyj6ARQXJ-L,C=US,O=*.wikimediafoundation.org,OU=GT55614722,OU=See www.rapidssl.com/resources/cps (c)11,OU=Domain Control Validated - RapidSSL(R),CN=*.wikimediafoundation.org\n Subject Public Key Algorithm: RSA\n Certificate Security Level: Low\n Modulus (bits 2048):\n 00:c3:79:a7:e0:cc:5f:7b:cc:10:5b:d2:eb:88:0d:55\n ee:66:da:63:7c:0d:73:19:e8:04:85:95:d1:7f:b1:ae\n fa:92:60:c8:8c:79:99:72:5b:c6:42:72:80:b9:b5:9a\n 11:6a:43:0f:d1:f3:c7:87:84:79:5d:56:56:b5:97:f9\n 2e:39:5a:61:18:8b:4f:83:56:94:38:30:44:a9:43:79\n 1f:ed:3f:36:ef:33:61:21:ca:fa:e3:90:3e:c9:52:18\n 6e:c5:3d:24:19:52:a7:90:ed:75:7a:b4:6f:40:e5:58\n 57:75:75:54:a2:ba:07:5c:26:57:66:7c:d4:46:f3:82\n fe:c9:29:be:86:be:3c:a2:d7:e4:6e:5a:3a:fe:77:df\n 76:85:97:79:08:00:6b:66:fd:be:fd:1d:e5:f5:36:16\n 7c:92:a3:12:17:b0:f5:72:9a:7a:6b:e4:d8:31:42:70\n 3e:84:b4:8c:ae:69:c2:29:34:b1:89:c7:60:85:f4:2e\n 33:8a:1a:4a:50:26:dd:4d:7b:34:71:85:02:1e:6f:1d\n 8f:f1:db:b2:e0:6c:05:a5:b0:98:c1:74:39:2d:04:9d\n cb:51:80:36:d9:e8:bb:3f:76:27:01:c9:65:f4:d5:dd\n 04:fe:1e:f7:0e:c2:c4:59:84:c8:b1:04:71:c8:f6:aa\n bb\n Exponent (bits 24):\n 01:00:01\n Extensions:\n Authority Key Identifier (not critical):\n 6b693d6a18424add8f026539fd35248678911630\n Key Usage (critical):\n Digital signature.', 'Key encipherment.', 'Key Purpose (not critical):\n TLS WWW Server.', 'TLS WWW Client.', 'Subject Alternative Name (not critical):\n DNSname: *.wikimediafoundation.org\n DNSname: wikimediafoundation.org\n CRL Distribution points (not critical):\n URI: URL\n Subject Key Identifier (not critical):\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n Basic Constraints (critical):\n Certificate Authority (CA): FALSE\n Unknown extension 1.3.6.1.5.5.7.1.1 (not critical):\n ASCII: 0;09..+.....0..-URL\n Hexdump: 303b303906082b06010505073002862d687474703a2f2f726170696473736c2d6169612e67656f74727573742e636f6d2f726170696473736c2e637274\n Signature Algorithm: RSA-SHA1\n Signature:\n 84:98:5c:64:9a:f1:09:05:31:5c:3f:89:56:41:a4:4c\n 02:3d:8c:87:db:d2:31:91:21:1b:4a:f8:a7:83:5d:2c\n 8d:90:63:ff:02:b5:7e:57:9e:42:22:63:23:cb:36:6d\n d8:a5:46:a2:97:68:97:ee:b9:ce:29:b4:89:bd:13:82\n 01:c3:d2:eb:81:07:16:5a:38:18:97:fe:05:22:e0:ad\n 7b:b1:c8:2a:8c:47:e8:60:cc:63:ae:61:2d:5f:45:a8\n e1:b6:eb:d2:8d:03:a1:84:0e:74:1c:af:75:f8:ab:10\n 09:85:31:c0:58:16:82:fd:ca:eb:4e:7c:79:4c:cb:ec\n a7:39:70:96:ce:f5:fb:56:14:5b:c6:20:f7:8b:63:b3\n f7:90:84:2f:dd:bb:99:54:86:cf:e6:38:b4:e1:f9:a2\n 85:61:05:0f:6f:51:73:04:76:60:a6:b5:c9:4d:18:ee\n 27:17:6a:a7:cb:d9:c4:3d:a3:8d:7e:74:5a:1d:25:41\n ad:9e:ea:41:03:d1:c3:0f:a1:62:ed:76:04:cd:1e:62\n e6:0c:77:c7:34:e4:48:6e:85:83:e1:a0:c4:62:ab:5d\n e4:21:7d:89:d8:0c:d4:e2:8f:79:86:a4:4b:09:01:79\n 05:64:5c:e3:ab:2c:85:1e:b1:be:fb:93:c1:ec:42:89\nOther Information:\n MD5 fingerprint:\n 272480c41a073648db7fedd9066e96be\n SHA-1 fingerprint:\n 70616f43e39edd64c5aedaa3f79372e654d0e30c\n Public Key Id:\n 16f250574f6b2250a9caa67c53a7b59b9eefbc5c\n\n\n-----BEGIN CERTIFICATE-----\nMIIFBTCCA+2gAwIBAgIDAnpfMA0GCSqGSIb3DQEBBQUAMDwxCzAJBgNVBAYTAlVT\nMRcwFQYDVQQKEw5HZW9UcnVzdCwgSW5jLjEUMBIGA1UEAxMLUmFwaWRTU0wgQ0Ew\nHhcNMTEwNzE4MDcxOTM4WhcNMTYwNzE5MTYxNDIwWjCB+TEpMCcGA1UEBRMgRE44\nNERCbFpLc29Mamk3UGxMSEU0UHlqNkFSUVhKLUwxCzAJBgNVBAYTAlVTMSIwIAYD\nVQQKDBkqLndpa2ltZWRpYWZvdW5kYXRpb24ub3JnMRMwEQYDVQQLEwpHVDU1NjE0\nNzIyMTEwLwYDVQQLEyhTZWUgd3d3LnJhcGlkc3NsLmNvbS9yZXNvdXJjZXMvY3Bz\nIChjKTExMS8wLQYDVQQLEyZEb21haW4gQ29udHJvbCBWYWxpZGF0ZWQgLSBSYXBp\nZFNTTChSKTEiMCAGA1UEAwwZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZzCCASIw\nDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMN5p+DMX3vMEFvS64gNVe5m2mN8\nDXMZ6ASFldF/sa76kmDIjHmZclvGQnKAubWaEWpDD9Hzx4eEeV1WVrWX+S45WmEY\ni0+DVpQ4MESpQ3kf7T827zNhIcr645A+yVIYbsU9JBlSp5DtdXq0b0DlWFd1dVSi\nugdcJldmfNRG84L+ySm+hr48otfkblo6/nffdoWXeQgAa2b9vv0d5fU2FnySoxIX\nsPVymnpr5NgxQnA+hLSMrmnCKTSxicdghfQuM4oaSlAm3U17NHGFAh5vHY/x27Lg\nbAWlsJjBdDktBJ3LUYA22ei7P3YnAcll9NXdBP4e9w7CxFmEyLEEccj2qrsCAwEA\nAaOCAVAwggFMMB8GA1UdIwQYMBaAFGtpPWoYQkrdjwJlOf01JIZ4kRYwMA4GA1Ud\nDwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwPQYDVR0R\nBDYwNIIZKi53aWtpbWVkaWFmb3VuZGF0aW9uLm9yZ4IXd2lraW1lZGlhZm91bmRh\ndGlvbi5vcmcwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL3JhcGlkc3NsLWNybC5n\nZW90cnVzdC5jb20vY3Jscy9yYXBpZHNzbC5jcmwwHQYDVR0OBBYEFBbyUFdPayJQ\nqcqmfFOntZue77xcMAwGA1UdEwEB/wQCMAAwSQYIKwYBBQUHAQEEPTA7MDkGCCsG\nAQUFBzAChi1odHRwOi8vcmFwaWRzc2wtYWlhLmdlb3RydXN0LmNvbS9yYXBpZHNz\nbC5jcnQwDQYJKoZIhvcNAQEFBQADggEBAISYXGSa8QkFMVw/iVZBpEwCPYyH29Ix\nkSEbSving10sjZBj/wK1fleeQiJjI8s2bdilRqKXaJfuuc4ptIm9E4IBw9LrgQcW\nWjgYl/4FIuCte7HIKoxH6GDMY65hLV9FqOG269KNA6GEDnQcr3X4qxAJhTHAWBaC\n/crrTnx5TMvspzlwls71+1YUW8Yg94tjs/eQhC/du5lUhs/mOLTh+aKFYQUPb1Fz\nBHZgprXJTRjuJxdqp8vZxD2jjX50Wh0lQa2e6kED0cMPoWLtdgTNHmLmDHfHNORI\nboWD4aDEYqtd5CF9idgM1OKPeYakSwkBeQVkXOOrLIUesb77k8HsQok=\n-----END CERTIFICATE-----\n\n$ host upload.wikimedia.org\nupload.wikimedia.org is an alias for upload.esams.wikimedia.org.', 'upload.esams.wikimedia.org has address 91.198.174.234\nupload.esams.wikimedia.org has IPv6 address 2620:0:862:1::80:2\n\n\nWhen using the IPv4 address a valid certificate is provided.', 'This is especially annoying because I get certificate warnings every time I vistit a wikipedia page via https.', 'Please let me know If you need any additional information.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +17311,"upload.wikimedia.org provides wrong certificate via IPv6","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v https://upload.wikimedia.org/ +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.",1337009170,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_subcomment","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v https://upload.wikimedia.org/ +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v URL +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-68,"True","['Seems resolved now, maybe in the overall SSL deployment?', '$ curl -v URL\n* About to connect() to upload.wikimedia.org port 443 (#0)\n* Trying 2620:0:862:1::80:2...\n* connected\n* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0)\n* successfully set certificate verify locations:\n* CAfile: none\n CApath: /etc/ssl/certs\n* SSLv3, TLS handshake, Client hello (1):\n* SSLv3, TLS handshake, Server hello (2):\n* SSLv3, TLS handshake, CERT (11):\n* SSLv3, TLS handshake, Server finished (14):\n* SSLv3, TLS handshake, Client key exchange (16):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSL connection using RC4-SHA\n* Server certificate:\n* \t subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org\n* \t start date: 2010-08-03 15:43:56 GMT\n* \t expire date: 2015-08-22 22:23:10 GMT\n* \t subjectAltName: upload.wikimedia.org matched\n* \t issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority\n* \t SSL certificate verify ok.']",NA,0,"Seems resolved now, maybe in the overall SSL deployment?" +17311,"upload.wikimedia.org provides wrong certificate via IPv6","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v https://upload.wikimedia.org/ +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.",1337009170,"PHID-USER-zjzhrhmn36icnzbckqy4","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_subcomment","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v https://upload.wikimedia.org/ +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.","Seems resolved now, maybe in the overall SSL deployment? + +$ curl -v URL +* About to connect() to upload.wikimedia.org port 443 (#0) +* Trying 2620:0:862:1::80:2... +* connected +* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0) +* successfully set certificate verify locations: +* CAfile: none + CApath: /etc/ssl/certs +* SSLv3, TLS handshake, Client hello (1): +* SSLv3, TLS handshake, Server hello (2): +* SSLv3, TLS handshake, CERT (11): +* SSLv3, TLS handshake, Server finished (14): +* SSLv3, TLS handshake, Client key exchange (16): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSLv3, TLS change cipher, Client hello (1): +* SSLv3, TLS handshake, Finished (20): +* SSL connection using RC4-SHA +* Server certificate: +* subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org +* start date: 2010-08-03 15:43:56 GMT +* expire date: 2015-08-22 22:23:10 GMT +* subjectAltName: upload.wikimedia.org matched +* issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority +* SSL certificate verify ok.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-68,"True","['Seems resolved now, maybe in the overall SSL deployment?', '$ curl -v URL\n* About to connect() to upload.wikimedia.org port 443 (#0)\n* Trying 2620:0:862:1::80:2...\n* connected\n* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0)\n* successfully set certificate verify locations:\n* CAfile: none\n CApath: /etc/ssl/certs\n* SSLv3, TLS handshake, Client hello (1):\n* SSLv3, TLS handshake, Server hello (2):\n* SSLv3, TLS handshake, CERT (11):\n* SSLv3, TLS handshake, Server finished (14):\n* SSLv3, TLS handshake, Client key exchange (16):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSL connection using RC4-SHA\n* Server certificate:\n* \t subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org\n* \t start date: 2010-08-03 15:43:56 GMT\n* \t expire date: 2015-08-22 22:23:10 GMT\n* \t subjectAltName: upload.wikimedia.org matched\n* \t issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority\n* \t SSL certificate verify ok.']",NA,0,"$ curl -v URL\n* About to connect() to upload.wikimedia.org port 443 (#0)\n* Trying 2620:0:862:1::80:2...\n* connected\n* Connected to upload.wikimedia.org (2620:0:862:1::80:2) port 443 (#0)\n* successfully set certificate verify locations:\n* CAfile: none\n CApath: /etc/ssl/certs\n* SSLv3, TLS handshake, Client hello (1):\n* SSLv3, TLS handshake, Server hello (2):\n* SSLv3, TLS handshake, CERT (11):\n* SSLv3, TLS handshake, Server finished (14):\n* SSLv3, TLS handshake, Client key exchange (16):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSLv3, TLS change cipher, Client hello (1):\n* SSLv3, TLS handshake, Finished (20):\n* SSL connection using RC4-SHA\n* Server certificate:\n* \t subject: serialNumber=3Te2KNVS3beWLBffkE0QtVQ4qxo3Ix10; C=US; O=*.wikimedia.org; OU=GT11518520; OU=See www.rapidssl.com/resources/cps (c)10; OU=Domain Control Validated - RapidSSL(R); CN=*.wikimedia.org\n* \t start date: 2010-08-03 15:43:56 GMT\n* \t expire date: 2015-08-22 22:23:10 GMT\n* \t subjectAltName: upload.wikimedia.org matched\n* \t issuer: C=US; O=Equifax; OU=Equifax Secure Certificate Authority\n* \t SSL certificate verify ok." +17312,"upload.wikimedia.org provides wrong certificate via IPv6","Filed in ops' internal RT tracker: http://rt.wikimedia.org/Ticket/Display.html?id=1763",1319049349,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-nqrcuemrhcsndbfnb7tv","task_subcomment","Filed in ops' internal RT tracker: http://rt.wikimedia.org/Ticket/Display.html?id=1763","Filed in ops' internal RT tracker: URL",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-97,"True","[""Filed in ops' internal RT tracker: URL""]",NA,0,"Filed in ops' internal RT tracker: URL" +17339,"Android app should support (or always?) use HTTPS","Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal",1318005300,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_description","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Medium",50,1324975021,NA,"resolved","True","c2",1,"True","False",-99,"True","['Android app should support (or always?)', 'use HTTPS.', 'Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.', ""Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue."", ':)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal']",TRUE,1,"Android app should support (or always?)" +17339,"Android app should support (or always?) use HTTPS","Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal",1318005300,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_description","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Medium",50,1324975021,NA,"resolved","True","c2",1,"True","False",-99,"True","['Android app should support (or always?)', 'use HTTPS.', 'Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.', ""Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue."", ':)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal']",TRUE,1,"use HTTPS." +17339,"Android app should support (or always?) use HTTPS","Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal",1318005300,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_description","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Medium",50,1324975021,NA,"resolved","True","c2",1,"True","False",-99,"True","['Android app should support (or always?)', 'use HTTPS.', 'Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.', ""Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue."", ':)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal']",TRUE,1,"Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL." +17339,"Android app should support (or always?) use HTTPS","Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal",1318005300,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_description","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Medium",50,1324975021,NA,"resolved","True","c2",1,"True","False",-99,"True","['Android app should support (or always?)', 'use HTTPS.', 'Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.', ""Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue."", ':)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal']",TRUE,1,":)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal" +17339,"Android app should support (or always?) use HTTPS","Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal",1318005300,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_description","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Android app should support (or always?) use HTTPS./n/nBefore any authentication-based features are added, should definitely make sure it can do all its network access over SSL. + +Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue. :) + +-------------------------- +**Version**: 1.0.0 (Android) +**Severity**: normal","Medium",50,1324975021,NA,"resolved","True","c2",1,"True","False",-99,"True","['Android app should support (or always?)', 'use HTTPS.', 'Before any authentication-based features are added, should definitely make sure it can do all its network access over SSL.', ""Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue."", ':)\n\n--------------------------\n**Version**: 1.0.0 (Android)\n**Severity**: normal']",TRUE,1,"Currently the mobile frontend on the m. domains don't offer SSL directly (bug 31333 etc) which might be an issue." +17340,"Android app should support (or always?) use HTTPS","fixed in https://github.com/wikimedia/WikipediaMobile/commit/6ff4f8b1f834e5a08944893c4abb3a3d19c5cd8d",1324975021,"PHID-USER-2nnm76h4ykalvvref2ye","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","fixed in https://github.com/wikimedia/WikipediaMobile/commit/6ff4f8b1f834e5a08944893c4abb3a3d19c5cd8d","fixed in URL",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['fixed in URL']",NA,1,"fixed in URL" +17341,"Android app should support (or always?) use HTTPS","Why? In what cases would someone want to use HTTP?",1324676767,"PHID-USER-2nnm76h4ykalvvref2ye","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","Why? In what cases would someone want to use HTTP?","Why? In what cases would someone want to use HTTP?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Why?', 'In what cases would someone want to use HTTP?']",NA,1,"Why?" +17341,"Android app should support (or always?) use HTTPS","Why? In what cases would someone want to use HTTP?",1324676767,"PHID-USER-2nnm76h4ykalvvref2ye","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","Why? In what cases would someone want to use HTTP?","Why? In what cases would someone want to use HTTP?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Why?', 'In what cases would someone want to use HTTP?']",NA,1,"In what cases would someone want to use HTTP?" +17342,"Android app should support (or always?) use HTTPS","Lets make it a configurable option",1324676725,"PHID-USER-qmantxp3p7omhisp3qgq","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","Lets make it a configurable option","Lets make it a configurable option",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-88,"True","['Lets make it a configurable option']",NA,1,"Lets make it a configurable option" +17343,"Android app should support (or always?) use HTTPS","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?",1324607901,"PHID-USER-2nnm76h4ykalvvref2ye","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Should we just go ahead do this for 1.0?', 'Just a URL change, or are there other potential issues?']",NA,1,"Should we just go ahead do this for 1.0?" +17343,"Android app should support (or always?) use HTTPS","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?",1324607901,"PHID-USER-2nnm76h4ykalvvref2ye","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?","Should we just go ahead do this for 1.0? Just a URL change, or are there other potential issues?",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-88,"True","['Should we just go ahead do this for 1.0?', 'Just a URL change, or are there other potential issues?']",NA,1,"Just a URL change, or are there other potential issues?" +17344,"Android app should support (or always?) use HTTPS","It hasn't, but I think since the site now supports it we could do this now.",1323998944,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","It hasn't, but I think since the site now supports it we could do this now.","It hasn't, but I think since the site now supports it we could do this now.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-89,"True","[""It hasn't, but I think since the site now supports it we could do this now.""]",NA,1,"It hasn't, but I think since the site now supports it we could do this now." +17345,"Android app should support (or always?) use HTTPS","**philinje** wrote: + +I believe this has been fixed.",1323997468,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-a4kn3ma5ui4rlecdfbvr","task_subcomment","**philinje** wrote: + +I believe this has been fixed.","**philinje** wrote: + +I believe this has been fixed.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-89,"True","['**philinje** wrote:\n\nI believe this has been fixed.']",NA,1,"**philinje** wrote:\n\nI believe this has been fixed." +17397,"Create Special:Login as a redirect to Special:UserLogin","Special:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1338110400,"PHID-USER-eob3rbz3vybcgnjfvmbn","PHID-TASK-5oxi4h646gofncgguima","task_description","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1373289760,NA,"resolved","True","c2",1,"False","False",-66,"True","['Create Special:Login as a redirect to Special:UserLogin.', 'Special:Login is more intuitive than Special:UserLogin.', ""I suppose there's no reason to move the current one, but could Special:Login be created as a redirect?"", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,0,"Create Special:Login as a redirect to Special:UserLogin." +17397,"Create Special:Login as a redirect to Special:UserLogin","Special:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1338110400,"PHID-USER-eob3rbz3vybcgnjfvmbn","PHID-TASK-5oxi4h646gofncgguima","task_description","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1373289760,NA,"resolved","True","c2",1,"False","False",-66,"True","['Create Special:Login as a redirect to Special:UserLogin.', 'Special:Login is more intuitive than Special:UserLogin.', ""I suppose there's no reason to move the current one, but could Special:Login be created as a redirect?"", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,0,"Special:Login is more intuitive than Special:UserLogin." +17397,"Create Special:Login as a redirect to Special:UserLogin","Special:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1338110400,"PHID-USER-eob3rbz3vybcgnjfvmbn","PHID-TASK-5oxi4h646gofncgguima","task_description","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1373289760,NA,"resolved","True","c2",1,"False","False",-66,"True","['Create Special:Login as a redirect to Special:UserLogin.', 'Special:Login is more intuitive than Special:UserLogin.', ""I suppose there's no reason to move the current one, but could Special:Login be created as a redirect?"", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +17397,"Create Special:Login as a redirect to Special:UserLogin","Special:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1338110400,"PHID-USER-eob3rbz3vybcgnjfvmbn","PHID-TASK-5oxi4h646gofncgguima","task_description","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Create Special:Login as a redirect to Special:UserLogin./n/nSpecial:Login is more intuitive than Special:UserLogin. I suppose there's no reason to move the current one, but could Special:Login be created as a redirect? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,1373289760,NA,"resolved","True","c2",1,"False","False",-66,"True","['Create Special:Login as a redirect to Special:UserLogin.', 'Special:Login is more intuitive than Special:UserLogin.', ""I suppose there's no reason to move the current one, but could Special:Login be created as a redirect?"", '--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",TRUE,0,"I suppose there's no reason to move the current one, but could Special:Login be created as a redirect?" +17398,"Create Special:Login as a redirect to Special:UserLogin","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +https://gerrit.wikimedia.org/r/52749",1373289816,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +https://gerrit.wikimedia.org/r/52749","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-8,"True","['Change 52749 merged by jenkins-bot:\nAdd Special:Login and Special:Logout as aliases.', 'GERRIT_URL']",NA,0,"Change 52749 merged by jenkins-bot:\nAdd Special:Login and Special:Logout as aliases." +17398,"Create Special:Login as a redirect to Special:UserLogin","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +https://gerrit.wikimedia.org/r/52749",1373289816,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +https://gerrit.wikimedia.org/r/52749","Change 52749 merged by jenkins-bot: +Add Special:Login and Special:Logout as aliases. + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-8,"True","['Change 52749 merged by jenkins-bot:\nAdd Special:Login and Special:Logout as aliases.', 'GERRIT_URL']",NA,0,"GERRIT_URL" +17399,"Create Special:Login as a redirect to Special:UserLogin","Merged.",1373289760,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Merged.","Merged.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-8,"True","['Merged.']",NA,0,"Merged." +17400,"Create Special:Login as a redirect to Special:UserLogin","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749",1362709229,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: GERRIT_URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['Done.', 'I made Special:Login and Special:Logout aliases, with the current titles remaining canonical.', 'Pending review: GERRIT_URL']",NA,0,"Done." +17400,"Create Special:Login as a redirect to Special:UserLogin","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749",1362709229,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: GERRIT_URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['Done.', 'I made Special:Login and Special:Logout aliases, with the current titles remaining canonical.', 'Pending review: GERRIT_URL']",NA,0,"I made Special:Login and Special:Logout aliases, with the current titles remaining canonical." +17400,"Create Special:Login as a redirect to Special:UserLogin","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749",1362709229,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: https://gerrit.wikimedia.org/r/52749","Done. I made Special:Login and Special:Logout aliases, with the current titles remaining canonical. + +Pending review: GERRIT_URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-25,"True","['Done.', 'I made Special:Login and Special:Logout aliases, with the current titles remaining canonical.', 'Pending review: GERRIT_URL']",NA,0,"Pending review: GERRIT_URL" +17401,"Create Special:Login as a redirect to Special:UserLogin","It is called ""alias"" (or special page alias) in mediawiki and it is maintenance in the language file.",1339113658,"PHID-USER-a6jwrurphpx6yl4coupk","PHID-TASK-5oxi4h646gofncgguima","task_subcomment","It is called ""alias"" (or special page alias) in mediawiki and it is maintenance in the language file.","It is called ""alias"" (or special page alias) in mediawiki and it is maintenance in the language file.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-64,"True","['It is called ""alias"" (or special page alias) in mediawiki and it is maintenance in the language file.']",NA,0,"It is called ""alias"" (or special page alias) in mediawiki and it is maintenance in the language file." +17402,"Change Meta (fav)icon on Special:Userlogin","Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial",1337464080,"PHID-USER-xqqqgn2dels45flxw5kb","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_description","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Low",25,1341590161,NA,"resolved","True","c2",1,"True","False",-67,"True","['Change Meta (fav)icon on Special:Userlogin.', 'Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial']",TRUE,0,"Change Meta (fav)icon on Special:Userlogin." +17402,"Change Meta (fav)icon on Special:Userlogin","Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial",1337464080,"PHID-USER-xqqqgn2dels45flxw5kb","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_description","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Low",25,1341590161,NA,"resolved","True","c2",1,"True","False",-67,"True","['Change Meta (fav)icon on Special:Userlogin.', 'Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial']",TRUE,0,"Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo." +17402,"Change Meta (fav)icon on Special:Userlogin","Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial",1337464080,"PHID-USER-xqqqgn2dels45flxw5kb","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_description","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Change Meta (fav)icon on Special:Userlogin./n/nChange Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo. + +-------------------------- +**Version**: unspecified +**Severity**: trivial","Low",25,1341590161,NA,"resolved","True","c2",1,"True","False",-67,"True","['Change Meta (fav)icon on Special:Userlogin.', 'Change Meta (fav)icon on Special:Userlogin (after form submit) from Wikimedia to the Community logo.', '--------------------------\n**Version**: unspecified\n**Severity**: trivial']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: trivial" +17403,"Change Meta (fav)icon on Special:Userlogin","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",1341590161,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-60,"True","[""'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done."", 'Delta compression using up to 2 threads.', 'Compressing objects: 100% (8/8), done.', 'Writing objects: 100% (9/9), 1.84 KiB, done.', 'Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master']",NA,0,"Delta compression using up to 2 threads." +17403,"Change Meta (fav)icon on Special:Userlogin","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",1341590161,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-60,"True","[""'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done."", 'Delta compression using up to 2 threads.', 'Compressing objects: 100% (8/8), done.', 'Writing objects: 100% (9/9), 1.84 KiB, done.', 'Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master']",NA,0,"Compressing objects: 100% (8/8), done." +17403,"Change Meta (fav)icon on Special:Userlogin","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",1341590161,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-60,"True","[""'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done."", 'Delta compression using up to 2 threads.', 'Compressing objects: 100% (8/8), done.', 'Writing objects: 100% (9/9), 1.84 KiB, done.', 'Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master']",NA,0,"Writing objects: 100% (9/9), 1.84 KiB, done." +17403,"Change Meta (fav)icon on Special:Userlogin","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",1341590161,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-60,"True","[""'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done."", 'Delta compression using up to 2 threads.', 'Compressing objects: 100% (8/8), done.', 'Writing objects: 100% (9/9), 1.84 KiB, done.', 'Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master']",NA,0,"Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master" +17403,"Change Meta (fav)icon on Special:Userlogin","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",1341590161,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master","'wmgCentralAuthLoginIcon' => array( + 'default' => false, + 'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png', + 'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png', + 'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png', + 'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png', + 'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png', + 'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png', + 'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png', + 'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png', + 'metawiki' => '/usr/local/apache/common/images/sul/meta.png', + 'commonswiki' => '/usr/local/apache/common/images/sul/commons.png', + 'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png', + 'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png', + 'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png', +), + +File physically replaced + +reedy@fenari:/home/wikipedia/common$ git commit -a +[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin + 1 files changed, 6 insertions(+), 6 deletions(-) + rewrite images/sul/meta.png (98%) +reedy@fenari:/home/wikipedia/common$ git push origin +Counting objects: 15, done. +Delta compression using up to 2 threads. +Compressing objects: 100% (8/8), done. +Writing objects: 100% (9/9), 1.84 KiB, done. +Total 9 (delta 5), reused 0 (delta 0) +remote: Resolving deltas: 100% (5/5) +remote: Processing changes: refs: 1, done +To ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git + c1b096d..5851952 master -> master",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-60,"True","[""'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done."", 'Delta compression using up to 2 threads.', 'Compressing objects: 100% (8/8), done.', 'Writing objects: 100% (9/9), 1.84 KiB, done.', 'Total 9 (delta 5), reused 0 (delta 0)\nremote: Resolving deltas: 100% (5/5)\nremote: Processing changes: refs: 1, done\nTo ssh://gerrit.wikimedia.org:29418/operations/mediawiki-config.git\n c1b096d..5851952 master -> master']",NA,0,"'wmgCentralAuthLoginIcon' => array(\n\t'default' => false,\n\t'wiki' => '/usr/local/apache/common/images/sul/wikipedia.png',\n\t'wikibooks' => '/usr/local/apache/common/images/sul/wikibooks.png',\n\t'wikinews' => '/usr/local/apache/common/images/sul/wikinews.png',\n\t'wikiquote' => '/usr/local/apache/common/images/sul/wikiquote.png',\n\t'wikisource' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'sourceswiki' => '/usr/local/apache/common/images/sul/wikisource.png',\n\t'wikiversity' => '/usr/local/apache/common/images/sul/wikiversity.png',\n\t'wiktionary' => '/usr/local/apache/common/images/sul/wiktionary.png',\n\t'metawiki' => '/usr/local/apache/common/images/sul/meta.png',\n\t'commonswiki' => '/usr/local/apache/common/images/sul/commons.png',\n\t'mediawikiwiki' => '/usr/local/apache/common/images/sul/mediawiki.png',\n\t'specieswiki' => '/usr/local/apache/common/images/sul/wikispecies.png',\n\t'incubatorwiki' => '/usr/local/apache/common/images/sul/incubatorwiki.png',\n),\n\nFile physically replaced\n\nreedy@fenari:/home/wikipedia/common$ git commit -a\n[master 5851952] Bug 36982 - Change Meta (fav)icon on Special:Userlogin\n 1 files changed, 6 insertions(+), 6 deletions(-)\n rewrite images/sul/meta.png (98%)\nreedy@fenari:/home/wikipedia/common$ git push origin\nCounting objects: 15, done." +17404,"Change Meta (fav)icon on Special:Userlogin","**Thehelpfulonewiki** wrote: + +http://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/20px-Wikimedia-logo.svg.png + +needs to be replaced with + +http://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.svg/20px-Wikimedia_Community_Logo.svg.png + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +",1337554272,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","**Thehelpfulonewiki** wrote: + +http://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/20px-Wikimedia-logo.svg.png + +needs to be replaced with + +http://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.svg/20px-Wikimedia_Community_Logo.svg.png + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +","**Thehelpfulonewiki** wrote: + +URL + +needs to be replaced with + +URL + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['**Thehelpfulonewiki** wrote:\n\nURL \n\nneeds to be replaced with\n\nURL\n\nwhere it says \n\n\nYou are now logged in to Outreach Wiki as ""Thehelpfulone"".', 'Logging you in to wikis of the Wikimedia Foundation:\n\n']",NA,0,"**Thehelpfulonewiki** wrote:\n\nURL \n\nneeds to be replaced with\n\nURL\n\nwhere it says \n\n\nYou are now logged in to Outreach Wiki as ""Thehelpfulone""." +17404,"Change Meta (fav)icon on Special:Userlogin","**Thehelpfulonewiki** wrote: + +http://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/20px-Wikimedia-logo.svg.png + +needs to be replaced with + +http://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.svg/20px-Wikimedia_Community_Logo.svg.png + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +",1337554272,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-gdoyi7qpscdxj6l3rg24","task_subcomment","**Thehelpfulonewiki** wrote: + +http://upload.wikimedia.org/wikipedia/commons/thumb/8/81/Wikimedia-logo.svg/20px-Wikimedia-logo.svg.png + +needs to be replaced with + +http://upload.wikimedia.org/wikipedia/commons/thumb/7/75/Wikimedia_Community_Logo.svg/20px-Wikimedia_Community_Logo.svg.png + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +","**Thehelpfulonewiki** wrote: + +URL + +needs to be replaced with + +URL + +where it says + + +You are now logged in to Outreach Wiki as ""Thehelpfulone"". +Logging you in to wikis of the Wikimedia Foundation: + +",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-67,"True","['**Thehelpfulonewiki** wrote:\n\nURL \n\nneeds to be replaced with\n\nURL\n\nwhere it says \n\n\nYou are now logged in to Outreach Wiki as ""Thehelpfulone"".', 'Logging you in to wikis of the Wikimedia Foundation:\n\n']",NA,0,"Logging you in to wikis of the Wikimedia Foundation:\n\n" +17490,"Access to HTTP 404 logs for Wiktionary","Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1321772700,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_description","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,NA,NA,"open","True","c2",1,"False","False",-93,"True","['Access to HTTP 404 logs for Wiktionary.', 'Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found.', 'Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"Access to HTTP 404 logs for Wiktionary." +17490,"Access to HTTP 404 logs for Wiktionary","Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1321772700,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_description","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,NA,NA,"open","True","c2",1,"False","False",-93,"True","['Access to HTTP 404 logs for Wiktionary.', 'Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found.', 'Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found." +17490,"Access to HTTP 404 logs for Wiktionary","Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement",1321772700,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_description","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Access to HTTP 404 logs for Wiktionary./n/nMost often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found. Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers + +-------------------------- +**Version**: unspecified +**Severity**: enhancement","Low",25,NA,NA,"open","True","c2",1,"False","False",-93,"True","['Access to HTTP 404 logs for Wiktionary.', 'Most often many users use wikitionary by directly entering the word they are looking out in the url and if article doesnt exist, get 404, page not found.', 'Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement']",FALSE,1,"Is it possible to get access to these 404 logs and share with the community, so that the community can create entries for nonexistant pages which are being looked up by the readers\n\n--------------------------\n**Version**: unspecified\n**Severity**: enhancement" +17491,"Access to HTTP 404 logs for Wiktionary","**sumanah** wrote: + +Pinging Srikanth once more. :)",1411512068,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**sumanah** wrote: + +Pinging Srikanth once more. :)","**sumanah** wrote: + +Pinging Srikanth once more. :)",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,55,"True","['**sumanah** wrote:\n\nPinging Srikanth once more.', ':)']",NA,1,"**sumanah** wrote:\n\nPinging Srikanth once more." +17491,"Access to HTTP 404 logs for Wiktionary","**sumanah** wrote: + +Pinging Srikanth once more. :)",1411512068,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**sumanah** wrote: + +Pinging Srikanth once more. :)","**sumanah** wrote: + +Pinging Srikanth once more. :)",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,55,"True","['**sumanah** wrote:\n\nPinging Srikanth once more.', ':)']",NA,1,":)" +17492,"Access to HTTP 404 logs for Wiktionary","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]",1362166082,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-26,"True","['Srikanth: Could you answer comment 6, please?', '[removing ops keyword -> analytics area]']",NA,1,"Srikanth: Could you answer comment 6, please?" +17492,"Access to HTTP 404 logs for Wiktionary","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]",1362166082,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]","Srikanth: Could you answer comment 6, please? + +[removing ops keyword -> analytics area]",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-26,"True","['Srikanth: Could you answer comment 6, please?', '[removing ops keyword -> analytics area]']",NA,1,"[removing ops keyword -> analytics area]" +17493,"Access to HTTP 404 logs for Wiktionary","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",1362007695,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See URL for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-26,"True","[""**wikimaas** wrote:\n\nNot exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario."", 'See URL for the thread.', 'I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...']",NA,1,"See URL for the thread." +17493,"Access to HTTP 404 logs for Wiktionary","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",1362007695,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See URL for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-26,"True","[""**wikimaas** wrote:\n\nNot exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario."", 'See URL for the thread.', 'I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...']",NA,1,"I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea..." +17493,"Access to HTTP 404 logs for Wiktionary","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",1362007695,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See http://en.wiktionary.org/wiki/Wiktionary:Beer_parlour/2013/February#Yahoo_Pipe_for_404s for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...","**wikimaas** wrote: + +Not exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario. + +See URL for the thread. + +I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-26,"True","[""**wikimaas** wrote:\n\nNot exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario."", 'See URL for the thread.', 'I realize probably it would be better if the api is totally parsed inside wiktionary, so not with using pipes, but well, its the idea...']",NA,1,"**wikimaas** wrote:\n\nNot exactly the same, but I developed a small javascript extension which is handy dealing with the 404s described in the Srikanth Logi's scenario." +17494,"Access to HTTP 404 logs for Wiktionary","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",1345759288,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-53,"True","['So what is this currently, a request for an automated regularly updated filtered version of the udp logs?', '(Maybe to be sent to the analytics team?)', 'A request for a tool which works on stats.grok.se data or its replacement of the mysterious future?', 'Please clarify summary and component.']",NA,1,"So what is this currently, a request for an automated regularly updated filtered version of the udp logs?" +17494,"Access to HTTP 404 logs for Wiktionary","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",1345759288,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-53,"True","['So what is this currently, a request for an automated regularly updated filtered version of the udp logs?', '(Maybe to be sent to the analytics team?)', 'A request for a tool which works on stats.grok.se data or its replacement of the mysterious future?', 'Please clarify summary and component.']",NA,1,"(Maybe to be sent to the analytics team?)" +17494,"Access to HTTP 404 logs for Wiktionary","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",1345759288,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-53,"True","['So what is this currently, a request for an automated regularly updated filtered version of the udp logs?', '(Maybe to be sent to the analytics team?)', 'A request for a tool which works on stats.grok.se data or its replacement of the mysterious future?', 'Please clarify summary and component.']",NA,1,"A request for a tool which works on stats.grok.se data or its replacement of the mysterious future?" +17494,"Access to HTTP 404 logs for Wiktionary","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",1345759288,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.","So what is this currently, a request for an automated regularly updated filtered version of the udp logs? (Maybe to be sent to the analytics team?) +A request for a tool which works on stats.grok.se data or its replacement of the mysterious future? +Please clarify summary and component.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-53,"True","['So what is this currently, a request for an automated regularly updated filtered version of the udp logs?', '(Maybe to be sent to the analytics team?)', 'A request for a tool which works on stats.grok.se data or its replacement of the mysterious future?', 'Please clarify summary and component.']",NA,1,"Please clarify summary and component." +17495,"Access to HTTP 404 logs for Wiktionary","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",1322375098,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ?', 'My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there.', 'After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community']",NA,1,"Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ?" +17495,"Access to HTTP 404 logs for Wiktionary","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",1322375098,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ?', 'My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there.', 'After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community']",NA,1,"My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there." +17495,"Access to HTTP 404 logs for Wiktionary","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",1322375098,"PHID-USER-3stle7x2whgjz463c4zz","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community","Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ? My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there. After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['Nice, can the monthly log of this made available in some place like dumps.wikimedia.org ?', 'My original request was based on Tamil Wiktionary in mind and the urlencoding needs to be decoded for the final output to be useful and unicode might not be junk there.', 'After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community']",NA,1,"After we get the data from across wiktionaries over a period, we could probably find patterns to exclude junk and give some useful data to community" +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary." +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"These pages have been requested 50 times or more in a three day period." +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps." +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk." +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"**Attached**: {F8500}" +17496,"Access to HTTP 404 logs for Wiktionary","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",1322349136,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}","**EN.WP.ST47** wrote: + +November 1-3, en.wikt, top 300 requested non-existent pages + +I have attached the 300 most commonly requested pages that do not exist for the english wiktionary. These pages have been requested 50 times or more in a three day period. Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps. These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk. I'll let the script keep running and update the attachment with data for the full month. + +**Attached**: {F8500}",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-92,"True","['**EN.WP.ST47** wrote:\n\nNovember 1-3, en.wikt, top 300 requested non-existent pages\n\nI have attached the 300 most commonly requested pages that do not exist for the english wiktionary.', 'These pages have been requested 50 times or more in a three day period.', 'Some of the titles look a little strange, such as for example ""%25D8%25AC%25D9%2585%25D8%25A7%25D8%25B9"", as though it was urlencoded twice, but the names used are the ones I got from the pageviews dumps.', 'These mostly contain url fragments - index.php is the number 1 most requested, but there are also some strange ones - as well as years and unicode gunk.', ""I'll let the script keep running and update the attachment with data for the full month."", '**Attached**: {F8500}']",NA,1,"I'll let the script keep running and update the attachment with data for the full month." +17497,"Access to HTTP 404 logs for Wiktionary","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",1321998910,"PHID-USER-jtxavgb3caz53o45csni","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there."", ""We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet)."", 'Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.']",NA,1,"Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit." +17497,"Access to HTTP 404 logs for Wiktionary","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",1321998910,"PHID-USER-jtxavgb3caz53o45csni","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there."", ""We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet)."", 'Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.']",NA,1,"The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there." +17497,"Access to HTTP 404 logs for Wiktionary","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",1321998910,"PHID-USER-jtxavgb3caz53o45csni","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.","The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there. + +We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet). Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""The sampled logs wouldn't be of use here anyways; most misses would probably not even show up there."", ""We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet)."", 'Comparing a list of known viewed titles against known titles on the project is the best bet for right now, and doable immediately by anyone who can script a little bit.']",NA,1,"We could write code to grab 404 statistics but that still wouldn't cover a chunk of the cases here (urls that are well formed but point to an article that isn't written yet)." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"We log /some/ of this information, but not all." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"The page view statistics at e.g." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"With the UDP log stream it should definitely be possible to produce 404 statistics." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"I guess we could release anonymized versions of them, but we don't do that currently." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)." +17498,"Access to HTTP 404 logs for Wiktionary","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",1321998611,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. http://stats.grok.se are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.","We log /some/ of this information, but not all. We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data. I guess we could release anonymized versions of them, but we don't do that currently. + +The page view statistics at e.g. URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI). With the UDP log stream it should definitely be possible to produce 404 statistics. + +Reopening because this isn't as impossible as suggested in comment 1.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","['We log /some/ of this information, but not all.', ""We have 1:1000 sampled Apache logs that we use for internal analysis, but we don't release these publicly because they contain private data."", ""I guess we could release anonymized versions of them, but we don't do that currently."", 'The page view statistics at e.g.', ""URL are obtained using the UDP logger that counts the requests for each page but doesn't write a log line to disk for each request (disk I/O tends to be the limiting factor here, AIUI)."", 'With the UDP log stream it should definitely be possible to produce 404 statistics.', ""Reopening because this isn't as impossible as suggested in comment 1.""]",NA,1,"Reopening because this isn't as impossible as suggested in comment 1." +17499,"Access to HTTP 404 logs for Wiktionary","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",1321906629,"PHID-USER-ogbcrxm45oo3n3xe5q25","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.","We don't log this information. You should be able to use the page views (URL and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""We don't log this information."", 'You should be able to use the page views (URL and compare it to the list of existing pages.', 'This would take some work, but I think it is your best bet.']",NA,1,"You should be able to use the page views (URL and compare it to the list of existing pages." +17499,"Access to HTTP 404 logs for Wiktionary","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",1321906629,"PHID-USER-ogbcrxm45oo3n3xe5q25","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.","We don't log this information. You should be able to use the page views (URL and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""We don't log this information."", 'You should be able to use the page views (URL and compare it to the list of existing pages.', 'This would take some work, but I think it is your best bet.']",NA,1,"This would take some work, but I think it is your best bet." +17499,"Access to HTTP 404 logs for Wiktionary","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",1321906629,"PHID-USER-ogbcrxm45oo3n3xe5q25","PHID-TASK-rng7tsijdjuhagtccn6z","task_subcomment","We don't log this information. You should be able to use the page views (http://dumps.wikimedia.org/other/) and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.","We don't log this information. You should be able to use the page views (URL and compare it to the list of existing pages. + +This would take some work, but I think it is your best bet.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-93,"True","[""We don't log this information."", 'You should be able to use the page views (URL and compare it to the list of existing pages.', 'This would take some work, but I think it is your best bet.']",NA,1,"We don't log this information." +17529,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","For https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1335143940,"PHID-USER-wqc7ciyvfzunj3l2tvjt","PHID-TASK-2sndzb2ydzwochmrxplf","task_description","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor URL + +URL + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Lowest",10,1569621040,"PHID-USER-j7jwnj5chzo76nqqvgqc","duplicate","True","c2",1,"False","False",-71,"True","['HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file.', 'For URL\n\nURL\n\nSome sort of Guru meditation.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",FALSE,0,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file." +17529,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","For https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1335143940,"PHID-USER-wqc7ciyvfzunj3l2tvjt","PHID-TASK-2sndzb2ydzwochmrxplf","task_description","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor URL + +URL + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Lowest",10,1569621040,"PHID-USER-j7jwnj5chzo76nqqvgqc","duplicate","True","c2",1,"False","False",-71,"True","['HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file.', 'For URL\n\nURL\n\nSome sort of Guru meditation.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",FALSE,0,"For URL\n\nURL\n\nSome sort of Guru meditation." +17529,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","For https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1335143940,"PHID-USER-wqc7ciyvfzunj3l2tvjt","PHID-TASK-2sndzb2ydzwochmrxplf","task_description","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor https://commons.wikimedia.org/wiki/File:Carbon_River_pano_01A.jpg + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file./n/nFor URL + +URL + +Some sort of Guru meditation. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Lowest",10,1569621040,"PHID-USER-j7jwnj5chzo76nqqvgqc","duplicate","True","c2",1,"False","False",-71,"True","['HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file.', 'For URL\n\nURL\n\nSome sort of Guru meditation.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",FALSE,0,"--------------------------\n**Version**: wmf-deployment\n**Severity**: normal" +17530,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","This is same as T200313, closing as duplicate.",1569621031,"PHID-USER-j7jwnj5chzo76nqqvgqc","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","This is same as T200313, closing as duplicate.","This is same as T200313, closing as duplicate.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,317,"True","['This is same as T200313, closing as duplicate.']",NA,0,"This is same as T200313, closing as duplicate." +17531,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","https://upload.wikimedia.org/wikipedia/commons/thumb/8/84/Logiz_de_la_Lune_Rousse-Affiche1900.jpg/120px-Logiz_de_la_Lune_Rousse-Affiche1900.jpg + +``` + +Error generating thumbnail + +There have been too many recent failed attempts (4 or more) to render this thumbnail. Please try again later. +```",1432295639,"PHID-USER-nuf2sujf7qrx4v5ixbs3","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","https://upload.wikimedia.org/wikipedia/commons/thumb/8/84/Logiz_de_la_Lune_Rousse-Affiche1900.jpg/120px-Logiz_de_la_Lune_Rousse-Affiche1900.jpg + +``` + +Error generating thumbnail + +There have been too many recent failed attempts (4 or more) to render this thumbnail. Please try again later. +```","URL + +``CODE``",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,90,"True","['URL\n\n``CODE``']",NA,0,"URL\n\n``CODE``" +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"Error code 137 = out of memory." +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it." +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"Progressive images are much more memory intensive to scale." +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"----\nNote: the Carbon river file is a baseline jpeg." +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails." +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?" +17532,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",1400351520,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +> http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/ +> Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg +> +> Some sort of Guru meditation. + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +> I determined that I'd hit bug 17645, saved the file as a baseline optimized +> JPEG rather than progressive and now the thumbnails work. Sorry for the +> noise. +> +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.","Error code 137 = out of memory. + +(In reply to Jasper Deng from comment #0) +QUOTE +QUOTE +QUOTE +QUOTE + +What's the use case for generating a 6000px wide thumbnail? + +(In reply to earthsound from comment #10) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yep, that would do it. Progressive images are much more memory intensive to scale. + +---- +Note: the Carbon river file is a baseline jpeg. + +Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail. I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,37,"True","['Error code 137 = out of memory.', ""(In reply to Jasper Deng from comment #0)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nWhat's the use case for generating a 6000px wide thumbnail?"", '(In reply to earthsound from comment #10)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYep, that would do it.', 'Progressive images are much more memory intensive to scale.', '----\nNote: the Carbon river file is a baseline jpeg.', ""Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail."", 'I feel like this bug should be wontfixed unless people have a compelling reason to need such huge thumbnails.']",NA,0,"Honestly I don't find it that surprising that it runs out of memory when you try to make a 66 megapixel thumbnail." +17533,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",1393968377,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.","(In reply to earthsound from comment #10) +QUOTE + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['(In reply to earthsound from comment #10)\nQUOTE\n\nOuch.', 'We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever.', ""I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot."", 'It\'s also possible that whatever you did (a null ""convert"" run?)', 'fixed *other* things.']",NA,0,"(In reply to earthsound from comment #10)\nQUOTE\n\nOuch." +17533,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",1393968377,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.","(In reply to earthsound from comment #10) +QUOTE + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['(In reply to earthsound from comment #10)\nQUOTE\n\nOuch.', 'We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever.', ""I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot."", 'It\'s also possible that whatever you did (a null ""convert"" run?)', 'fixed *other* things.']",NA,0,"We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever." +17533,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",1393968377,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.","(In reply to earthsound from comment #10) +QUOTE + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['(In reply to earthsound from comment #10)\nQUOTE\n\nOuch.', 'We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever.', ""I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot."", 'It\'s also possible that whatever you did (a null ""convert"" run?)', 'fixed *other* things.']",NA,0,"It\" +17533,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",1393968377,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.","(In reply to earthsound from comment #10) +QUOTE + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['(In reply to earthsound from comment #10)\nQUOTE\n\nOuch.', 'We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever.', ""I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot."", 'It\'s also possible that whatever you did (a null ""convert"" run?)', 'fixed *other* things.']",NA,0,"I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot." +17533,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",1393968377,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to earthsound from comment #10) +> Perhaps the images reported in this bug are saved similarly (progressive)? + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.","(In reply to earthsound from comment #10) +QUOTE + +Ouch. We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever. I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot. +It's also possible that whatever you did (a null ""convert"" run?) fixed *other* things.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['(In reply to earthsound from comment #10)\nQUOTE\n\nOuch.', 'We have lists of progressive images, attachment 11220 and attachment 11500, and you can easily test the cases above with exiftools or whatever.', ""I think we've replaced by bot (most) of the bigger ones, but there may be other factors beyond size that make them fail: in that case, it would be nice to determine what they are, to fix them by bot."", 'It\'s also possible that whatever you did (a null ""convert"" run?)', 'fixed *other* things.']",NA,0,"convert" +17534,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",1393957092,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","[""**earthsound** wrote:\n\nI determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work."", 'Sorry for the noise.', 'Perhaps the images reported in this bug are saved similarly (progressive)?']",NA,0,"Sorry for the noise." +17534,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",1393957092,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","[""**earthsound** wrote:\n\nI determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work."", 'Sorry for the noise.', 'Perhaps the images reported in this bug are saved similarly (progressive)?']",NA,0,"Perhaps the images reported in this bug are saved similarly (progressive)?" +17534,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",1393957092,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?","**earthsound** wrote: + +I determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work. Sorry for the noise. + +Perhaps the images reported in this bug are saved similarly (progressive)?",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","[""**earthsound** wrote:\n\nI determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work."", 'Sorry for the noise.', 'Perhaps the images reported in this bug are saved similarly (progressive)?']",NA,0,"**earthsound** wrote:\n\nI determined that I'd hit bug 17645, saved the file as a baseline optimized JPEG rather than progressive and now the thumbnails work." +17535,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",1393954894,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +URL + +The preview on that page (1280px width) is broken: + +URL + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","['**earthsound** wrote:\n\nI have been seeing this error (as mentioned in comment 8, it\'s generating ""Error code:137"" now) for this particular image: \n\nURL\n\nThe preview on that page (1280px width) is broken:\n\nURL\n\nAfter a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail.', 'Please try again later.""', 'I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.']",NA,0,"**earthsound** wrote:\n\nI have been seeing this error (as mentioned in comment 8, it\" +17535,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",1393954894,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +URL + +The preview on that page (1280px width) is broken: + +URL + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","['**earthsound** wrote:\n\nI have been seeing this error (as mentioned in comment 8, it\'s generating ""Error code:137"" now) for this particular image: \n\nURL\n\nThe preview on that page (1280px width) is broken:\n\nURL\n\nAfter a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail.', 'Please try again later.""', 'I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.']",NA,0,"Error code:137" +17535,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",1393954894,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +https://commons.wikimedia.org/wiki/File:Aerial_drawing,_1885,_of_Birmingham,_Alabama.jpg + +The preview on that page (1280px width) is broken: + +https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg/1280px-Aerial_drawing%2C_1885%2C_of_Birmingham%2C_Alabama.jpg + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.","**earthsound** wrote: + +I have been seeing this error (as mentioned in comment 8, it's generating ""Error code:137"" now) for this particular image: + +URL + +The preview on that page (1280px width) is broken: + +URL + +After a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail. Please try again later."" + +I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,26,"True","['**earthsound** wrote:\n\nI have been seeing this error (as mentioned in comment 8, it\'s generating ""Error code:137"" now) for this particular image: \n\nURL\n\nThe preview on that page (1280px width) is broken:\n\nURL\n\nAfter a few failed attempts, it will generate this error: ""Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail.', 'Please try again later.""', 'I have found that any size thumbnail up to a width of 1234px will generate OK, but anything 1235px width or larger fails 100% of the time, even though the full resolution image is OK.']",NA,0,"Error generating thumbnail - There have been too many recent failed attempts (5 or more) to render this thumbnail.', 'Please try again later." +17536,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","I get ""Error code: 137"" nowadays.",1393621965,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","I get ""Error code: 137"" nowadays.","I get ""Error code: 137"" nowadays.",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,26,"True","['I get ""Error code: 137"" nowadays.']",NA,0,"I get ""Error code: 137"" nowadays." +17537,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to comment #6) +> I am getting a similar error when trying to download van Gogh: + +That's covered in bug 44071 instead.",1358500573,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to comment #6) +> I am getting a similar error when trying to download van Gogh: + +That's covered in bug 44071 instead.","(In reply to comment #6) +QUOTE + +That's covered in bug 44071 instead.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-32,"True","[""(In reply to comment #6)\nQUOTE\n\nThat's covered in bug 44071 instead.""]",NA,0,"(In reply to comment #6)\nQUOTE\n\nThat's covered in bug 44071 instead." +17538,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**DIA.Keyser** wrote: + +I am getting a similar error when trying to download any size larger than 2048px for this van Gogh: + +http://commons.wikimedia.org/wiki/File:Vincent_van_Gogh_-_De_slaapkamer_-_Google_Art_Project.jpg#file",1358449619,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**DIA.Keyser** wrote: + +I am getting a similar error when trying to download any size larger than 2048px for this van Gogh: + +http://commons.wikimedia.org/wiki/File:Vincent_van_Gogh_-_De_slaapkamer_-_Google_Art_Project.jpg#file","**DIA.Keyser** wrote: + +I am getting a similar error when trying to download any size larger than 2048px for this van Gogh: + +URL",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-32,"True","['**DIA.Keyser** wrote:\n\nI am getting a similar error when trying to download any size larger than 2048px for this van Gogh:\n\nURL']",NA,0,"**DIA.Keyser** wrote:\n\nI am getting a similar error when trying to download any size larger than 2048px for this van Gogh:\n\nURL" +17539,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",1351149257,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").","**sumanah** wrote: + +Still reproducible at + +URL + +When I change the width: + +URL + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-44,"True","[""**sumanah** wrote:\n\nStill reproducible at\n\nURL\n\nWhen I change the width:\n\nURL\n\nthen it's fine."", 'This may be related to bug 13493 (""Can\'t create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?', '"").']",NA,0,"This may be related to bug 13493 (""Can\" +17539,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",1351149257,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").","**sumanah** wrote: + +Still reproducible at + +URL + +When I change the width: + +URL + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-44,"True","[""**sumanah** wrote:\n\nStill reproducible at\n\nURL\n\nWhen I change the width:\n\nURL\n\nthen it's fine."", 'This may be related to bug 13493 (""Can\'t create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?', '"").']",NA,0,"**sumanah** wrote:\n\nStill reproducible at\n\nURL\n\nWhen I change the width:\n\nURL\n\nthen it's fine." +17539,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",1351149257,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**sumanah** wrote: + +Still reproducible at + +http://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/6565px-Carbon_River_pano_01A.jpg + +When I change the width: + +https://upload.wikimedia.org/wikipedia/commons/thumb/f/f6/Carbon_River_pano_01A.jpg/72px-Carbon_River_pano_01A.jpg + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").","**sumanah** wrote: + +Still reproducible at + +URL + +When I change the width: + +URL + +then it's fine. + +This may be related to bug 13493 (""Can't create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?"").",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-44,"True","[""**sumanah** wrote:\n\nStill reproducible at\n\nURL\n\nWhen I change the width:\n\nURL\n\nthen it's fine."", 'This may be related to bug 13493 (""Can\'t create thumbnail of images with a peculiar aspect ratio"") and bug 20312 (""Error creating thumbnail: Image was not scaled, is the requested width bigger than the source?', '"").']",NA,0,") and bug 20312 (" +17540,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to comment #3) +> my guess is that it's failing to resize to a thumbnail that is 6565 pixels +> wide. It works for smaller images. + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)",1345141253,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to comment #3) +> my guess is that it's failing to resize to a thumbnail that is 6565 pixels +> wide. It works for smaller images. + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)","(In reply to comment #3) +QUOTE +QUOTE + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-54,"True","['(In reply to comment #3)\nQUOTE\nQUOTE\n\nIs it a Wikimedia or a MediaWiki issue then?', '(Still happening.)']",NA,0,"(In reply to comment #3)\nQUOTE\nQUOTE\n\nIs it a Wikimedia or a MediaWiki issue then?" +17540,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to comment #3) +> my guess is that it's failing to resize to a thumbnail that is 6565 pixels +> wide. It works for smaller images. + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)",1345141253,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to comment #3) +> my guess is that it's failing to resize to a thumbnail that is 6565 pixels +> wide. It works for smaller images. + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)","(In reply to comment #3) +QUOTE +QUOTE + +Is it a Wikimedia or a MediaWiki issue then? (Still happening.)",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-54,"True","['(In reply to comment #3)\nQUOTE\nQUOTE\n\nIs it a Wikimedia or a MediaWiki issue then?', '(Still happening.)']",NA,0,"(Still happening.)" +17541,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",1335995479,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-69,"True","[""**bhartshorne** wrote:\n\nmy guess is that it's failing to resize to a thumbnail that is 6565 pixels wide."", 'It works for smaller images.', 'fwiw, convert is failing with exit code 153.']",NA,0,"It works for smaller images." +17541,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",1335995479,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-69,"True","[""**bhartshorne** wrote:\n\nmy guess is that it's failing to resize to a thumbnail that is 6565 pixels wide."", 'It works for smaller images.', 'fwiw, convert is failing with exit code 153.']",NA,0,"fwiw, convert is failing with exit code 153." +17541,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",1335995479,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.","**bhartshorne** wrote: + +my guess is that it's failing to resize to a thumbnail that is 6565 pixels wide. It works for smaller images. fwiw, convert is failing with exit code 153.",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-69,"True","[""**bhartshorne** wrote:\n\nmy guess is that it's failing to resize to a thumbnail that is 6565 pixels wide."", 'It works for smaller images.', 'fwiw, convert is failing with exit code 153.']",NA,0,"**bhartshorne** wrote:\n\nmy guess is that it's failing to resize to a thumbnail that is 6565 pixels wide." +17542,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","(In reply to comment #1) +> XID: 1391948384 + +This XID value seems to change on page refresh, by the way.",1335222024,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","(In reply to comment #1) +> XID: 1391948384 + +This XID value seems to change on page refresh, by the way.","(In reply to comment #1) +QUOTE + +This XID value seems to change on page refresh, by the way.",NA,NA,NA,NA,NA,"True","c2",1,"True",NA,-71,"True","['(In reply to comment #1)\nQUOTE\n\nThis XID value seems to change on page refresh, by the way.']",NA,0,"(In reply to comment #1)\nQUOTE\n\nThis XID value seems to change on page refresh, by the way." +17543,"HTTP 500 error when generating 6000px wide thumbnail of a 6912px wide and 12.5MB JPEG file","XID: 1391948384",1335214085,"PHID-USER-ogbcrxm45oo3n3xe5q25","PHID-TASK-2sndzb2ydzwochmrxplf","task_subcomment","XID: 1391948384","XID: 1391948384",NA,NA,NA,NA,NA,"True","c2",1,"False",NA,-71,"True","['XID: 1391948384']",NA,0,"XID: 1391948384" +17631,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Error message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}",1383598080,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-72rziu6fsgfsmc5bjdnx","task_description","VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE./n/nError message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}","VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE./n/nError message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}","Needs Triage",90,1383598243,NA,"resolved","True","c2",3,"False","False",9,"True","['VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE.', 'Error message\n\nSteps to reproduce:\nClick on the edit button\n\nObserved Result:\n""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE\n\nSee the screenshot attached\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F12683}']",TRUE,0,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE." +17631,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Error message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}",1383598080,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-72rziu6fsgfsmc5bjdnx","task_description","VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE./n/nError message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}","VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE./n/nError message + +Steps to reproduce: +Click on the edit button + +Observed Result: +""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE + +See the screenshot attached + +-------------------------- +**Version**: unspecified +**Severity**: normal + +**Attached**: {F12683}","Needs Triage",90,1383598243,NA,"resolved","True","c2",3,"False","False",9,"True","['VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE.', 'Error message\n\nSteps to reproduce:\nClick on the edit button\n\nObserved Result:\n""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE\n\nSee the screenshot attached\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F12683}']",TRUE,0,"Error message\n\nSteps to reproduce:\nClick on the edit button\n\nObserved Result:\n""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE\n\nSee the screenshot attached\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal\n\n**Attached**: {F12683}" +17632,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",1383598243,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-72rziu6fsgfsmc5bjdnx","task_subcomment","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,9,"True","['Fallout from fixing bug 56583.', 'Should be okay now.', '*** This bug has been marked as a duplicate of bug 56583 ***']",NA,0,"Fallout from fixing bug 56583." +17632,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",1383598243,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-72rziu6fsgfsmc5bjdnx","task_subcomment","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,9,"True","['Fallout from fixing bug 56583.', 'Should be okay now.', '*** This bug has been marked as a duplicate of bug 56583 ***']",NA,0,"Should be okay now." +17632,"VisualEditor: ""Error loading data from server:parsoidserver-http-bad-status:503"" shows while attempting to edit using VE","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",1383598243,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-72rziu6fsgfsmc5bjdnx","task_subcomment","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***","Fallout from fixing bug 56583. Should be okay now. + +*** This bug has been marked as a duplicate of bug 56583 ***",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,9,"True","['Fallout from fixing bug 56583.', 'Should be okay now.', '*** This bug has been marked as a duplicate of bug 56583 ***']",NA,0,"*** This bug has been marked as a duplicate of bug 56583 ***" +17676,"Change interwiki for smw.o to https","semantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki",1385325840,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_description","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1385342222,NA,"invalid","True","c2",3,"True","False",12,"True","['Change interwiki for smw.o to https.', 'semantic-mediawiki.org offers https access.', 'Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance!', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"Change interwiki for smw.o to https." +17676,"Change interwiki for smw.o to https","semantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki",1385325840,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_description","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1385342222,NA,"invalid","True","c2",3,"True","False",12,"True","['Change interwiki for smw.o to https.', 'semantic-mediawiki.org offers https access.', 'Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance!', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"semantic-mediawiki.org offers https access." +17676,"Change interwiki for smw.o to https","semantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki",1385325840,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_description","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1385342222,NA,"invalid","True","c2",3,"True","False",12,"True","['Change interwiki for smw.o to https.', 'semantic-mediawiki.org offers https access.', 'Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance!', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance!" +17676,"Change interwiki for smw.o to https","semantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki",1385325840,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_description","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""https://www.semantic-mediawiki.org/wiki/$1"". Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki","Change interwiki for smw.o to https./n/nsemantic-mediawiki.org offers https access. Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance! + +-------------------------- +**Version**: unspecified +**Severity**: normal +**URL**: URL","Medium",50,1385342222,NA,"invalid","True","c2",3,"True","False",12,"True","['Change interwiki for smw.o to https.', 'semantic-mediawiki.org offers https access.', 'Thus it will be nice if the link for the existing interwiki prefix ""semantic-mw"" could be changed to ""URL Many thanks in advance!', '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL']",TRUE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal\n**URL**: URL" +17677,"Change interwiki for smw.o to https","Thank you for the hint. I filed the request at https://meta.wikimedia.org/wiki/Talk:Interwiki_map#semantic-mw",1385369204,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_subcomment","Thank you for the hint. I filed the request at https://meta.wikimedia.org/wiki/Talk:Interwiki_map#semantic-mw","Thank you for the hint. I filed the request at URL",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,12,"True","['Thank you for the hint.', 'I filed the request at URL']",NA,0,"Thank you for the hint." +17677,"Change interwiki for smw.o to https","Thank you for the hint. I filed the request at https://meta.wikimedia.org/wiki/Talk:Interwiki_map#semantic-mw",1385369204,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_subcomment","Thank you for the hint. I filed the request at https://meta.wikimedia.org/wiki/Talk:Interwiki_map#semantic-mw","Thank you for the hint. I filed the request at URL",NA,NA,NA,NA,NA,"True","c2",3,"True",NA,12,"True","['Thank you for the hint.', 'I filed the request at URL']",NA,0,"I filed the request at URL" +17678,"Change interwiki for smw.o to https","Please ask at [[m:Talk:Interwiki map]].",1385342222,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-dt7vhebhzjxphnpx6qqs","task_subcomment","Please ask at [[m:Talk:Interwiki map]].","Please ask at [[m:Talk:Interwiki map]].",NA,NA,NA,NA,NA,"True","c2",3,"False",NA,12,"True","['Please ask at [[m:Talk:Interwiki map]].']",NA,0,"Please ask at [[m:Talk:Interwiki map]]." +18090,"Login with unicode username fails","This is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal",1407613020,"PHID-USER-cfsvvgbtlqnbt2yokfjf","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_description","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1407640172,NA,"resolved","True","c3",1,"False","False",-47,"True","['Login with unicode username fails.', 'This is probably due to recent changes in the user agent string.', 'File ""core/pywikibot/data/api.py"", line 337, in submit\tbody=paramstring)\n\tFile ""core/pywikibot/comms/http.py"", line 164, in request\n\tusername=quote(username),\n\tFile ""/usr/lib/python2.7/urllib.py"", line 1268, in quote\n\treturn ”.join(map(quoter, s))\n\tKeyError: u\'\\u05e2\'\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Login with unicode username fails." +18090,"Login with unicode username fails","This is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal",1407613020,"PHID-USER-cfsvvgbtlqnbt2yokfjf","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_description","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1407640172,NA,"resolved","True","c3",1,"False","False",-47,"True","['Login with unicode username fails.', 'This is probably due to recent changes in the user agent string.', 'File ""core/pywikibot/data/api.py"", line 337, in submit\tbody=paramstring)\n\tFile ""core/pywikibot/comms/http.py"", line 164, in request\n\tusername=quote(username),\n\tFile ""/usr/lib/python2.7/urllib.py"", line 1268, in quote\n\treturn ”.join(map(quoter, s))\n\tKeyError: u\'\\u05e2\'\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"This is probably due to recent changes in the user agent string." +18090,"Login with unicode username fails","This is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal",1407613020,"PHID-USER-cfsvvgbtlqnbt2yokfjf","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_description","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1407640172,NA,"resolved","True","c3",1,"False","False",-47,"True","['Login with unicode username fails.', 'This is probably due to recent changes in the user agent string.', 'File ""core/pywikibot/data/api.py"", line 337, in submit\tbody=paramstring)\n\tFile ""core/pywikibot/comms/http.py"", line 164, in request\n\tusername=quote(username),\n\tFile ""/usr/lib/python2.7/urllib.py"", line 1268, in quote\n\treturn ”.join(map(quoter, s))\n\tKeyError: u\'\\u05e2\'\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"File ""core/pywikibot/data/api.py"", line 337, in submit\tbody=paramstring)\n\tFile ""core/pywikibot/comms/http.py"", line 164, in request\n\tusername=quote(username),\n\tFile ""/usr/lib/python2.7/urllib.py"", line 1268, in quote\n\treturn ”.join(map(quoter, s))\n\tKeyError: u\" +18090,"Login with unicode username fails","This is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal",1407613020,"PHID-USER-cfsvvgbtlqnbt2yokfjf","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_description","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Login with unicode username fails./n/nThis is probably due to recent changes in the user agent string. + +File ""core/pywikibot/data/api.py"", line 337, in submit body=paramstring) + File ""core/pywikibot/comms/http.py"", line 164, in request + username=quote(username), + File ""/usr/lib/python2.7/urllib.py"", line 1268, in quote + return ”.join(map(quoter, s)) + KeyError: u'\u05e2' + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1407640172,NA,"resolved","True","c3",1,"False","False",-47,"True","['Login with unicode username fails.', 'This is probably due to recent changes in the user agent string.', 'File ""core/pywikibot/data/api.py"", line 337, in submit\tbody=paramstring)\n\tFile ""core/pywikibot/comms/http.py"", line 164, in request\n\tusername=quote(username),\n\tFile ""/usr/lib/python2.7/urllib.py"", line 1268, in quote\n\treturn ”.join(map(quoter, s))\n\tKeyError: u\'\\u05e2\'\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal" +18091,"Login with unicode username fails","Change 153221 merged by jenkins-bot: +Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221",1407618982,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_subcomment","Change 153221 merged by jenkins-bot: +Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221","Change 153221 merged by jenkins-bot: +Allow unicode usernames in headers + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['Change 153221 merged by jenkins-bot:\nAllow unicode usernames in headers\n\nGERRIT_URL']",NA,0,"Change 153221 merged by jenkins-bot:\nAllow unicode usernames in headers\n\nGERRIT_URL" +18092,"Login with unicode username fails","Change 153221 had a related patch set uploaded by Legoktm: +Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221",1407618889,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_subcomment","Change 153221 had a related patch set uploaded by Legoktm: +Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221","Change 153221 had a related patch set uploaded by Legoktm: +Allow unicode usernames in headers + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['Change 153221 had a related patch set uploaded by Legoktm:\nAllow unicode usernames in headers\n\nGERRIT_URL']",NA,0,"Change 153221 had a related patch set uploaded by Legoktm:\nAllow unicode usernames in headers\n\nGERRIT_URL" +18093,"Login with unicode username fails","Change 153221 had a related patch set uploaded by Merlijn van Deen: +Bug 69354 Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221",1407614619,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-7v57yx3ngtnzzx22sz2v","task_subcomment","Change 153221 had a related patch set uploaded by Merlijn van Deen: +Bug 69354 Allow unicode usernames in headers + +https://gerrit.wikimedia.org/r/153221","Change 153221 had a related patch set uploaded by Merlijn van Deen: +Bug 69354 Allow unicode usernames in headers + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['Change 153221 had a related patch set uploaded by Merlijn van Deen:\nBug 69354 Allow unicode usernames in headers\n\nGERRIT_URL']",NA,0,"Change 153221 had a related patch set uploaded by Merlijn van Deen:\nBug 69354 Allow unicode usernames in headers\n\nGERRIT_URL" +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"Login not possible and nor error message it username is deleted/merged by UserMerge extension." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"The user is always redirected to the main wiki page with status ""not login""." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"That means ""Login"" is still available in the upper right corner of MW." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"--------------------------\n**Version**: master\n**Severity**: normal" +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry." +18153,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal",1405941360,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wxxjqfa225z6fpb5272k","task_description","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** `mluxen` + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Login not possible and nor error message it username is deleted/merged by UserMerge extension./n/n**Author:** CODE + +**Description:** +A new Wiki user is created and linked to a Google account. If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case). +Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry. The user is always redirected to the main wiki page with status ""not login"". That means ""Login"" is still available in the upper right corner of MW. +The table must be created again if it's deleted completely in the step before. + +-------------------------- +**Version**: master +**Severity**: normal","Needs Triage",90,1407714038,NA,"resolved","True","c3",1,"False","False",-50,"True","['Login not possible and nor error message it username is deleted/merged by UserMerge extension.', '**Author:** CODE\n\n**Description:**\nA new Wiki user is created and linked to a Google account.', ""If this user is now deleted by UserMerge extension the reference within the user_google_user table doesn't match as it's not deleted automatically by another extension (UserMerge in this case)."", ""Afterwards it's not possible to login again another/new user until the whole table is deleted or this specific user entry."", 'The user is always redirected to the main wiki page with status ""not login"".', 'That means ""Login"" is still available in the upper right corner of MW.', ""The table must be created again if it's deleted completely in the step before."", '--------------------------\n**Version**: master\n**Severity**: normal']",TRUE,1,"The table must be created again if it's deleted completely in the step before." +18154,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","@Mike: I will set this as fixed, if you have still problems, feel free to reopen.",1407714038,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wxxjqfa225z6fpb5272k","task_subcomment","@Mike: I will set this as fixed, if you have still problems, feel free to reopen.","SCREEN_NAME: I will set this as fixed, if you have still problems, feel free to reopen.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-47,"True","['SCREEN_NAME: I will set this as fixed, if you have still problems, feel free to reopen.']",NA,1,"SCREEN_NAME: I will set this as fixed, if you have still problems, feel free to reopen." +18155,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","@Mike: Can you please verify, that this helps in your problem? :) Just load the extension new please.",1406010571,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wxxjqfa225z6fpb5272k","task_subcomment","@Mike: Can you please verify, that this helps in your problem? :) Just load the extension new please.","SCREEN_NAME: Can you please verify, that this helps in your problem? :) Just load the extension new please.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-50,"True","['SCREEN_NAME: Can you please verify, that this helps in your problem?', ':) Just load the extension new please.']",NA,1,"SCREEN_NAME: Can you please verify, that this helps in your problem?" +18155,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","@Mike: Can you please verify, that this helps in your problem? :) Just load the extension new please.",1406010571,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wxxjqfa225z6fpb5272k","task_subcomment","@Mike: Can you please verify, that this helps in your problem? :) Just load the extension new please.","SCREEN_NAME: Can you please verify, that this helps in your problem? :) Just load the extension new please.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-50,"True","['SCREEN_NAME: Can you please verify, that this helps in your problem?', ':) Just load the extension new please.']",NA,1,":) Just load the extension new please." +18156,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","Change 148108 merged by jenkins-bot: +Extended Login-workflow + +https://gerrit.wikimedia.org/r/148108",1406010442,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wxxjqfa225z6fpb5272k","task_subcomment","Change 148108 merged by jenkins-bot: +Extended Login-workflow + +https://gerrit.wikimedia.org/r/148108","Change 148108 merged by jenkins-bot: +Extended Login-workflow + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-50,"True","['Change 148108 merged by jenkins-bot:\nExtended Login-workflow\n\nGERRIT_URL']",NA,1,"Change 148108 merged by jenkins-bot:\nExtended Login-workflow\n\nGERRIT_URL" +18157,"Login not possible and nor error message it username is deleted/merged by UserMerge extension","Change 148108 had a related patch set uploaded by Florianschmidtwelzow: +WIP: Extended Login-workflow + +https://gerrit.wikimedia.org/r/148108",1405962664,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wxxjqfa225z6fpb5272k","task_subcomment","Change 148108 had a related patch set uploaded by Florianschmidtwelzow: +WIP: Extended Login-workflow + +https://gerrit.wikimedia.org/r/148108","Change 148108 had a related patch set uploaded by Florianschmidtwelzow: +WIP: Extended Login-workflow + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-50,"True","['Change 148108 had a related patch set uploaded by Florianschmidtwelzow:\nWIP: Extended Login-workflow\n\nGERRIT_URL']",NA,1,"Change 148108 had a related patch set uploaded by Florianschmidtwelzow:\nWIP: Extended Login-workflow\n\nGERRIT_URL" +18215,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Getting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal",1400617680,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-z47j727fj45rve5q5uwp","task_description","Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)./n/nGetting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal","Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)./n/nGetting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1400620161,NA,"resolved","True","c3",1,"False","False",-59,"True","['Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load).', 'Getting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)." +18215,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Getting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal",1400617680,"PHID-USER-24djtv3gj5gua2y6u2g5","PHID-TASK-z47j727fj45rve5q5uwp","task_description","Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)./n/nGetting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal","Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)./n/nGetting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503 + +-------------------------- +**Version**: unspecified +**Severity**: normal","Needs Triage",90,1400620161,NA,"resolved","True","c3",1,"False","False",-59,"True","['Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load).', 'Getting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,0,"Getting the following while trying to load VE on Betalabs : Error loading data from server: parsoidserver-http-bad-status: 503\n\n--------------------------\n**Version**: unspecified\n**Severity**: normal" +18216,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.",1400620153,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker.', 'This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.']",NA,0,"Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker." +18216,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.",1400620153,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.","Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker. This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['Parsoid broke in beta labs because someone swapped the UIDs of the parsoid user and mwalker.', 'This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it.']",NA,0,"This caused various things that should have been owned by parsoid to be owned by mwalker until I manually fixed it." +18217,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","*** Bug 65555 has been marked as a duplicate of this bug. ***",1400619845,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","*** Bug 65555 has been marked as a duplicate of this bug. ***","*** Bug 65555 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['*** Bug 65555 has been marked as a duplicate of this bug.', '***']",NA,0,"*** Bug 65555 has been marked as a duplicate of this bug." +18217,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","*** Bug 65555 has been marked as a duplicate of this bug. ***",1400619845,"PHID-USER-ydswvwhh5pm4lshahjje","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","*** Bug 65555 has been marked as a duplicate of this bug. ***","*** Bug 65555 has been marked as a duplicate of this bug. ***",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['*** Bug 65555 has been marked as a duplicate of this bug.', '***']",NA,0,"***" +18218,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",1400617898,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['Parsoid is down completely in beta labs.', ""I tried restarting it but it doesn't come up."", 'Investigating.']",NA,0,"Parsoid is down completely in beta labs." +18218,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",1400617898,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['Parsoid is down completely in beta labs.', ""I tried restarting it but it doesn't come up."", 'Investigating.']",NA,0,"Investigating." +18218,"Parsoid dead on BetaLabs (getting ""parsoidserver-http-bad-status: 503"" on VE load)","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",1400617898,"PHID-USER-fovtl67ew4l4cc3oeypc","PHID-TASK-z47j727fj45rve5q5uwp","task_subcomment","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.","Parsoid is down completely in beta labs. I tried restarting it but it doesn't come up. Investigating.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-59,"True","['Parsoid is down completely in beta labs.', ""I tried restarting it but it doesn't come up."", 'Investigating.']",NA,0,"I tried restarting it but it doesn't come up." +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"Getting rid of own login page (tracking)." +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"It also happens for alpha mode (yay!" +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"), i want to have a bug for this for tracking purposes." +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices." +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"It isn't really needed anymore, the login page customisations should be done with special css rules or in core." +18639,"Getting rid of own login page (tracking)","It also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1415036040,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_description","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Getting rid of own login page (tracking)./n/nIt also happens for alpha mode (yay!), i want to have a bug for this for tracking purposes. + +The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices. It isn't really needed anymore, the login page customisations should be done with special css rules or in core. Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension. + +-------------------------- +**Version**: unspecified +**Severity**: normal","High",80,1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",1,"True","True",-35,"True","['Getting rid of own login page (tracking).', 'It also happens for alpha mode (yay!', '), i want to have a bug for this for tracking purposes.', ""The login page of MobileFrontend actually is provided by it's own implementation to fit the needs of mobile devices."", ""It isn't really needed anymore, the login page customisations should be done with special css rules or in core."", ""Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension."", '--------------------------\n**Version**: unspecified\n**Severity**: normal']",TRUE,1,"Actually it's difficult to overwrite the loginpage for other extensions (like GoogleLogin), if MobileFrontend loads after this extension." +18640,"Getting rid of own login page (tracking)","Change 231146 merged by jenkins-bot: +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]]",1441316635,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Change 231146 merged by jenkins-bot: +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]]","Change 231146 merged by jenkins-bot: +Use core login form + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,9,"True","['Change 231146 merged by jenkins-bot:\nUse core login form\n\n[[GERRIT_URL]]']",NA,1,"Change 231146 merged by jenkins-bot:\nUse core login form\n\n[[GERRIT_URL]]" +18641,"Getting rid of own login page (tracking)","*yay*",1441316105,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","*yay*","*yay*",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,9,"True","['*yay*']",NA,1,"*yay*" +18642,"Getting rid of own login page (tracking)","@jdlrobson I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)",1440787627,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","@jdlrobson I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)","SCREEN_NAME I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME I know you wanted to get this done sooner than later.', 'Feel free to put subtasks into the next sprint board (search for 55 on phab)']",NA,1,"SCREEN_NAME I know you wanted to get this done sooner than later." +18642,"Getting rid of own login page (tracking)","@jdlrobson I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)",1440787627,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","@jdlrobson I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)","SCREEN_NAME I know you wanted to get this done sooner than later. Feel free to put subtasks into the next sprint board (search for 55 on phab)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME I know you wanted to get this done sooner than later.', 'Feel free to put subtasks into the next sprint board (search for 55 on phab)']",NA,1,"Feel free to put subtasks into the next sprint board (search for 55 on phab)" +18643,"Getting rid of own login page (tracking)","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",1440407666,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""It's already on high priority so it will show up on searches."", 'I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set.', ""As said this is high and will show up for next sprints so don't worry!"", 'Maybe ping reviewers manually?']",NA,1,"I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set." +18643,"Getting rid of own login page (tracking)","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",1440407666,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""It's already on high priority so it will show up on searches."", 'I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set.', ""As said this is high and will show up for next sprints so don't worry!"", 'Maybe ping reviewers manually?']",NA,1,"Maybe ping reviewers manually?" +18643,"Getting rid of own login page (tracking)","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",1440407666,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""It's already on high priority so it will show up on searches."", 'I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set.', ""As said this is high and will show up for next sprints so don't worry!"", 'Maybe ping reviewers manually?']",NA,1,"It's already on high priority so it will show up on searches." +18643,"Getting rid of own login page (tracking)","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",1440407666,"PHID-USER-cjstd4vv3u3gq2sijr7d","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +","It's already on high priority so it will show up on searches. + +I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set. + +As said this is high and will show up for next sprints so don't worry! + +Maybe ping reviewers manually? + +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""It's already on high priority so it will show up on searches."", 'I agree this needs to happen sooner than later, but we also need to focus more on getting quick surveys and performance work done, we may be spreading a bit too thin and we may be risking not accomplishing the goals we set.', ""As said this is high and will show up for next sprints so don't worry!"", 'Maybe ping reviewers manually?']",NA,1,"As said this is high and will show up for next sprints so don't worry!" +18644,"Getting rid of own login page (tracking)","@JHernandez can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!",1440194382,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","@JHernandez can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!","SCREEN_NAME can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""SCREEN_NAME can we look to make sure this put in the next sprint if it hasn't been merged by then?"", ""I'm keen to see the back of this code!""]",NA,1,"SCREEN_NAME can we look to make sure this put in the next sprint if it hasn't been merged by then?" +18644,"Getting rid of own login page (tracking)","@JHernandez can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!",1440194382,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","@JHernandez can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!","SCREEN_NAME can we look to make sure this put in the next sprint if it hasn't been merged by then? I'm keen to see the back of this code!",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","[""SCREEN_NAME can we look to make sure this put in the next sprint if it hasn't been merged by then?"", ""I'm keen to see the back of this code!""]",NA,1,"I'm keen to see the back of this code!" +18645,"Getting rid of own login page (tracking)","Change 231184 merged by jenkins-bot: +Do not override login form in beta + +[[https://gerrit.wikimedia.org/r/231184]]",1439422602,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Change 231184 merged by jenkins-bot: +Do not override login form in beta + +[[https://gerrit.wikimedia.org/r/231184]]","Change 231184 merged by jenkins-bot: +Do not override login form in beta + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,5,"True","['Change 231184 merged by jenkins-bot:\nDo not override login form in beta\n\n[[GERRIT_URL]]']",NA,1,"Change 231184 merged by jenkins-bot:\nDo not override login form in beta\n\n[[GERRIT_URL]]" +18646,"Getting rid of own login page (tracking)","Change 231146 had a related patch set uploaded (by Jdlrobson): +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]] +",1439419397,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Change 231146 had a related patch set uploaded (by Jdlrobson): +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]] +","Change 231146 had a related patch set uploaded (by Jdlrobson): +Use core login form + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,5,"True","['Change 231146 had a related patch set uploaded (by Jdlrobson):\nUse core login form\n\n[[GERRIT_URL]]']",NA,1,"Change 231146 had a related patch set uploaded (by Jdlrobson):\nUse core login form\n\n[[GERRIT_URL]]" +18647,"Getting rid of own login page (tracking)","Change 231184 had a related patch set uploaded (by Jdlrobson): +Do not override login form in beta + +[[https://gerrit.wikimedia.org/r/231184]] +",1439418634,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Change 231184 had a related patch set uploaded (by Jdlrobson): +Do not override login form in beta + +[[https://gerrit.wikimedia.org/r/231184]] +","Change 231184 had a related patch set uploaded (by Jdlrobson): +Do not override login form in beta + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,5,"True","['Change 231184 had a related patch set uploaded (by Jdlrobson):\nDo not override login form in beta\n\n[[GERRIT_URL]]']",NA,1,"Change 231184 had a related patch set uploaded (by Jdlrobson):\nDo not override login form in beta\n\n[[GERRIT_URL]]" +18648,"Getting rid of own login page (tracking)","Change 231146 had a related patch set uploaded (by Florianschmidtwelzow): +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]] +",1439410431,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Change 231146 had a related patch set uploaded (by Florianschmidtwelzow): +Use core login form + +[[https://gerrit.wikimedia.org/r/231146]] +","Change 231146 had a related patch set uploaded (by Florianschmidtwelzow): +Use core login form + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,5,"True","['Change 231146 had a related patch set uploaded (by Florianschmidtwelzow):\nUse core login form\n\n[[GERRIT_URL]]']",NA,1,"Change 231146 had a related patch set uploaded (by Florianschmidtwelzow):\nUse core login form\n\n[[GERRIT_URL]]" +18649,"Getting rid of own login page (tracking)","Alpha patch: I8f89bdaf3dc7fde104f199554b18486c30580910",1415036120,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","Alpha patch: I8f89bdaf3dc7fde104f199554b18486c30580910","Alpha patch: I8f89bdaf3dc7fde104f199554b18486c30580910",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-35,"True","['Alpha patch: I8f89bdaf3dc7fde104f199554b18486c30580910']",NA,1,"Alpha patch: I8f89bdaf3dc7fde104f199554b18486c30580910" +18650,"Getting rid of own login page (tracking)","**bingle-admin** wrote: + +Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/tOKYUJrd",1415036113,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-wmes5uwwfa4lhsk2s5fp","task_subcomment","**bingle-admin** wrote: + +Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/tOKYUJrd","**bingle-admin** wrote: + +Prioritization and scheduling of this bug is tracked on Trello card URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-35,"True","['**bingle-admin** wrote:\n\nPrioritization and scheduling of this bug is tracked on Trello card URL']",NA,1,"**bingle-admin** wrote:\n\nPrioritization and scheduling of this bug is tracked on Trello card URL" +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"Unable to login and reset password: ""Invalid hash given"" in all cases." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!" +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"User Yustas is having trouble with login and password reset." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"He has email entered: yustas@yustas.com." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"He tries to reset password and successfully receives reset email." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him)." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"He tried several browsers and OSes." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"Please help him." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}" +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"He hasn't been logging in for a while." +18789,"Unable to login and reset password: ""Invalid hash given"" in all cases","Unable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}",1409166420,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_description","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons https://commons.wikimedia.org/wiki/User_talk:Yustas + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","Unable to login and reset password: ""Invalid hash given"" in all cases./n/nUnable to login and reset password: ""Invalid hash given"" in all cases + +Greetings! + +User Yustas is having trouble with login and password reset. He hasn't been logging in for a while. Now, he tries to login, but can't. He has email entered: yustas@yustas.com. He tries to reset password and successfully receives reset email. But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him). He tried several browsers and OSes. + +Please help him. You can contact him directly at the email given, or at talk page at Commons URL + +-------------------------- +**Version**: wmf-deployment +**Severity**: major + +**Attached**: {F14304}","High",80,1414713212,NA,"resolved","True","c3",1,"False","False",-45,"True","['Unable to login and reset password: ""Invalid hash given"" in all cases.', 'Unable to login and reset password: ""Invalid hash given"" in all cases\n\nGreetings!', 'User Yustas is having trouble with login and password reset.', ""He hasn't been logging in for a while."", ""Now, he tries to login, but can't."", 'He has email entered: yustas@yustas.com.', 'He tries to reset password and successfully receives reset email.', 'But when he enters old and new passwords, he sees permanent ""Invalid hash given"" message (I have attached the screenshot received from him).', 'He tried several browsers and OSes.', 'Please help him.', 'You can contact him directly at the email given, or at talk page at Commons URL\n\n--------------------------\n**Version**: wmf-deployment\n**Severity**: major\n\n**Attached**: {F14304}']",TRUE,0,"Now, he tries to login, but can't." +18790,"Unable to login and reset password: ""Invalid hash given"" in all cases","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.",1414713212,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-35,"True","[""I think we fixed the general issue, and the specific user is in, so I'm going to close this."", 'Reopen if anything else is needed.']",NA,0,"Reopen if anything else is needed." +18790,"Unable to login and reset password: ""Invalid hash given"" in all cases","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.",1414713212,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.","I think we fixed the general issue, and the specific user is in, so I'm going to close this. Reopen if anything else is needed.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-35,"True","[""I think we fixed the general issue, and the specific user is in, so I'm going to close this."", 'Reopen if anything else is needed.']",NA,0,"I think we fixed the general issue, and the specific user is in, so I'm going to close this." +18791,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",1414396611,"PHID-USER-3ampiwske4lc434cm6ot","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?","(In reply to Chris Steipp from comment #10) +QUOTE +QUOTE + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +QUOTE +QUOTE + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-36,"True","['(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem.', ""We may need a DB cleanup script and/or the compatibility hack I thought we didn't need."", 'QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?', 'That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object.', 'Though why would we have :A: hashes in the DB at all?']",NA,0,"(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem." +18791,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",1414396611,"PHID-USER-3ampiwske4lc434cm6ot","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?","(In reply to Chris Steipp from comment #10) +QUOTE +QUOTE + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +QUOTE +QUOTE + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-36,"True","['(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem.', ""We may need a DB cleanup script and/or the compatibility hack I thought we didn't need."", 'QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?', 'That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object.', 'Though why would we have :A: hashes in the DB at all?']",NA,0,"QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?" +18791,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",1414396611,"PHID-USER-3ampiwske4lc434cm6ot","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?","(In reply to Chris Steipp from comment #10) +QUOTE +QUOTE + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +QUOTE +QUOTE + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-36,"True","['(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem.', ""We may need a DB cleanup script and/or the compatibility hack I thought we didn't need."", 'QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?', 'That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object.', 'Though why would we have :A: hashes in the DB at all?']",NA,0,"That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object." +18791,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",1414396611,"PHID-USER-3ampiwske4lc434cm6ot","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?","(In reply to Chris Steipp from comment #10) +QUOTE +QUOTE + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +QUOTE +QUOTE + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-36,"True","['(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem.', ""We may need a DB cleanup script and/or the compatibility hack I thought we didn't need."", 'QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?', 'That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object.', 'Though why would we have :A: hashes in the DB at all?']",NA,0,"Though why would we have :A: hashes in the DB at all?" +18791,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",1414396611,"PHID-USER-3ampiwske4lc434cm6ot","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #10) +> [...] the password was updated to +> :A::, and I couldn't login. + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +> [...] I'm not able to find a reliable +> reproduction for ending up in that state though. + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?","(In reply to Chris Steipp from comment #10) +QUOTE +QUOTE + +I think I753c135a would fix that problem. We may need a DB cleanup script and/or the compatibility hack I thought we didn't need. + +QUOTE +QUOTE + +Perhaps the user had tried to reset his password by email before attempting to log in with his existing password? That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object. Though why would we have :A: hashes in the DB at all?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-36,"True","['(In reply to Chris Steipp from comment #10)\nQUOTE\nQUOTE\n\nI think I753c135a would fix that problem.', ""We may need a DB cleanup script and/or the compatibility hack I thought we didn't need."", 'QUOTE\nQUOTE\n\nPerhaps the user had tried to reset his password by email before attempting to log in with his existing password?', 'That would cause $user->saveSettings() to be called, which to get the string to store in the DB, would call toString() on the MWOldPassword object.', 'Though why would we have :A: hashes in the DB at all?']",NA,0,"We may need a DB cleanup script and/or the compatibility hack I thought we didn't need." +18792,"Unable to login and reset password: ""Invalid hash given"" in all cases","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.",1409176403,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL + +Adding Tyler in case he has ideas.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['For the actual issue, I managed to reproduce the effect that caused the problem.', ""A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login."", ""I'm not able to find a reliable reproduction for ending up in that state though."", ""I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL\n\nAdding Tyler in case he has ideas.""]",NA,0,"For the actual issue, I managed to reproduce the effect that caused the problem." +18792,"Unable to login and reset password: ""Invalid hash given"" in all cases","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.",1409176403,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL + +Adding Tyler in case he has ideas.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['For the actual issue, I managed to reproduce the effect that caused the problem.', ""A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login."", ""I'm not able to find a reliable reproduction for ending up in that state though."", ""I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL\n\nAdding Tyler in case he has ideas.""]",NA,0,"A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login." +18792,"Unable to login and reset password: ""Invalid hash given"" in all cases","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.",1409176403,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL + +Adding Tyler in case he has ideas.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['For the actual issue, I managed to reproduce the effect that caused the problem.', ""A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login."", ""I'm not able to find a reliable reproduction for ending up in that state though."", ""I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL\n\nAdding Tyler in case he has ideas.""]",NA,0,"I'm not able to find a reliable reproduction for ending up in that state though." +18792,"Unable to login and reset password: ""Invalid hash given"" in all cases","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.",1409176403,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L1230 vs. checking $wgPasswordSalt like in https://github.com/wikimedia/mediawiki-core/blob/2f491ef504b0489afd8a85d6a145058c29c46e61/includes/User.php#L4655 + +Adding Tyler in case he has ideas.","For the actual issue, I managed to reproduce the effect that caused the problem. A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login. I'm not able to find a reliable reproduction for ending up in that state though. + +I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL + +Adding Tyler in case he has ideas.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['For the actual issue, I managed to reproduce the effect that caused the problem.', ""A user with type :A: password with a hard expired password, I logged in several times and in one case, the password was updated to :A::, and I couldn't login."", ""I'm not able to find a reliable reproduction for ending up in that state though."", ""I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL\n\nAdding Tyler in case he has ideas.""]",NA,0,"I'm a little suspicious of URL vs. checking $wgPasswordSalt like in URL\n\nAdding Tyler in case he has ideas." +18793,"Unable to login and reset password: ""Invalid hash given"" in all cases","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",1409172954,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Got it!', 'He says he has successfully logged in first on commons, then on several wikis.', 'Thank you very much!']",NA,0,"Got it!" +18793,"Unable to login and reset password: ""Invalid hash given"" in all cases","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",1409172954,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Got it!', 'He says he has successfully logged in first on commons, then on several wikis.', 'Thank you very much!']",NA,0,"He says he has successfully logged in first on commons, then on several wikis." +18793,"Unable to login and reset password: ""Invalid hash given"" in all cases","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",1409172954,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!","Got it! He says he has successfully logged in first on commons, then on several wikis. + +Thank you very much!",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Got it!', 'He says he has successfully logged in first on commons, then on several wikis.', 'Thank you very much!']",NA,0,"Thank you very much!" +18794,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #6) +> Yeah, we have a hook doing that, since their on the list of users who's +> password hashes were leaked. We could remove the username from our hook too, +> to simplify that bit. + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.",1409172487,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #6) +> Yeah, we have a hook doing that, since their on the list of users who's +> password hashes were leaked. We could remove the username from our hook too, +> to simplify that bit. + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.","(In reply to Chris Steipp from comment #6) +QUOTE +QUOTE +QUOTE + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""(In reply to Chris Steipp from comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nOk, I marked that username as having already reset their password, so they shouldn't get the reset form on login."", 'Should be able to login now.']",NA,0,"Should be able to login now." +18794,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Chris Steipp from comment #6) +> Yeah, we have a hook doing that, since their on the list of users who's +> password hashes were leaked. We could remove the username from our hook too, +> to simplify that bit. + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.",1409172487,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Chris Steipp from comment #6) +> Yeah, we have a hook doing that, since their on the list of users who's +> password hashes were leaked. We could remove the username from our hook too, +> to simplify that bit. + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.","(In reply to Chris Steipp from comment #6) +QUOTE +QUOTE +QUOTE + +Ok, I marked that username as having already reset their password, so they shouldn't get the reset form on login. Should be able to login now.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""(In reply to Chris Steipp from comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nOk, I marked that username as having already reset their password, so they shouldn't get the reset form on login."", 'Should be able to login now.']",NA,0,"(In reply to Chris Steipp from comment #6)\nQUOTE\nQUOTE\nQUOTE\n\nOk, I marked that username as having already reset their password, so they shouldn't get the reset form on login." +18795,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?",1409171933,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","[""Well, we're not able to properly understand some of the technical terms."", 'Can you please give us some simple instructions on what to do, if needed?']",NA,0,"Can you please give us some simple instructions on what to do, if needed?" +18795,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?",1409171933,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?","Well, we're not able to properly understand some of the technical terms. Can you please give us some simple instructions on what to do, if needed?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","[""Well, we're not able to properly understand some of the technical terms."", 'Can you please give us some simple instructions on what to do, if needed?']",NA,0,"Well, we're not able to properly understand some of the technical terms." +18796,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Sergei S. Rublev from comment #3) +> Not completely sure about SUL though. He says years ago he was creating +> same-username account on several wikis. +> +> He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he +> gets message about wrong password. When he types correct password, the reset +> procedure is started. + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.",1409171702,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Sergei S. Rublev from comment #3) +> Not completely sure about SUL though. He says years ago he was creating +> same-username account on several wikis. +> +> He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he +> gets message about wrong password. When he types correct password, the reset +> procedure is started. + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.","(In reply to Sergei S. Rublev from comment #3) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""(In reply to Sergei S. Rublev from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, we have a hook doing that, since their on the list of users who's password hashes were leaked."", 'We could remove the username from our hook too, to simplify that bit.']",NA,0,"We could remove the username from our hook too, to simplify that bit." +18796,"Unable to login and reset password: ""Invalid hash given"" in all cases","(In reply to Sergei S. Rublev from comment #3) +> Not completely sure about SUL though. He says years ago he was creating +> same-username account on several wikis. +> +> He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he +> gets message about wrong password. When he types correct password, the reset +> procedure is started. + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.",1409171702,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","(In reply to Sergei S. Rublev from comment #3) +> Not completely sure about SUL though. He says years ago he was creating +> same-username account on several wikis. +> +> He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he +> gets message about wrong password. When he types correct password, the reset +> procedure is started. + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.","(In reply to Sergei S. Rublev from comment #3) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Yeah, we have a hook doing that, since their on the list of users who's password hashes were leaked. We could remove the username from our hook too, to simplify that bit.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""(In reply to Sergei S. Rublev from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, we have a hook doing that, since their on the list of users who's password hashes were leaked."", 'We could remove the username from our hook too, to simplify that bit.']",NA,0,"(In reply to Sergei S. Rublev from comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nYeah, we have a hook doing that, since their on the list of users who's password hashes were leaked." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"Or it may be a valid :B: hash, and so we can just change the type." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"That shouldn't ever happen." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"I'm guessing something in there messed it up." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"I'm testing a couple solutions." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"I think we'll be able to either blank the password and let them use password reset." +18797,"Unable to login and reset password: ""Invalid hash given"" in all cases","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",1409171574,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.","Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it. That shouldn't ever happen. + +The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:. I'm guessing something in there messed it up. + +I'm testing a couple solutions. I think we'll be able to either blank the password and let them use password reset. Or it may be a valid :B: hash, and so we can just change the type. I'm working on a reproduction so I can test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","[""Well something is definitely wrong... Yustas'es password is :A: type, but has a salt stored with it."", ""That shouldn't ever happen."", 'The password api patch did a trick to pretend un-prefixed hashes were type :A:, even if password salting was used, so the hash would get upgraded to type :B:.', ""I'm guessing something in there messed it up."", ""I'm testing a couple solutions."", ""I think we'll be able to either blank the password and let them use password reset."", 'Or it may be a valid :B: hash, and so we can just change the type.', ""I'm working on a reproduction so I can test it.""]",NA,0,"I'm working on a reproduction so I can test it." +18798,"Unable to login and reset password: ""Invalid hash given"" in all cases","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.",1409169357,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['He says there is no email confirmation when he tyes correct password.', 'He immediately gets dialog presented at screenshot.']",NA,0,"He says there is no email confirmation when he tyes correct password." +18798,"Unable to login and reset password: ""Invalid hash given"" in all cases","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.",1409169357,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.","He says there is no email confirmation when he tyes correct password. He immediately gets dialog presented at screenshot.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['He says there is no email confirmation when he tyes correct password.', 'He immediately gets dialog presented at screenshot.']",NA,0,"He immediately gets dialog presented at screenshot." +18799,"Unable to login and reset password: ""Invalid hash given"" in all cases","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",1409169094,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Not completely sure about SUL though.', 'He says years ago he was creating same-username account on several wikis.', 'He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password.', 'When he types correct password, the reset procedure is started.']",NA,0,"Not completely sure about SUL though." +18799,"Unable to login and reset password: ""Invalid hash given"" in all cases","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",1409169094,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Not completely sure about SUL though.', 'He says years ago he was creating same-username account on several wikis.', 'He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password.', 'When he types correct password, the reset procedure is started.']",NA,0,"He says years ago he was creating same-username account on several wikis." +18799,"Unable to login and reset password: ""Invalid hash given"" in all cases","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",1409169094,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Not completely sure about SUL though.', 'He says years ago he was creating same-username account on several wikis.', 'He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password.', 'When he types correct password, the reset procedure is started.']",NA,0,"He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password." +18799,"Unable to login and reset password: ""Invalid hash given"" in all cases","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",1409169094,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.","Not completely sure about SUL though. He says years ago he was creating same-username account on several wikis. + +He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password. When he types correct password, the reset procedure is started.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['Not completely sure about SUL though.', 'He says years ago he was creating same-username account on several wikis.', 'He says: on commonswiki, enwiki and ruwiki: if he types wrong password, he gets message about wrong password.', 'When he types correct password, the reset procedure is started.']",NA,0,"When he types correct password, the reset procedure is started." +18800,"Unable to login and reset password: ""Invalid hash given"" in all cases","The main goal now is to login to Commons. He says he remembers he was activating SUL...",1409168261,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","The main goal now is to login to Commons. He says he remembers he was activating SUL...","The main goal now is to login to Commons. He says he remembers he was activating SUL...",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['The main goal now is to login to Commons.', 'He says he remembers he was activating SUL...']",NA,0,"The main goal now is to login to Commons." +18800,"Unable to login and reset password: ""Invalid hash given"" in all cases","The main goal now is to login to Commons. He says he remembers he was activating SUL...",1409168261,"PHID-USER-lymul4gxoprpd55zqrm5","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","The main goal now is to login to Commons. He says he remembers he was activating SUL...","The main goal now is to login to Commons. He says he remembers he was activating SUL...",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-45,"True","['The main goal now is to login to Commons.', 'He says he remembers he was activating SUL...']",NA,0,"He says he remembers he was activating SUL..." +18801,"Unable to login and reset password: ""Invalid hash given"" in all cases","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..",1409168169,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['Which Wiki is he using?', 'I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..']",NA,0,"Which Wiki is he using?" +18801,"Unable to login and reset password: ""Invalid hash given"" in all cases","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..",1409168169,"PHID-USER-6vzzsmi22zem6yttr6vp","PHID-TASK-qa72wvdgnut3fefct73m","task_subcomment","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..","Which Wiki is he using? + +I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-45,"True","['Which Wiki is he using?', 'I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed..']",NA,0,"I note he seems to have a :A: password on commonswiki, but on enwiki user_password is unprefixed, but user_newpassword is :B: prefixed.." +19098,"URGENT: CERT for old-bugzilla.wikimedia.org","**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +",1416613448,"PHID-USER-j3rt67f2xk5rpkgcegnj","PHID-TASK-rlhi7yxbtv2ak22guh73","task_description","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** CODE + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%URL +","Medium",50,1418860800,NA,"declined","True","c3",1,"False","False",-32,"True","['URGENT: CERT for old-bugzilla.wikimedia.org.', '**Author:** CODE\n\n**Description:**\n%%%Sorry for this last minute notice.%%%\n%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%%\n%%%This is related to the Bugzilla - Phabricator migration.', 'We had forgot this%%%\n%%%little detail.%%%\n%%%I can assume the cost of the CERT from the Engineering Community budget.%%%\n%%%Thank you in advance.%%%\n%%%--%%%\n%%%Quim Gil%%%\n%%%Engineering Community Manager @ Wikimedia Foundation%%%\n%%%URL']",TRUE,0,"URGENT: CERT for old-bugzilla.wikimedia.org." +19098,"URGENT: CERT for old-bugzilla.wikimedia.org","**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +",1416613448,"PHID-USER-j3rt67f2xk5rpkgcegnj","PHID-TASK-rlhi7yxbtv2ak22guh73","task_description","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** CODE + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%URL +","Medium",50,1418860800,NA,"declined","True","c3",1,"False","False",-32,"True","['URGENT: CERT for old-bugzilla.wikimedia.org.', '**Author:** CODE\n\n**Description:**\n%%%Sorry for this last minute notice.%%%\n%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%%\n%%%This is related to the Bugzilla - Phabricator migration.', 'We had forgot this%%%\n%%%little detail.%%%\n%%%I can assume the cost of the CERT from the Engineering Community budget.%%%\n%%%Thank you in advance.%%%\n%%%--%%%\n%%%Quim Gil%%%\n%%%Engineering Community Manager @ Wikimedia Foundation%%%\n%%%URL']",TRUE,0,"**Author:** CODE\n\n**Description:**\n%%%Sorry for this last minute notice.%%%\n%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%%\n%%%This is related to the Bugzilla - Phabricator migration." +19098,"URGENT: CERT for old-bugzilla.wikimedia.org","**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +",1416613448,"PHID-USER-j3rt67f2xk5rpkgcegnj","PHID-TASK-rlhi7yxbtv2ak22guh73","task_description","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** `qgil@wikimedia.org` + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%http://www.mediawiki.org/wiki/User:Qgil%%% +","URGENT: CERT for old-bugzilla.wikimedia.org./n/n**Author:** CODE + +**Description:** +%%%Sorry for this last minute notice.%%% +%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%% +%%%This is related to the Bugzilla - Phabricator migration. We had forgot this%%% +%%%little detail.%%% +%%%I can assume the cost of the CERT from the Engineering Community budget.%%% +%%%Thank you in advance.%%% +%%%--%%% +%%%Quim Gil%%% +%%%Engineering Community Manager @ Wikimedia Foundation%%% +%%%URL +","Medium",50,1418860800,NA,"declined","True","c3",1,"False","False",-32,"True","['URGENT: CERT for old-bugzilla.wikimedia.org.', '**Author:** CODE\n\n**Description:**\n%%%Sorry for this last minute notice.%%%\n%%%Can we get a CERT for old-bugzilla.wikimedia.org?%%%\n%%%This is related to the Bugzilla - Phabricator migration.', 'We had forgot this%%%\n%%%little detail.%%%\n%%%I can assume the cost of the CERT from the Engineering Community budget.%%%\n%%%Thank you in advance.%%%\n%%%--%%%\n%%%Quim Gil%%%\n%%%Engineering Community Manager @ Wikimedia Foundation%%%\n%%%URL']",TRUE,0,"We had forgot this%%%\n%%%little detail.%%%\n%%%I can assume the cost of the CERT from the Engineering Community budget.%%%\n%%%Thank you in advance.%%%\n%%%--%%%\n%%%Quim Gil%%%\n%%%Engineering Community Manager @ Wikimedia Foundation%%%\n%%%URL" +19099,"URGENT: CERT for old-bugzilla.wikimedia.org","//Status changed from 'open' to 'rejected' by dzahn//",1416882171,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","//Status changed from 'open' to 'rejected' by dzahn//","//Status changed from 'open' to 'rejected' by dzahn//",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","[""//Status changed from 'open' to 'rejected' by dzahn//""]",NA,0,"//Status changed from 'open' to 'rejected' by dzahn//" +19100,"URGENT: CERT for old-bugzilla.wikimedia.org","//Status changed from 'new' to 'open' by RT_System//",1416882163,"PHID-USER-j3rt67f2xk5rpkgcegnj","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","//Status changed from 'new' to 'open' by RT_System//","//Status changed from 'new' to 'open' by RT_System//",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-32,"True","[""//Status changed from 'new' to 'open' by RT_System//""]",NA,0,"//Status changed from 'new' to 'open' by RT_System//" +19101,"URGENT: CERT for old-bugzilla.wikimedia.org","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%https://gerrit.wikimedia.org/r/#/c/175595/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175601/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175615/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175646/%%% +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%",1416882162,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%https://gerrit.wikimedia.org/r/#/c/175595/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175601/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175615/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175646/%%% +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%URL +%%%URL +%%%URL +%%%URL +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","['%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%%\n%%%instead.%%%\n%%%that way it gets to use the wildcard *.wikimedia.org cert and we don\'t have to%%%\n%%%buy anything, but the error should be gone.%%%\n%%%related changes:%%%\n%%%URL\n%%%URL\n%%%URL\n%%%URL\n%%%so the issue is resolved but i\'m technically saying ""rejected"" because we won\'t%%%\n%%%buy a new cert :)%%%']",NA,0,"%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%%\n%%%instead.%%%\n%%%that way it gets to use the wildcard *.wikimedia.org cert and we don\" +19101,"URGENT: CERT for old-bugzilla.wikimedia.org","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%https://gerrit.wikimedia.org/r/#/c/175595/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175601/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175615/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175646/%%% +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%",1416882162,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%https://gerrit.wikimedia.org/r/#/c/175595/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175601/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175615/%%% +%%%https://gerrit.wikimedia.org/r/#/c/175646/%%% +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%","%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%% +%%%instead.%%% +%%%that way it gets to use the wildcard *.wikimedia.org cert and we don't have to%%% +%%%buy anything, but the error should be gone.%%% +%%%related changes:%%% +%%%URL +%%%URL +%%%URL +%%%URL +%%%so the issue is resolved but i'm technically saying ""rejected"" because we won't%%% +%%%buy a new cert :)%%%",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","['%%%we solved this issue by moving old-bugzilla behind misc-web varnish/nginx layer%%%\n%%%instead.%%%\n%%%that way it gets to use the wildcard *.wikimedia.org cert and we don\'t have to%%%\n%%%buy anything, but the error should be gone.%%%\n%%%related changes:%%%\n%%%URL\n%%%URL\n%%%URL\n%%%URL\n%%%so the issue is resolved but i\'m technically saying ""rejected"" because we won\'t%%%\n%%%buy a new cert :)%%%']",NA,0,"m technically saying ""rejected"" because we won\" +19102,"URGENT: CERT for old-bugzilla.wikimedia.org","Issue taken by **dzahn**",1416882058,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","Issue taken by **dzahn**","Issue taken by **dzahn**",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","['Issue taken by **dzahn**']",NA,0,"Issue taken by **dzahn**" +19103,"URGENT: CERT for old-bugzilla.wikimedia.org","//Subject changed from 'Fwd: Ticket creation failed: URGENT: CERT for old-bugzilla.wikimedia.org' to 'URGENT: CERT for old-bugzilla.wikimedia.org' by aklapper//",1416614021,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","//Subject changed from 'Fwd: Ticket creation failed: URGENT: CERT for old-bugzilla.wikimedia.org' to 'URGENT: CERT for old-bugzilla.wikimedia.org' by aklapper//","//Subject changed from 'Fwd: Ticket creation failed: URGENT: CERT for old-bugzilla.wikimedia.org' to 'URGENT: CERT for old-bugzilla.wikimedia.org' by aklapper//",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","[""//Subject changed from 'Fwd: Ticket creation failed: URGENT: CERT for old-bugzilla.wikimedia.org' to 'URGENT: CERT for old-bugzilla.wikimedia.org' by aklapper//""]",NA,0,"//Subject changed from 'Fwd: Ticket creation failed: URGENT: CERT for old-bugzilla.wikimedia.org' to 'URGENT: CERT for old-bugzilla.wikimedia.org' by aklapper//" +19104,"URGENT: CERT for old-bugzilla.wikimedia.org","//Cc aklapper added by aklapper//",1416614008,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-rlhi7yxbtv2ak22guh73","task_subcomment","//Cc aklapper added by aklapper//","//Cc aklapper added by aklapper//",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","['//Cc aklapper added by aklapper//']",NA,0,"//Cc aklapper added by aklapper//" +19726,"Wikimedia Commons support for Flickr HTTPS","Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr",1396091160,"PHID-USER-uhn27l5qsridnw4vbhko","PHID-TASK-ucww6xpqaxu7libepgi6","task_description","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: URL","Medium",50,1447576284,"PHID-USER-6dmbpidylyt4dzsxzjg4","resolved","True","c3",1,"False","False",-66,"True","['Wikimedia Commons support for Flickr HTTPS.', ""Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet)."", 'Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up:\n\n The source must be a URL pointing to the image description at Flickr.', '--------------------------\n**Version**: 1.23.0\n**Severity**: enhancement\n**URL**: URL']",FALSE,0,"Wikimedia Commons support for Flickr HTTPS." +19726,"Wikimedia Commons support for Flickr HTTPS","Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr",1396091160,"PHID-USER-uhn27l5qsridnw4vbhko","PHID-TASK-ucww6xpqaxu7libepgi6","task_description","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: URL","Medium",50,1447576284,"PHID-USER-6dmbpidylyt4dzsxzjg4","resolved","True","c3",1,"False","False",-66,"True","['Wikimedia Commons support for Flickr HTTPS.', ""Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet)."", 'Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up:\n\n The source must be a URL pointing to the image description at Flickr.', '--------------------------\n**Version**: 1.23.0\n**Severity**: enhancement\n**URL**: URL']",FALSE,0,"Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up:\n\n The source must be a URL pointing to the image description at Flickr." +19726,"Wikimedia Commons support for Flickr HTTPS","Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr",1396091160,"PHID-USER-uhn27l5qsridnw4vbhko","PHID-TASK-ucww6xpqaxu7libepgi6","task_description","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: URL","Medium",50,1447576284,"PHID-USER-6dmbpidylyt4dzsxzjg4","resolved","True","c3",1,"False","False",-66,"True","['Wikimedia Commons support for Flickr HTTPS.', ""Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet)."", 'Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up:\n\n The source must be a URL pointing to the image description at Flickr.', '--------------------------\n**Version**: 1.23.0\n**Severity**: enhancement\n**URL**: URL']",FALSE,0,"--------------------------\n**Version**: 1.23.0\n**Severity**: enhancement\n**URL**: URL" +19726,"Wikimedia Commons support for Flickr HTTPS","Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr",1396091160,"PHID-USER-uhn27l5qsridnw4vbhko","PHID-TASK-ucww6xpqaxu7libepgi6","task_description","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: https://commons.wikimedia.org/w/index.php?title=Special:Upload&uselang=fromflickr","Wikimedia Commons support for Flickr HTTPS./n/nRecent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet). Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up: + + The source must be a URL pointing to the image description at Flickr. + +-------------------------- +**Version**: 1.23.0 +**Severity**: enhancement +**URL**: URL","Medium",50,1447576284,"PHID-USER-6dmbpidylyt4dzsxzjg4","resolved","True","c3",1,"False","False",-66,"True","['Wikimedia Commons support for Flickr HTTPS.', ""Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet)."", 'Specifically when inputting an HTTPS URL into the ""Original source"" field this error pops up:\n\n The source must be a URL pointing to the image description at Flickr.', '--------------------------\n**Version**: 1.23.0\n**Severity**: enhancement\n**URL**: URL']",FALSE,0,"Recent switchover to HTTPS protocol for Flickr is throwing errors not only for FlickreviewR bot but also for Special:Upload (and possibly UploadWizard but I haven't checked yet)." +19727,"Wikimedia Commons support for Flickr HTTPS","https://commons.wikimedia.org/w/index.php?title=MediaWiki:UploadForm.js&diff=prev&oldid=122410947",1447576284,"PHID-USER-6dmbpidylyt4dzsxzjg4","PHID-TASK-ucww6xpqaxu7libepgi6","task_subcomment","https://commons.wikimedia.org/w/index.php?title=MediaWiki:UploadForm.js&diff=prev&oldid=122410947","URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,19,"True","['URL']",NA,0,"URL" +19728,"Wikimedia Commons support for Flickr HTTPS","I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed).",1406084918,"PHID-USER-dpu5hmqvprhycqlkdzrk","PHID-TASK-ucww6xpqaxu7libepgi6","task_subcomment","I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed).","I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-50,"True","['I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed).']",NA,0,"I think this might be an issue with commons javascript and not mediawiki (In which case it would have to be filed with the commons folks in order to be fixed)." +19729,"Wikimedia Commons support for Flickr HTTPS","Testing with UploadWizard welcome (see bug 43450 for a list of Flickr issues)",1396257963,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-ucww6xpqaxu7libepgi6","task_subcomment","Testing with UploadWizard welcome (see bug 43450 for a list of Flickr issues)","Testing with UploadWizard welcome (see bug 43450 for a list of Flickr issues)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-66,"True","['Testing with UploadWizard welcome (see bug 43450 for a list of Flickr issues)']",NA,0,"Testing with UploadWizard welcome (see bug 43450 for a list of Flickr issues)" +19850,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal",1389634920,"PHID-USER-uqcn2l4ng4murmyfnvyp","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_description","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Medium",50,1391534698,NA,"resolved","True","c3",1,"True","False",-77,"True","['Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes.', ""Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method."", 'But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects.', '--------------------------\n**Version**: 1.23.0\n**Severity**: normal']",TRUE,0,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes." +19850,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal",1389634920,"PHID-USER-uqcn2l4ng4murmyfnvyp","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_description","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Medium",50,1391534698,NA,"resolved","True","c3",1,"True","False",-77,"True","['Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes.', ""Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method."", 'But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects.', '--------------------------\n**Version**: 1.23.0\n**Severity**: normal']",TRUE,0,"But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects." +19850,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal",1389634920,"PHID-USER-uqcn2l4ng4murmyfnvyp","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_description","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Medium",50,1391534698,NA,"resolved","True","c3",1,"True","False",-77,"True","['Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes.', ""Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method."", 'But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects.', '--------------------------\n**Version**: 1.23.0\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: 1.23.0\n**Severity**: normal" +19850,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal",1389634920,"PHID-USER-uqcn2l4ng4murmyfnvyp","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_description","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes./n/nGerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method. + +But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects. + +-------------------------- +**Version**: 1.23.0 +**Severity**: normal","Medium",50,1391534698,NA,"resolved","True","c3",1,"True","False",-77,"True","['Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes.', ""Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method."", 'But then Gerrit change 47821 broke things worse by changing Special:UserLogin to pass a raw string rather than a Message object or message key as Status::newFatal expects.', '--------------------------\n**Version**: 1.23.0\n**Severity**: normal']",TRUE,0,"Gerrit change 17952 changed Special:UserLogin to return a Status object from the account creation function, passing it a RawMessage which breaks the expectation of the API's dieStatus method that it can get a sane key from the message object's getKey method." +19851,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 111113 merged by MaxSem: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/111113",1391470005,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 111113 merged by MaxSem: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/111113","Change 111113 merged by MaxSem: +Add Status outparam for AbortNewAccount hook to fix API error handling + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-74,"True","['Change 111113 merged by MaxSem:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL']",NA,0,"Change 111113 merged by MaxSem:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL" +19852,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 111118 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/111118",1391469878,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 111118 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/111118","Change 111118 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-74,"True","['Change 111118 merged by jenkins-bot:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL']",NA,0,"Change 111118 merged by jenkins-bot:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL" +19853,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 111118 had a related patch set uploaded by MaxSem: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/111118",1391469822,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 111118 had a related patch set uploaded by MaxSem: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/111118","Change 111118 had a related patch set uploaded by MaxSem: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-74,"True","['Change 111118 had a related patch set uploaded by MaxSem:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL']",NA,0,"Change 111118 had a related patch set uploaded by MaxSem:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL" +19854,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 111113 had a related patch set uploaded by JGonera: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/111113",1391469016,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 111113 had a related patch set uploaded by JGonera: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/111113","Change 111113 had a related patch set uploaded by JGonera: +Add Status outparam for AbortNewAccount hook to fix API error handling + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-74,"True","['Change 111113 had a related patch set uploaded by JGonera:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL']",NA,0,"Change 111113 had a related patch set uploaded by JGonera:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL" +19855,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 108088 merged by jenkins-bot: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/108088",1390508822,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 108088 merged by jenkins-bot: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/108088","Change 108088 merged by jenkins-bot: +Add Status outparam for AbortNewAccount hook to fix API error handling + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-75,"True","['Change 108088 merged by jenkins-bot:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL']",NA,0,"Change 108088 merged by jenkins-bot:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL" +19856,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 108089 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/108089",1390001573,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 108089 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/108089","Change 108089 merged by jenkins-bot: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['Change 108089 merged by jenkins-bot:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL']",NA,0,"Change 108089 merged by jenkins-bot:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL" +19857,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Yay! :)",1389994644,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Yay! :)","Yay! :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","['Yay!', ':)']",NA,0,"Yay!" +19857,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Yay! :)",1389994644,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Yay! :)","Yay! :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","['Yay!', ':)']",NA,0,":)" +19858,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","(In reply to comment #6) +> Any strong objections to using this existing approach as a basic fix? + +Nope (as indicated by my +1).",1389992813,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","(In reply to comment #6) +> Any strong objections to using this existing approach as a basic fix? + +Nope (as indicated by my +1).","(In reply to comment #6) +QUOTE + +Nope (as indicated by my +1).",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['(In reply to comment #6)\nQUOTE\n\nNope (as indicated by my +1).']",NA,0,"(In reply to comment #6)\nQUOTE\n\nNope (as indicated by my +1)." +19859,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","(In reply to comment #3) +> The issue here is that the Status class is too intertwined with the Message +> class, and this was even before RawMessage was introduced. When you made a +> Status object, it was assumed any error keys were backed by messages. +> +> The solution should be that the concerns need to be separated. The Status +> class +> should not have anything to do with the Message class. However, that may be a +> bit difficult to achieve, so at the very least there needs to be a separation +> between error codes and message keys. + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?",1389992375,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","(In reply to comment #3) +> The issue here is that the Status class is too intertwined with the Message +> class, and this was even before RawMessage was introduced. When you made a +> Status object, it was assumed any error keys were backed by messages. +> +> The solution should be that the concerns need to be separated. The Status +> class +> should not have anything to do with the Message class. However, that may be a +> bit difficult to achieve, so at the very least there needs to be a separation +> between error codes and message keys. + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?","(In reply to comment #3) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","[""(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going."", 'Any strong objections to using this existing approach as a basic fix?']",NA,0,"Any strong objections to using this existing approach as a basic fix?" +19859,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","(In reply to comment #3) +> The issue here is that the Status class is too intertwined with the Message +> class, and this was even before RawMessage was introduced. When you made a +> Status object, it was assumed any error keys were backed by messages. +> +> The solution should be that the concerns need to be separated. The Status +> class +> should not have anything to do with the Message class. However, that may be a +> bit difficult to achieve, so at the very least there needs to be a separation +> between error codes and message keys. + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?",1389992375,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","(In reply to comment #3) +> The issue here is that the Status class is too intertwined with the Message +> class, and this was even before RawMessage was introduced. When you made a +> Status object, it was assumed any error keys were backed by messages. +> +> The solution should be that the concerns need to be separated. The Status +> class +> should not have anything to do with the Message class. However, that may be a +> bit difficult to achieve, so at the very least there needs to be a separation +> between error codes and message keys. + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?","(In reply to comment #3) +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +I'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going. Any strong objections to using this existing approach as a basic fix?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","[""(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going."", 'Any strong objections to using this existing approach as a basic fix?']",NA,0,"(In reply to comment #3)\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI'd rather not redo the entire interface of SpecialUserlogin and ApiCreateAccount just to get this going." +19860,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 108089 had a related patch set uploaded by Brion VIBBER: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/108089",1389990977,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 108089 had a related patch set uploaded by Brion VIBBER: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +https://gerrit.wikimedia.org/r/108089","Change 108089 had a related patch set uploaded by Brion VIBBER: +Update ConfirmEdit to return Status object on AbortNewAccount hook + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['Change 108089 had a related patch set uploaded by Brion VIBBER:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL']",NA,0,"Change 108089 had a related patch set uploaded by Brion VIBBER:\nUpdate ConfirmEdit to return Status object on AbortNewAccount hook\n\nGERRIT_URL" +19861,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Change 108088 had a related patch set uploaded by Brion VIBBER: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/108088",1389990808,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Change 108088 had a related patch set uploaded by Brion VIBBER: +Add Status outparam for AbortNewAccount hook to fix API error handling + +https://gerrit.wikimedia.org/r/108088","Change 108088 had a related patch set uploaded by Brion VIBBER: +Add Status outparam for AbortNewAccount hook to fix API error handling + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['Change 108088 had a related patch set uploaded by Brion VIBBER:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL']",NA,0,"Change 108088 had a related patch set uploaded by Brion VIBBER:\nAdd Status outparam for AbortNewAccount hook to fix API error handling\n\nGERRIT_URL" +19862,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",1389990545,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced.', 'When you made a Status object, it was assumed any error keys were backed by messages.', 'The solution should be that the concerns need to be separated.', 'The Status class should not have anything to do with the Message class.', 'However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.']",NA,0,"The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced." +19862,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",1389990545,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced.', 'When you made a Status object, it was assumed any error keys were backed by messages.', 'The solution should be that the concerns need to be separated.', 'The Status class should not have anything to do with the Message class.', 'However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.']",NA,0,"When you made a Status object, it was assumed any error keys were backed by messages." +19862,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",1389990545,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced.', 'When you made a Status object, it was assumed any error keys were backed by messages.', 'The solution should be that the concerns need to be separated.', 'The Status class should not have anything to do with the Message class.', 'However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.']",NA,0,"The solution should be that the concerns need to be separated." +19862,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",1389990545,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced.', 'When you made a Status object, it was assumed any error keys were backed by messages.', 'The solution should be that the concerns need to be separated.', 'The Status class should not have anything to do with the Message class.', 'However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.']",NA,0,"The Status class should not have anything to do with the Message class." +19862,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",1389990545,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.","The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced. When you made a Status object, it was assumed any error keys were backed by messages. + +The solution should be that the concerns need to be separated. The Status class should not have anything to do with the Message class. However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-76,"True","['The issue here is that the Status class is too intertwined with the Message class, and this was even before RawMessage was introduced.', 'When you made a Status object, it was assumed any error keys were backed by messages.', 'The solution should be that the concerns need to be separated.', 'The Status class should not have anything to do with the Message class.', 'However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys.']",NA,0,"However, that may be a bit difficult to achieve, so at the very least there needs to be a separation between error codes and message keys." +19863,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...",1389988805,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","['I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error.', 'Lemme try...']",NA,0,"I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error." +19863,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...",1389988805,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...","I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error. Lemme try...",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","['I think the thing to do here is to allow sending back a *useful* Status object from the hook in place of just a string, which should be able to return a sane error.', 'Lemme try...']",NA,0,"Lemme try..." +19864,"Special:UserLogin calls Status::newFatal incorrectly on account creation, generates odd API error codes","Taking this as we want this to work smoothly for mobile apps.",1389987946,"PHID-USER-yek7ymogrv4qc67oilhf","PHID-TASK-iaxgsj6ezhpsebgwzwht","task_subcomment","Taking this as we want this to work smoothly for mobile apps.","Taking this as we want this to work smoothly for mobile apps.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-76,"True","['Taking this as we want this to work smoothly for mobile apps.']",NA,0,"Taking this as we want this to work smoothly for mobile apps." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"P.s." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,": Yes, the banner as a whole takes more space than is available for the article (T108256)." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}" +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"Can't see or click login button due to fundraising banner." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything." +20015,"Can't see or click login button due to fundraising banner","Trying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}",1413268380,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_description","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Can't see or click login button due to fundraising banner./n/nTrying to click the login button with a fundraising banner in my way + +The image speaks by itself. + +Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything. + +P.s.: Yes, the banner as a whole takes more space than is available for the article (T108256). I guess that's a milestone too. + +-------------------------- +**Version**: unspecified +**Severity**: normal +**OS**: Linux +**Platform**: PC + +**Attached**: {F15045}","Low",25,1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","invalid","True","c3",1,"True","False",-38,"True","[""Can't see or click login button due to fundraising banner."", 'Trying to click the login button with a fundraising banner in my way\n\nThe image speaks by itself.', ""Yes, if I know there is a register/login button I can move the cursor away and then back, but this doesn't help anything."", 'P.s.', ': Yes, the banner as a whole takes more space than is available for the article (T108256).', ""I guess that's a milestone too."", '--------------------------\n**Version**: unspecified\n**Severity**: normal\n**OS**: Linux\n**Platform**: PC\n\n**Attached**: {F15045}']",FALSE,0,"I guess that's a milestone too." +20016,"Can't see or click login button due to fundraising banner","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,123,"True","['This ticket is from 2014.', ""We probably don't even use that particular banner anymore."", 'Can be reopened if the issue is encountered again.']",NA,0,"This ticket is from 2014." +20016,"Can't see or click login button due to fundraising banner","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,123,"True","['This ticket is from 2014.', ""We probably don't even use that particular banner anymore."", 'Can be reopened if the issue is encountered again.']",NA,0,"Can be reopened if the issue is encountered again." +20016,"Can't see or click login button due to fundraising banner","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",1510237483,"PHID-USER-wrimmmr5w2zt7nk2t753","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.","This ticket is from 2014. We probably don't even use that particular banner anymore. Can be reopened if the issue is encountered again.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,123,"True","['This ticket is from 2014.', ""We probably don't even use that particular banner anymore."", 'Can be reopened if the issue is encountered again.']",NA,0,"We probably don't even use that particular banner anymore." +20017,"Can't see or click login button due to fundraising banner","I'm not sure how this task is low priority.",1445447223,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","I'm not sure how this task is low priority.","I'm not sure how this task is low priority.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","[""I'm not sure how this task is low priority.""]",NA,0,"I'm not sure how this task is low priority." +20018,"Can't see or click login button due to fundraising banner","Should this be blocked on something about fullscreen banners?",1445413988,"PHID-USER-p6hvqn5njgnxuagekh4b","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","Should this be blocked on something about fullscreen banners?","Should this be blocked on something about fullscreen banners?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['Should this be blocked on something about fullscreen banners?']",NA,0,"Should this be blocked on something about fullscreen banners?" +20019,"Can't see or click login button due to fundraising banner","LOL, even https://archive.today/TSorY does ""better"", one can see the buttons in transparency.",1417029913,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","LOL, even https://archive.today/TSorY does ""better"", one can see the buttons in transparency.","LOL, even URL does ""better"", one can see the buttons in transparency.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-32,"True","['LOL, even URL does ""better"", one can see the buttons in transparency.']",NA,0,"LOL, even URL does ""better"", one can see the buttons in transparency." +20020,"Can't see or click login button due to fundraising banner","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",1416314211,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.","(In reply to Peter Coombe from comment #5) +QUOTE +QUOTE + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered."", '* Dismissing upon click.', '* Using some transparency so that the button is partly visible behind the banner.', '* Pushing the page down so that everything is visible below the banner.', '* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.']",NA,0,"* Dismissing upon click." +20020,"Can't see or click login button due to fundraising banner","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",1416314211,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.","(In reply to Peter Coombe from comment #5) +QUOTE +QUOTE + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered."", '* Dismissing upon click.', '* Using some transparency so that the button is partly visible behind the banner.', '* Pushing the page down so that everything is visible below the banner.', '* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.']",NA,0,"* Using some transparency so that the button is partly visible behind the banner." +20020,"Can't see or click login button due to fundraising banner","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",1416314211,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.","(In reply to Peter Coombe from comment #5) +QUOTE +QUOTE + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered."", '* Dismissing upon click.', '* Using some transparency so that the button is partly visible behind the banner.', '* Pushing the page down so that everything is visible below the banner.', '* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.']",NA,0,"* Pushing the page down so that everything is visible below the banner." +20020,"Can't see or click login button due to fundraising banner","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",1416314211,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.","(In reply to Peter Coombe from comment #5) +QUOTE +QUOTE + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered."", '* Dismissing upon click.', '* Using some transparency so that the button is partly visible behind the banner.', '* Pushing the page down so that everything is visible below the banner.', '* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.']",NA,0,"* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools." +20020,"Can't see or click login button due to fundraising banner","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",1416314211,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Peter Coombe from comment #5) +> suggestions for a better +> way to do it are always welcome. + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.","(In reply to Peter Coombe from comment #5) +QUOTE +QUOTE + +* Not using the full width, so that the login button isn't covered. +* Dismissing upon click. +* Using some transparency so that the button is partly visible behind the banner. +* Pushing the page down so that everything is visible below the banner. +* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered."", '* Dismissing upon click.', '* Using some transparency so that the button is partly visible behind the banner.', '* Pushing the page down so that everything is visible below the banner.', '* Uncollapse towards the top rather than the bottom, by covering part of the banner rather than the content and personal tools.']",NA,0,"(In reply to Peter Coombe from comment #5)\nQUOTE\nQUOTE\n\n* Not using the full width, so that the login button isn't covered." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"The alternatives are to always show it, and make the whole banner bigger by default." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"You also seem to be overriding font settings, which is making the banner appear larger than it would normally." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"That part of the banner only appears when a user's cursor is over the banner." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"As for the overall size, it looks like you're using a browser width of 1024px." +20021,"Can't see or click login button due to fundraising banner","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",1416313334,"PHID-USER-grgqimagqq3ankitlzm5","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.","That part of the banner only appears when a user's cursor is over the banner. It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors. The alternatives are to always show it, and make the whole banner bigger by default. Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space. I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome. + +As for the overall size, it looks like you're using a browser width of 1024px. Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them. You also seem to be overriding font settings, which is making the banner appear larger than it would normally.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-33,"True","[""That part of the banner only appears when a user's cursor is over the banner."", ""It is the most unobtrusive way we've found to present the information which we are legally obliged to display to donors."", 'The alternatives are to always show it, and make the whole banner bigger by default.', 'Or we can add extra space below the banner so that it never covers the log in links, at which point people will complain that we are wasting space.', ""I'm going to close this as WONTFIX, although suggestions for a better way to do it are always welcome."", ""As for the overall size, it looks like you're using a browser width of 1024px."", ""Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them."", 'You also seem to be overriding font settings, which is making the banner appear larger than it would normally.']",NA,0,"Estimates are that only around 6% of users have their browser at or below this size, but I'll see if we can add some media queries to reduce the font-size for them." +20022,"Can't see or click login button due to fundraising banner","Thanks Nemo! Added info to https://www.mediawiki.org/w/index.php?title=Bug_management%2FHow_to_triage&diff=1241213&oldid=1041070",1414415751,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","Thanks Nemo! Added info to https://www.mediawiki.org/w/index.php?title=Bug_management%2FHow_to_triage&diff=1241213&oldid=1041070","Thanks Nemo! Added info to URL",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-36,"True","['Thanks Nemo!', 'Added info to URL']",NA,0,"Thanks Nemo!" +20022,"Can't see or click login button due to fundraising banner","Thanks Nemo! Added info to https://www.mediawiki.org/w/index.php?title=Bug_management%2FHow_to_triage&diff=1241213&oldid=1041070",1414415751,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","Thanks Nemo! Added info to https://www.mediawiki.org/w/index.php?title=Bug_management%2FHow_to_triage&diff=1241213&oldid=1041070","Thanks Nemo! Added info to URL",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-36,"True","['Thanks Nemo!', 'Added info to URL']",NA,0,"Added info to URL" +20023,"Can't see or click login button due to fundraising banner","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",1413369387,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.","(In reply to Andre Klapper from comment #2) +QUOTE + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['(In reply to Andre Klapper from comment #2)\nQUOTE\n\n?force=1&banner=$name.', 'Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]].', 'Oh, there\'s even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.']",NA,0,"(In reply to Andre Klapper from comment #2)\nQUOTE\n\n?force=1&banner=$name." +20023,"Can't see or click login button due to fundraising banner","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",1413369387,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.","(In reply to Andre Klapper from comment #2) +QUOTE + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['(In reply to Andre Klapper from comment #2)\nQUOTE\n\n?force=1&banner=$name.', 'Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]].', 'Oh, there\'s even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.']",NA,0,"Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]." +20023,"Can't see or click login button due to fundraising banner","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",1413369387,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.","(In reply to Andre Klapper from comment #2) +QUOTE + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['(In reply to Andre Klapper from comment #2)\nQUOTE\n\n?force=1&banner=$name.', 'Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]].', 'Oh, there\'s even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.']",NA,0,"Oh, there\" +20023,"Can't see or click login button due to fundraising banner","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",1413369387,"PHID-USER-v7bwpq3rs3zdxegibdbh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","(In reply to Andre Klapper from comment #2) +> Hmm, what was the URL parameter to enforce showing that banner... + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.","(In reply to Andre Klapper from comment #2) +QUOTE + +?force=1&banner=$name. Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]]. Oh, there's even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['(In reply to Andre Klapper from comment #2)\nQUOTE\n\n?force=1&banner=$name.', 'Names can be retrieved from the banners associated to active (green) campaigns at [[m:Special:CentralNotice]].', 'Oh, there\'s even an ""on-wiki preview"" link now from [[m:Special:CentralNoticeBanners]] and individual banner pages.']",NA,0,"on-wiki preview" +20024,"Can't see or click login button due to fundraising banner","Hmm, what was the URL parameter to enforce showing that banner...",1413368730,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","Hmm, what was the URL parameter to enforce showing that banner...","Hmm, what was the URL parameter to enforce showing that banner...",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['Hmm, what was the URL parameter to enforce showing that banner...']",NA,0,"Hmm, what was the URL parameter to enforce showing that banner..." +20025,"Can't see or click login button due to fundraising banner","Please provide browser information for such rendering issues...",1413283668,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-3zvnakisitc6ddoo67vb","task_subcomment","Please provide browser information for such rendering issues...","Please provide browser information for such rendering issues...",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-38,"True","['Please provide browser information for such rendering issues...']",NA,0,"Please provide browser information for such rendering issues..." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"on loginwiki." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Please choose a different name." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"This one has 6!" +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"attempts, 5 of which fail." +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: normal" +20163,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","I think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal",1405383660,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_description","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki./n/nI think this is a race condition of some kind: + +2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username]) +2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed. Here's a scarier one: + +2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2]) +2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. +Please choose a different name. + +This one has 6! attempts, 5 of which fail. + +-------------------------- +**Version**: unspecified +**Severity**: normal","Low",25,1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","resolved","True","c3",1,"True","False",-51,"True","['CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'on loginwiki.', 'I think this is a race condition of some kind:\n\n2014-07-14 23:44:02 mw1209 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username])\n2014-07-14 23:44:02 mw1049 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'For some reason, there were two simultaneous autocreation attempts, one succeeded, and the other of course failed.', ""Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use."", 'Please choose a different name.', '2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', '2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1038 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use.', 'Please choose a different name.', 'This one has 6!', 'attempts, 5 of which fail.', '--------------------------\n**Version**: unspecified\n**Severity**: normal']",FALSE,0,"Here's a scarier one:\n\n2014-07-14 23:44:53 mw1150 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1062 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1019 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1187 loginwiki: CentralAuthHooks::attemptAddUser: creating new user ([username2])\n2014-07-14 23:44:53 mw1174 loginwiki: CentralAuthHooks::attemptAddUser: failed with message Username entered already in use." +20164,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","The warning disappeared from the logs pretty much the same time the patch was deployed, and no ill effects were reported.",1457056180,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","The warning disappeared from the logs pretty much the same time the patch was deployed, and no ill effects were reported.","The warning disappeared from the logs pretty much the same time the patch was deployed, and no ill effects were reported.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,35,"True","['The warning disappeared from the logs pretty much the same time the patch was deployed, and no ill effects were reported.']",NA,0,"The warning disappeared from the logs pretty much the same time the patch was deployed, and no ill effects were reported." +20165,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","Change 272835 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/272835]]",1456273045,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","Change 272835 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/272835]]","Change 272835 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,33,"True","['Change 272835 merged by jenkins-bot:\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]']",NA,0,"Change 272835 merged by jenkins-bot:\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]" +20166,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","Change 272835 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/272835]] +",1456262662,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","Change 272835 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/272835]] +","Change 272835 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,33,"True","['Change 272835 had a related patch set uploaded (by Gergő Tisza):\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]']",NA,0,"Change 272835 had a related patch set uploaded (by Gergő Tisza):\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]" +20167,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","Change 271460 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/271460]]",1455814314,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","Change 271460 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/271460]]","Change 271460 merged by jenkins-bot: +Do not unauthenticate if autocreation fails due to a race + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,33,"True","['Change 271460 merged by jenkins-bot:\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]']",NA,0,"Change 271460 merged by jenkins-bot:\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]" +20168,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","Change 271460 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/271460]] +",1455761898,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","Change 271460 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[https://gerrit.wikimedia.org/r/271460]] +","Change 271460 had a related patch set uploaded (by Gergő Tisza): +Do not unauthenticate if autocreation fails due to a race + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,33,"True","['Change 271460 had a related patch set uploaded (by Gergő Tisza):\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]']",NA,0,"Change 271460 had a related patch set uploaded (by Gergő Tisza):\nDo not unauthenticate if autocreation fails due to a race\n\n[[GERRIT_URL]]" +20169,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","``` +tgr@fluorine:~$ zcat /a/mw-log/archive/CentralAuth-Bug39996.log-20151215.gz | grep 'Username entered already in use.' | wc -l +1681 +``` +https://logstash.wikimedia.org/#dashboard/temp/AVLx4-B5ptxhN1Xap4QK +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.",1455757280,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","``` +tgr@fluorine:~$ zcat /a/mw-log/archive/CentralAuth-Bug39996.log-20151215.gz | grep 'Username entered already in use.' | wc -l +1681 +``` +https://logstash.wikimedia.org/#dashboard/temp/AVLx4-B5ptxhN1Xap4QK +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.","``CODE`` +URL +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,33,"True","[""``CODE``\nURL\n1445\n\nSo it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054)."", 'Nevertheless, should be an easy fix.']",NA,0,"Nevertheless, should be an easy fix." +20169,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","``` +tgr@fluorine:~$ zcat /a/mw-log/archive/CentralAuth-Bug39996.log-20151215.gz | grep 'Username entered already in use.' | wc -l +1681 +``` +https://logstash.wikimedia.org/#dashboard/temp/AVLx4-B5ptxhN1Xap4QK +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.",1455757280,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","``` +tgr@fluorine:~$ zcat /a/mw-log/archive/CentralAuth-Bug39996.log-20151215.gz | grep 'Username entered already in use.' | wc -l +1681 +``` +https://logstash.wikimedia.org/#dashboard/temp/AVLx4-B5ptxhN1Xap4QK +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.","``CODE`` +URL +1445 + +So it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054). Nevertheless, should be an easy fix.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,33,"True","[""``CODE``\nURL\n1445\n\nSo it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054)."", 'Nevertheless, should be an easy fix.']",NA,0,"``CODE``\nURL\n1445\n\nSo it does not seem like this bug has been significantly affected by SessionManager (and as such it's probably not the reason for T125054)." +20170,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki",">>! In T70012#1141762, @Aklapper wrote: +> Anybody knows if this is still an issue nowadays? + +Happens fairly often, yes (on the scale of 1/s). https://logstash.wikimedia.org/#dashboard/temp/AVLTn06zptxhN1XaS38e",1455249439,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment",">>! In T70012#1141762, @Aklapper wrote: +> Anybody knows if this is still an issue nowadays? + +Happens fairly often, yes (on the scale of 1/s). https://logstash.wikimedia.org/#dashboard/temp/AVLTn06zptxhN1XaS38e","QUOTE +QUOTE + +Happens fairly often, yes (on the scale of 1/s). URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","['QUOTE\nQUOTE\n\nHappens fairly often, yes (on the scale of 1/s).', 'URL']",NA,0,"QUOTE\nQUOTE\n\nHappens fairly often, yes (on the scale of 1/s)." +20170,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki",">>! In T70012#1141762, @Aklapper wrote: +> Anybody knows if this is still an issue nowadays? + +Happens fairly often, yes (on the scale of 1/s). https://logstash.wikimedia.org/#dashboard/temp/AVLTn06zptxhN1XaS38e",1455249439,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment",">>! In T70012#1141762, @Aklapper wrote: +> Anybody knows if this is still an issue nowadays? + +Happens fairly often, yes (on the scale of 1/s). https://logstash.wikimedia.org/#dashboard/temp/AVLTn06zptxhN1XaS38e","QUOTE +QUOTE + +Happens fairly often, yes (on the scale of 1/s). URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","['QUOTE\nQUOTE\n\nHappens fairly often, yes (on the scale of 1/s).', 'URL']",NA,0,"URL" +20171,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",1455249242,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","[""What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain."", 'Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in.', 'These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions.', ""Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails."", 'Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.']",NA,0,"Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in." +20171,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",1455249242,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","[""What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain."", 'Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in.', 'These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions.', ""Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails."", 'Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.']",NA,0,"These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions." +20171,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",1455249242,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","[""What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain."", 'Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in.', 'These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions.', ""Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails."", 'Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.']",NA,0,"Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki." +20171,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",1455249242,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","[""What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain."", 'Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in.', 'These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions.', ""Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails."", 'Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.']",NA,0,"What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain." +20171,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",1455249242,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.","What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain. Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in. These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions. + +Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails. Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,32,"True","[""What probably happens here is that when the user makes their first login after account creation, CentralAuth displays a bunch of site icons (one for each SUL-enabled second-level domain that's not wikimedia.org, plus one for meta and commons each) which are supposed to preemptively log the user in on sites on that domain."", 'Those images are generated by Special:CentralAuthAutologin on the respective sites, and those first redirect to loginwiki to check that the user is centrally logged in.', 'These requests happen simultaneously and they each trigger autocreation, and that apparently results in race conditions.', ""Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails."", 'Not a big deal because there is still the normal autologin which is triggered when the users visits the given wiki.']",NA,0,"Is that's true then there is some user effect from this as the autocreation failure means the user ends up as unauthenticated in that request, so the preemptive autologin fails." +20172,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","Yes, it is still occurring.",1427132334,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","Yes, it is still occurring.","Yes, it is still occurring.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-15,"True","['Yes, it is still occurring.']",NA,0,"Yes, it is still occurring." +20173,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki",">>! In T70012#723577, @Legoktm wrote: +> There's some weird stuff going on here. + +Anybody knows if this is still an issue nowadays?",1427132222,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment",">>! In T70012#723577, @Legoktm wrote: +> There's some weird stuff going on here. + +Anybody knows if this is still an issue nowadays?","QUOTE +QUOTE + +Anybody knows if this is still an issue nowadays?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-15,"True","['QUOTE\nQUOTE\n\nAnybody knows if this is still an issue nowadays?']",NA,0,"QUOTE\nQUOTE\n\nAnybody knows if this is still an issue nowadays?" +20174,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",1405394378,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-51,"True","[""There's some weird stuff going on here."", '2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso.', 'Now, if we just autocreated the user, how is their language already set to Spanish?', ""metawiki's default should be English.""]",NA,0,"2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso." +20174,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",1405394378,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-51,"True","[""There's some weird stuff going on here."", '2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso.', 'Now, if we just autocreated the user, how is their language already set to Spanish?', ""metawiki's default should be English.""]",NA,0,"Now, if we just autocreated the user, how is their language already set to Spanish?" +20174,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",1405394378,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-51,"True","[""There's some weird stuff going on here."", '2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso.', 'Now, if we just autocreated the user, how is their language already set to Spanish?', ""metawiki's default should be English.""]",NA,0,"There's some weird stuff going on here." +20174,"CentralAuthHooks::attemptAddUser: failed with message Username entered already in use. on loginwiki","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",1405394378,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-fu6lhqe3kuntohxjirr7","task_subcomment","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.","There's some weird stuff going on here. + +2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3]) +2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso. + +Now, if we just autocreated the user, how is their language already set to Spanish? metawiki's default should be English.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-51,"True","[""There's some weird stuff going on here."", '2014-07-15 01:29:15 mw1025 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: creating new user ([username3])\n2014-07-15 01:29:15 mw1188 metawiki: CentralAuthHooks::attemptAddUser: failed with message El nombre de usuario indicado ya está en uso.', 'Now, if we just autocreated the user, how is their language already set to Spanish?', ""metawiki's default should be English.""]",NA,0,"metawiki's default should be English." +20252,"Deleted pages should be served as HTTP 404 instead of HTTP 200","The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor",1389032040,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_description","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Low",25,NA,NA,"open","True","c3",1,"False","False",-78,"True","['Deleted pages should be served as HTTP 404 instead of HTTP 200.', 'The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages).', 'Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?', ']], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons.', '--------------------------\n**Version**: 1.23.0\n**Severity**: minor']",FALSE,0,"Deleted pages should be served as HTTP 404 instead of HTTP 200." +20252,"Deleted pages should be served as HTTP 404 instead of HTTP 200","The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor",1389032040,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_description","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Low",25,NA,NA,"open","True","c3",1,"False","False",-78,"True","['Deleted pages should be served as HTTP 404 instead of HTTP 200.', 'The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages).', 'Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?', ']], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons.', '--------------------------\n**Version**: 1.23.0\n**Severity**: minor']",FALSE,0,"The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages)." +20252,"Deleted pages should be served as HTTP 404 instead of HTTP 200","The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor",1389032040,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_description","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Low",25,NA,NA,"open","True","c3",1,"False","False",-78,"True","['Deleted pages should be served as HTTP 404 instead of HTTP 200.', 'The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages).', 'Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?', ']], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons.', '--------------------------\n**Version**: 1.23.0\n**Severity**: minor']",FALSE,0,"Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?" +20252,"Deleted pages should be served as HTTP 404 instead of HTTP 200","The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor",1389032040,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_description","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Low",25,NA,NA,"open","True","c3",1,"False","False",-78,"True","['Deleted pages should be served as HTTP 404 instead of HTTP 200.', 'The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages).', 'Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?', ']], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons.', '--------------------------\n**Version**: 1.23.0\n**Severity**: minor']",FALSE,0,"]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons." +20252,"Deleted pages should be served as HTTP 404 instead of HTTP 200","The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor",1389032040,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_description","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[https://en.wikipedia.org/w/index.php?title=Wikipedia:Biographies_of_living_persons/Noticeboard&oldid=589460695#Does_the_statement_.22A_page_with_this_title_has_previously_been_deleted.22_create_a_BLP_problem.3F|Wikipedia:Biographies of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Deleted pages should be served as HTTP 404 instead of HTTP 200./n/nThe ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages). + +Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?]], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons. + +-------------------------- +**Version**: 1.23.0 +**Severity**: minor","Low",25,NA,NA,"open","True","c3",1,"False","False",-78,"True","['Deleted pages should be served as HTTP 404 instead of HTTP 200.', 'The ""this page has been deleted"" message should be served as HTTP 404 (note: not HTTP 410, as in WONTFIXed bug {T14345}, which implies that the resource will never come back - that is not necessarily true for deleted pages).', 'Related: the 2014 discussion [[URL of living persons/Noticeboard#Does the statement ""A page with this title has previously been deleted"" create a BLP problem?', ']], regarding potential consequences of the ""this page has been deleted"" message appearing in search results for living persons.', '--------------------------\n**Version**: 1.23.0\n**Severity**: minor']",FALSE,0,"--------------------------\n**Version**: 1.23.0\n**Severity**: minor" +20253,"Deleted pages should be served as HTTP 404 instead of HTTP 200","I wasn't aware of that change - good to know - but no, mainspace (and presumably other namespace) pages.",1389694792,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","I wasn't aware of that change - good to know - but no, mainspace (and presumably other namespace) pages.","I wasn't aware of that change - good to know - but no, mainspace (and presumably other namespace) pages.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-77,"True","[""I wasn't aware of that change - good to know - but no, mainspace (and presumably other namespace) pages.""]",NA,0,"I wasn't aware of that change - good to know - but no, mainspace (and presumably other namespace) pages." +20254,"Deleted pages should be served as HTTP 404 instead of HTTP 200","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.",1389522549,"PHID-USER-a6jwrurphpx6yl4coupk","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-77,"True","['Are you talking about user pages?', 'That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.']",NA,0,"Are you talking about user pages?" +20254,"Deleted pages should be served as HTTP 404 instead of HTTP 200","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.",1389522549,"PHID-USER-a6jwrurphpx6yl4coupk","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.","Are you talking about user pages? That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-77,"True","['Are you talking about user pages?', 'That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID.']",NA,0,"That was changed to always return HTTP 200 (excepted unknown and blocked users) to allow use of the url as OpenID." +20255,"Deleted pages should be served as HTTP 404 instead of HTTP 200","Ah, thanks! I misread.",1389283043,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","Ah, thanks! I misread.","Ah, thanks! I misread.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-77,"True","['Ah, thanks!', 'I misread.']",NA,0,"Ah, thanks!" +20255,"Deleted pages should be served as HTTP 404 instead of HTTP 200","Ah, thanks! I misread.",1389283043,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","Ah, thanks! I misread.","Ah, thanks! I misread.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-77,"True","['Ah, thanks!', 'I misread.']",NA,0,"I misread." +20256,"Deleted pages should be served as HTTP 404 instead of HTTP 200","Hi Andre, I've changed the title again as the pages aren't currently being served as 410. :)",1389281317,"PHID-USER-uia2q3o33h5pb5lf7exz","PHID-TASK-yiiwgfkfdpsxxe6q3dxt","task_subcomment","Hi Andre, I've changed the title again as the pages aren't currently being served as 410. :)","Hi Andre, I've changed the title again as the pages aren't currently being served as 410. :)",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-77,"True","[""Hi Andre, I've changed the title again as the pages aren't currently being served as 410. :)""]",NA,0,"Hi Andre, I've changed the title again as the pages aren't currently being served as 410. :)" +20280,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","At some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1387244220,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_description","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Low",25,1388035605,NA,"resolved","True","c3",1,"True","False",-81,"True","['Pre-login destination not remembered when login succeeds in Wikimania Scholarships application.', 'At some point a regression was introduced in the login path.', 'The app used to redirect the user to the URL they initial specified before they were redirected to the login screen.', 'The user seems to always be redirected to the default page now.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",TRUE,0,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application." +20280,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","At some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1387244220,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_description","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Low",25,1388035605,NA,"resolved","True","c3",1,"True","False",-81,"True","['Pre-login destination not remembered when login succeeds in Wikimania Scholarships application.', 'At some point a regression was introduced in the login path.', 'The app used to redirect the user to the URL they initial specified before they were redirected to the login screen.', 'The user seems to always be redirected to the default page now.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",TRUE,0,"At some point a regression was introduced in the login path." +20280,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","At some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1387244220,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_description","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Low",25,1388035605,NA,"resolved","True","c3",1,"True","False",-81,"True","['Pre-login destination not remembered when login succeeds in Wikimania Scholarships application.', 'At some point a regression was introduced in the login path.', 'The app used to redirect the user to the URL they initial specified before they were redirected to the login screen.', 'The user seems to always be redirected to the default page now.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",TRUE,0,"The app used to redirect the user to the URL they initial specified before they were redirected to the login screen." +20280,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","At some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1387244220,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_description","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Low",25,1388035605,NA,"resolved","True","c3",1,"True","False",-81,"True","['Pre-login destination not remembered when login succeeds in Wikimania Scholarships application.', 'At some point a regression was introduced in the login path.', 'The app used to redirect the user to the URL they initial specified before they were redirected to the login screen.', 'The user seems to always be redirected to the default page now.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",TRUE,0,"The user seems to always be redirected to the default page now." +20280,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","At some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal",1387244220,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_description","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Pre-login destination not remembered when login succeeds in Wikimania Scholarships application./n/nAt some point a regression was introduced in the login path. The app used to redirect the user to the URL they initial specified before they were redirected to the login screen. The user seems to always be redirected to the default page now. + +-------------------------- +**Version**: wmf-deployment +**Severity**: normal","Low",25,1388035605,NA,"resolved","True","c3",1,"True","False",-81,"True","['Pre-login destination not remembered when login succeeds in Wikimania Scholarships application.', 'At some point a regression was introduced in the login path.', 'The app used to redirect the user to the URL they initial specified before they were redirected to the login screen.', 'The user seems to always be redirected to the default page now.', '--------------------------\n**Version**: wmf-deployment\n**Severity**: normal']",TRUE,0,"--------------------------\n**Version**: wmf-deployment\n**Severity**: normal" +20281,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","Change 102969 merged by jenkins-bot: +Store full URL in session when redirecting to login form + +https://gerrit.wikimedia.org/r/102969",1387567498,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jcaupbxiop5wftgva7q4","task_subcomment","Change 102969 merged by jenkins-bot: +Store full URL in session when redirecting to login form + +https://gerrit.wikimedia.org/r/102969","Change 102969 merged by jenkins-bot: +Store full URL in session when redirecting to login form + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-80,"True","['Change 102969 merged by jenkins-bot:\nStore full URL in session when redirecting to login form\n\nGERRIT_URL']",NA,0,"Change 102969 merged by jenkins-bot:\nStore full URL in session when redirecting to login form\n\nGERRIT_URL" +20282,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.",1387563508,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_subcomment","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-80,"True","[""This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session."", 'The redirect code now expects to find a full qualified URL rather than just the local route path.']",NA,0,"The redirect code now expects to find a full qualified URL rather than just the local route path." +20282,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.",1387563508,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-jcaupbxiop5wftgva7q4","task_subcomment","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.","This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session. The redirect code now expects to find a full qualified URL rather than just the local route path.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-80,"True","[""This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session."", 'The redirect code now expects to find a full qualified URL rather than just the local route path.']",NA,0,"This was broken by a change made during the security review to validate the URL stored in the users' pre-authentication session." +20283,"Pre-login destination not remembered when login succeeds in Wikimania Scholarships application","Change 102969 had a related patch set uploaded by BryanDavis: +Store full URL in session when redirecting to login form + +https://gerrit.wikimedia.org/r/102969",1387563391,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-jcaupbxiop5wftgva7q4","task_subcomment","Change 102969 had a related patch set uploaded by BryanDavis: +Store full URL in session when redirecting to login form + +https://gerrit.wikimedia.org/r/102969","Change 102969 had a related patch set uploaded by BryanDavis: +Store full URL in session when redirecting to login form + +GERRIT_URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-80,"True","['Change 102969 had a related patch set uploaded by BryanDavis:\nStore full URL in session when redirecting to login form\n\nGERRIT_URL']",NA,0,"Change 102969 had a related patch set uploaded by BryanDavis:\nStore full URL in session when redirecting to login form\n\nGERRIT_URL" +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"Users can unblock the content but they might not know that they can do this." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"I did not know at first." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"The solution would be for the extension to deliver the content from youtube over https - youtube can do this." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format." +20374,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask",1407897660,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_description","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** `ttguy1` + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: https://userbase.kde.org/Kdenlive/Manual/Effects/Blur_and_hide/Auto_Mask","EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content./n/n**Author:** CODE + +**Description:** +If you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http. If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked. + +Users can unblock the content but they might not know that they can do this. I did not know at first. + +The solution would be for the extension to deliver the content from youtube over https - youtube can do this. I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format. + +-------------------------- +**Version**: REL1_20-branch +**Severity**: normal +**URL**: URL","Lowest",10,1408078573,NA,"invalid","True","c3",1,"False","False",-47,"True","['EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content.', '**Author:** CODE\n\n**Description:**\nIf you use the EmbedVideo extension to embed a youtube video eg {{#ev:youtube|dMH0bHeiRNg}} then the html created delivers the youtube content over http.', 'If the wiki running the EmbedVideo extension is delivering content over https then the resulting page is detected by modern browsers as containing mixed content and the youtube embeded video is blocked.', 'Users can unblock the content but they might not know that they can do this.', 'I did not know at first.', 'The solution would be for the extension to deliver the content from youtube over https - youtube can do this.', 'I guess the extension should some how detect if the wiki is using http or https and send youtube data in the matching format.', '--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL']",TRUE,0,"--------------------------\n**Version**: REL1_20-branch\n**Severity**: normal\n**URL**: URL" +20375,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here",1408078573,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-46,"True","['Ah, thanks for finding that.', ""Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here""]",NA,0,"Ah, thanks for finding that." +20375,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here",1408078573,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here","Ah, thanks for finding that. Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-46,"True","['Ah, thanks for finding that.', ""Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here""]",NA,0,"Looks like it should be handled there, hence closing the ticket in WIkimedia Bugzilla as it's not handled here" +20376,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as https://github.com/Whiteknight/mediawiki-embedvideo/pull/39",1407969709,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as https://github.com/Whiteknight/mediawiki-embedvideo/pull/39","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['**ttguy1** wrote:\n\nThanks Andre.', 'I think this issue is being covered as URL']",NA,0,"**ttguy1** wrote:\n\nThanks Andre." +20376,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as https://github.com/Whiteknight/mediawiki-embedvideo/pull/39",1407969709,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as https://github.com/Whiteknight/mediawiki-embedvideo/pull/39","**ttguy1** wrote: + +Thanks Andre. I think this issue is being covered as URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['**ttguy1** wrote:\n\nThanks Andre.', 'I think this issue is being covered as URL']",NA,0,"I think this issue is being covered as URL" +20377,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","https://www.mediawiki.org/wiki/Extension:EmbedVideo says this is not maintained anymore and hosted on Github, so the bug reports should probably be created at +https://github.com/Whiteknight/mediawiki-embedvideo/issues instead.",1407917987,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","https://www.mediawiki.org/wiki/Extension:EmbedVideo says this is not maintained anymore and hosted on Github, so the bug reports should probably be created at +https://github.com/Whiteknight/mediawiki-embedvideo/issues instead.","URL says this is not maintained anymore and hosted on Github, so the bug reports should probably be created at +URL instead.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-47,"True","['URL says this is not maintained anymore and hosted on Github, so the bug reports should probably be created at\nURL instead.']",NA,0,"URL says this is not maintained anymore and hosted on Github, so the bug reports should probably be created at\nURL instead." +20378,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**ttguy1** wrote: + +A comment at https://www.mediawiki.org/wiki/Extension_talk:EmbedVideo#HTTPS_support_with_embedded_youtube says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""http://"" by ""https://"" in youtube* php array.",1407900180,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","**ttguy1** wrote: + +A comment at https://www.mediawiki.org/wiki/Extension_talk:EmbedVideo#HTTPS_support_with_embedded_youtube says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""http://"" by ""https://"" in youtube* php array.","**ttguy1** wrote: + +A comment at URL says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""URL by ""URL in youtube* php array.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['**ttguy1** wrote:\n\nA comment at URL says this could be fixed:\nIt\'s pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""URL by ""URL in youtube* php array.']",NA,0,"**ttguy1** wrote:\n\nA comment at URL says this could be fixed:\nIt\" +20378,"EmbedVideo extension delivers youtube videos using http instead of https causing modern browsers to block the content","**ttguy1** wrote: + +A comment at https://www.mediawiki.org/wiki/Extension_talk:EmbedVideo#HTTPS_support_with_embedded_youtube says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""http://"" by ""https://"" in youtube* php array.",1407900180,"PHID-USER-ynivjflmc2dcl6w5ut5v","PHID-TASK-4azbdzfz7shotyvicbmj","task_subcomment","**ttguy1** wrote: + +A comment at https://www.mediawiki.org/wiki/Extension_talk:EmbedVideo#HTTPS_support_with_embedded_youtube says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""http://"" by ""https://"" in youtube* php array.","**ttguy1** wrote: + +A comment at URL says this could be fixed: +It's pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""URL by ""URL in youtube* php array.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-47,"True","['**ttguy1** wrote:\n\nA comment at URL says this could be fixed:\nIt\'s pretty easy : simply modify EmbedVideo.Services.php to replace frame src ""URL by ""URL in youtube* php array.']",NA,0,"URL by " +20412,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.","This is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}",1391046600,"PHID-USER-omdcggvudfkuawipp23i","PHID-TASK-24bclzoyrficwse5xql3","task_description","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Lowest",10,1690131831,"PHID-USER-mqhfa5y5f5tg6g3b5hui","duplicate","True","c3",1,"False","False",-74,"True","[""Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.."", 'This is basically a followup to bug 57866, where such options were discussed.', 'Is this possible?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T47469}']",FALSE,0,"This is basically a followup to bug 57866, where such options were discussed." +20412,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.","This is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}",1391046600,"PHID-USER-omdcggvudfkuawipp23i","PHID-TASK-24bclzoyrficwse5xql3","task_description","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Lowest",10,1690131831,"PHID-USER-mqhfa5y5f5tg6g3b5hui","duplicate","True","c3",1,"False","False",-74,"True","[""Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.."", 'This is basically a followup to bug 57866, where such options were discussed.', 'Is this possible?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T47469}']",FALSE,0,"Is this possible?" +20412,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.","This is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}",1391046600,"PHID-USER-omdcggvudfkuawipp23i","PHID-TASK-24bclzoyrficwse5xql3","task_description","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Lowest",10,1690131831,"PHID-USER-mqhfa5y5f5tg6g3b5hui","duplicate","True","c3",1,"False","False",-74,"True","[""Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.."", 'This is basically a followup to bug 57866, where such options were discussed.', 'Is this possible?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T47469}']",FALSE,0,"--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T47469}" +20412,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.","This is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}",1391046600,"PHID-USER-omdcggvudfkuawipp23i","PHID-TASK-24bclzoyrficwse5xql3","task_description","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message../n/nThis is basically a followup to bug 57866, where such options were discussed. +Is this possible? + +-------------------------- +**Version**: unspecified +**Severity**: enhancement +**See Also**: +{T47469}","Lowest",10,1690131831,"PHID-USER-mqhfa5y5f5tg6g3b5hui","duplicate","True","c3",1,"False","False",-74,"True","[""Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.."", 'This is basically a followup to bug 57866, where such options were discussed.', 'Is this possible?', '--------------------------\n**Version**: unspecified\n**Severity**: enhancement\n**See Also**:\n{T47469}']",FALSE,0,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.." +20419,"Add lock reason (from log) or [[Special:CentralAuth/$1]] ($1=username) link to 'centralauth-login-error-locked' message.","They were also discussed in comments here: https://gerrit.wikimedia.org/r/#/c/98568/",1391046674,"PHID-USER-omdcggvudfkuawipp23i","PHID-TASK-24bclzoyrficwse5xql3","task_subcomment","They were also discussed in comments here: https://gerrit.wikimedia.org/r/#/c/98568/","They were also discussed in comments here: URL",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-74,"True","['They were also discussed in comments here: URL']",NA,0,"They were also discussed in comments here: URL" +20713,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?",1439535298,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-un2pilpqiazqdfsiinqa","task_description","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* URL +* {T108999} (probably incorrectly duped) +* URL +* Lydia said some people also reported this via Twitter. +*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","Unbreak Now!",100,1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","resolved","True","c3",3,"True","False",6,"True","['[Bug] Users are unable to login on wikidata.org until they clear their cookies.', ""People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in."", 'Clearing all cookies fixes the issue.', 'Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter.', ""*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?""]",TRUE,0,"[Bug] Users are unable to login on wikidata.org until they clear their cookies." +20713,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?",1439535298,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-un2pilpqiazqdfsiinqa","task_description","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* URL +* {T108999} (probably incorrectly duped) +* URL +* Lydia said some people also reported this via Twitter. +*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","Unbreak Now!",100,1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","resolved","True","c3",3,"True","False",6,"True","['[Bug] Users are unable to login on wikidata.org until they clear their cookies.', ""People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in."", 'Clearing all cookies fixes the issue.', 'Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter.', ""*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?""]",TRUE,0,"Clearing all cookies fixes the issue." +20713,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?",1439535298,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-un2pilpqiazqdfsiinqa","task_description","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* URL +* {T108999} (probably incorrectly duped) +* URL +* Lydia said some people also reported this via Twitter. +*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","Unbreak Now!",100,1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","resolved","True","c3",3,"True","False",6,"True","['[Bug] Users are unable to login on wikidata.org until they clear their cookies.', ""People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in."", 'Clearing all cookies fixes the issue.', 'Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter.', ""*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?""]",TRUE,0,"Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter." +20713,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?",1439535298,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-un2pilpqiazqdfsiinqa","task_description","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* URL +* {T108999} (probably incorrectly duped) +* URL +* Lydia said some people also reported this via Twitter. +*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","Unbreak Now!",100,1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","resolved","True","c3",3,"True","False",6,"True","['[Bug] Users are unable to login on wikidata.org until they clear their cookies.', ""People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in."", 'Clearing all cookies fixes the issue.', 'Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter.', ""*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?""]",TRUE,0,"People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in." +20713,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?",1439535298,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-un2pilpqiazqdfsiinqa","task_description","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team#Cannot_log_in +* {T108999} (probably incorrectly duped) +* https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#InterWiki +* Lydia said some people also reported this via Twitter. +* @aude said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","[Bug] Users are unable to login on wikidata.org until they clear their cookies./n/nPeople are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in. Clearing all cookies fixes the issue. + +Reports: +* URL +* {T108999} (probably incorrectly duped) +* URL +* Lydia said some people also reported this via Twitter. +*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC + +Possible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?","Unbreak Now!",100,1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","resolved","True","c3",3,"True","False",6,"True","['[Bug] Users are unable to login on wikidata.org until they clear their cookies.', ""People are reporting that they are unable to log into wikidata.org and being redirected even though they're not logged in."", 'Clearing all cookies fixes the issue.', 'Reports:\n* URL\n* {T108999} (probably incorrectly duped)\n* URL\n* Lydia said some people also reported this via Twitter.', ""*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?""]",TRUE,0,"*SCREEN_NAME said she couldn't log in until she cleared her cookies on IRC\n\nPossible cause could be {0275738d2d10544b474ea1aaa8a5080912323407}?" +20714,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 238418 merged by BBlack: +Remove wikidata CA cookie hacks + +[[https://gerrit.wikimedia.org/r/238418]]",1442495900,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 238418 merged by BBlack: +Remove wikidata CA cookie hacks + +[[https://gerrit.wikimedia.org/r/238418]]","Change 238418 merged by BBlack: +Remove wikidata CA cookie hacks + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,11,"True","['Change 238418 merged by BBlack:\nRemove wikidata CA cookie hacks\n\n[[GERRIT_URL]]']",NA,0,"Change 238418 merged by BBlack:\nRemove wikidata CA cookie hacks\n\n[[GERRIT_URL]]" +20715,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 238418 had a related patch set uploaded (by BBlack): +Remove wikidata CA cookie hacks + +[[https://gerrit.wikimedia.org/r/238418]] +",1442319468,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 238418 had a related patch set uploaded (by BBlack): +Remove wikidata CA cookie hacks + +[[https://gerrit.wikimedia.org/r/238418]] +","Change 238418 had a related patch set uploaded (by BBlack): +Remove wikidata CA cookie hacks + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,10,"True","['Change 238418 had a related patch set uploaded (by BBlack):\nRemove wikidata CA cookie hacks\n\n[[GERRIT_URL]]']",NA,0,"Change 238418 had a related patch set uploaded (by BBlack):\nRemove wikidata CA cookie hacks\n\n[[GERRIT_URL]]" +20716,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@sjoerddebruin: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.",1440784763,"PHID-USER-7n5fvppwj4ueprv2iuys","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@sjoerddebruin: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.","SCREEN_NAME: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME: This also fixed it for one of the people in the office who still had the issue.', 'I think we can take down the note on the main page.']",NA,0,"SCREEN_NAME: This also fixed it for one of the people in the office who still had the issue." +20716,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@sjoerddebruin: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.",1440784763,"PHID-USER-7n5fvppwj4ueprv2iuys","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@sjoerddebruin: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.","SCREEN_NAME: This also fixed it for one of the people in the office who still had the issue. I think we can take down the note on the main page.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME: This also fixed it for one of the people in the office who still had the issue.', 'I think we can take down the note on the main page.']",NA,0,"I think we can take down the note on the main page." +20717,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@JanZerebecki Fixed for me.",1440781565,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@JanZerebecki Fixed for me.","SCREEN_NAME Fixed for me.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['SCREEN_NAME Fixed for me.']",NA,0,"SCREEN_NAME Fixed for me." +20718,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 234517 merged by BBlack: +refactor wikidata CA cookies workarounds a bit + +[[https://gerrit.wikimedia.org/r/234517]]",1440776206,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 234517 merged by BBlack: +refactor wikidata CA cookies workarounds a bit + +[[https://gerrit.wikimedia.org/r/234517]]","Change 234517 merged by BBlack: +refactor wikidata CA cookies workarounds a bit + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['Change 234517 merged by BBlack:\nrefactor wikidata CA cookies workarounds a bit\n\n[[GERRIT_URL]]']",NA,0,"Change 234517 merged by BBlack:\nrefactor wikidata CA cookies workarounds a bit\n\n[[GERRIT_URL]]" +20719,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 234517 had a related patch set uploaded (by BBlack): +refactor wikidata CA cookies workarounds a bit + +[[https://gerrit.wikimedia.org/r/234517]] +",1440766915,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 234517 had a related patch set uploaded (by BBlack): +refactor wikidata CA cookies workarounds a bit + +[[https://gerrit.wikimedia.org/r/234517]] +","Change 234517 had a related patch set uploaded (by BBlack): +refactor wikidata CA cookies workarounds a bit + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['Change 234517 had a related patch set uploaded (by BBlack):\nrefactor wikidata CA cookies workarounds a bit\n\n[[GERRIT_URL]]']",NA,0,"Change 234517 had a related patch set uploaded (by BBlack):\nrefactor wikidata CA cookies workarounds a bit\n\n[[GERRIT_URL]]" +20720,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@Keegan Thx. Should be fixed now. Please retry.",1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@Keegan Thx. Should be fixed now. Please retry.","SCREEN_NAME Thx. Should be fixed now. Please retry.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME Thx.', 'Should be fixed now.', 'Please retry.']",NA,0,"SCREEN_NAME Thx." +20720,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@Keegan Thx. Should be fixed now. Please retry.",1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@Keegan Thx. Should be fixed now. Please retry.","SCREEN_NAME Thx. Should be fixed now. Please retry.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME Thx.', 'Should be fixed now.', 'Please retry.']",NA,0,"Should be fixed now." +20720,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@Keegan Thx. Should be fixed now. Please retry.",1440766680,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@Keegan Thx. Should be fixed now. Please retry.","SCREEN_NAME Thx. Should be fixed now. Please retry.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,8,"True","['SCREEN_NAME Thx.', 'Should be fixed now.', 'Please retry.']",NA,0,"Please retry." +20721,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 234510 merged by BBlack: +Another CentralAuth double cookie workaround + +[[https://gerrit.wikimedia.org/r/234510]]",1440765422,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 234510 merged by BBlack: +Another CentralAuth double cookie workaround + +[[https://gerrit.wikimedia.org/r/234510]]","Change 234510 merged by BBlack: +Another CentralAuth double cookie workaround + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['Change 234510 merged by BBlack:\nAnother CentralAuth double cookie workaround\n\n[[GERRIT_URL]]']",NA,0,"Change 234510 merged by BBlack:\nAnother CentralAuth double cookie workaround\n\n[[GERRIT_URL]]" +20722,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 234510 had a related patch set uploaded (by JanZerebecki): +Another CentralAuth double cookie workaround + +[[https://gerrit.wikimedia.org/r/234510]] +",1440764544,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 234510 had a related patch set uploaded (by JanZerebecki): +Another CentralAuth double cookie workaround + +[[https://gerrit.wikimedia.org/r/234510]] +","Change 234510 had a related patch set uploaded (by JanZerebecki): +Another CentralAuth double cookie workaround + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['Change 234510 had a related patch set uploaded (by JanZerebecki):\nAnother CentralAuth double cookie workaround\n\n[[GERRIT_URL]]']",NA,0,"Change 234510 had a related patch set uploaded (by JanZerebecki):\nAnother CentralAuth double cookie workaround\n\n[[GERRIT_URL]]" +20723,"[Bug] Users are unable to login on wikidata.org until they clear their cookies",">>! In T109038#1576174, @JanZerebecki wrote: +> If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.) + +Reproduced and sent to @JanZerebecki and @aude",1440706863,"PHID-USER-fwlidikyeorzj35hufwu","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment",">>! In T109038#1576174, @JanZerebecki wrote: +> If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.) + +Reproduced and sent to @JanZerebecki and @aude","QUOTE +QUOTE + +Reproduced and sent toSCREEN_NAME andSCREEN_NAME",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,8,"True","['QUOTE\nQUOTE\n\nReproduced and sent toSCREEN_NAME andSCREEN_NAME']",NA,0,"QUOTE\nQUOTE\n\nReproduced and sent toSCREEN_NAME andSCREEN_NAME" +20724,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",1440610704,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this.', ""(At least the cookie names/keys, don't publicly publish the values."", 'You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)']",NA,0,"If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this." +20724,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",1440610704,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this.', ""(At least the cookie names/keys, don't publicly publish the values."", 'You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)']",NA,0,"You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)" +20724,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",1440610704,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)","If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this. (At least the cookie names/keys, don't publicly publish the values. You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['If you can still reproduce this, we need to know your cookies for wikidata.org and subdomains to be able to fix this.', ""(At least the cookie names/keys, don't publicly publish the values."", 'You can send me a private message through Phabricator or on wiki if you want to be sure to not accidentally publish something private.)']",NA,0,"(At least the cookie names/keys, don't publicly publish the values." +20725,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Added a notice to our homepage, a sitenotice seems annoying to me.",1440486938,"PHID-USER-pr6rfjdcmkknkex6dgn5","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Added a notice to our homepage, a sitenotice seems annoying to me.","Added a notice to our homepage, a sitenotice seems annoying to me.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,7,"True","['Added a notice to our homepage, a sitenotice seems annoying to me.']",NA,0,"Added a notice to our homepage, a sitenotice seems annoying to me." +20726,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Apparently people are still having issues: https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login_.282.29 :(",1440486821,"PHID-USER-7n5fvppwj4ueprv2iuys","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Apparently people are still having issues: https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login_.282.29 :(","Apparently people are still having issues: URL :(",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['Apparently people are still having issues: URL :(']",NA,0,"Apparently people are still having issues: URL :(" +20727,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Pushed a fix for deleting the duplicate centralauth_User for wikidata.org, should be in effect globally now.",1440204947,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Pushed a fix for deleting the duplicate centralauth_User for wikidata.org, should be in effect globally now.","Pushed a fix for deleting the duplicate centralauth_User for wikidata.org, should be in effect globally now.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['Pushed a fix for deleting the duplicate centralauth_User for wikidata.org, should be in effect globally now.']",NA,0,"Pushed a fix for deleting the duplicate centralauth_User for wikidata.org, should be in effect globally now." +20728,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 233086 merged by BBlack: +Fix remaining wikidata login issues: duplicate CA User + +[[https://gerrit.wikimedia.org/r/233086]]",1440204625,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 233086 merged by BBlack: +Fix remaining wikidata login issues: duplicate CA User + +[[https://gerrit.wikimedia.org/r/233086]]","Change 233086 merged by BBlack: +Fix remaining wikidata login issues: duplicate CA User + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,7,"True","['Change 233086 merged by BBlack:\nFix remaining wikidata login issues: duplicate CA User\n\n[[GERRIT_URL]]']",NA,0,"Change 233086 merged by BBlack:\nFix remaining wikidata login issues: duplicate CA User\n\n[[GERRIT_URL]]" +20729,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 233086 had a related patch set uploaded (by BBlack): +Fix remaining wikidata login issues: duplicate CA User + +[[https://gerrit.wikimedia.org/r/233086]] +",1440204525,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 233086 had a related patch set uploaded (by BBlack): +Fix remaining wikidata login issues: duplicate CA User + +[[https://gerrit.wikimedia.org/r/233086]] +","Change 233086 had a related patch set uploaded (by BBlack): +Fix remaining wikidata login issues: duplicate CA User + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,7,"True","['Change 233086 had a related patch set uploaded (by BBlack):\nFix remaining wikidata login issues: duplicate CA User\n\n[[GERRIT_URL]]']",NA,0,"Change 233086 had a related patch set uploaded (by BBlack):\nFix remaining wikidata login issues: duplicate CA User\n\n[[GERRIT_URL]]" +20730,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....",1440204220,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['Ah, that makes some logical sense.', 'We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....']",NA,0,"Ah, that makes some logical sense." +20730,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....",1440204220,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....","Ah, that makes some logical sense. We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,7,"True","['Ah, that makes some logical sense.', 'We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it....']",NA,0,"We should probably stripping duplicate _User the way we are for duplicate _Token to address the bulk of it...." +20731,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)",1440198231,"PHID-USER-2ji2k3idgmipacu4ftck","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,7,"True","['I hit this also tonight.', 'If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)']",NA,0,"I hit this also tonight." +20731,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)",1440198231,"PHID-USER-2ji2k3idgmipacu4ftck","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)","I hit this also tonight. + +If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,7,"True","['I hit this also tonight.', 'If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)']",NA,0,"If it helps: I had two ""centralauth_User"" cookies: one for previously logged user and another one for currently logged user (I was relogging to another account)" +20732,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Sadly there is no way to reproduce it once the cookies are deleted.",1439893344,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Sadly there is no way to reproduce it once the cookies are deleted.","Sadly there is no way to reproduce it once the cookies are deleted.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['Sadly there is no way to reproduce it once the cookies are deleted.']",NA,0,"Sadly there is no way to reproduce it once the cookies are deleted." +20733,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","At least one user still had this problem today. See https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login.",1439880836,"PHID-USER-74kolctr2gbwr2mtan63","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","At least one user still had this problem today. See https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login.","At least one user still had this problem today. See URL",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['At least one user still had this problem today.', 'See URL']",NA,0,"At least one user still had this problem today." +20733,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","At least one user still had this problem today. See https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login.",1439880836,"PHID-USER-74kolctr2gbwr2mtan63","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","At least one user still had this problem today. See https://www.wikidata.org/wiki/Wikidata:Project_chat#Central_login.","At least one user still had this problem today. See URL",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['At least one user still had this problem today.', 'See URL']",NA,0,"See URL" +20734,"[Bug] Users are unable to login on wikidata.org until they clear their cookies",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",1439575080,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.","QUOTE +QUOTE + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['QUOTE\nQUOTE\n\nYeah, I was mostly interested if that was in fact the issue.', 'So confirmed.', 'To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.']",NA,0,"QUOTE\nQUOTE\n\nYeah, I was mostly interested if that was in fact the issue." +20734,"[Bug] Users are unable to login on wikidata.org until they clear their cookies",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",1439575080,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.","QUOTE +QUOTE + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['QUOTE\nQUOTE\n\nYeah, I was mostly interested if that was in fact the issue.', 'So confirmed.', 'To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.']",NA,0,"So confirmed." +20734,"[Bug] Users are unable to login on wikidata.org until they clear their cookies",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",1439575080,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment",">>! In T109038#1540332, @JanZerebecki wrote: +> @csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth? + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.","QUOTE +QUOTE + +Yeah, I was mostly interested if that was in fact the issue. So confirmed. + +To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['QUOTE\nQUOTE\n\nYeah, I was mostly interested if that was in fact the issue.', 'So confirmed.', 'To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in.']",NA,0,"To avoid this in the future, we could look at how CentralAuth gets the cookie and see if we can either identify the correct one or check all of the ones that come in." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"SCREEN_NAME Sorry I missed that." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"One for www.wikidata.org and one for .wikidata.org ." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"See the patch for the regex that matched that situation." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"After that the .wikidata.org one was deleted." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"Should that also be fixed in CentralAuth?" +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"I don't have the tab open anymore." +20735,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",1439572858,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@csteipp Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?","SCREEN_NAME Sorry I missed that. I don't have the tab open anymore. I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values. One for www.wikidata.org and one for .wikidata.org . See the patch for the regex that matched that situation. After that the .wikidata.org one was deleted. Should that also be fixed in CentralAuth?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['SCREEN_NAME Sorry I missed that.', ""I don't have the tab open anymore."", ""I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values."", 'One for www.wikidata.org and one for .wikidata.org .', 'See the patch for the regex that matched that situation.', 'After that the .wikidata.org one was deleted.', 'Should that also be fixed in CentralAuth?']",NA,0,"I don't remember the order but in the Cookie HTTP header there where two key-value pairs for centralauth_Token with different values." +20736,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?",1439561653,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?","We think the workaround deployed via GERRIT_URL should fix this up well enough. It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out. Can others confirm?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['We think the workaround deployed via GERRIT_URL should fix this up well enough.', 'It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out.', 'Can others confirm?']",NA,0,"We think the workaround deployed via GERRIT_URL should fix this up well enough." +20736,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?",1439561653,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?","We think the workaround deployed via GERRIT_URL should fix this up well enough. It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out. Can others confirm?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['We think the workaround deployed via GERRIT_URL should fix this up well enough.', 'It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out.', 'Can others confirm?']",NA,0,"It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out." +20736,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?",1439561653,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","We think the workaround deployed via https://gerrit.wikimedia.org/r/231556 should fix this up well enough. It worked for @JanZerebecki who still had the old bad cookie, which the fixup wiped out. Can others confirm?","We think the workaround deployed via GERRIT_URL should fix this up well enough. It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out. Can others confirm?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['We think the workaround deployed via GERRIT_URL should fix this up well enough.', 'It worked forSCREEN_NAME who still had the old bad cookie, which the fixup wiped out.', 'Can others confirm?']",NA,0,"Can others confirm?" +20737,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 231558 merged by BBlack: +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[https://gerrit.wikimedia.org/r/231558]]",1439561543,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 231558 merged by BBlack: +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[https://gerrit.wikimedia.org/r/231558]]","Change 231558 merged by BBlack: +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Change 231558 merged by BBlack:\nwikidata.org cookie workaround: add comments re task and when it can be removed\n\n[[GERRIT_URL]]']",NA,0,"Change 231558 merged by BBlack:\nwikidata.org cookie workaround: add comments re task and when it can be removed\n\n[[GERRIT_URL]]" +20738,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 231558 had a related patch set uploaded (by BBlack): +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[https://gerrit.wikimedia.org/r/231558]] +",1439561509,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 231558 had a related patch set uploaded (by BBlack): +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[https://gerrit.wikimedia.org/r/231558]] +","Change 231558 had a related patch set uploaded (by BBlack): +wikidata.org cookie workaround: add comments re task and when it can be removed + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Change 231558 had a related patch set uploaded (by BBlack):\nwikidata.org cookie workaround: add comments re task and when it can be removed\n\n[[GERRIT_URL]]']",NA,0,"Change 231558 had a related patch set uploaded (by BBlack):\nwikidata.org cookie workaround: add comments re task and when it can be removed\n\n[[GERRIT_URL]]" +20739,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 231556 merged by BBlack: +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[https://gerrit.wikimedia.org/r/231556]]",1439560596,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 231556 merged by BBlack: +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[https://gerrit.wikimedia.org/r/231556]]","Change 231556 merged by BBlack: +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Change 231556 merged by BBlack:\nAttempt to fix CA token issue via double-value detection -> delete on .wikidata.org\n\n[[GERRIT_URL]]']",NA,0,"Change 231556 merged by BBlack:\nAttempt to fix CA token issue via double-value detection -> delete on .wikidata.org\n\n[[GERRIT_URL]]" +20740,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Change 231556 had a related patch set uploaded (by BBlack): +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[https://gerrit.wikimedia.org/r/231556]] +",1439559312,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Change 231556 had a related patch set uploaded (by BBlack): +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[https://gerrit.wikimedia.org/r/231556]] +","Change 231556 had a related patch set uploaded (by BBlack): +Attempt to fix CA token issue via double-value detection -> delete on .wikidata.org + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Change 231556 had a related patch set uploaded (by BBlack):\nAttempt to fix CA token issue via double-value detection -> delete on .wikidata.org\n\n[[GERRIT_URL]]']",NA,0,"Change 231556 had a related patch set uploaded (by BBlack):\nAttempt to fix CA token issue via double-value detection -> delete on .wikidata.org\n\n[[GERRIT_URL]]" +20741,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",1439558032,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm","SCREEN_NAME, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","[""SCREEN_NAME, if you're able to reproduce, can you capture the headers and send\nthem to me?"", ""Or post here if you're comfortable."", ""I'm guessing you ended up with two token/session cookies, and either guy\nthe wrong one or the browser sends both and we're parsing the wrong one\nout."", 'But would like to confirm']",NA,0,"But would like to confirm" +20741,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",1439558032,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm","SCREEN_NAME, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","[""SCREEN_NAME, if you're able to reproduce, can you capture the headers and send\nthem to me?"", ""Or post here if you're comfortable."", ""I'm guessing you ended up with two token/session cookies, and either guy\nthe wrong one or the browser sends both and we're parsing the wrong one\nout."", 'But would like to confirm']",NA,0,"SCREEN_NAME, if you're able to reproduce, can you capture the headers and send\nthem to me?" +20741,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",1439558032,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm","SCREEN_NAME, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","[""SCREEN_NAME, if you're able to reproduce, can you capture the headers and send\nthem to me?"", ""Or post here if you're comfortable."", ""I'm guessing you ended up with two token/session cookies, and either guy\nthe wrong one or the browser sends both and we're parsing the wrong one\nout."", 'But would like to confirm']",NA,0,"Or post here if you're comfortable." +20741,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",1439558032,"PHID-USER-doeppszazlm3r7xah4il","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","@bblack, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm","SCREEN_NAME, if you're able to reproduce, can you capture the headers and send +them to me? Or post here if you're comfortable. + +I'm guessing you ended up with two token/session cookies, and either guy +the wrong one or the browser sends both and we're parsing the wrong one +out. But would like to confirm",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","[""SCREEN_NAME, if you're able to reproduce, can you capture the headers and send\nthem to me?"", ""Or post here if you're comfortable."", ""I'm guessing you ended up with two token/session cookies, and either guy\nthe wrong one or the browser sends both and we're parsing the wrong one\nout."", 'But would like to confirm']",NA,0,"I'm guessing you ended up with two token/session cookies, and either guy\nthe wrong one or the browser sends both and we're parsing the wrong one\nout." +20742,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","A site notice would probably be really useful for WD users telling them what to do (yes, old technology)",1439556939,"PHID-USER-bmenasgfntvftznu6wxs","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","A site notice would probably be really useful for WD users telling them what to do (yes, old technology)","A site notice would probably be really useful for WD users telling them what to do (yes, old technology)",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['A site notice would probably be really useful for WD users telling them what to do (yes, old technology)']",NA,0,"A site notice would probably be really useful for WD users telling them what to do (yes, old technology)" +20743,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556126,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org)." +20743,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556126,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix." +20743,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556126,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that." +20743,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556126,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"There might be some better application-level way of dealing with this, though." +20743,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556126,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to www.wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request." +20744,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556072,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org)." +20744,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556072,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix." +20744,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556072,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that." +20744,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556072,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"There might be some better application-level way of dealing with this, though." +20744,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",1439556072,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit https://wikidata.org/ to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.","As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org). + +From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request. So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix. We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that. There might be some better application-level way of dealing with this, though.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['As best I can tell from my own testing (but I think someone with deeper insight into the CORS change for (www|query).wikidata.org and S:UL and such would need to confirm this sounds sane): I was able to reproduce the issue, and I was able to apparently perma-fix it for myself by deleting the centralauth_Token cookie in my browser cookie set that was stored under ""wikidata.org"" (as opposed to www.wikidata.org).', ""From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request."", 'So we could, for example, put a hack in varnish to delete the centralauth_Token cookie on requests with the exact Host header ""wikidata.org"" just to kill the one problematic cookie, but users would actually have to visit URL to trigger the fix.', 'We could maybe do that part by embedding a request to it in all accesses to wikidata.org temporarily or something like that.', 'There might be some better application-level way of dealing with this, though.']",NA,0,"From the server end, we can't tell what domain a cookie was set for, only that it matched for the browser's request." +20745,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Does someone have the specific details here on what cookie name to wipe on requests to what domainname(s)?",1439553274,"PHID-USER-lhtlnmkdbzlz6pbxaqdd","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Does someone have the specific details here on what cookie name to wipe on requests to what domainname(s)?","Does someone have the specific details here on what cookie name to wipe on requests to what domainname(s)?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['Does someone have the specific details here on what cookie name to wipe on requests to what domainname(s)?']",NA,0,"Does someone have the specific details here on what cookie name to wipe on requests to what domainname(s)?" +20746,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","The way to go here is probably to unset the old cookies via varnish, if they exist. @bblack can help with that.",1439546558,"PHID-USER-2mey32xhshfnf7rz7jjn","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","The way to go here is probably to unset the old cookies via varnish, if they exist. @bblack can help with that.","The way to go here is probably to unset the old cookies via varnish, if they exist.SCREEN_NAME can help with that.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,6,"True","['The way to go here is probably to unset the old cookies via varnish, if they exist.SCREEN_NAME can help with that.']",NA,0,"The way to go here is probably to unset the old cookies via varnish, if they exist.SCREEN_NAME can help with that." +20747,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Could the cause of this issue and {T50389} be the same?",1439543480,"PHID-USER-u6ycqhfpa3k4yvlpxjt2","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Could the cause of this issue and {T50389} be the same?","Could the cause of this issue and {T50389} be the same?",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Could the cause of this issue and {T50389} be the same?']",NA,0,"Could the cause of this issue and {T50389} be the same?" +20748,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",1439539743,"PHID-USER-hms7bpiczbwhx4dxgiqw","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Had the same issue.', 'Clearing cookies lets me log into Wikidata, but ""locally"".', 'Logging into another Wikimedia site activates the ""global"" login for those.', 'Both work now (no ""you are centrally logged in"" message on Wikidata again).']",NA,0,"Had the same issue." +20748,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",1439539743,"PHID-USER-hms7bpiczbwhx4dxgiqw","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Had the same issue.', 'Clearing cookies lets me log into Wikidata, but ""locally"".', 'Logging into another Wikimedia site activates the ""global"" login for those.', 'Both work now (no ""you are centrally logged in"" message on Wikidata again).']",NA,0,"Clearing cookies lets me log into Wikidata, but ""locally""." +20748,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",1439539743,"PHID-USER-hms7bpiczbwhx4dxgiqw","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Had the same issue.', 'Clearing cookies lets me log into Wikidata, but ""locally"".', 'Logging into another Wikimedia site activates the ""global"" login for those.', 'Both work now (no ""you are centrally logged in"" message on Wikidata again).']",NA,0,"Logging into another Wikimedia site activates the ""global"" login for those." +20748,"[Bug] Users are unable to login on wikidata.org until they clear their cookies","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",1439539743,"PHID-USER-hms7bpiczbwhx4dxgiqw","PHID-TASK-un2pilpqiazqdfsiinqa","task_subcomment","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).","Had the same issue. Clearing cookies lets me log into Wikidata, but ""locally"". Logging into another Wikimedia site activates the ""global"" login for those. Both work now (no ""you are centrally logged in"" message on Wikidata again).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,6,"True","['Had the same issue.', 'Clearing cookies lets me log into Wikidata, but ""locally"".', 'Logging into another Wikimedia site activates the ""global"" login for those.', 'Both work now (no ""you are centrally logged in"" message on Wikidata again).']",NA,0,"Both work now (no ""you are centrally logged in"" message on Wikidata again)." +20820,"VE - External links between [[ ]], with uppercase Http","I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.",1442856665,"PHID-USER-o34e5i3eq4nstbvcf26w","PHID-TASK-rtfuhijwnygauf3dsovj","task_description","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +URL +URL +URL + +Please, fix VE so that all those strange links are correct.","Needs Triage",90,1443113323,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c3",3,"False","False",11,"True","['VE - External links between [[ ]], with uppercase Http.', ""I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http."", 'URL\nURL\nURL\n\nPlease, fix VE so that all those strange links are correct.']",TRUE,1,"VE - External links between [[ ]], with uppercase Http." +20820,"VE - External links between [[ ]], with uppercase Http","I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.",1442856665,"PHID-USER-o34e5i3eq4nstbvcf26w","PHID-TASK-rtfuhijwnygauf3dsovj","task_description","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +URL +URL +URL + +Please, fix VE so that all those strange links are correct.","Needs Triage",90,1443113323,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c3",3,"False","False",11,"True","['VE - External links between [[ ]], with uppercase Http.', ""I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http."", 'URL\nURL\nURL\n\nPlease, fix VE so that all those strange links are correct.']",TRUE,1,"URL\nURL\nURL\n\nPlease, fix VE so that all those strange links are correct." +20820,"VE - External links between [[ ]], with uppercase Http","I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.",1442856665,"PHID-USER-o34e5i3eq4nstbvcf26w","PHID-TASK-rtfuhijwnygauf3dsovj","task_description","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +https://fr.wikipedia.org/w/index.php?title=Chuzelles&type=revision&diff=118800735&oldid=114011228 +https://fr.wikipedia.org/w/index.php?title=Sabine_Huynh&diff=prev&oldid=118802299 +https://fr.wikipedia.org/w/index.php?title=Cerizay&type=revision&diff=118828198&oldid=117504304 + +Please, fix VE so that all those strange links are correct.","VE - External links between [[ ]], with uppercase Http./n/nI've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http. + +URL +URL +URL + +Please, fix VE so that all those strange links are correct.","Needs Triage",90,1443113323,"PHID-USER-ydswvwhh5pm4lshahjje","duplicate","True","c3",3,"False","False",11,"True","['VE - External links between [[ ]], with uppercase Http.', ""I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http."", 'URL\nURL\nURL\n\nPlease, fix VE so that all those strange links are correct.']",TRUE,1,"I've the feeling of seeing more and more cases of external links between double square brackets with an uppercase H for http." +20821,"VE - External links between [[ ]], with uppercase Http","I think https://phabricator.wikimedia.org/rEVED8e63c9e991adedb2f1d4c1e1d39520aba5bf4fe7 solves it? (If so, we'll know when it lands on Wikipedia).",1443092037,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-rtfuhijwnygauf3dsovj","task_subcomment","I think https://phabricator.wikimedia.org/rEVED8e63c9e991adedb2f1d4c1e1d39520aba5bf4fe7 solves it? (If so, we'll know when it lands on Wikipedia).","I think URL solves it? (If so, we'll know when it lands on Wikipedia).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,12,"True","['I think URL solves it?', ""(If so, we'll know when it lands on Wikipedia).""]",NA,1,"I think URL solves it?" +20821,"VE - External links between [[ ]], with uppercase Http","I think https://phabricator.wikimedia.org/rEVED8e63c9e991adedb2f1d4c1e1d39520aba5bf4fe7 solves it? (If so, we'll know when it lands on Wikipedia).",1443092037,"PHID-USER-wil4b5lylrvf3krixlkl","PHID-TASK-rtfuhijwnygauf3dsovj","task_subcomment","I think https://phabricator.wikimedia.org/rEVED8e63c9e991adedb2f1d4c1e1d39520aba5bf4fe7 solves it? (If so, we'll know when it lands on Wikipedia).","I think URL solves it? (If so, we'll know when it lands on Wikipedia).",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,12,"True","['I think URL solves it?', ""(If so, we'll know when it lands on Wikipedia).""]",NA,1,"(If so, we'll know when it lands on Wikipedia)." +20842,"Fix login browser tests","These are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/",1441339489,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-gouantw3muaylxrp4c2d","task_description","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +URL","Needs Triage",90,1441624679,"PHID-USER-w3pd7vqenmta6vpmhwcn","resolved","True","c3",3,"True","False",9,"True","['Fix login browser tests.', 'These are not smoke tests so were broken by the change to use core login.', 'Please ensure nothing got broken.', 'URL']",TRUE,0,"Fix login browser tests." +20842,"Fix login browser tests","These are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/",1441339489,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-gouantw3muaylxrp4c2d","task_description","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +URL","Needs Triage",90,1441624679,"PHID-USER-w3pd7vqenmta6vpmhwcn","resolved","True","c3",3,"True","False",9,"True","['Fix login browser tests.', 'These are not smoke tests so were broken by the change to use core login.', 'Please ensure nothing got broken.', 'URL']",TRUE,0,"These are not smoke tests so were broken by the change to use core login." +20842,"Fix login browser tests","These are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/",1441339489,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-gouantw3muaylxrp4c2d","task_description","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +URL","Needs Triage",90,1441624679,"PHID-USER-w3pd7vqenmta6vpmhwcn","resolved","True","c3",3,"True","False",9,"True","['Fix login browser tests.', 'These are not smoke tests so were broken by the change to use core login.', 'Please ensure nothing got broken.', 'URL']",TRUE,0,"Please ensure nothing got broken." +20842,"Fix login browser tests","These are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/",1441339489,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-gouantw3muaylxrp4c2d","task_description","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +https://integration.wikimedia.org/ci/job/browsertests-MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox-sauce/806/","Fix login browser tests./n/nThese are not smoke tests so were broken by the change to use core login. Please ensure nothing got broken. +URL","Needs Triage",90,1441624679,"PHID-USER-w3pd7vqenmta6vpmhwcn","resolved","True","c3",3,"True","False",9,"True","['Fix login browser tests.', 'These are not smoke tests so were broken by the change to use core login.', 'Please ensure nothing got broken.', 'URL']",TRUE,0,"URL" +20843,"Fix login browser tests","This is a technical task.",1441624679,"PHID-USER-w3pd7vqenmta6vpmhwcn","PHID-TASK-gouantw3muaylxrp4c2d","task_subcomment","This is a technical task.","This is a technical task.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,9,"True","['This is a technical task.']",NA,0,"This is a technical task." +20844,"Fix login browser tests","Change 236037 merged by jenkins-bot: +QA: Fix failing tests due to change to desktop login form + +[[https://gerrit.wikimedia.org/r/236037]]",1441389283,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-gouantw3muaylxrp4c2d","task_subcomment","Change 236037 merged by jenkins-bot: +QA: Fix failing tests due to change to desktop login form + +[[https://gerrit.wikimedia.org/r/236037]]","Change 236037 merged by jenkins-bot: +QA: Fix failing tests due to change to desktop login form + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,9,"True","['Change 236037 merged by jenkins-bot:\nQA: Fix failing tests due to change to desktop login form\n\n[[GERRIT_URL]]']",NA,0,"Change 236037 merged by jenkins-bot:\nQA: Fix failing tests due to change to desktop login form\n\n[[GERRIT_URL]]" +20845,"Fix login browser tests","Change 236037 had a related patch set uploaded (by Jdlrobson): +Fix failing tests due to change to desktop login form + +[[https://gerrit.wikimedia.org/r/236037]] +",1441383327,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-gouantw3muaylxrp4c2d","task_subcomment","Change 236037 had a related patch set uploaded (by Jdlrobson): +Fix failing tests due to change to desktop login form + +[[https://gerrit.wikimedia.org/r/236037]] +","Change 236037 had a related patch set uploaded (by Jdlrobson): +Fix failing tests due to change to desktop login form + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,9,"True","['Change 236037 had a related patch set uploaded (by Jdlrobson):\nFix failing tests due to change to desktop login form\n\n[[GERRIT_URL]]']",NA,0,"Change 236037 had a related patch set uploaded (by Jdlrobson):\nFix failing tests due to change to desktop login form\n\n[[GERRIT_URL]]" +20878,"Update AjaxLogin to use AuthManager","Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.",1440571935,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-ze2n7oviiqce2yyn7775","task_description","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Needs Triage",90,1499175625,"PHID-USER-mlp7cjyksjzemkdr5ued","declined","True","c3",3,"True","False",7,"True","['Update AjaxLogin to use AuthManager.', 'Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module.', 'The existing code will not continue to reliably work with AuthManager.']",FALSE,0,"Update AjaxLogin to use AuthManager." +20878,"Update AjaxLogin to use AuthManager","Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.",1440571935,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-ze2n7oviiqce2yyn7775","task_description","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Needs Triage",90,1499175625,"PHID-USER-mlp7cjyksjzemkdr5ued","declined","True","c3",3,"True","False",7,"True","['Update AjaxLogin to use AuthManager.', 'Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module.', 'The existing code will not continue to reliably work with AuthManager.']",FALSE,0,"Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module." +20878,"Update AjaxLogin to use AuthManager","Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.",1440571935,"PHID-USER-a6p24cvyblhfzc7we7nc","PHID-TASK-ze2n7oviiqce2yyn7775","task_description","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Update AjaxLogin to use AuthManager./n/nNeeds to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module. The existing code will not continue to reliably work with AuthManager.","Needs Triage",90,1499175625,"PHID-USER-mlp7cjyksjzemkdr5ued","declined","True","c3",3,"True","False",7,"True","['Update AjaxLogin to use AuthManager.', 'Needs to be redone to be based on the APIs provided by MediaWiki core instead of reinventing everything in its own API module.', 'The existing code will not continue to reliably work with AuthManager.']",FALSE,0,"The existing code will not continue to reliably work with AuthManager." +20879,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",1499178622,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service. ]]', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"[[ URL | Done now as a service. ]]" +20879,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",1499178622,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service. ]]', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"Anyways, thanks for dealing with this task and giving the status update." +20879,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",1499178622,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service. ]]', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"SCREEN_NAME It will be cool if you could update the extension's pages accordingly." +20879,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",1499178622,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]] Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service. ]]', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"I know that's painful but that's where users land in the first place." +20880,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",1499178610,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service.', ']].', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"[[ URL | Done now as a service." +20880,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",1499178610,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service.', ']].', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"]]." +20880,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",1499178610,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service.', ']].', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"Anyways, thanks for dealing with this task and giving the status update." +20880,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",1499178610,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service.', ']].', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"SCREEN_NAME It will be cool if you could update the extension's pages accordingly." +20880,"Update AjaxLogin to use AuthManager","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",1499178610,"PHID-USER-37d2msujvpp2rippbzoq","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","@ashley It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ https://www.mediawiki.org/w/index.php?title=Extension%3AAjaxLogin&type=revision&diff=2507168&oldid=2314315 | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.","SCREEN_NAME It will be cool if you could update the extension's pages accordingly. I know that's painful but that's where users land in the first place. [[ URL | Done now as a service. ]]. Anyways, thanks for dealing with this task and giving the status update.",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,104,"True","[""SCREEN_NAME It will be cool if you could update the extension's pages accordingly."", ""I know that's painful but that's where users land in the first place."", '[[ URL | Done now as a service.', ']].', 'Anyways, thanks for dealing with this task and giving the status update.']",NA,0,"I know that's painful but that's where users land in the first place." +20881,"Update AjaxLogin to use AuthManager","Given the existence of Florian's awesome [[https://www.mediawiki.org/wiki/Extension:OOJsUIAjaxLogin|OOJsUIAjaxLogin extension]], which actually works, looks modern and isn't a horrible pile of hacks on top of hacks, I'm going to say that AjaxLogin is deprecated in favor of OOJsUIAjaxLogin and thus I'm declining this task.",1499175625,"PHID-USER-mlp7cjyksjzemkdr5ued","PHID-TASK-ze2n7oviiqce2yyn7775","task_subcomment","Given the existence of Florian's awesome [[https://www.mediawiki.org/wiki/Extension:OOJsUIAjaxLogin|OOJsUIAjaxLogin extension]], which actually works, looks modern and isn't a horrible pile of hacks on top of hacks, I'm going to say that AjaxLogin is deprecated in favor of OOJsUIAjaxLogin and thus I'm declining this task.","Given the existence of Florian's awesome [[URL extension]], which actually works, looks modern and isn't a horrible pile of hacks on top of hacks, I'm going to say that AjaxLogin is deprecated in favor of OOJsUIAjaxLogin and thus I'm declining this task.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,104,"True","[""Given the existence of Florian's awesome [[URL extension]], which actually works, looks modern and isn't a horrible pile of hacks on top of hacks, I'm going to say that AjaxLogin is deprecated in favor of OOJsUIAjaxLogin and thus I'm declining this task.""]",NA,0,"Given the existence of Florian's awesome [[URL extension]], which actually works, looks modern and isn't a horrible pile of hacks on top of hacks, I'm going to say that AjaxLogin is deprecated in favor of OOJsUIAjaxLogin and thus I'm declining this task." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"Link account after login with Google." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\" +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"Or a good and short explanation how to unlink the accounts." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"It's more intuitive to just login and link the google account with a (new or already registered) wiki user." +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"I have a wiki account already" +20926,"Link account after login with Google","After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.",1437599409,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-snmbwgyli2n55stob7ki","task_description","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Link account after login with Google./n/nAfter a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user. + +Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account. It's more intuitive to just login and link the google account with a (new or already registered) wiki user. + +Possible workflow: +- user go to Special:UserLogin +- user clicks Login eith Google +- the, that this google account isn't linked with any wiki user so far, appears +- user selects ""I have a wiki account already"" and clicks ""Next"" +- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user +- after login the user get's the success message, that the google and wiki account is linked together + +Maybe there is an intermediate step before the success message, asking if you really want to link the accounts. Or a good and short explanation how to unlink the accounts.","Needs Triage",90,1439041217,"PHID-USER-c5xwrfdyp3dckkh2nkoj","resolved","True","c3",3,"True","True",2,"True","['Link account after login with Google.', 'After a user logged in with a non-linked Google account, it should be possible to link this account with an already existing wiki user, instead of just the possibility to create a new wiki user.', 'Background: It is, so far, difficult to explain/understand, why a user needs to be logged in to connect the user account with a Google account.', ""It's more intuitive to just login and link the google account with a (new or already registered) wiki user."", 'Possible workflow:\n- user go to Special:UserLogin\n- user clicks Login eith Google\n- the, that this google account isn\'t linked with any wiki user so far, appears\n- user selects ""I have a wiki account already"" and clicks ""Next""\n- user will be redirected to Special:UserLogin with the warning message, that he has to login to merge the user\n- after login the user get\'s the success message, that the google and wiki account is linked together\n\nMaybe there is an intermediate step before the success message, asking if you really want to link the accounts.', 'Or a good and short explanation how to unlink the accounts.']",TRUE,0,"Next" +20927,"Link account after login with Google","Change 226577 merged by jenkins-bot: +Enable to link a new Google account with an existing wiki account + +[[https://gerrit.wikimedia.org/r/226577]]",1439041191,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-snmbwgyli2n55stob7ki","task_subcomment","Change 226577 merged by jenkins-bot: +Enable to link a new Google account with an existing wiki account + +[[https://gerrit.wikimedia.org/r/226577]]","Change 226577 merged by jenkins-bot: +Enable to link a new Google account with an existing wiki account + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,5,"True","['Change 226577 merged by jenkins-bot:\nEnable to link a new Google account with an existing wiki account\n\n[[GERRIT_URL]]']",NA,0,"Change 226577 merged by jenkins-bot:\nEnable to link a new Google account with an existing wiki account\n\n[[GERRIT_URL]]" +20928,"Link account after login with Google","Change 226577 had a related patch set uploaded (by Florianschmidtwelzow): +Enable to link a new Google account with an existing wiki account + +[[https://gerrit.wikimedia.org/r/226577]] +",1437673903,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-snmbwgyli2n55stob7ki","task_subcomment","Change 226577 had a related patch set uploaded (by Florianschmidtwelzow): +Enable to link a new Google account with an existing wiki account + +[[https://gerrit.wikimedia.org/r/226577]] +","Change 226577 had a related patch set uploaded (by Florianschmidtwelzow): +Enable to link a new Google account with an existing wiki account + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,3,"True","['Change 226577 had a related patch set uploaded (by Florianschmidtwelzow):\nEnable to link a new Google account with an existing wiki account\n\n[[GERRIT_URL]]']",NA,0,"Change 226577 had a related patch set uploaded (by Florianschmidtwelzow):\nEnable to link a new Google account with an existing wiki account\n\n[[GERRIT_URL]]" +20974,"Add services team as a contact alert for RESTBase back-end HTTP checks","As of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.",1435878993,"PHID-USER-hxwwywcyzpooynxuo7a2","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_description","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Needs Triage",90,1435880265,"PHID-USER-hxwwywcyzpooynxuo7a2","resolved","True","c3",3,"True","True",0,"True","['Add services team as a contact alert for RESTBase back-end HTTP checks.', 'As of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries.', 'The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.']",TRUE,0,"Add services team as a contact alert for RESTBase back-end HTTP checks." +20974,"Add services team as a contact alert for RESTBase back-end HTTP checks","As of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.",1435878993,"PHID-USER-hxwwywcyzpooynxuo7a2","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_description","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Needs Triage",90,1435880265,"PHID-USER-hxwwywcyzpooynxuo7a2","resolved","True","c3",3,"True","True",0,"True","['Add services team as a contact alert for RESTBase back-end HTTP checks.', 'As of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries.', 'The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.']",TRUE,0,"As of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries." +20974,"Add services team as a contact alert for RESTBase back-end HTTP checks","As of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.",1435878993,"PHID-USER-hxwwywcyzpooynxuo7a2","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_description","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of https://gerrit.wikimedia.org/r/222272 we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Add services team as a contact alert for RESTBase back-end HTTP checks./n/nAs of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries. The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.","Needs Triage",90,1435880265,"PHID-USER-hxwwywcyzpooynxuo7a2","resolved","True","c3",3,"True","True",0,"True","['Add services team as a contact alert for RESTBase back-end HTTP checks.', 'As of GERRIT_URL we have HTTP checks in place to ensure each of the RESTBase nodes responds to simple queries.', 'The Services team would need to be able to receive mails when such checks fail to ensure a prompt response.']",TRUE,0,"The Services team would need to be able to receive mails when such checks fail to ensure a prompt response." +20975,"Add services team as a contact alert for RESTBase back-end HTTP checks","applied on neon: + + +``` +- contact_groups admins ++ contact_groups admins,team-services + host_name restbase1001 + +``` +...",1435880402,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_subcomment","applied on neon: + + +``` +- contact_groups admins ++ contact_groups admins,team-services + host_name restbase1001 + +``` +...","applied on neon: + + +``CODE`` +...",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,0,"True","['applied on neon:\n\n\n``CODE``\n...']",NA,0,"applied on neon:\n\n\n``CODE``\n..." +20976,"Add services team as a contact alert for RESTBase back-end HTTP checks","Thank you, @Dzahn !",1435880291,"PHID-USER-hxwwywcyzpooynxuo7a2","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_subcomment","Thank you, @Dzahn !","Thank you,SCREEN_NAME !",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,0,"True","['Thank you,SCREEN_NAME !']",NA,0,"Thank you,SCREEN_NAME !" +20977,"Add services team as a contact alert for RESTBase back-end HTTP checks","Change 222508 merged by Dzahn: +Add the Services team to the contact list for RESTBase HTTP checks + +[[https://gerrit.wikimedia.org/r/222508]]",1435880076,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_subcomment","Change 222508 merged by Dzahn: +Add the Services team to the contact list for RESTBase HTTP checks + +[[https://gerrit.wikimedia.org/r/222508]]","Change 222508 merged by Dzahn: +Add the Services team to the contact list for RESTBase HTTP checks + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,0,"True","['Change 222508 merged by Dzahn:\nAdd the Services team to the contact list for RESTBase HTTP checks\n\n[[GERRIT_URL]]']",NA,0,"Change 222508 merged by Dzahn:\nAdd the Services team to the contact list for RESTBase HTTP checks\n\n[[GERRIT_URL]]" +20978,"Add services team as a contact alert for RESTBase back-end HTTP checks","Change 222508 had a related patch set uploaded (by Mobrovac): +Add the Services team to the contact list for RESTBase HTTP checks + +[[https://gerrit.wikimedia.org/r/222508]] +",1435879465,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-pzkamw6ajqc4pqyxjyeo","task_subcomment","Change 222508 had a related patch set uploaded (by Mobrovac): +Add the Services team to the contact list for RESTBase HTTP checks + +[[https://gerrit.wikimedia.org/r/222508]] +","Change 222508 had a related patch set uploaded (by Mobrovac): +Add the Services team to the contact list for RESTBase HTTP checks + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,0,"True","['Change 222508 had a related patch set uploaded (by Mobrovac):\nAdd the Services team to the contact list for RESTBase HTTP checks\n\n[[GERRIT_URL]]']",NA,0,"Change 222508 had a related patch set uploaded (by Mobrovac):\nAdd the Services team to the contact list for RESTBase HTTP checks\n\n[[GERRIT_URL]]" +20988,"Login-needed text isn't displayed for all newsletter-pages","The referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=requiredlogintext +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterManage&returntoquery=&warning=requiredlogintext +Although for Special:Newsletters a (different) notice is displayed: +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletters&returntoquery=&warning=exception-nologin-text + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.",1435487640,"PHID-USER-jcypqodpdpbcicgwgh7j","PHID-TASK-uo5x4miw3tt6q2aggbse","task_description","Login-needed text isn't displayed for all newsletter-pages./n/nThe referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=requiredlogintext +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterManage&returntoquery=&warning=requiredlogintext +Although for Special:Newsletters a (different) notice is displayed: +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletters&returntoquery=&warning=exception-nologin-text + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.","Login-needed text isn't displayed for all newsletter-pages./n/nThe referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* URL +* URL +Although for Special:Newsletters a (different) notice is displayed: +* URL + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.","Needs Triage",90,1435493401,"PHID-USER-jcypqodpdpbcicgwgh7j","resolved","True","c3",2,"True","True",-1,"True","[""Login-needed text isn't displayed for all newsletter-pages."", ""The referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage\n* URL\n* URL\nAlthough for Special:Newsletters a (different) notice is displayed:\n* URL\n\nProbably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.""]",TRUE,0,"Login-needed text isn't displayed for all newsletter-pages." +20988,"Login-needed text isn't displayed for all newsletter-pages","The referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=requiredlogintext +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterManage&returntoquery=&warning=requiredlogintext +Although for Special:Newsletters a (different) notice is displayed: +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletters&returntoquery=&warning=exception-nologin-text + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.",1435487640,"PHID-USER-jcypqodpdpbcicgwgh7j","PHID-TASK-uo5x4miw3tt6q2aggbse","task_description","Login-needed text isn't displayed for all newsletter-pages./n/nThe referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=requiredlogintext +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterManage&returntoquery=&warning=requiredlogintext +Although for Special:Newsletters a (different) notice is displayed: +* http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletters&returntoquery=&warning=exception-nologin-text + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.","Login-needed text isn't displayed for all newsletter-pages./n/nThe referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage +* URL +* URL +Although for Special:Newsletters a (different) notice is displayed: +* URL + +Probably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.","Needs Triage",90,1435493401,"PHID-USER-jcypqodpdpbcicgwgh7j","resolved","True","c3",2,"True","True",-1,"True","[""Login-needed text isn't displayed for all newsletter-pages."", ""The referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage\n* URL\n* URL\nAlthough for Special:Newsletters a (different) notice is displayed:\n* URL\n\nProbably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other.""]",TRUE,0,"The referenced warning that login is needed doesn't show up for me for Special:NewsletterCreate and Special:NewsletterManage\n* URL\n* URL\nAlthough for Special:Newsletters a (different) notice is displayed:\n* URL\n\nProbably also shouldn't be 2 different messages where requiredlogintext (defined by newsletter extension) basically duplicates the other." +20989,"Login-needed text isn't displayed for all newsletter-pages","^^ That made every special page on no-login uniform. @Se4598 close it if http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=exception-nologin-text looks good to you",1435492935,"PHID-USER-b3xlpjqyzhcppjoumu63","PHID-TASK-uo5x4miw3tt6q2aggbse","task_subcomment","^^ That made every special page on no-login uniform. @Se4598 close it if http://newsletter-test.wmflabs.org/w/index.php?title=Special:UserLogin&returnto=Special%3ANewsletterCreate&returntoquery=&warning=exception-nologin-text looks good to you","^^ That made every special page on no-login uniform.SCREEN_NAME close it if URL looks good to you",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['^^ That made every special page on no-login uniform.SCREEN_NAME close it if URL looks good to you']",NA,0,"^^ That made every special page on no-login uniform.SCREEN_NAME close it if URL looks good to you" +20990,"Login-needed text isn't displayed for all newsletter-pages","Change 221441 merged by jenkins-bot: +Remove unnecessary parameter passed to requireLogin() + +[[https://gerrit.wikimedia.org/r/221441]]",1435492759,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-uo5x4miw3tt6q2aggbse","task_subcomment","Change 221441 merged by jenkins-bot: +Remove unnecessary parameter passed to requireLogin() + +[[https://gerrit.wikimedia.org/r/221441]]","Change 221441 merged by jenkins-bot: +Remove unnecessary parameter passed to requireLogin() + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['Change 221441 merged by jenkins-bot:\nRemove unnecessary parameter passed to requireLogin()\n\n[[GERRIT_URL]]']",NA,0,"Change 221441 merged by jenkins-bot:\nRemove unnecessary parameter passed to requireLogin()\n\n[[GERRIT_URL]]" +20991,"Login-needed text isn't displayed for all newsletter-pages","Change 221441 had a related patch set uploaded (by Tinaj1234): +Remove unnecessary parameter passed to requireLogin() + +[[https://gerrit.wikimedia.org/r/221441]] +",1435491549,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-uo5x4miw3tt6q2aggbse","task_subcomment","Change 221441 had a related patch set uploaded (by Tinaj1234): +Remove unnecessary parameter passed to requireLogin() + +[[https://gerrit.wikimedia.org/r/221441]] +","Change 221441 had a related patch set uploaded (by Tinaj1234): +Remove unnecessary parameter passed to requireLogin() + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['Change 221441 had a related patch set uploaded (by Tinaj1234):\nRemove unnecessary parameter passed to requireLogin()\n\n[[GERRIT_URL]]']",NA,0,"Change 221441 had a related patch set uploaded (by Tinaj1234):\nRemove unnecessary parameter passed to requireLogin()\n\n[[GERRIT_URL]]" +20992,"Login-needed text isn't displayed for all newsletter-pages","That's strange. For the first two SpecialPage code, we have ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletterCreate.php#L14 ) +``` + $this->requireLogin( 'requiredlogintext' ); +``` +which never shows up in labs, and for the Special:Newsletter which showed up a message, the message-param was not given ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletters.php#L13 ) + +``` +$this->requireLogin(); +```",1435487917,"PHID-USER-b3xlpjqyzhcppjoumu63","PHID-TASK-uo5x4miw3tt6q2aggbse","task_subcomment","That's strange. For the first two SpecialPage code, we have ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletterCreate.php#L14 ) +``` + $this->requireLogin( 'requiredlogintext' ); +``` +which never shows up in labs, and for the Special:Newsletter which showed up a message, the message-param was not given ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletters.php#L13 ) + +``` +$this->requireLogin(); +```","That's strange. For the first two SpecialPage code, we have ( URL ) +``CODE`CODE`CODE``",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","[""That's strange."", 'For the first two SpecialPage code, we have ( URL )\n``CODE`CODE`CODE``']",NA,0,"For the first two SpecialPage code, we have ( URL )\n``CODE`CODE`CODE``" +20992,"Login-needed text isn't displayed for all newsletter-pages","That's strange. For the first two SpecialPage code, we have ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletterCreate.php#L14 ) +``` + $this->requireLogin( 'requiredlogintext' ); +``` +which never shows up in labs, and for the Special:Newsletter which showed up a message, the message-param was not given ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletters.php#L13 ) + +``` +$this->requireLogin(); +```",1435487917,"PHID-USER-b3xlpjqyzhcppjoumu63","PHID-TASK-uo5x4miw3tt6q2aggbse","task_subcomment","That's strange. For the first two SpecialPage code, we have ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletterCreate.php#L14 ) +``` + $this->requireLogin( 'requiredlogintext' ); +``` +which never shows up in labs, and for the Special:Newsletter which showed up a message, the message-param was not given ( https://github.com/wikimedia/mediawiki-extensions-Newsletter/blob/master/includes/SpecialNewsletters.php#L13 ) + +``` +$this->requireLogin(); +```","That's strange. For the first two SpecialPage code, we have ( URL ) +``CODE`CODE`CODE``",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","[""That's strange."", 'For the first two SpecialPage code, we have ( URL )\n``CODE`CODE`CODE``']",NA,0,"That's strange." +21021,"MF Special:Login doesn't have a field for 2FA","This doesn't allow for logins to WT on mobile with TOTP codes.",1435194938,"PHID-USER-zcsdm7lwcehnusyhh6xp","PHID-TASK-xhlvq5ortc7umakdby2q","task_description","MF Special:Login doesn't have a field for 2FA./n/nThis doesn't allow for logins to WT on mobile with TOTP codes.","MF Special:Login doesn't have a field for 2FA./n/nThis doesn't allow for logins to WT on mobile with TOTP codes.","Needs Triage",90,1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","resolved","True","c3",2,"False","False",-1,"True","[""MF Special:Login doesn't have a field for 2FA."", ""This doesn't allow for logins to WT on mobile with TOTP codes.""]",TRUE,0,"MF Special:Login doesn't have a field for 2FA." +21021,"MF Special:Login doesn't have a field for 2FA","This doesn't allow for logins to WT on mobile with TOTP codes.",1435194938,"PHID-USER-zcsdm7lwcehnusyhh6xp","PHID-TASK-xhlvq5ortc7umakdby2q","task_description","MF Special:Login doesn't have a field for 2FA./n/nThis doesn't allow for logins to WT on mobile with TOTP codes.","MF Special:Login doesn't have a field for 2FA./n/nThis doesn't allow for logins to WT on mobile with TOTP codes.","Needs Triage",90,1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","resolved","True","c3",2,"False","False",-1,"True","[""MF Special:Login doesn't have a field for 2FA."", ""This doesn't allow for logins to WT on mobile with TOTP codes.""]",TRUE,0,"This doesn't allow for logins to WT on mobile with TOTP codes." +21022,"MF Special:Login doesn't have a field for 2FA","@Jdlrobson: sorry for not responding here, but i'm in vacation and a bit busy :) But yeah, that will help, enabling this option for wikitech only sounds resonable, too.",1435784248,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","@Jdlrobson: sorry for not responding here, but i'm in vacation and a bit busy :) But yeah, that will help, enabling this option for wikitech only sounds resonable, too.","SCREEN_NAME: sorry for not responding here, but i'm in vacation and a bit busy :) But yeah, that will help, enabling this option for wikitech only sounds resonable, too.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","[""SCREEN_NAME: sorry for not responding here, but i'm in vacation and a bit busy :) But yeah, that will help, enabling this option for wikitech only sounds resonable, too.""]",NA,0,"SCREEN_NAME: sorry for not responding here, but i'm in vacation and a bit busy :) But yeah, that will help, enabling this option for wikitech only sounds resonable, too." +21023,"MF Special:Login doesn't have a field for 2FA","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","['That patch got merged.', 'If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal.', 'If not please file a new more specific bug.', 'Hope that helps!']",NA,0,"That patch got merged." +21023,"MF Special:Login doesn't have a field for 2FA","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","['That patch got merged.', 'If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal.', 'If not please file a new more specific bug.', 'Hope that helps!']",NA,0,"If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal." +21023,"MF Special:Login doesn't have a field for 2FA","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","['That patch got merged.', 'If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal.', 'If not please file a new more specific bug.', 'Hope that helps!']",NA,0,"If not please file a new more specific bug." +21023,"MF Special:Login doesn't have a field for 2FA","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",1435697577,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!","That patch got merged. +If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal. If not please file a new more specific bug. +Hope that helps!",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","['That patch got merged.', 'If you enable $wgMFNoLoginOverride = true; in your LocalSettings it should work as normal.', 'If not please file a new more specific bug.', 'Hope that helps!']",NA,0,"Hope that helps!" +21024,"MF Special:Login doesn't have a field for 2FA","@florian won't https://gerrit.wikimedia.org/r/#/c/219754/ fix this? +",1435264338,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","@florian won't https://gerrit.wikimedia.org/r/#/c/219754/ fix this? +","SCREEN_NAME won't URL fix this? +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","[""SCREEN_NAME won't URL fix this?""]",NA,0,"SCREEN_NAME won't URL fix this?" +21025,"MF Special:Login doesn't have a field for 2FA","I think the best way of resolving this would be to fix: {T74910}",1435264176,"PHID-USER-c5xwrfdyp3dckkh2nkoj","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","I think the best way of resolving this would be to fix: {T74910}","I think the best way of resolving this would be to fix: {T74910}",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","['I think the best way of resolving this would be to fix: {T74910}']",NA,0,"I think the best way of resolving this would be to fix: {T74910}" +21026,"MF Special:Login doesn't have a field for 2FA","The token input will soon no longer be on the login page anyway, but I am not sure how MobileFrontend renders extension special pages.",1435200114,"PHID-USER-ea6gwat27oulytc5tvsy","PHID-TASK-xhlvq5ortc7umakdby2q","task_subcomment","The token input will soon no longer be on the login page anyway, but I am not sure how MobileFrontend renders extension special pages.","The token input will soon no longer be on the login page anyway, but I am not sure how MobileFrontend renders extension special pages.",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['The token input will soon no longer be on the login page anyway, but I am not sure how MobileFrontend renders extension special pages.']",NA,0,"The token input will soon no longer be on the login page anyway, but I am not sure how MobileFrontend renders extension special pages." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"With the unplanned expiration of a couple of SSL certificates, T112542 was generated." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"We need to determine which of these will get icinga checks." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"ssl expiry tracking in icinga - we don't monitor that many domains." +21173,"ssl expiry tracking in icinga - we don't monitor that many domains","With the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +",1443482524,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-qckzskdoj6qw4aeornnu","task_description","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +>>! In T112542#1640176, @BBlack wrote: +> We only have that icinga check on the primary unified cert, which covers the production endpoints for: +> +> - wikipedia.org +> - mediawiki.org +> - wikibooks.org +> - wikidata.org +> - wikimediafoundation.org +> - wikimedia.org +> - wikinews.org +> - wikiquote.org +> - wikisource.org +> - wikiversity.org +> - wikivoyage.org +> - wiktionary.org +> +> ... and all of their mobile subdomains and whatnot. It's a pretty verbose check, validates functional SSL for all of the SAN domains, checks the cert expiry, etc. +> +> But we don't have any kind of checking in place for the various other misc certs we own that are deployed for smaller or one-off services, or deployed to third parties (or in some cases, rare today but important later - not deployed at all but still critical). Just looking at puppet's files/ssl/ today, that list is something like: +> +> +> archiva.wikimedia.org.crt +> blog.wikimedia.org.crt +> dumps.wikimedia.org.crt +> ecc-star.wmfusercontent.org.crt +> eventdonations.wikimedia.org.crt +> ganglia.wikimedia.org.crt +> gerrit.wikimedia.org.crt +> icinga.wikimedia.org.crt +> labvirt-star.eqiad.wmnet.crt +> ldap-codfw.wikimedia.org.crt +> ldap-eqiad.wikimedia.org.crt +> ldap-mirror.wikimedia.org.crt +> librenms.wikimedia.org.crt +> lists.wikimedia.org.crt +> policy.wikimedia.org.crt +> rt.wikimedia.org.crt +> star.planet.wikimedia.org.crt +> star.wmflabs.org.crt +> star.wmfusercontent.org.crt +> stream.wikimedia.org.crt +> tendril.wikimedia.org.crt +> ticket.wikimedia.org.crt +> toolserver.org.crt +> virt-star.eqiad.wmnet.crt +> wikitech.wikimedia.org.crt +> +> +> Of those, I can see in our icinga config direct expiry checks only for: +> +> lists.wikimedia.org +> ticket.wikimedia.org +> ldap-codfw.wikimedia.org +> ldap-eqiad.wikimedia.org +> + +Additionally: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1yT5rvoEEUHhNeJAQRVamr8ECqN3TLsMaO8N_At4Ki3I/edit?usp=sharing lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","ssl expiry tracking in icinga - we don't monitor that many domains./n/nWith the unplanned expiration of a couple of SSL certificates, T112542 was generated. Since then, we've listed all of the domains we purchased certificates from. + +Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate. +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +Additionally: URL lists all the certificates and expiry info. + +We need to determine which of these will get icinga checks. +","High",80,1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","resolved","True","c3",3,"True","False",12,"True","[""ssl expiry tracking in icinga - we don't monitor that many domains."", 'With the unplanned expiration of a couple of SSL certificates, T112542 was generated.', ""Since then, we've listed all of the domains we purchased certificates from."", 'Now we need to decide if we are going to put in icinga checks for all of them, or just some, and how to differentiate.', 'QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nAdditionally: URL lists all the certificates and expiry info.', 'We need to determine which of these will get icinga checks.']",FALSE,0,"Since then, we've listed all of the domains we purchased certificates from." +21174,"ssl expiry tracking in icinga - we don't monitor that many domains","https://etherpad.wikimedia.org/p/T114059",1445551786,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","https://etherpad.wikimedia.org/p/T114059","URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['URL']",NA,0,"URL" +21175,"ssl expiry tracking in icinga - we don't monitor that many domains","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ",1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['All the certs in the original list in the ticket are covered now.', 'The only exception is the special case for labvirtstar.']",NA,0,"All the certs in the original list in the ticket are covered now." +21175,"ssl expiry tracking in icinga - we don't monitor that many domains","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ",1445551708,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ","All the certs in the original list in the ticket are covered now. The only exception is the special case for labvirtstar. ",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['All the certs in the original list in the ticket are covered now.', 'The only exception is the special case for labvirtstar.']",NA,0,"The only exception is the special case for labvirtstar." +21176,"ssl expiry tracking in icinga - we don't monitor that many domains","We agreed to split this special case into a non-blocking subtask -> T116332",1445551255,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","We agreed to split this special case into a non-blocking subtask -> T116332","We agreed to split this special case into a non-blocking subtask -> T116332",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['We agreed to split this special case into a non-blocking subtask -> T116332']",NA,0,"We agreed to split this special case into a non-blocking subtask -> T116332" +21177,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",1445526623,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on."", ""(edit: labvirt-star is the interesting one, virt-star isn't used in production.)""]",NA,0,"virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another." +21177,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",1445526623,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on."", ""(edit: labvirt-star is the interesting one, virt-star isn't used in production.)""]",NA,0,"It's almost certainly self-signed." +21177,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",1445526623,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on."", ""(edit: labvirt-star is the interesting one, virt-star isn't used in production.)""]",NA,0,"I'll try to figure out what port you can test it on." +21177,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",1445526623,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on. + +(edit: labvirt-star is the interesting one, virt-star isn't used in production.)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on."", ""(edit: labvirt-star is the interesting one, virt-star isn't used in production.)""]",NA,0,"(edit: labvirt-star is the interesting one, virt-star isn't used in production.)" +21178,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",1445522253,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on.""]",NA,0,"virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another." +21178,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",1445522253,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on.""]",NA,0,"It's almost certainly self-signed." +21178,"ssl expiry tracking in icinga - we don't monitor that many domains","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",1445522253,"PHID-USER-22bsa5u75jz3ci3wnplu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.","virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another. It's almost certainly self-signed. I'll try to figure out what port you can test it on.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['virt-star is used by the nova-compute services to talk to each other, for example when migrating instances from one place to another.', ""It's almost certainly self-signed."", ""I'll try to figure out what port you can test it on.""]",NA,0,"I'll try to figure out what port you can test it on." +21179,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476677,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"SCREEN_NAME which service on which port uses the virt-star cert?" +21179,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476677,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?" +21179,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476677,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrew which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"seem to respond to openssl" +21180,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476667,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"SCREEN_NAME which service on which port uses the virt-star cert?" +21180,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476667,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?" +21180,"ssl expiry tracking in icinga - we don't monitor that many domains","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",1445476667,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","@andrewbogott which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl","SCREEN_NAME which service on which port uses the virt-star cert? i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ? seem to respond to openssl",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['SCREEN_NAME which service on which port uses the virt-star cert?', 'i see virt100x compute nodes had it, and exist in site.pp but _not in DNS_ and labvirt1001 should have it now but none of the services on thse high ports 59xx ?', 'seem to respond to openssl']",NA,0,"seem to respond to openssl" +21181,"ssl expiry tracking in icinga - we don't monitor that many domains","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",1445473969,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['re: LDAP-mirror: nothing to monitor here, because Icinga said:\n\n""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused ""\n\nand puppet code says:\n\nport => \'389\', # Yes, explicitly not supporting LDAPS (port 636)\n\n(but we still have the cert for it?', 'oh well)']",NA,0,"re: LDAP-mirror: nothing to monitor here, because Icinga said:\n\n""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused ""\n\nand puppet code says:\n\nport => \" +21181,"ssl expiry tracking in icinga - we don't monitor that many domains","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",1445473969,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['re: LDAP-mirror: nothing to monitor here, because Icinga said:\n\n""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused ""\n\nand puppet code says:\n\nport => \'389\', # Yes, explicitly not supporting LDAPS (port 636)\n\n(but we still have the cert for it?', 'oh well)']",NA,0,", # Yes, explicitly not supporting LDAPS (port 636)\n\n(but we still have the cert for it?" +21181,"ssl expiry tracking in icinga - we don't monitor that many domains","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",1445473969,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)","re: LDAP-mirror: nothing to monitor here, because Icinga said: + +""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused "" + +and puppet code says: + +port => '389', # Yes, explicitly not supporting LDAPS (port 636) + +(but we still have the cert for it? oh well)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['re: LDAP-mirror: nothing to monitor here, because Icinga said:\n\n""SSL CRITICAL - failed to connect or SSL handshake:IO::Socket::SSL: connect: Connection refused ""\n\nand puppet code says:\n\nport => \'389\', # Yes, explicitly not supporting LDAPS (port 636)\n\n(but we still have the cert for it?', 'oh well)']",NA,0,"oh well)" +21182,"ssl expiry tracking in icinga - we don't monitor that many domains","wmfusercontent done: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=phab.wmfusercontent.org&service=HTTPS-wmfusercontent + +LDAP (corp/OIT) mirror (has issues): + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=plutonium&service=SSL-LDAP +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=pollux&service=SSL-LDAP + +virt-star: ?",1445473513,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","wmfusercontent done: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=phab.wmfusercontent.org&service=HTTPS-wmfusercontent + +LDAP (corp/OIT) mirror (has issues): + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=plutonium&service=SSL-LDAP +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=pollux&service=SSL-LDAP + +virt-star: ?","wmfusercontent done: URL + +LDAP (corp/OIT) mirror (has issues): + +URL +URL + +virt-star: ?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['wmfusercontent done: URL\n\nLDAP (corp/OIT) mirror (has issues):\n\nURL \nURL\n\nvirt-star: ?']",NA,0,"wmfusercontent done: URL\n\nLDAP (corp/OIT) mirror (has issues):\n\nURL \nURL\n\nvirt-star: ?" +21183,"ssl expiry tracking in icinga - we don't monitor that many domains","skip ldap-mirror. that should be this https://gerrit.wikimedia.org/r/#/c/247936/1/manifests/role/openldap.pp",1445470863,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","skip ldap-mirror. that should be this https://gerrit.wikimedia.org/r/#/c/247936/1/manifests/role/openldap.pp","skip ldap-mirror. that should be this URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['skip ldap-mirror.', 'that should be this URL']",NA,0,"skip ldap-mirror." +21183,"ssl expiry tracking in icinga - we don't monitor that many domains","skip ldap-mirror. that should be this https://gerrit.wikimedia.org/r/#/c/247936/1/manifests/role/openldap.pp",1445470863,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","skip ldap-mirror. that should be this https://gerrit.wikimedia.org/r/#/c/247936/1/manifests/role/openldap.pp","skip ldap-mirror. that should be this URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['skip ldap-mirror.', 'that should be this URL']",NA,0,"that should be this URL" +21184,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?",1445470110,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +SCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt\nSCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?']",NA,0,"ok, all done, except these remnants." +21184,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?",1445470110,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +SCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt\nSCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?']",NA,0,"can you help me here?" +21184,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?",1445470110,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +SCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt\nSCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?']",NA,0,"ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt\nSCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?" +21184,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?",1445470110,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt + +@andrew @chasemp @yuvipanda can you tell me if these certs above are actually used and on which FQDN they are expected?","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +SCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt\nSCREEN_NAMESCREEN_NAMESCREEN_NAME can you tell me if these certs above are actually used and on which FQDN they are expected?']",NA,0,"what's the status?" +21185,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",1445469829,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt']",NA,0,"ok, all done, except these remnants." +21185,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",1445469829,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt']",NA,0,"can you help me here?" +21185,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",1445469829,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt']",NA,0,"ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt" +21185,"ssl expiry tracking in icinga - we don't monitor that many domains","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",1445469829,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +","ok, all done, except these remnants. + +can you help me here? what's the status? + +ecc-star.wmfusercontent.org.crt +labvirt-star.eqiad.wmnet.crt +ldap-mirror.wikimedia.org.crt +star.wmfusercontent.org.crt +virt-star.eqiad.wmnet.crt +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['ok, all done, except these remnants.', 'can you help me here?', ""what's the status?"", 'ecc-star.wmfusercontent.org.crt \nlabvirt-star.eqiad.wmnet.crt \nldap-mirror.wikimedia.org.crt \nstar.wmfusercontent.org.crt\nvirt-star.eqiad.wmnet.crt']",NA,0,"what's the status?" +21186,"ssl expiry tracking in icinga - we don't monitor that many domains","planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=1&host=en.planet.wikimedia.org +labs / tools.wmflabs.org https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=tools.wmflabs.org&service=HTTPS-wmflabs +ldap-codfw: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=nembus&service=LDAP-SSL +ldap-eqiad: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neptunium&service=LDAP-SSL +",1445469703,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=1&host=en.planet.wikimedia.org +labs / tools.wmflabs.org https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=tools.wmflabs.org&service=HTTPS-wmflabs +ldap-codfw: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=nembus&service=LDAP-SSL +ldap-eqiad: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neptunium&service=LDAP-SSL +","planet: URL +labs / tools.wmflabs.org URL +ldap-codfw: URL +ldap-eqiad: URL +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['planet: URL\nlabs / tools.wmflabs.org URL\nldap-codfw: URL\nldap-eqiad: URL']",NA,0,"planet: URL\nlabs / tools.wmflabs.org URL\nldap-codfw: URL\nldap-eqiad: URL" +21187,"ssl expiry tracking in icinga - we don't monitor that many domains","policy: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=1&host=policy.wikimedia.org +blog: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=blog.wikimedia.org&service=HTTPS-blog +toolserver: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=www.toolserver.org&service=HTTPS-toolserver +eventdonations: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=eventdonations.wikimedia.org&service=HTTPS-eventdonations (HOST down due to filtered ICMP?) +",1445465830,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","policy: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=1&host=policy.wikimedia.org +blog: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=blog.wikimedia.org&service=HTTPS-blog +toolserver: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=www.toolserver.org&service=HTTPS-toolserver +eventdonations: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=eventdonations.wikimedia.org&service=HTTPS-eventdonations (HOST down due to filtered ICMP?) +","policy: URL +blog: URL +toolserver: URL +eventdonations: URL (HOST down due to filtered ICMP?) +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['policy: URL\nblog: URL\ntoolserver: URL\neventdonations: URL (HOST down due to filtered ICMP?)']",NA,0,"policy: URL\nblog: URL\ntoolserver: URL\neventdonations: URL (HOST down due to filtered ICMP?)" +21188,"ssl expiry tracking in icinga - we don't monitor that many domains","archiva: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=titanium&service=HTTPS +ganglia: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=uranium&service=HTTPS +rcstream: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=rcs1001&service=HTTPS",1445458696,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","archiva: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=titanium&service=HTTPS +ganglia: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=uranium&service=HTTPS +rcstream: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=rcs1001&service=HTTPS","archiva: URL +ganglia: URL +rcstream: URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['archiva: URL\nganglia: URL\nrcstream: URL']",NA,0,"archiva: URL\nganglia: URL\nrcstream: URL" +21189,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 247905 merged by Dzahn: +icinga: ssl cert monitoring for external services + +[[https://gerrit.wikimedia.org/r/247905]]",1445458424,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 247905 merged by Dzahn: +icinga: ssl cert monitoring for external services + +[[https://gerrit.wikimedia.org/r/247905]]","Change 247905 merged by Dzahn: +icinga: ssl cert monitoring for external services + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 247905 merged by Dzahn:\nicinga: ssl cert monitoring for external services\n\n[[GERRIT_URL]]']",NA,0,"Change 247905 merged by Dzahn:\nicinga: ssl cert monitoring for external services\n\n[[GERRIT_URL]]" +21190,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 247905 had a related patch set uploaded (by Dzahn): +icinga: ssl cert monitoring for external services + +[[https://gerrit.wikimedia.org/r/247905]] +",1445456759,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 247905 had a related patch set uploaded (by Dzahn): +icinga: ssl cert monitoring for external services + +[[https://gerrit.wikimedia.org/r/247905]] +","Change 247905 had a related patch set uploaded (by Dzahn): +icinga: ssl cert monitoring for external services + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 247905 had a related patch set uploaded (by Dzahn):\nicinga: ssl cert monitoring for external services\n\n[[GERRIT_URL]]']",NA,0,"Change 247905 had a related patch set uploaded (by Dzahn):\nicinga: ssl cert monitoring for external services\n\n[[GERRIT_URL]]" +21191,"ssl expiry tracking in icinga - we don't monitor that many domains","dumps: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=dataset1001&service=HTTPS +OTRS: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=iodine&service=HTTPS +lists: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=fermium&service=HTTPS +icinga: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS +gerrit: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS +RT: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=magnesium&service=HTTPS +planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=planet1001&service=HTTPS (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=netmon1001&service=HTTPS",1445382346,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","dumps: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=dataset1001&service=HTTPS +OTRS: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=iodine&service=HTTPS +lists: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=fermium&service=HTTPS +icinga: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS +gerrit: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS +RT: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=magnesium&service=HTTPS +planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=planet1001&service=HTTPS (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=netmon1001&service=HTTPS","dumps: URL +OTRS: URL +lists: URL +icinga: URL +gerrit: URL +RT: URL +planet: URL (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['dumps: URL\nOTRS: URL\nlists: URL\nicinga: URL\ngerrit: URL\nRT: URL\nplanet: URL (BROKEN, this needs to be on the cp boxes, special case! )', 'librenms: URL']",NA,0,"dumps: URL\nOTRS: URL\nlists: URL\nicinga: URL\ngerrit: URL\nRT: URL\nplanet: URL (BROKEN, this needs to be on the cp boxes, special case! )" +21191,"ssl expiry tracking in icinga - we don't monitor that many domains","dumps: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=dataset1001&service=HTTPS +OTRS: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=iodine&service=HTTPS +lists: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=fermium&service=HTTPS +icinga: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS +gerrit: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS +RT: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=magnesium&service=HTTPS +planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=planet1001&service=HTTPS (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=netmon1001&service=HTTPS",1445382346,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","dumps: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=dataset1001&service=HTTPS +OTRS: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=iodine&service=HTTPS +lists: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=fermium&service=HTTPS +icinga: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS +gerrit: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS +RT: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=magnesium&service=HTTPS +planet: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=planet1001&service=HTTPS (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=netmon1001&service=HTTPS","dumps: URL +OTRS: URL +lists: URL +icinga: URL +gerrit: URL +RT: URL +planet: URL (BROKEN, this needs to be on the cp boxes, special case! ) +librenms: URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['dumps: URL\nOTRS: URL\nlists: URL\nicinga: URL\ngerrit: URL\nRT: URL\nplanet: URL (BROKEN, this needs to be on the cp boxes, special case! )', 'librenms: URL']",NA,0,"librenms: URL" +21192,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 247744 merged by Dzahn: +planet: add ssl cert expiry check + +[[https://gerrit.wikimedia.org/r/247744]]",1445379300,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 247744 merged by Dzahn: +planet: add ssl cert expiry check + +[[https://gerrit.wikimedia.org/r/247744]]","Change 247744 merged by Dzahn: +planet: add ssl cert expiry check + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 247744 merged by Dzahn:\nplanet: add ssl cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 247744 merged by Dzahn:\nplanet: add ssl cert expiry check\n\n[[GERRIT_URL]]" +21193,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 247744 had a related patch set uploaded (by Dzahn): +planet: add ssl cert expiry check + +[[https://gerrit.wikimedia.org/r/247744]] +",1445379159,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 247744 had a related patch set uploaded (by Dzahn): +planet: add ssl cert expiry check + +[[https://gerrit.wikimedia.org/r/247744]] +","Change 247744 had a related patch set uploaded (by Dzahn): +planet: add ssl cert expiry check + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 247744 had a related patch set uploaded (by Dzahn):\nplanet: add ssl cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 247744 had a related patch set uploaded (by Dzahn):\nplanet: add ssl cert expiry check\n\n[[GERRIT_URL]]" +21194,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244617 merged by Dzahn: +dumps: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244617]]",1445378386,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244617 merged by Dzahn: +dumps: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244617]]","Change 244617 merged by Dzahn: +dumps: add cert expiry check + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 244617 merged by Dzahn:\ndumps: add cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 244617 merged by Dzahn:\ndumps: add cert expiry check\n\n[[GERRIT_URL]]" +21195,"ssl expiry tracking in icinga - we don't monitor that many domains","progress tracking on etherpad now: + +https://etherpad.wikimedia.org/p/T114059",1445372893,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","progress tracking on etherpad now: + +https://etherpad.wikimedia.org/p/T114059","progress tracking on etherpad now: + +URL",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['progress tracking on etherpad now:\n\nURL']",NA,0,"progress tracking on etherpad now:\n\nURL" +21196,"ssl expiry tracking in icinga - we don't monitor that many domains","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)",1445369326,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +URL + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","[""and let's also have meta monitoring."", 'icinga itself should have a working cert :)\n\nadded:\n\nURL\n\nSSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)']",NA,0,"icinga itself should have a working cert :)\n\nadded:\n\nURL\n\nSSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)" +21196,"ssl expiry tracking in icinga - we don't monitor that many domains","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)",1445369326,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=neon&service=HTTPS + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)","and let's also have meta monitoring. icinga itself should have a working cert :) + +added: + +URL + +SSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","[""and let's also have meta monitoring."", 'icinga itself should have a working cert :)\n\nadded:\n\nURL\n\nSSL OK - Certificate icinga.wikimedia.org valid until 2016-01-08 03:00:46 +0000 (expires in 79 days)']",NA,0,"and let's also have meta monitoring." +21197,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244614 merged by Dzahn: +icinga: add cert expiry check for icinga itself + +[[https://gerrit.wikimedia.org/r/244614]]",1445364298,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244614 merged by Dzahn: +icinga: add cert expiry check for icinga itself + +[[https://gerrit.wikimedia.org/r/244614]]","Change 244614 merged by Dzahn: +icinga: add cert expiry check for icinga itself + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 244614 merged by Dzahn:\nicinga: add cert expiry check for icinga itself\n\n[[GERRIT_URL]]']",NA,0,"Change 244614 merged by Dzahn:\nicinga: add cert expiry check for icinga itself\n\n[[GERRIT_URL]]" +21198,"ssl expiry tracking in icinga - we don't monitor that many domains","https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=silver&service=HTTPS + +SSL OK - Certificate wikitech.wikimedia.org valid until 2016-01-25 04:44:13 +0000 (expires in 96 days) +",1445352123,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=silver&service=HTTPS + +SSL OK - Certificate wikitech.wikimedia.org valid until 2016-01-25 04:44:13 +0000 (expires in 96 days) +","URL + +SSL OK - Certificate wikitech.wikimedia.org valid until 2016-01-25 04:44:13 +0000 (expires in 96 days) +",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['URL\n\nSSL OK - Certificate wikitech.wikimedia.org valid until 2016-01-25 04:44:13 +0000 (expires in 96 days)']",NA,0,"URL\n\nSSL OK - Certificate wikitech.wikimedia.org valid until 2016-01-25 04:44:13 +0000 (expires in 96 days)" +21199,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244610 merged by Faidon Liambotis: +wikitech: add SSL cert expiry monitoring + +[[https://gerrit.wikimedia.org/r/244610]]",1445349629,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244610 merged by Faidon Liambotis: +wikitech: add SSL cert expiry monitoring + +[[https://gerrit.wikimedia.org/r/244610]]","Change 244610 merged by Faidon Liambotis: +wikitech: add SSL cert expiry monitoring + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 244610 merged by Faidon Liambotis:\nwikitech: add SSL cert expiry monitoring\n\n[[GERRIT_URL]]']",NA,0,"Change 244610 merged by Faidon Liambotis:\nwikitech: add SSL cert expiry monitoring\n\n[[GERRIT_URL]]" +21200,"ssl expiry tracking in icinga - we don't monitor that many domains","check for gerrit cert added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""",1445301253,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","check for gerrit cert added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""","check for gerrit cert added: + +URL + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['check for gerrit cert added:\n\nURL\n\n""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""']",NA,0,"check for gerrit cert added:\n\nURL\n\n""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""" +21201,"ssl expiry tracking in icinga - we don't monitor that many domains","check forgerrit cert added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""",1445301213,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","check forgerrit cert added: + +https://icinga.wikimedia.org/cgi-bin/icinga/extinfo.cgi?type=2&host=ytterbium&service=HTTPS + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""","check forgerrit cert added: + +URL + +""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,15,"True","['check forgerrit cert added:\n\nURL\n\n""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""']",NA,0,"check forgerrit cert added:\n\nURL\n\n""SSL OK - Certificate gerrit.wikimedia.org valid until 2018-05-25 21:30:06 +0000 (expires in 948 days)""" +21202,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244618 merged by Dzahn: +gerrit: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244618]]",1445299346,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244618 merged by Dzahn: +gerrit: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244618]]","Change 244618 merged by Dzahn: +gerrit: add cert expiry check + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,15,"True","['Change 244618 merged by Dzahn:\ngerrit: add cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 244618 merged by Dzahn:\ngerrit: add cert expiry check\n\n[[GERRIT_URL]]" +21203,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244618 had a related patch set uploaded (by Dzahn): +gerrit: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244618]] +",1444345854,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244618 had a related patch set uploaded (by Dzahn): +gerrit: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244618]] +","Change 244618 had a related patch set uploaded (by Dzahn): +gerrit: add cert expiry check + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,14,"True","['Change 244618 had a related patch set uploaded (by Dzahn):\ngerrit: add cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 244618 had a related patch set uploaded (by Dzahn):\ngerrit: add cert expiry check\n\n[[GERRIT_URL]]" +21204,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244617 had a related patch set uploaded (by Dzahn): +dumps: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244617]] +",1444345726,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244617 had a related patch set uploaded (by Dzahn): +dumps: add cert expiry check + +[[https://gerrit.wikimedia.org/r/244617]] +","Change 244617 had a related patch set uploaded (by Dzahn): +dumps: add cert expiry check + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,14,"True","['Change 244617 had a related patch set uploaded (by Dzahn):\ndumps: add cert expiry check\n\n[[GERRIT_URL]]']",NA,0,"Change 244617 had a related patch set uploaded (by Dzahn):\ndumps: add cert expiry check\n\n[[GERRIT_URL]]" +21205,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244614 had a related patch set uploaded (by Dzahn): +icinga: add ssl cert expiry for icinga itself + +[[https://gerrit.wikimedia.org/r/244614]] +",1444345547,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244614 had a related patch set uploaded (by Dzahn): +icinga: add ssl cert expiry for icinga itself + +[[https://gerrit.wikimedia.org/r/244614]] +","Change 244614 had a related patch set uploaded (by Dzahn): +icinga: add ssl cert expiry for icinga itself + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,14,"True","['Change 244614 had a related patch set uploaded (by Dzahn):\nicinga: add ssl cert expiry for icinga itself\n\n[[GERRIT_URL]]']",NA,0,"Change 244614 had a related patch set uploaded (by Dzahn):\nicinga: add ssl cert expiry for icinga itself\n\n[[GERRIT_URL]]" +21206,"ssl expiry tracking in icinga - we don't monitor that many domains","Change 244610 had a related patch set uploaded (by Dzahn): +wikitech: add SSL cert expiry monitoring + +[[https://gerrit.wikimedia.org/r/244610]] +",1444345251,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","Change 244610 had a related patch set uploaded (by Dzahn): +wikitech: add SSL cert expiry monitoring + +[[https://gerrit.wikimedia.org/r/244610]] +","Change 244610 had a related patch set uploaded (by Dzahn): +wikitech: add SSL cert expiry monitoring + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,14,"True","['Change 244610 had a related patch set uploaded (by Dzahn):\nwikitech: add SSL cert expiry monitoring\n\n[[GERRIT_URL]]']",NA,0,"Change 244610 had a related patch set uploaded (by Dzahn):\nwikitech: add SSL cert expiry monitoring\n\n[[GERRIT_URL]]" +21207,"ssl expiry tracking in icinga - we don't monitor that many domains","The following are covered already: + +- lists +- otrs + +because they use the `check_ssl_http` check_command which is defined in `modules/nagios_common/files/check_commands/check_ssl.cfg` and set to warn at 60 and go CRIT at 30 days before expiry, it uses `check_ssl`, written by Faidon, which has a `sub ssl_expiry_check`. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.",1444344782,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","The following are covered already: + +- lists +- otrs + +because they use the `check_ssl_http` check_command which is defined in `modules/nagios_common/files/check_commands/check_ssl.cfg` and set to warn at 60 and go CRIT at 30 days before expiry, it uses `check_ssl`, written by Faidon, which has a `sub ssl_expiry_check`. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.","The following are covered already: + +- lists +- otrs + +because they use the CODE check_command which is defined in CODE and set to warn at 60 and go CRIT at 30 days before expiry, it uses CODE, written by Faidon, which has a CODE. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,14,"True","['The following are covered already:\n\n- lists\n- otrs\n\nbecause they use the CODE check_command which is defined in CODE and set to warn at 60 and go CRIT at 30 days before expiry, it uses CODE, written by Faidon, which has a CODE.', ""i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.""]",NA,0,"The following are covered already:\n\n- lists\n- otrs\n\nbecause they use the CODE check_command which is defined in CODE and set to warn at 60 and go CRIT at 30 days before expiry, it uses CODE, written by Faidon, which has a CODE." +21207,"ssl expiry tracking in icinga - we don't monitor that many domains","The following are covered already: + +- lists +- otrs + +because they use the `check_ssl_http` check_command which is defined in `modules/nagios_common/files/check_commands/check_ssl.cfg` and set to warn at 60 and go CRIT at 30 days before expiry, it uses `check_ssl`, written by Faidon, which has a `sub ssl_expiry_check`. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.",1444344782,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","The following are covered already: + +- lists +- otrs + +because they use the `check_ssl_http` check_command which is defined in `modules/nagios_common/files/check_commands/check_ssl.cfg` and set to warn at 60 and go CRIT at 30 days before expiry, it uses `check_ssl`, written by Faidon, which has a `sub ssl_expiry_check`. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.","The following are covered already: + +- lists +- otrs + +because they use the CODE check_command which is defined in CODE and set to warn at 60 and go CRIT at 30 days before expiry, it uses CODE, written by Faidon, which has a CODE. + +i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,14,"True","['The following are covered already:\n\n- lists\n- otrs\n\nbecause they use the CODE check_command which is defined in CODE and set to warn at 60 and go CRIT at 30 days before expiry, it uses CODE, written by Faidon, which has a CODE.', ""i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class.""]",NA,0,"i'm going to upload a change or more to add checks for other services using the same method, in a monitoring::service in the role class." +21208,"ssl expiry tracking in icinga - we don't monitor that many domains","The following are covered already: + +- lists +- otrs",1444344473,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-qckzskdoj6qw4aeornnu","task_subcomment","The following are covered already: + +- lists +- otrs","The following are covered already: + +- lists +- otrs",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,14,"True","['The following are covered already:\n\n- lists\n- otrs']",NA,0,"The following are covered already:\n\n- lists\n- otrs" +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Trying to run a script on cron for the HostBot project." +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Script works as expected when manually run from the command line, fails on JSUB." +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent." +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Is this expected behavior?" +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Can that Python be updated?" +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``" +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"can't import _SSL in /usr/lib/python2.7/ssl.py." +21423,"can't import _SSL in /usr/lib/python2.7/ssl.py","Trying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```",1436477749,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_description","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import `_ssl`. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``` +*/5 * * * * jsub -N matchbotenwiki /data/project/hostbot/matchbot/bin/python /data/project/hostbot/bot/matchbot/matchbot/matchbot.py /data/project/hostbot/bot/matchbot/matchbot/ +``` + +Stack trace: + +``` +Traceback (most recent call last): + File ""/data/project/hostbot/bot/matchbot/matchbot/matchbot.py"", line 34, in + import mwclient + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/__init__.py"", line 27, in + from client import Site, __ver__ + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/mwclient/client.py"", line 22, in + import requests + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/__init__.py"", line 58, in + from . import utils + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/utils.py"", line 26, in + from .compat import parse_http_list as _parse_list_header + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/compat.py"", line 7, in + from .packages import chardet + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/__init__.py"", line 3, in + from . import urllib3 + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/__init__.py"", line 10, in + from .connectionpool import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py"", line 31, in + from .connection import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/connection.py"", line 45, in + from .util.ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/__init__.py"", line 5, in + from .ssl_ import ( + File ""/data/project/hostbot/matchbot/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py"", line 12, in + import ssl + File ""/usr/lib/python2.7/ssl.py"", line 60, in + import _ssl # if we can't import it, let the error propagate +ImportError: No module named _ssl +```","can't import _SSL in /usr/lib/python2.7/ssl.py./n/nTrying to run a script on cron for the HostBot project. Script works as expected when manually run from the command line, fails on JSUB. This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent. + +Looks like it's using an instance of Python that can't import CODE. Is this expected behavior? Can that Python be updated? Any help appreciated :) + +cron job: + +``CODE`CODE`CODE``","High",80,1436479534,"PHID-USER-i6la3rbocleoqjqldvzu","resolved","True","c3",3,"True","True",1,"True","[""can't import _SSL in /usr/lib/python2.7/ssl.py."", 'Trying to run a script on cron for the HostBot project.', 'Script works as expected when manually run from the command line, fails on JSUB.', 'This is using a virtualenv with the dev version of mwclient, since the version on labs is an older one without support for setting a user-agent.', ""Looks like it's using an instance of Python that can't import CODE."", 'Is this expected behavior?', 'Can that Python be updated?', 'Any help appreciated :)\n\ncron job:\n\n``CODE`CODE`CODE``']",TRUE,0,"Looks like it's using an instance of Python that can't import CODE." +21424,"can't import _SSL in /usr/lib/python2.7/ssl.py","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```",1436479522,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_subcomment","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```","Fixed bySCREEN_NAME andSCREEN_NAME. Solution below. + +``CODE``",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,1,"True","['Fixed bySCREEN_NAME andSCREEN_NAME.', 'Solution below.', '``CODE``']",NA,0,"Fixed bySCREEN_NAME andSCREEN_NAME." +21424,"can't import _SSL in /usr/lib/python2.7/ssl.py","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```",1436479522,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_subcomment","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```","Fixed bySCREEN_NAME andSCREEN_NAME. Solution below. + +``CODE``",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,1,"True","['Fixed bySCREEN_NAME andSCREEN_NAME.', 'Solution below.', '``CODE``']",NA,0,"Solution below." +21424,"can't import _SSL in /usr/lib/python2.7/ssl.py","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```",1436479522,"PHID-USER-i6la3rbocleoqjqldvzu","PHID-TASK-kcqa6up27sfqrdwqqfed","task_subcomment","Fixed by @yuvipanda and @fhocutt. Solution below. + +``` + jsub -N -l release=trusty +```","Fixed bySCREEN_NAME andSCREEN_NAME. Solution below. + +``CODE``",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,1,"True","['Fixed bySCREEN_NAME andSCREEN_NAME.', 'Solution below.', '``CODE``']",NA,0,"``CODE``" +21661,"Authenticate via the API for login steps","Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).",1442506850,"PHID-USER-7bifphmxtcqgvdofuzla","PHID-TASK-szootqtj2wa72tc5big3","task_description","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Medium",50,1442934396,"PHID-USER-7bifphmxtcqgvdofuzla","resolved","True","c3",3,"True","True",11,"True","['Authenticate via the API for login steps.', 'Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser.', 'It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).']",TRUE,1,"Authenticate via the API for login steps." +21661,"Authenticate via the API for login steps","Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).",1442506850,"PHID-USER-7bifphmxtcqgvdofuzla","PHID-TASK-szootqtj2wa72tc5big3","task_description","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Medium",50,1442934396,"PHID-USER-7bifphmxtcqgvdofuzla","resolved","True","c3",3,"True","True",11,"True","['Authenticate via the API for login steps.', 'Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser.', 'It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).']",TRUE,1,"Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser." +21661,"Authenticate via the API for login steps","Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).",1442506850,"PHID-USER-7bifphmxtcqgvdofuzla","PHID-TASK-szootqtj2wa72tc5big3","task_description","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Authenticate via the API for login steps./n/nAuthenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser. It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).","Medium",50,1442934396,"PHID-USER-7bifphmxtcqgvdofuzla","resolved","True","c3",3,"True","True",11,"True","['Authenticate via the API for login steps.', 'Authenticating via the API to satisfy test preconditions should be more reliable and faster than driving the browser.', 'It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353}).']",TRUE,1,"It also has the added benefit of not exposing credentials in the Selenium logs (see {T89353})." +21662,"Authenticate via the API for login steps","Change 226950 merged by jenkins-bot: +Login helper for fast API-based authentication + +[[https://gerrit.wikimedia.org/r/226950]]",1442841122,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-szootqtj2wa72tc5big3","task_subcomment","Change 226950 merged by jenkins-bot: +Login helper for fast API-based authentication + +[[https://gerrit.wikimedia.org/r/226950]]","Change 226950 merged by jenkins-bot: +Login helper for fast API-based authentication + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,11,"True","['Change 226950 merged by jenkins-bot:\nLogin helper for fast API-based authentication\n\n[[GERRIT_URL]]']",NA,1,"Change 226950 merged by jenkins-bot:\nLogin helper for fast API-based authentication\n\n[[GERRIT_URL]]" +21663,"Authenticate via the API for login steps","Change 226950 had a related patch set uploaded (by Dduvall): +Login helper for fast API-based authentication + +[[https://gerrit.wikimedia.org/r/226950]] +",1442506925,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-szootqtj2wa72tc5big3","task_subcomment","Change 226950 had a related patch set uploaded (by Dduvall): +Login helper for fast API-based authentication + +[[https://gerrit.wikimedia.org/r/226950]] +","Change 226950 had a related patch set uploaded (by Dduvall): +Login helper for fast API-based authentication + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",3,"False",NA,11,"True","['Change 226950 had a related patch set uploaded (by Dduvall):\nLogin helper for fast API-based authentication\n\n[[GERRIT_URL]]']",NA,1,"Change 226950 had a related patch set uploaded (by Dduvall):\nLogin helper for fast API-based authentication\n\n[[GERRIT_URL]]" +21664,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!",1442455023,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-3d4umhveb7t4oejcuz5l","task_description","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +QUOTE +QUOTE + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","Medium",50,1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","declined","True","c3",3,"True","False",11,"True","['The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions .', ""Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page."", 'See the description of T110878:\n\nQUOTE\nQUOTE\n\nThis error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn\'t tell users where to report the error.', 'It doesn\'t even show the skin interface, which may make some users worry that they have ""broken the site""!']",FALSE,1,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ." +21664,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!",1442455023,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-3d4umhveb7t4oejcuz5l","task_description","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +QUOTE +QUOTE + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","Medium",50,1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","declined","True","c3",3,"True","False",11,"True","['The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions .', ""Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page."", 'See the description of T110878:\n\nQUOTE\nQUOTE\n\nThis error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn\'t tell users where to report the error.', 'It doesn\'t even show the skin interface, which may make some users worry that they have ""broken the site""!']",FALSE,1,"See the description of T110878:\n\nQUOTE\nQUOTE\n\nThis error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn\" +21664,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!",1442455023,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-3d4umhveb7t4oejcuz5l","task_description","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +QUOTE +QUOTE + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","Medium",50,1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","declined","True","c3",3,"True","False",11,"True","['The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions .', ""Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page."", 'See the description of T110878:\n\nQUOTE\nQUOTE\n\nThis error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn\'t tell users where to report the error.', 'It doesn\'t even show the skin interface, which may make some users worry that they have ""broken the site""!']",FALSE,1,"t even show the skin interface, which may make some users worry that they have ""broken the site""!" +21664,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!",1442455023,"PHID-USER-sx63fwaih5kjt7bz4u6z","PHID-TASK-3d4umhveb7t4oejcuz5l","task_description","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +> What is interesting is that on WMF sites, this doesn't show the usual ""Wikimedia Foundation error"" page, but instead shows a quasi-plain text response of a kind that I have never seen before: https://www.mediawiki.org/wiki/Special:WhatLinksHere/Media:Wiki.png The HTML source of the returned page is exactly the following: +> ```MediaWiki internal error.
+>
+>Exception caught inside exception handler.
+>
+>Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.
``` + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ./n/nCertain errors (unhandled exceptions, I guess) don't result in the usual WMF error page. See the description of T110878: + +QUOTE +QUOTE + +This error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn't tell users where to report the error. It doesn't even show the skin interface, which may make some users worry that they have ""broken the site""!","Medium",50,1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","declined","True","c3",3,"True","False",11,"True","['The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions .', ""Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page."", 'See the description of T110878:\n\nQUOTE\nQUOTE\n\nThis error is unhelpful to non-developers, because it uses highly technical jargon like ""exception caught inside exception handler"", and doesn\'t tell users where to report the error.', 'It doesn\'t even show the skin interface, which may make some users worry that they have ""broken the site""!']",FALSE,1,"Certain errors (unhandled exceptions, I guess) don't result in the usual WMF error page." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"A lot has changed in 2015." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"For the most part cases like these are covered, and they do always return HTTP 500 now." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"However, there remains a small edge case where if there are several layers of errors, it can still show in plain text." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"This is in cases where there are two or three layers of cascading errors within MediaWiki." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"The last layer there is a generic MediaWiki HTML output, which still looks like the above." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"for Segfaults), there is a pretty error page again." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"There is an easy alternative, which is to render a blank response that the traffic-layer (e.g." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"Varnish or Apache) would backfill with a generic nice error page." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"But this goes at the cost of being able to determine what went wrong (eg." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"an error message with details as to what happened and how it might be solved)." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem." +21665,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",1569620011,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved). + +Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).', ""Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding.""]",NA,1,"Given this class of errors is among the most rare and yet the worst/most difficult to investigate, I think we'd prefer some details about what happened over no details but branding." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"A lot has changed in 2015." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"For the most part cases like these are covered, and they do always return HTTP 500 now." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"However, there remains a small edge case where if there are several layers of errors, it can still show in plain text." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"This is in cases where there are two or three layers of cascading errors within MediaWiki." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"The last layer there is a generic MediaWiki HTML output, which still looks like the above." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"for Segfaults), there is a pretty error page again." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"There is an easy alternative, which is to render a blank response that the traffic-layer (e.g." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"Varnish or Apache) would backfill with a generic nice error page." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"But this goes at the cost of being able to determine what went wrong (eg." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"an error message with details as to what happened and how it might be solved)." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g." +21666,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",1569619966,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).","A lot has changed in 2015. For the most part cases like these are covered, and they do always return HTTP 500 now. + +However, there remains a small edge case where if there are several layers of errors, it can still show in plain text. This is in cases where there are two or three layers of cascading errors within MediaWiki. The last layer there is a generic MediaWiki HTML output, which still looks like the above. This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point. + +As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g. for Segfaults), there is a pretty error page again. Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem. There is an easy alternative, which is to render a blank response that the traffic-layer (e.g. Varnish or Apache) would backfill with a generic nice error page. But this goes at the cost of being able to determine what went wrong (eg. an error message with details as to what happened and how it might be solved).",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,221,"True","['A lot has changed in 2015.', 'For the most part cases like these are covered, and they do always return HTTP 500 now.', 'However, there remains a small edge case where if there are several layers of errors, it can still show in plain text.', 'This is in cases where there are two or three layers of cascading errors within MediaWiki.', 'The last layer there is a generic MediaWiki HTML output, which still looks like the above.', 'This layer cannot read Wikipedia or WMF branding as the ability to do that is among the things that has failed at that point.', ""As of PHP7 we have the php-wmerrors extension deployed again which means if this layer isn't reached either, the next level above that (e.g."", 'for Segfaults), there is a pretty error page again.', ""Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem."", 'There is an easy alternative, which is to render a blank response that the traffic-layer (e.g.', 'Varnish or Apache) would backfill with a generic nice error page.', 'But this goes at the cost of being able to determine what went wrong (eg.', 'an error message with details as to what happened and how it might be solved).']",NA,1,"Closing as declined for now as I don't think is feasible to enhance this, rather the class of errors is sufficiently small that I don't think it's worth the cost and overhead of trying to enhance this with an additional subsystem." +21667,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","Er, we should depending on the stack trace :\",1445962659,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","Er, we should depending on the stack trace :\","Er, we should depending on the stack trace :\",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['Er, we should depending on the stack trace :\\']",NA,1,"Er, we should depending on the stack trace :\\" +21668,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.",1445962564,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['This should be pretty easy to do.', ""We don't actually return a 500 in this scenario afaict...we should.""]",NA,1,"This should be pretty easy to do." +21668,"The usual WMF HTTP 500 error page is not displayed in the case of unhandled exceptions ","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.",1445962564,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-3d4umhveb7t4oejcuz5l","task_subcomment","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.","This should be pretty easy to do. We don't actually return a 500 in this scenario afaict...we should.",NA,NA,NA,NA,NA,"True","c3",3,"True",NA,16,"True","['This should be pretty easy to do.', ""We don't actually return a 500 in this scenario afaict...we should.""]",NA,1,"We don't actually return a 500 in this scenario afaict...we should." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"Add support for login and create account by hovering over login button." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"That skin looks really nice." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"It should be the default on Wikimedia." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"But I would like to allow users to hover over the login button and login." +22276,"Add support for login and create account by hovering over login button","Hi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.",1437662784,"PHID-USER-bxp7xrbobtrp5o3q3swv","PHID-TASK-mbs7qdokcz7xn5upzj24","task_description","Add support for login and create account by hovering over login button./n/nHi @Ashley could you add support for loging by hovering over the login button like you can http://social-tools.wmflabs.org/wiki/Main_Page?useskin=bluesky here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Add support for login and create account by hovering over login button./n/nHiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here. That skin looks really nice. It should be the default on Wikimedia. But I would like to allow users to hover over the login button and login. Same goes for create account there should be a button that loads up the create form without having to leave page.","Medium",50,NA,NA,"open","True","c3",3,"True","False",3,"True","['Add support for login and create account by hovering over login button.', 'HiSCREEN_NAME could you add support for loging by hovering over the login button like you can URL here.', 'That skin looks really nice.', 'It should be the default on Wikimedia.', 'But I would like to allow users to hover over the login button and login.', 'Same goes for create account there should be a button that loads up the create form without having to leave page.']",FALSE,0,"Same goes for create account there should be a button that loads up the create form without having to leave page." +22553,"https switch changed wdata prefix to https:","After the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.",1434492549,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_description","https switch changed wdata prefix to https:./n/nAfter the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","https switch changed wdata prefix to https:./n/nAfter the https switch, the page URL redirects to URL - which produces this prefix: + +``CODE`` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","Medium",50,1435213716,"PHID-USER-4qe5niesec534hksvuch","resolved","True","c3",2,"True","True",-3,"True","['https switch changed wdata prefix to https:.', ""After the https switch, the page URL redirects to URL - which produces this prefix:\n\n``CODE``\n\nWhich doesn't seem right since our URLs are defined as http:// canonically."", 'Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https.', 'Data should not depend on the transfer protocol IMO.']",TRUE,1,"https switch changed wdata prefix to https:." +22553,"https switch changed wdata prefix to https:","After the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.",1434492549,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_description","https switch changed wdata prefix to https:./n/nAfter the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","https switch changed wdata prefix to https:./n/nAfter the https switch, the page URL redirects to URL - which produces this prefix: + +``CODE`` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","Medium",50,1435213716,"PHID-USER-4qe5niesec534hksvuch","resolved","True","c3",2,"True","True",-3,"True","['https switch changed wdata prefix to https:.', ""After the https switch, the page URL redirects to URL - which produces this prefix:\n\n``CODE``\n\nWhich doesn't seem right since our URLs are defined as http:// canonically."", 'Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https.', 'Data should not depend on the transfer protocol IMO.']",TRUE,1,"Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https." +22553,"https switch changed wdata prefix to https:","After the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.",1434492549,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_description","https switch changed wdata prefix to https:./n/nAfter the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","https switch changed wdata prefix to https:./n/nAfter the https switch, the page URL redirects to URL - which produces this prefix: + +``CODE`` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","Medium",50,1435213716,"PHID-USER-4qe5niesec534hksvuch","resolved","True","c3",2,"True","True",-3,"True","['https switch changed wdata prefix to https:.', ""After the https switch, the page URL redirects to URL - which produces this prefix:\n\n``CODE``\n\nWhich doesn't seem right since our URLs are defined as http:// canonically."", 'Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https.', 'Data should not depend on the transfer protocol IMO.']",TRUE,1,"Data should not depend on the transfer protocol IMO." +22553,"https switch changed wdata prefix to https:","After the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.",1434492549,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_description","https switch changed wdata prefix to https:./n/nAfter the https switch, the page http://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump redirects to https://www.wikidata.org/wiki/Special:EntityData/Q1.ttl?flavor=dump - which produces this prefix: + +``` +@prefix wdata: . +``` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","https switch changed wdata prefix to https:./n/nAfter the https switch, the page URL redirects to URL - which produces this prefix: + +``CODE`` + +Which doesn't seem right since our URLs are defined as http:// canonically. Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https. Data should not depend on the transfer protocol IMO.","Medium",50,1435213716,"PHID-USER-4qe5niesec534hksvuch","resolved","True","c3",2,"True","True",-3,"True","['https switch changed wdata prefix to https:.', ""After the https switch, the page URL redirects to URL - which produces this prefix:\n\n``CODE``\n\nWhich doesn't seem right since our URLs are defined as http:// canonically."", 'Should we change the definition or (my preference) fix the output so it displays http:// even if current page is https.', 'Data should not depend on the transfer protocol IMO.']",TRUE,1,"After the https switch, the page URL redirects to URL - which produces this prefix:\n\n``CODE``\n\nWhich doesn't seem right since our URLs are defined as http:// canonically." +22554,"https switch changed wdata prefix to https:","Change 220832 merged by jenkins-bot: +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[https://gerrit.wikimedia.org/r/220832]]",1435254547,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Change 220832 merged by jenkins-bot: +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[https://gerrit.wikimedia.org/r/220832]]","Change 220832 merged by jenkins-bot: +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['Change 220832 merged by jenkins-bot:\nT103767: Revert ""T102717: Fix the RDF links always use http:""\n\n[[GERRIT_URL]]']",NA,1,"Change 220832 merged by jenkins-bot:\nT103767: Revert ""T102717: Fix the RDF links always use http:""\n\n[[GERRIT_URL]]" +22555,"https switch changed wdata prefix to https:","Change 220832 had a related patch set uploaded (by Smalyshev): +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[https://gerrit.wikimedia.org/r/220832]] +",1435254272,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Change 220832 had a related patch set uploaded (by Smalyshev): +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[https://gerrit.wikimedia.org/r/220832]] +","Change 220832 had a related patch set uploaded (by Smalyshev): +T103767: Revert ""T102717: Fix the RDF links always use http:"" + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['Change 220832 had a related patch set uploaded (by Smalyshev):\nT103767: Revert ""T102717: Fix the RDF links always use http:""\n\n[[GERRIT_URL]]']",NA,1,"Change 220832 had a related patch set uploaded (by Smalyshev):\nT103767: Revert ""T102717: Fix the RDF links always use http:""\n\n[[GERRIT_URL]]" +22556,"https switch changed wdata prefix to https:","Change 218994 merged by jenkins-bot: +T102717: Fix the RDF links always use http: + +[[https://gerrit.wikimedia.org/r/218994]]",1435213607,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Change 218994 merged by jenkins-bot: +T102717: Fix the RDF links always use http: + +[[https://gerrit.wikimedia.org/r/218994]]","Change 218994 merged by jenkins-bot: +T102717: Fix the RDF links always use http: + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-1,"True","['Change 218994 merged by jenkins-bot:\nT102717: Fix the RDF links always use http:\n\n[[GERRIT_URL]]']",NA,1,"Change 218994 merged by jenkins-bot:\nT102717: Fix the RDF links always use http:\n\n[[GERRIT_URL]]" +22557,"https switch changed wdata prefix to https:","Basing on @dnaiel's comments on the ticket, I think we can commit this one as short-term fix and then develop longer-term consensus in T103767 (if it's different from the short-term one).",1435190792,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Basing on @dnaiel's comments on the ticket, I think we can commit this one as short-term fix and then develop longer-term consensus in T103767 (if it's different from the short-term one).","Basing onSCREEN_NAME's comments on the ticket, I think we can commit this one as short-term fix and then develop longer-term consensus in T103767 (if it's different from the short-term one).",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-1,"True","[""Basing onSCREEN_NAME's comments on the ticket, I think we can commit this one as short-term fix and then develop longer-term consensus in T103767 (if it's different from the short-term one).""]",NA,1,"Basing onSCREEN_NAME's comments on the ticket, I think we can commit this one as short-term fix and then develop longer-term consensus in T103767 (if it's different from the short-term one)." +22558,"https switch changed wdata prefix to https:","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",1435089387,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['I agree that we need to pick one.', ""But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource."", ""If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?)"", 'anyways.']",NA,1,"I agree that we need to pick one." +22558,"https switch changed wdata prefix to https:","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",1435089387,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['I agree that we need to pick one.', ""But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource."", ""If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?)"", 'anyways.']",NA,1,"anyways." +22558,"https switch changed wdata prefix to https:","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",1435089387,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['I agree that we need to pick one.', ""But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource."", ""If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?)"", 'anyways.']",NA,1,"But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource." +22558,"https switch changed wdata prefix to https:","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",1435089387,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ","I agree that we need to pick one. But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource. If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?) anyways. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['I agree that we need to pick one.', ""But the URI in the data and the URL ultimately used to deliver the data doesn't have to be the same, I think - it only need to lead ultimately to the same resource."", ""If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?)"", 'anyways.']",NA,1,"If we choose https, then we'll need to ensure there URL is always https even if the page is somehow accessed with http (I know right now there's a redirect but what if that redirect is or will be disabled for some clients/IPs/countries/etc.?)" +22559,"https switch changed wdata prefix to https:","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",1435084937,"PHID-USER-objbp2gsw5aadxihyhsh","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-2,"True","['While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems.', 'It is not so extensively tested maybe, but in most contexts it should work fine.', 'A bigger issue is that some people are already using our http URIs.']",NA,1,"While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems." +22559,"https switch changed wdata prefix to https:","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",1435084937,"PHID-USER-objbp2gsw5aadxihyhsh","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-2,"True","['While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems.', 'It is not so extensively tested maybe, but in most contexts it should work fine.', 'A bigger issue is that some people are already using our http URIs.']",NA,1,"It is not so extensively tested maybe, but in most contexts it should work fine." +22559,"https switch changed wdata prefix to https:","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",1435084937,"PHID-USER-objbp2gsw5aadxihyhsh","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.","While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems. It is not so extensively tested maybe, but in most contexts it should work fine. + +A bigger issue is that some people are already using our http URIs.",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-2,"True","['While I did say that pretty much all URIs I know use http, I do not have any reason to believe that https would cause problems.', 'It is not so extensively tested maybe, but in most contexts it should work fine.', 'A bigger issue is that some people are already using our http URIs.']",NA,1,"A bigger issue is that some people are already using our http URIs." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"It is important to pick one and stick to it." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"WMF hosted things changed to https being the default for good reason, which was in preparation for years." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"We should pick https for things we host." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"QUOTE\n\nThis actually does not talk about not using https at all." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"The example has explanations for all parts, except the missing s, probably it is only important that it is either one." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"Throughout the document they act like http and https are the same thing." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"QUOTE\n\nThis explicitly says you should pick one and always return that." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"Note that this one is after the one above in the same document, i.e." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"they technically suggest https without making it so explicity." +22560,"https switch changed wdata prefix to https:","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",1435080195,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +> This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the Study on persistent URIs by the ISA. + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls + +This states that it is about being able to dereference, not that it should be http over https. + +> https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.","It is important to pick one and stick to it. WMF hosted things changed to https being the default for good reason, which was in preparation for years. We should pick https for things we host. + +QUOTE + +This actually does not talk about not using https at all. The example has explanations for all parts, except the missing s, probably it is only important that it is either one. Throughout the document they act like http and https are the same thing. + +QUOTE + +This states that it is about being able to dereference, not that it should be http over https. + +QUOTE + +This explicitly says you should pick one and always return that. It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical. Note that this one is after the one above in the same document, i.e. they technically suggest https without making it so explicity. Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['It is important to pick one and stick to it.', 'WMF hosted things changed to https being the default for good reason, which was in preparation for years.', 'We should pick https for things we host.', 'QUOTE\n\nThis actually does not talk about not using https at all.', 'The example has explanations for all parts, except the missing s, probably it is only important that it is either one.', 'Throughout the document they act like http and https are the same thing.', 'QUOTE\n\nThis states that it is about being able to dereference, not that it should be http over https.', 'QUOTE\n\nThis explicitly says you should pick one and always return that.', 'It also mentions that http without s is not sufficient to trust that a certain response may define what is canonical.', 'Note that this one is after the one above in the same document, i.e.', 'they technically suggest https without making it so explicity.', 'Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188.']",NA,1,"Possibly that was done as to not divide the Working Group over things that were already decided and enshrined as BCP 188." +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"So, I think we have a consensus that we want to use CODE." +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always." +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\" +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"t find existing one and I don\" +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,", ""Or maybe there" +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"Thoughts welcome on this." +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"So let's now figure out what is the best way to do it." +22561,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",1435079871,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. +Or maybe there's another way of getting canonical URL with http which I am missing. + +Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', ""Or maybe there's another way of getting canonical URL with http which I am missing."", 'Thoughts welcome on this.']",NA,1,"canonicalize URL to be http" +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"So, I think we have a consensus that we want to use CODE." +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always." +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\" +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"t find existing one and I don\" +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"So let's now figure out what is the best way to do it." +22562,"https switch changed wdata prefix to https:","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",1435079802,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","So, I think we have a consensus that we want to use `http:`. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs `http:` always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.","So, I think we have a consensus that we want to use CODE. So let's now figure out what is the best way to do it. I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always. But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don't feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn't find existing one and I don't want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor. Thoughts welcome on this.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['So, I think we have a consensus that we want to use CODE.', ""So let's now figure out what is the best way to do it."", 'I made it in RdfVocabulary kind of brute-force - just make the URLs CODE always.', 'But it may be too harsh - maybe we could have the clients use RdfVocabulary::alwaysHTTP (I don\'t feel 100% happy with such a basic function like ""canonicalize URL to be http"" reside in very specialized class but I couldn\'t find existing one and I don\'t want to introduce cross-module dependencies) voluntarily instead of RdfVocabulary forcing http in the ctor.', 'Thoughts welcome on this.']",NA,1,"canonicalize URL to be http" +22563,"https switch changed wdata prefix to https:","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.",1435079262,"PHID-USER-7n5fvppwj4ueprv2iuys","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Markus: I seem to remember you saying pretty much everyone does http and not https?', 'If this is indeed the case then I think we should follow conventions and do the same.']",NA,1,"Markus: I seem to remember you saying pretty much everyone does http and not https?" +22563,"https switch changed wdata prefix to https:","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.",1435079262,"PHID-USER-7n5fvppwj4ueprv2iuys","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.","Markus: I seem to remember you saying pretty much everyone does http and not https? If this is indeed the case then I think we should follow conventions and do the same.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Markus: I seem to remember you saying pretty much everyone does http and not https?', 'If this is indeed the case then I think we should follow conventions and do the same.']",NA,1,"If this is indeed the case then I think we should follow conventions and do the same." +22564,"https switch changed wdata prefix to https:","Random but interesting Google results I found: +* http://www.ebi.ac.uk/rdf/does-rdf-platform-support-https +* https://pubchem.ncbi.nlm.nih.gov/rdf/#_Toc376426185 (search for ""https"") + +Possibly relevant but currently unlinked tickets: +* {T97195}",1435068079,"PHID-USER-u6ycqhfpa3k4yvlpxjt2","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Random but interesting Google results I found: +* http://www.ebi.ac.uk/rdf/does-rdf-platform-support-https +* https://pubchem.ncbi.nlm.nih.gov/rdf/#_Toc376426185 (search for ""https"") + +Possibly relevant but currently unlinked tickets: +* {T97195}","Random but interesting Google results I found: +* URL +* URL (search for ""https"") + +Possibly relevant but currently unlinked tickets: +* {T97195}",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-2,"True","['Random but interesting Google results I found:\n* URL\n* URL (search for ""https"")\n\nPossibly relevant but currently unlinked tickets:\n* {T97195}']",NA,1,"Random but interesting Google results I found:\n* URL\n* URL (search for ""https"")\n\nPossibly relevant but currently unlinked tickets:\n* {T97195}" +22565,"https switch changed wdata prefix to https:","@Lydia_Pintscher have a look above. What do you think? ",1434998834,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@Lydia_Pintscher have a look above. What do you think? ","SCREEN_NAME have a look above. What do you think? ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME have a look above.', 'What do you think?']",NA,1,"SCREEN_NAME have a look above." +22565,"https switch changed wdata prefix to https:","@Lydia_Pintscher have a look above. What do you think? ",1434998834,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@Lydia_Pintscher have a look above. What do you think? ","SCREEN_NAME have a look above. What do you think? ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME have a look above.', 'What do you think?']",NA,1,"What do you think?" +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Sorry for the initial misunderstanding." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"I was thinking of concept URIs, which are controlled by the conceptBaseUri setting." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Both rely on the canonical URL of Special:EntityData." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"While this is not cirticial for the application at hand, it should be avoided in general." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"In particular, how should URLs for rel=""alternate"" be constructed?" +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"See T96298 and URL for that." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA." +22566,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.",1435002542,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. + +@Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that.","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP. The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation. While this is not cirticial for the application at hand, it should be avoided in general. +SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documens URLs should use the https protocoll, and the plain http URLs should redirect to the https URLs, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', 'Considering the protocol conundrum above, we probably need to change this, and make the canonical document URIs use plain HTTP.', 'The downside of this is security: when resolving the document URI (or the concept URI, for that matter), which should be supported in the spirit of Open Data, then the initial request will be unencrypted, and subject to manipulation.', 'While this is not cirticial for the application at hand, it should be avoided in general.', ""SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"SCREEN_NAME's [[URL patch]] will change the document URIs to use plain http for RDF output - do we need a more generic solution?" +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Sorry for the initial misunderstanding." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"I was thinking of concept URIs, which are controlled by the conceptBaseUri setting." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Both rely on the canonical URL of Special:EntityData." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"In particular, how should URLs for rel=""alternate"" be constructed?" +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"See T96298 and URL for that." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA." +22567,"https switch changed wdata prefix to https:","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +",1434998753,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking to @Smalyshev, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#respond-with-primary-urls-and-use-them-for-identity-comparison|section 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html#predicate-uris-should-be-http-urls section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[https://joinup.ec.europa.eu/sites/default/files/c0/7d/10/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf|Study on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see https://gerrit.wikimedia.org/r/#/c/219782/2 + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this. @Smalyshev's [[https://gerrit.wikimedia.org/r/#/c/218994/|original patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and https://gerrit.wikimedia.org/r/#/c/219001/ for that. +","Sorry for the initial misunderstanding. I was thinking of concept URIs, which are controlled by the conceptBaseUri setting. + +So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL. + +The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]. + +However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]]. This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA. + +We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php. Both rely on the canonical URL of Special:EntityData. Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL + +So, currently, our canonical URIs are based on canonical URLs. Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution? In particular, how should URLs for rel=""alternate"" be constructed? See T96298 and URL for that. +",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['Sorry for the initial misunderstanding.', 'I was thinking of concept URIs, which are controlled by the conceptBaseUri setting.', ""So, after some digging around and talking toSCREEN_NAME, I think he's right: the canonical document URI should use the http schema, even though the canonical document URL should be a https URL."", ""The reason is: we want documents to be retrieved via HTTPS if possible, so our canonical documenr URLs should be https URLs, and the plain http urls should redirect to the https url, as per [[URL 2.11 of W3C's Linked Data recommendation]]."", 'However, be the same recommendations, URIs should always use the HTTP schema, see [[URL section 2.1]].', ""This seems a bit arbitrary and annoying, but it's backed by other documents, such as section 4.1 of the [[URL on persistent URIs]] by the ISA."", 'We currently construct the base URI for documents in two places, SpecialEntityData.php and dumpRdf.php.', 'Both rely on the canonical URL of Special:EntityData.', 'Note that the notion of canonical page URLs in core has recently been discussed, and the implementation improved, see URL\n\nSo, currently, our canonical URIs are based on canonical URLs.', ""Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?"", 'In particular, how should URLs for rel=""alternate"" be constructed?', 'See T96298 and URL for that.']",NA,1,"Considering the protocol conundrum above, we probably need to change this.SCREEN_NAME's [[URL patch]] will fix this for RDF output - do we need a more generic solution?" +22568,"https switch changed wdata prefix to https:","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",1434651657,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?","SCREEN_NAME - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME - check out the link, conceptBaseUri is fine.', 'However, data URL, which is derived from canonical URL, is not.', ""I'm also not sure which inconsistencies the patch will lead to, could you explain?""]",NA,1,"SCREEN_NAME - check out the link, conceptBaseUri is fine." +22568,"https switch changed wdata prefix to https:","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",1434651657,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?","SCREEN_NAME - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME - check out the link, conceptBaseUri is fine.', 'However, data URL, which is derived from canonical URL, is not.', ""I'm also not sure which inconsistencies the patch will lead to, could you explain?""]",NA,1,"However, data URL, which is derived from canonical URL, is not." +22568,"https switch changed wdata prefix to https:","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",1434651657,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?","SCREEN_NAME - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. I'm also not sure which inconsistencies the patch will lead to, could you explain?",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME - check out the link, conceptBaseUri is fine.', 'However, data URL, which is derived from canonical URL, is not.', ""I'm also not sure which inconsistencies the patch will lead to, could you explain?""]",NA,1,"I'm also not sure which inconsistencies the patch will lead to, could you explain?" +22569,"https switch changed wdata prefix to https:","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ",1434651409,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ","SCREEN_NAME - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME - check out the link, conceptBaseUri is fine.', 'However, data URL, which is derived from canonical URL, is not.']",NA,1,"SCREEN_NAME - check out the link, conceptBaseUri is fine." +22569,"https switch changed wdata prefix to https:","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ",1434651409,"PHID-USER-4qe5niesec534hksvuch","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","@daniel - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ","SCREEN_NAME - check out the link, conceptBaseUri is fine. However, data URL, which is derived from canonical URL, is not. ",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","['SCREEN_NAME - check out the link, conceptBaseUri is fine.', 'However, data URL, which is derived from canonical URL, is not.']",NA,1,"However, data URL, which is derived from canonical URL, is not." +22570,"https switch changed wdata prefix to https:","Instead of the proposed patch, which would lead to inconsistencies, just set the concept base URI explicitly in the config: + + $wgWBRepoSetting['conceptBaseUri'] = 'http://www.wikidata.org/entity/'; + +That would go into the wikibase.php config file, if I understand correctly.",1434633544,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Instead of the proposed patch, which would lead to inconsistencies, just set the concept base URI explicitly in the config: + + $wgWBRepoSetting['conceptBaseUri'] = 'http://www.wikidata.org/entity/'; + +That would go into the wikibase.php config file, if I understand correctly.","Instead of the proposed patch, which would lead to inconsistencies, just set the concept base URI explicitly in the config: + + $wgWBRepoSetting['conceptBaseUri'] = 'URL + +That would go into the wikibase.php config file, if I understand correctly.",NA,NA,NA,NA,NA,"True","c3",2,"True",NA,-2,"True","[""Instead of the proposed patch, which would lead to inconsistencies, just set the concept base URI explicitly in the config:\n\n $wgWBRepoSetting['conceptBaseUri'] = 'URL\n\nThat would go into the wikibase.php config file, if I understand correctly.""]",NA,1,"Instead of the proposed patch, which would lead to inconsistencies, just set the concept base URI explicitly in the config:\n\n $wgWBRepoSetting['conceptBaseUri'] = 'URL\n\nThat would go into the wikibase.php config file, if I understand correctly." +22571,"https switch changed wdata prefix to https:","Change 218994 had a related patch set uploaded (by Smalyshev): +T102717: Fix the RDF links always use http: + +[[https://gerrit.wikimedia.org/r/218994]] +",1434568583,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-vaaztnerkhieqw4eb6ua","task_subcomment","Change 218994 had a related patch set uploaded (by Smalyshev): +T102717: Fix the RDF links always use http: + +[[https://gerrit.wikimedia.org/r/218994]] +","Change 218994 had a related patch set uploaded (by Smalyshev): +T102717: Fix the RDF links always use http: + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",2,"False",NA,-3,"True","['Change 218994 had a related patch set uploaded (by Smalyshev):\nT102717: Fix the RDF links always use http:\n\n[[GERRIT_URL]]']",NA,1,"Change 218994 had a related patch set uploaded (by Smalyshev):\nT102717: Fix the RDF links always use http:\n\n[[GERRIT_URL]]" +23182,"MediaWiki.org shows wrong login icon","It shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).",1432803933,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-alq542s32wmmdpy7x4v7","task_description","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (URL maybe without the text).","Low",25,1433374570,"PHID-USER-5dwuaigmkz2vzg65lape","resolved","True","c3",1,"True","False",-5,"True","['MediaWiki.org shows wrong login icon.', 'It shows the Wikimedia Foundation logo on the MediaWiki.org login screen.', 'It should show the MediaWiki.org logo (URL maybe without the text).']",TRUE,0,"MediaWiki.org shows wrong login icon." +23182,"MediaWiki.org shows wrong login icon","It shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).",1432803933,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-alq542s32wmmdpy7x4v7","task_description","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (URL maybe without the text).","Low",25,1433374570,"PHID-USER-5dwuaigmkz2vzg65lape","resolved","True","c3",1,"True","False",-5,"True","['MediaWiki.org shows wrong login icon.', 'It shows the Wikimedia Foundation logo on the MediaWiki.org login screen.', 'It should show the MediaWiki.org logo (URL maybe without the text).']",TRUE,0,"It shows the Wikimedia Foundation logo on the MediaWiki.org login screen." +23182,"MediaWiki.org shows wrong login icon","It shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).",1432803933,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-alq542s32wmmdpy7x4v7","task_description","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (https://www.mediawiki.org/static/images/project-logos/mediawikiwiki.png, maybe without the text).","MediaWiki.org shows wrong login icon./n/nIt shows the Wikimedia Foundation logo on the MediaWiki.org login screen. It should show the MediaWiki.org logo (URL maybe without the text).","Low",25,1433374570,"PHID-USER-5dwuaigmkz2vzg65lape","resolved","True","c3",1,"True","False",-5,"True","['MediaWiki.org shows wrong login icon.', 'It shows the Wikimedia Foundation logo on the MediaWiki.org login screen.', 'It should show the MediaWiki.org logo (URL maybe without the text).']",TRUE,0,"It should show the MediaWiki.org logo (URL maybe without the text)." +23183,"MediaWiki.org shows wrong login icon","done!",1433374570,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","done!","done!",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-5,"True","['done!']",NA,0,"done!" +23184,"MediaWiki.org shows wrong login icon","Change 215361 merged by jenkins-bot: +Enable MediaWiki logo on mobile login page + +[[https://gerrit.wikimedia.org/r/215361]]",1433373684,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","Change 215361 merged by jenkins-bot: +Enable MediaWiki logo on mobile login page + +[[https://gerrit.wikimedia.org/r/215361]]","Change 215361 merged by jenkins-bot: +Enable MediaWiki logo on mobile login page + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-5,"True","['Change 215361 merged by jenkins-bot:\nEnable MediaWiki logo on mobile login page\n\n[[GERRIT_URL]]']",NA,0,"Change 215361 merged by jenkins-bot:\nEnable MediaWiki logo on mobile login page\n\n[[GERRIT_URL]]" +23185,"MediaWiki.org shows wrong login icon","Requested deploy https://wikitech.wikimedia.org/wiki/Deployments#Wednesday.2C.C2.A0June.C2.A003",1433361367,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","Requested deploy https://wikitech.wikimedia.org/wiki/Deployments#Wednesday.2C.C2.A0June.C2.A003","Requested deploy URL",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-5,"True","['Requested deploy URL']",NA,0,"Requested deploy URL" +23186,"MediaWiki.org shows wrong login icon","Change 215361 had a related patch set uploaded (by Jdlrobson): +Enable MediaWiki logo on mobile login page + +[[https://gerrit.wikimedia.org/r/215361]] +",1433265284,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","Change 215361 had a related patch set uploaded (by Jdlrobson): +Enable MediaWiki logo on mobile login page + +[[https://gerrit.wikimedia.org/r/215361]] +","Change 215361 had a related patch set uploaded (by Jdlrobson): +Enable MediaWiki logo on mobile login page + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-5,"True","['Change 215361 had a related patch set uploaded (by Jdlrobson):\nEnable MediaWiki logo on mobile login page\n\n[[GERRIT_URL]]']",NA,0,"Change 215361 had a related patch set uploaded (by Jdlrobson):\nEnable MediaWiki logo on mobile login page\n\n[[GERRIT_URL]]" +23187,"MediaWiki.org shows wrong login icon","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.",1433265262,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-5,"True","[""It's a config variable which defaults to Wikimedia Foundation logo."", 'Easy config fix.']",NA,0,"Easy config fix." +23187,"MediaWiki.org shows wrong login icon","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.",1433265262,"PHID-USER-5dwuaigmkz2vzg65lape","PHID-TASK-alq542s32wmmdpy7x4v7","task_subcomment","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.","It's a config variable which defaults to Wikimedia Foundation logo. Easy config fix.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-5,"True","[""It's a config variable which defaults to Wikimedia Foundation logo."", 'Easy config fix.']",NA,0,"It's a config variable which defaults to Wikimedia Foundation logo." +23565,"Shorten update interval of lighttpd error logs","Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.",1422277333,"PHID-USER-zzbdvschb2zxhrxixhcr","PHID-TASK-fatfiflitno2tuzvuchf","task_description","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Needs Triage",90,1428307018,"PHID-USER-vk6mlmacfhx77egryy5i","resolved","True","c3",1,"False","False",-23,"True","['Shorten update interval of lighttpd error logs.', 'Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen.', 'This makes debugging web programming stuff or lighttpd configuration problems a pain.', 'Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.']",TRUE,0,"Shorten update interval of lighttpd error logs." +23565,"Shorten update interval of lighttpd error logs","Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.",1422277333,"PHID-USER-zzbdvschb2zxhrxixhcr","PHID-TASK-fatfiflitno2tuzvuchf","task_description","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Needs Triage",90,1428307018,"PHID-USER-vk6mlmacfhx77egryy5i","resolved","True","c3",1,"False","False",-23,"True","['Shorten update interval of lighttpd error logs.', 'Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen.', 'This makes debugging web programming stuff or lighttpd configuration problems a pain.', 'Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.']",TRUE,0,"Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen." +23565,"Shorten update interval of lighttpd error logs","Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.",1422277333,"PHID-USER-zzbdvschb2zxhrxixhcr","PHID-TASK-fatfiflitno2tuzvuchf","task_description","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Needs Triage",90,1428307018,"PHID-USER-vk6mlmacfhx77egryy5i","resolved","True","c3",1,"False","False",-23,"True","['Shorten update interval of lighttpd error logs.', 'Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen.', 'This makes debugging web programming stuff or lighttpd configuration problems a pain.', 'Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.']",TRUE,0,"This makes debugging web programming stuff or lighttpd configuration problems a pain." +23565,"Shorten update interval of lighttpd error logs","Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.",1422277333,"PHID-USER-zzbdvschb2zxhrxixhcr","PHID-TASK-fatfiflitno2tuzvuchf","task_description","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Shorten update interval of lighttpd error logs./n/nTool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen. This makes debugging web programming stuff or lighttpd configuration problems a pain. + +Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.","Needs Triage",90,1428307018,"PHID-USER-vk6mlmacfhx77egryy5i","resolved","True","c3",1,"False","False",-23,"True","['Shorten update interval of lighttpd error logs.', 'Tool error and access log files (~sometool/error.log, ~sometool/access.log) are currently updated apparently in fixed intervals, so information appears in the logs a few minutes after errors happen.', 'This makes debugging web programming stuff or lighttpd configuration problems a pain.', 'Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly.']",TRUE,0,"Either the update interval (or buffering limit, or whatever causes it) should be decreased, or there should be some way to access the tool error log directly." +23566,"Shorten update interval of lighttpd error logs","I assume this is resolved by fulfilling ""there should be some way to access the tool error log directly"".",1428307018,"PHID-USER-vk6mlmacfhx77egryy5i","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","I assume this is resolved by fulfilling ""there should be some way to access the tool error log directly"".","I assume this is resolved by fulfilling ""there should be some way to access the tool error log directly"".",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-13,"True","['I assume this is resolved by fulfilling ""there should be some way to access the tool error log directly"".']",NA,0,"I assume this is resolved by fulfilling ""there should be some way to access the tool error log directly""." +23567,"Shorten update interval of lighttpd error logs","valhallasw: works for me, thanks.",1422980610,"PHID-USER-zzbdvschb2zxhrxixhcr","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","valhallasw: works for me, thanks.","valhallasw: works for me, thanks.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-22,"True","['valhallasw: works for me, thanks.']",NA,0,"valhallasw: works for me, thanks." +23568,"Shorten update interval of lighttpd error logs","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +",1422279246,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE`` +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-23,"True","['This is probably because this is an NFS mount, which means updates can take a while.', 'If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there.', 'First, find the host using qstat:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``']",NA,0,"This is probably because this is an NFS mount, which means updates can take a while." +23568,"Shorten update interval of lighttpd error logs","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +",1422279246,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE`` +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-23,"True","['This is probably because this is an NFS mount, which means updates can take a while.', 'If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there.', 'First, find the host using qstat:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``']",NA,0,"If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there." +23568,"Shorten update interval of lighttpd error logs","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +",1422279246,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. + +Then you can ssh and tail: +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there. + +First, find the host using qstat: + +``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE`` +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-23,"True","['This is probably because this is an NFS mount, which means updates can take a while.', 'If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there.', 'First, find the host using qstat:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``']",NA,0,"First, find the host using qstat:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``" +23569,"Shorten update interval of lighttpd error logs","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. Then, +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +",1422278182,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. Then, +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE`` +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-23,"True","['This is probably because this is an NFS mount, which means updates can take a while.', 'If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``']",NA,0,"This is probably because this is an NFS mount, which means updates can take a while." +23569,"Shorten update interval of lighttpd error logs","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. Then, +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +",1422278182,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-fatfiflitno2tuzvuchf","task_subcomment","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``` +tools.gerrit-patch-uploader@tools-login:~$ qstat -xml + + + + + 7233076 + 0.32253 + lighttpd-gerrit-patch-uploader + tools.gerrit-patch-uploader + r + 2015-01-11T18:46:18 + webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs + 1 + + + + + +``` + +Where the `webgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs ` line tells you it's running on tools-webgrid-02. Then, +``` +$ ssh tools-webgrid-02 tail -f error.log +(...new log entries will appear here instantaneously...) +``` +","This is probably because this is an NFS mount, which means updates can take a while. If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there: + +``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE`` +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-23,"True","['This is probably because this is an NFS mount, which means updates can take a while.', 'If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``']",NA,0,"If you want quicker updates, you can ssh to the relevant -webgrid node, and tail the error log there:\n\n``CODE`CODEwebgrid-lighttpd@tools-webgrid-02.eqiad.wmflabs CODE`CODE``" +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500)." +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"Thus, writing it to ""the exception log"" with wfDebugLog( \" +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,", ... ) is misleading." +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500." +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e." +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"""http-error"" instead of the generic ""exception"" log." +23679,"HttpError should not be logged as an unhandled exception.","HttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.",1420465532,"PHID-USER-5dqihbanu3caaj7pigif","PHID-TASK-cgood7sc62oac3adwbux","task_description","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","HttpError should not be logged as an unhandled exception../n/nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500). Thus, writing it to ""the exception log"" with wfDebugLog( 'exception', ... ) is misleading. + +I suggest the following behavior: +* HttpError::isLoggable should return false if $this->httpCode < 500. +* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400 + +Alternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e. ""http-error"" instead of the generic ""exception"" log. To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.","Needs Triage",90,1426705982,"PHID-USER-2mey32xhshfnf7rz7jjn","resolved","True","c3",1,"True","False",-26,"True","['HttpError should not be logged as an unhandled exception.. \n\nHttpError is a way to signal an issue to the client, it does not generally imply a programming error or failure on the server side (at least for status codes < 500).', 'Thus, writing it to ""the exception log"" with wfDebugLog( \'exception\', ... ) is misleading.', 'I suggest the following behavior: \n* HttpError::isLoggable should return false if $this->httpCode < 500.', '* HttpError::report should write to the web server error log (via wfLogWarning or error_log) if $this->httpCode >= 400\n\nAlternatively, MWExceptionHandler::logException could implement a special case for HttpError, using a different log stream, i.e.', '""http-error"" instead of the generic ""exception"" log.', 'To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default.']",TRUE,0,"To avoid the special case in MWExceptionHandler, MWException could get a getLogStream() method that would return ""exception"" per default." +23680,"HttpError should not be logged as an unhandled exception.","Change 183020 merged by jenkins-bot: +Don't log HttpErrors in the exception log, use MWLogger + +[[https://gerrit.wikimedia.org/r/183020]]",1426694449,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","Change 183020 merged by jenkins-bot: +Don't log HttpErrors in the exception log, use MWLogger + +[[https://gerrit.wikimedia.org/r/183020]]","Change 183020 merged by jenkins-bot: +Don't log HttpErrors in the exception log, use MWLogger + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-16,"True","[""Change 183020 merged by jenkins-bot:\nDon't log HttpErrors in the exception log, use MWLogger\n\n[[GERRIT_URL]]""]",NA,0,"Change 183020 merged by jenkins-bot:\nDon't log HttpErrors in the exception log, use MWLogger\n\n[[GERRIT_URL]]" +23681,"HttpError should not be logged as an unhandled exception.","Change 197503 merged by Legoktm: +Log HttpErrors with a 500 code + +[[https://gerrit.wikimedia.org/r/197503]]",1426693431,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","Change 197503 merged by Legoktm: +Log HttpErrors with a 500 code + +[[https://gerrit.wikimedia.org/r/197503]]","Change 197503 merged by Legoktm: +Log HttpErrors with a 500 code + +[[GERRIT_URL]]",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-16,"True","['Change 197503 merged by Legoktm:\nLog HttpErrors with a 500 code\n\n[[GERRIT_URL]]']",NA,0,"Change 197503 merged by Legoktm:\nLog HttpErrors with a 500 code\n\n[[GERRIT_URL]]" +23682,"HttpError should not be logged as an unhandled exception.","Change 197503 had a related patch set uploaded (by Hoo man): +Log HttpErrors with a 500 code + +[[https://gerrit.wikimedia.org/r/197503]] +",1426674262,"PHID-USER-idceizaw6elwiwm5xshb","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","Change 197503 had a related patch set uploaded (by Hoo man): +Log HttpErrors with a 500 code + +[[https://gerrit.wikimedia.org/r/197503]] +","Change 197503 had a related patch set uploaded (by Hoo man): +Log HttpErrors with a 500 code + +[[GERRIT_URL]] +",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-16,"True","['Change 197503 had a related patch set uploaded (by Hoo man):\nLog HttpErrors with a 500 code\n\n[[GERRIT_URL]]']",NA,0,"Change 197503 had a related patch set uploaded (by Hoo man):\nLog HttpErrors with a 500 code\n\n[[GERRIT_URL]]" +23683,"HttpError should not be logged as an unhandled exception.",">>! In T85795#960163, @Legoktm wrote: +>>>! In T85795#960109, @JanZerebecki wrote: +>> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +> +> Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.",1420658816,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#960163, @Legoktm wrote: +>>>! In T85795#960109, @JanZerebecki wrote: +>> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +> +> Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe severity filter stuff will hit group0 today.', '\\o/ No config updates have been done to use it yet.']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe severity filter stuff will hit group0 today." +23683,"HttpError should not be logged as an unhandled exception.",">>! In T85795#960163, @Legoktm wrote: +>>>! In T85795#960109, @JanZerebecki wrote: +>> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +> +> Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.",1420658816,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#960163, @Legoktm wrote: +>>>! In T85795#960109, @JanZerebecki wrote: +>> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +> +> Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The severity filter stuff will hit group0 today. \o/ No config updates have been done to use it yet.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe severity filter stuff will hit group0 today.', '\\o/ No config updates have been done to use it yet.']",NA,0,"\\o/ No config updates have been done to use it yet." +23684,"HttpError should not be logged as an unhandled exception.",">>! In T85795#960109, @JanZerebecki wrote: +> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. + +Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +",1420654141,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#960109, @JanZerebecki wrote: +> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. + +Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +","QUOTE +QUOTE + +Actually, we now have structured logging in MW: CODE will return an instance of CODE that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['QUOTE\nQUOTE\n\nActually, we now have structured logging in MW: CODE will return an instance of CODE that you can use.', 'You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though).']",NA,0,"QUOTE\nQUOTE\n\nActually, we now have structured logging in MW: CODE will return an instance of CODE that you can use." +23684,"HttpError should not be logged as an unhandled exception.",">>! In T85795#960109, @JanZerebecki wrote: +> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. + +Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +",1420654141,"PHID-USER-v7vgzvvcw7v2umf737ri","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#960109, @JanZerebecki wrote: +> The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. + +Actually, we now have structured logging in MW: `MWLogger::getInstance('HttpError')` will return an instance of `Psr\Log\LoggerInterface` that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +","QUOTE +QUOTE + +Actually, we now have structured logging in MW: CODE will return an instance of CODE that you can use. You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though). +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['QUOTE\nQUOTE\n\nActually, we now have structured logging in MW: CODE will return an instance of CODE that you can use.', 'You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though).']",NA,0,"You can also set a minimum log severity level in $wgDebugLogGroups (unsure if that has been deployed yet though)." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"The goal is that everything that is logged can be easily differentiated according to its severity." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"A 404 of this case is the later case." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"AFAIK in Mediawiki the log group is the only thing that can be currently used for this." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group." +23685,"HttpError should not be logged as an unhandled exception.","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",1420653258,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?","The goal is that everything that is logged can be easily differentiated according to its severity. Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation. A 404 of this case is the later case. AFAIK in Mediawiki the log group is the only thing that can be currently used for this. +To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group. How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['The goal is that everything that is logged can be easily differentiated according to its severity.', 'Like fatals/errors/warnings/notices vs things that might be helpful for debugging something but are normal operation.', 'A 404 of this case is the later case.', 'AFAIK in Mediawiki the log group is the only thing that can be currently used for this.', 'To have isLoggable() return false but then have the exception log itself inside report() is more of a workaround for the lack of being able to specify the log group.', 'How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?']",NA,0,"How about having logGroups() in MWException which MWExceptionHandler then uses instead of isLoggable() to determine to log the exception to the normal exception channel?" +23686,"HttpError should not be logged as an unhandled exception.","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.",1420565761,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['Thx.', ""No wonder searching for type in that file didn't find where it was set to HttpError.""]",NA,0,"Thx." +23686,"HttpError should not be logged as an unhandled exception.","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.",1420565761,"PHID-USER-mdihg2tyzmlvyhn3h32y","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.","Thx. No wonder searching for type in that file didn't find where it was set to HttpError.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['Thx.', ""No wonder searching for type in that file didn't find where it was set to HttpError.""]",NA,0,"No wonder searching for type in that file didn't find where it was set to HttpError." +23687,"HttpError should not be logged as an unhandled exception.",">>! In T85795#957697, @JanZerebecki wrote: +> I can't figure out why currently these show up in logstash as type:HttpError instead of type:exception. Any ideas? + +It happens from the exception-json event processing. See ",1420565282,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#957697, @JanZerebecki wrote: +> I can't figure out why currently these show up in logstash as type:HttpError instead of type:exception. Any ideas? + +It happens from the exception-json event processing. See ","QUOTE +QUOTE + +It happens from the exception-json event processing. See >! In T85795#957697, @JanZerebecki wrote: +> I can't figure out why currently these show up in logstash as type:HttpError instead of type:exception. Any ideas? + +It happens from the exception-json event processing. See ",1420565282,"PHID-USER-ll6tmaogat2b5q7tnqas","PHID-TASK-cgood7sc62oac3adwbux","task_subcomment",">>! In T85795#957697, @JanZerebecki wrote: +> I can't figure out why currently these show up in logstash as type:HttpError instead of type:exception. Any ideas? + +It happens from the exception-json event processing. See ","QUOTE +QUOTE + +It happens from the exception-json event processing. See >> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.",1418191715,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_description","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``` +>>> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``CODE`` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","High",80,1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","resolved","True","c3",1,"True","True",-30,"True","['exceptions in threadedhttp.Http._follow_redirect cause a lock up.', '``CODE``\n\nAnd the main thread doesnt return.', 'This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.']",TRUE,0,"exceptions in threadedhttp.Http._follow_redirect cause a lock up." +24090,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","``` +>>> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.",1418191715,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_description","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``` +>>> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``CODE`` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","High",80,1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","resolved","True","c3",1,"True","True",-30,"True","['exceptions in threadedhttp.Http._follow_redirect cause a lock up.', '``CODE``\n\nAnd the main thread doesnt return.', 'This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.']",TRUE,0,"``CODE``\n\nAnd the main thread doesnt return." +24090,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","``` +>>> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.",1418191715,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_description","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``` +>>> http.fetch(uri='http://getstatuscode.com/301') +Exception in thread Thread-1: +Traceback (most recent call last): + File ""/usr/lib64/python2.7/threading.py"", line 811, in __bootstrap_inner + self.run() + File ""pywikibot/comms/threadedhttp.py"", line 486, in run + item.data = self.http.request(*item.args, **item.kwargs) + File ""pywikibot/comms/threadedhttp.py"", line 254, in request + uri, method, body, headers, response, content, max_redirects) + File ""pywikibot/comms/threadedhttp.py"", line 273, in _follow_redirect + response, content) +RedirectMissingLocation: Redirected but the response is missing a Location: header. +``` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","exceptions in threadedhttp.Http._follow_redirect cause a lock up./n/n``CODE`` + +And the main thread doesnt return. + +This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.","High",80,1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","resolved","True","c3",1,"True","True",-30,"True","['exceptions in threadedhttp.Http._follow_redirect cause a lock up.', '``CODE``\n\nAnd the main thread doesnt return.', 'This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread.']",TRUE,0,"This exception is thrown by threadedhttp, whereas threadedhttp normally returns the exception to be passed back to the main thread." +24091,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.",1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ). +So nothing left to do here.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-4,"True","['The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed.', 'However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ).', 'So nothing left to do here.']",NA,0,"The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed." +24091,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.",1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ). +So nothing left to do here.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-4,"True","['The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed.', 'However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ).', 'So nothing left to do here.']",NA,0,"However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL )." +24091,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.",1433512651,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (https://gerrit.wikimedia.org/r/#/c/215603/ ). +So nothing left to do here.","The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed. +However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ). +So nothing left to do here.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-4,"True","['The original bug was resolved in 35936a7abfdd9531073215994f5376d3ed2004df and another problem was fix in d398fdc56e2601659088a60aa199224cb247f9cd (with more general problem detection added), but the actual broader problem probably wasnt fixed.', 'However httplib2 has been replaced by requests, and boarder solutions are not needed for the 2.0 branch, and the possible re-introduction of httplib2 support would be a cut down implementation without follow support as it isnt needed according to my inquiries (see last comment on this bug) and the test suit confirms this with the minimal implementation on the table (URL ).', 'So nothing left to do here.']",NA,0,"So nothing left to do here." +24092,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",1418246578,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client.', ""I think that should not be changed, which is where 503's normally happen."", 'It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created.', 'I am also interested in why we need the special follow code.', 'Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.']",NA,0,"ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client." +24092,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",1418246578,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client.', ""I think that should not be changed, which is where 503's normally happen."", 'It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created.', 'I am also interested in why we need the special follow code.', 'Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.']",NA,0,"It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created." +24092,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",1418246578,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client.', ""I think that should not be changed, which is where 503's normally happen."", 'It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created.', 'I am also interested in why we need the special follow code.', 'Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.']",NA,0,"I am also interested in why we need the special follow code." +24092,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",1418246578,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client.', ""I think that should not be changed, which is where 503's normally happen."", 'It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created.', 'I am also interested in why we need the special follow code.', 'Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.']",NA,0,"Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days." +24092,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",1418246578,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.","ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client. I think that should not be changed, which is where 503's normally happen. It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created. + +I am also interested in why we need the special follow code. Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['ya, we have a try.. catch inside .request , and it returns the exception to be processed by the client.', ""I think that should not be changed, which is where 503's normally happen."", 'It would only be unexpected exceptions which would be handled by HttpProcessor.run and result in a new worker being created.', 'I am also interested in why we need the special follow code.', 'Im pretty sure it is being used because of %20 -> _ on MediaWiki sites, but that should only be needed for full urls to wiki pages, which is very rare occurrence in pywikibot core these days.']",NA,0,"I think that should not be changed, which is where 503's normally happen." +24093,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",1418245951,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['Yes, that sounds reasonable.', 'This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g.', '503s).']",NA,0,"Yes, that sounds reasonable." +24093,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",1418245951,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['Yes, that sounds reasonable.', 'This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g.', '503s).']",NA,0,"This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g." +24093,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",1418245951,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).","Yes, that sounds reasonable. This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g. 503s).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['Yes, that sounds reasonable.', 'This does have some implications for when we can and cannot re-use a connection, though -- we should prevent spinning up a new connection for typical issues (e.g.', '503s).']",NA,0,"503s)." +24094,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: https://gerrit.wikimedia.org/r/#/c/178789/ ), it would be sensible to replace the dead http worker with a new one.",1418245466,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: https://gerrit.wikimedia.org/r/#/c/178789/ ), it would be sensible to replace the dead http worker with a new one.","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: URL ), it would be sensible to replace the dead http worker with a new one.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch.', 'depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: URL ), it would be sensible to replace the dead http worker with a new one.']",NA,0,"I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch." +24094,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: https://gerrit.wikimedia.org/r/#/c/178789/ ), it would be sensible to replace the dead http worker with a new one.",1418245466,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: https://gerrit.wikimedia.org/r/#/c/178789/ ), it would be sensible to replace the dead http worker with a new one.","I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch. depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: URL ), it would be sensible to replace the dead http worker with a new one.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['I was thinking it should be in HttpProcessor.run , which has a try..finally , .. but not catch.', 'depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: URL ), it would be sensible to replace the dead http worker with a new one.']",NA,0,"depending on how bad the exception is (and it is best to assume the worst, like some state has been irreparably altered: URL ), it would be sensible to replace the dead http worker with a new one." +24095,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","I think that instead of the current + +``` + try: + (response, content) = httplib2.Http.request( + self, uri, method, body, headers, + max_redirects, connection_type + ) + except Exception as e: # what types? + # return exception instance to be retrieved by the calling thread + return e +``` + +wrapper, we should actually just wrap all of `def request` with a try-catch block which returns e on error. Does that sound like the right solution to you?",1418244166,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","I think that instead of the current + +``` + try: + (response, content) = httplib2.Http.request( + self, uri, method, body, headers, + max_redirects, connection_type + ) + except Exception as e: # what types? + # return exception instance to be retrieved by the calling thread + return e +``` + +wrapper, we should actually just wrap all of `def request` with a try-catch block which returns e on error. Does that sound like the right solution to you?","I think that instead of the current + +``CODE`CODEdef request` with a try-catch block which returns e on error. Does that sound like the right solution to you?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['I think that instead of the current\n\n``CODE`CODEdef request` with a try-catch block which returns e on error.', 'Does that sound like the right solution to you?']",NA,0,"I think that instead of the current\n\n``CODE`CODEdef request` with a try-catch block which returns e on error." +24095,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","I think that instead of the current + +``` + try: + (response, content) = httplib2.Http.request( + self, uri, method, body, headers, + max_redirects, connection_type + ) + except Exception as e: # what types? + # return exception instance to be retrieved by the calling thread + return e +``` + +wrapper, we should actually just wrap all of `def request` with a try-catch block which returns e on error. Does that sound like the right solution to you?",1418244166,"PHID-USER-muirnivxp5hzppn2a3z7","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","I think that instead of the current + +``` + try: + (response, content) = httplib2.Http.request( + self, uri, method, body, headers, + max_redirects, connection_type + ) + except Exception as e: # what types? + # return exception instance to be retrieved by the calling thread + return e +``` + +wrapper, we should actually just wrap all of `def request` with a try-catch block which returns e on error. Does that sound like the right solution to you?","I think that instead of the current + +``CODE`CODEdef request` with a try-catch block which returns e on error. Does that sound like the right solution to you?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","['I think that instead of the current\n\n``CODE`CODEdef request` with a try-catch block which returns e on error.', 'Does that sound like the right solution to you?']",NA,0,"Does that sound like the right solution to you?" +24096,"exceptions in threadedhttp.Http._follow_redirect cause a lock up","Presumably the same happens with 'raise httplib2.RedirectLimit' in the same method.",1418235345,"PHID-USER-oxd6f6xemkuyttw7z7wl","PHID-TASK-wia5aomivmjvpvurekei","task_subcomment","Presumably the same happens with 'raise httplib2.RedirectLimit' in the same method.","Presumably the same happens with 'raise httplib2.RedirectLimit' in the same method.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-30,"True","[""Presumably the same happens with 'raise httplib2.RedirectLimit' in the same method.""]",NA,0,"Presumably the same happens with 'raise httplib2.RedirectLimit' in the same method." +24099,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Chrome: +> The identity of this website has been verified by RapidSSL CA but it does not have public audit records. +> The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it. + +{F18152}",1417590103,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_description","Chrome warns about insecure certificate on gerrit.wikimedia.org./n/nChrome: +> The identity of this website has been verified by RapidSSL CA but it does not have public audit records. +> The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it. + +{F18152}","Chrome warns about insecure certificate on gerrit.wikimedia.org./n/nChrome: +QUOTE +QUOTE + +{F18152}","High",80,1422997247,"PHID-USER-xy6c3ul27f336aaedx2d","resolved","True","c3",1,"True","False",-31,"True","['Chrome warns about insecure certificate on gerrit.wikimedia.org.', 'Chrome:\nQUOTE\nQUOTE\n\n{F18152}']",TRUE,0,"Chrome warns about insecure certificate on gerrit.wikimedia.org." +24099,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Chrome: +> The identity of this website has been verified by RapidSSL CA but it does not have public audit records. +> The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it. + +{F18152}",1417590103,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_description","Chrome warns about insecure certificate on gerrit.wikimedia.org./n/nChrome: +> The identity of this website has been verified by RapidSSL CA but it does not have public audit records. +> The site is using outdated security settings that may prevent future versions of Chrome from being able to safely access it. + +{F18152}","Chrome warns about insecure certificate on gerrit.wikimedia.org./n/nChrome: +QUOTE +QUOTE + +{F18152}","High",80,1422997247,"PHID-USER-xy6c3ul27f336aaedx2d","resolved","True","c3",1,"True","False",-31,"True","['Chrome warns about insecure certificate on gerrit.wikimedia.org.', 'Chrome:\nQUOTE\nQUOTE\n\n{F18152}']",TRUE,0,"Chrome:\nQUOTE\nQUOTE\n\n{F18152}" +24100,"Chrome warns about insecure certificate on gerrit.wikimedia.org","gerrit.wikimedia.org now has a new globalsign cert that is sha256, resolving.",1422997247,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","gerrit.wikimedia.org now has a new globalsign cert that is sha256, resolving.","gerrit.wikimedia.org now has a new globalsign cert that is sha256, resolving.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-22,"True","['gerrit.wikimedia.org now has a new globalsign cert that is sha256, resolving.']",NA,0,"gerrit.wikimedia.org now has a new globalsign cert that is sha256, resolving." +24101,"Chrome warns about insecure certificate on gerrit.wikimedia.org","cert has been purchased, the patchset to merge for this is: + +https://gerrit.wikimedia.org/r/#/c/188396/ + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)",1422987166,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","cert has been purchased, the patchset to merge for this is: + +https://gerrit.wikimedia.org/r/#/c/188396/ + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)","cert has been purchased, the patchset to merge for this is: + +URL + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-22,"True","['cert has been purchased, the patchset to merge for this is:\n\nURL\n\nWhen this happens, someone has to rm the chained file for it to be properly recreated.', ""I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)""]",NA,0,"cert has been purchased, the patchset to merge for this is:\n\nURL\n\nWhen this happens, someone has to rm the chained file for it to be properly recreated." +24101,"Chrome warns about insecure certificate on gerrit.wikimedia.org","cert has been purchased, the patchset to merge for this is: + +https://gerrit.wikimedia.org/r/#/c/188396/ + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)",1422987166,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","cert has been purchased, the patchset to merge for this is: + +https://gerrit.wikimedia.org/r/#/c/188396/ + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)","cert has been purchased, the patchset to merge for this is: + +URL + +When this happens, someone has to rm the chained file for it to be properly recreated. I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-22,"True","['cert has been purchased, the patchset to merge for this is:\n\nURL\n\nWhen this happens, someone has to rm the chained file for it to be properly recreated.', ""I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)""]",NA,0,"I've put in both Daniel and Chad to possibly review my patch (I rather not be the only set of eyes)" +24102,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Mark: I assigned https://rt.wikimedia.org/Ticket/Display.html?id=9130 to you for your approval.",1421780481,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Mark: I assigned https://rt.wikimedia.org/Ticket/Display.html?id=9130 to you for your approval.","Mark: I assigned URL to you for your approval.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Mark: I assigned URL to you for your approval.']",NA,0,"Mark: I assigned URL to you for your approval." +24103,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Alright, if it's complicated to do with misc-web, let's buy a one-off ticket for it then.",1421712205,"PHID-USER-hovi6c77qompv5qd7gtz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Alright, if it's complicated to do with misc-web, let's buy a one-off ticket for it then.","Alright, if it's complicated to do with misc-web, let's buy a one-off ticket for it then.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-24,"True","[""Alright, if it's complicated to do with misc-web, let's buy a one-off ticket for it then.""]",NA,0,"Alright, if it's complicated to do with misc-web, let's buy a one-off ticket for it then." +24104,"Chrome warns about insecure certificate on gerrit.wikimedia.org","the suggestion to use an iptables rule to forward 22 to 29418 came from Faidon recently on IRC",1421272311,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","the suggestion to use an iptables rule to forward 22 to 29418 came from Faidon recently on IRC","the suggestion to use an iptables rule to forward 22 to 29418 came from Faidon recently on IRC",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['the suggestion to use an iptables rule to forward 22 to 29418 came from Faidon recently on IRC']",NA,0,"the suggestion to use an iptables rule to forward 22 to 29418 came from Faidon recently on IRC" +24105,"Chrome warns about insecure certificate on gerrit.wikimedia.org","for the related issue that we want to make Gerrit listen on 22, and not on 29418, which we'd like anyways, besides the cert issue being influence by it + +https://phabricator.wikimedia.org/T84713 +https://gerrit.wikimedia.org/r/#/c/174015/ +https://gerrit.wikimedia.org/r/#/c/172313/ +https://phabricator.wikimedia.org/T37611",1421272219,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","for the related issue that we want to make Gerrit listen on 22, and not on 29418, which we'd like anyways, besides the cert issue being influence by it + +https://phabricator.wikimedia.org/T84713 +https://gerrit.wikimedia.org/r/#/c/174015/ +https://gerrit.wikimedia.org/r/#/c/172313/ +https://phabricator.wikimedia.org/T37611","for the related issue that we want to make Gerrit listen on 22, and not on 29418, which we'd like anyways, besides the cert issue being influence by it + +URL +URL +URL +URL",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""for the related issue that we want to make Gerrit listen on 22, and not on 29418, which we'd like anyways, besides the cert issue being influence by it\n\nURL\nURL\nURL\nURL""]",NA,0,"for the related issue that we want to make Gerrit listen on 22, and not on 29418, which we'd like anyways, besides the cert issue being influence by it\n\nURL\nURL\nURL\nURL" +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"Gerrit runs and listens to 8080 for jetty on ytterbium." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh)." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"(This isn't confusing at all!)" +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"Also note we'll have this issue again when gerrit is replaced by phabricator." +24106,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",1421271551,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.","Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this. + +Gerrit runs and listens to 8080 for jetty on ytterbium. It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080. (This isn't confusing at all!) If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address. However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418. + +So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh). + +Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue. So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own. + +Also note we'll have this issue again when gerrit is replaced by phabricator. We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['Ok, I was wrong about some of the above, Chad volunteered a bit more time so we could properly detail this.', 'Gerrit runs and listens to 8080 for jetty on ytterbium.', 'It also listens on 80 for redirection to 443, and then 443 in apache redirects to 8080.', ""(This isn't confusing at all!)"", 'If we moved this behind misc-web, we would drop all the apache config, and simply have misc-web direct traffic to 8080, and configure jetty to listen on the IP address.', ""However, this doesn't address the actual issue; ssh pulls for git/gerrit use port 29418."", 'So the issue is we need to use port 8080 (gerrit web) and port 29418 (git/gerrit ssh).', ""Daniel suggested that we could use an iptables rule on the misc-web systems to redirect all traffic for ytterbium port 29418 to bypass the varnish directly and go to the system, but we aren't entirely certain if it would work properly, and it is a non-standard solution to the issue."", ""So I'm not sure if we should adopt it, test it, or simply purchase the SSL certificate for gerrit to use on its own."", ""Also note we'll have this issue again when gerrit is replaced by phabricator."", ""We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue.""]",NA,0,"We'll either have to disable ssl pulls (and use https only, which is what Chad and I discussed but we aren't 100% certain ssl pull is needed), or do a similar hack as the above suggestion, since we want/need phabricator to stay cached, just buying a certificate won't solve that issue." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Additionally, it has to use the typical 443 or port 80 for web requests." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"My understanding of the varnish backend config is you can only route a single port (default 80)." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)" +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Previous testing discussion with both Daniel and Chad seem to back this up." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"(RT#9130)" +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work." +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"Again, this is my understanding of it, and if I'm wrong, please let me know!" +24107,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",1421269439,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)","Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it. I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point. + +Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions. Additionally, it has to use the typical 443 or port 80 for web requests. My understanding of the varnish backend config is you can only route a single port (default 80). The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement. Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work. Again, this is my understanding of it, and if I'm wrong, please let me know! (The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.) + +Previous testing discussion with both Daniel and Chad seem to back this up. While there may be a work around, I don't quite know how to do so. + +So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate. (RT#9130)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""Well, first Faidon advised this wouldn't work, and that I shouldn't waste time on it."", ""I wanted to confirm why it wouldn't work, since I imagined I'd be asked in a ticket at some point."", 'Ytterbium is the current gerrit host, and it communicates over port 8080 for some of its functions.', 'Additionally, it has to use the typical 443 or port 80 for web requests.', 'My understanding of the varnish backend config is you can only route a single port (default 80).', 'The role/cache:misc shows port 80 for default, but previous attempts to make gerrit work listing the port 8080 requirement.', ""Since we cannot do forwards for both 8080 and 80 (replacing 443 once we used misc-web), it seems this wouldn't work."", ""Again, this is my understanding of it, and if I'm wrong, please let me know!"", '(The ideal is this goes behind misc-web if only to simplify our ssl certificate requirements.)', 'Previous testing discussion with both Daniel and Chad seem to back this up.', ""While there may be a work around, I don't quite know how to do so."", 'So if a work around is known, we can attempt it, or we can simply purchase a new gerrit certificate.', '(RT#9130)']",NA,0,"While there may be a work around, I don't quite know how to do so." +24108,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#964609, @RobH wrote: +> So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) +> +> The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster. + +I don't understand what this means. Can you elaborate?",1421252877,"PHID-USER-hovi6c77qompv5qd7gtz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#964609, @RobH wrote: +> So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) +> +> The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster. + +I don't understand what this means. Can you elaborate?","QUOTE +QUOTE +QUOTE +QUOTE + +I don't understand what this means. Can you elaborate?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't understand what this means."", 'Can you elaborate?']",NA,0,"Can you elaborate?" +24108,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#964609, @RobH wrote: +> So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) +> +> The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster. + +I don't understand what this means. Can you elaborate?",1421252877,"PHID-USER-hovi6c77qompv5qd7gtz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#964609, @RobH wrote: +> So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) +> +> The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster. + +I don't understand what this means. Can you elaborate?","QUOTE +QUOTE +QUOTE +QUOTE + +I don't understand what this means. Can you elaborate?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't understand what this means."", 'Can you elaborate?']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\n\nI don't understand what this means." +24109,"Chrome warns about insecure certificate on gerrit.wikimedia.org","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",1421176369,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['There are two issues here that I can see:\n\n1) gerrit.wikimedia.org certificate is sha1\n\n2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor.', ""As such, I've created an RT ticket (9130) to get approval to order a new certificate for this."", ""Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.""]",NA,0,"There are two issues here that I can see:\n\n1) gerrit.wikimedia.org certificate is sha1\n\n2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor." +24109,"Chrome warns about insecure certificate on gerrit.wikimedia.org","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",1421176369,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['There are two issues here that I can see:\n\n1) gerrit.wikimedia.org certificate is sha1\n\n2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor.', ""As such, I've created an RT ticket (9130) to get approval to order a new certificate for this."", ""Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.""]",NA,0,"As such, I've created an RT ticket (9130) to get approval to order a new certificate for this." +24109,"Chrome warns about insecure certificate on gerrit.wikimedia.org","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",1421176369,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.","There are two issues here that I can see: + +1) gerrit.wikimedia.org certificate is sha1 + +2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor. + +As such, I've created an RT ticket (9130) to get approval to order a new certificate for this. Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['There are two issues here that I can see:\n\n1) gerrit.wikimedia.org certificate is sha1\n\n2) gerrit.wikimedia.org is rapidssl certificate, a vendor we have migrated away from, so any reissues or revocations of a certificate means we just move it to the new vendor.', ""As such, I've created an RT ticket (9130) to get approval to order a new certificate for this."", ""Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented.""]",NA,0,"Since our procurement process has not migrated quite yet (it will soon, but will be last RT item to migrate), I'll just keep this assigned to me until after the order is completed and implemented." +24110,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",1420770490,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that's the problem."", 'The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge).', '{F27060}\n{F18152}']",NA,0,"The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge)." +24110,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",1420770490,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that's the problem."", 'The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge).', '{F27060}\n{F18152}']",NA,0,"{F27060}\n{F18152}" +24110,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",1420770490,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The message does sound like that, but I don't think that's the problem. The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that's the problem."", 'The same message is shown when in the details about phrabricator.wikimedia.org (which has a green badge).', '{F27060}\n{F18152}']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that's the problem." +24111,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",1420770448,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge)."", '{F27060}\n{F18152}']",NA,0,"{F27060}\n{F18152}" +24111,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",1420770448,"PHID-USER-sai77mtxmpqnm6pycyvz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#939750, @Dzahn wrote: +>>>! In T76562#846225, @Seb35 wrote: +>> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. +> +> The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ? + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}","QUOTE +QUOTE +QUOTE +QUOTE +QUOTE + +The message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge). + +{F27060} +{F18152}",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge)."", '{F27060}\n{F18152}']",NA,0,"QUOTE\nQUOTE\nQUOTE\nQUOTE\nQUOTE\n\nThe message does sound like that, but I don't think that is the issue since the same message is displayed when I pop up details about the encryption on phrabricator.wikimedia.org (which has a green badge)." +24112,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",1420756871,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.)"", 'The sshd port could be configured to a second interface to work around this.', ""I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.""]",NA,0,"The sshd port could be configured to a second interface to work around this." +24112,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",1420756871,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.)"", 'The sshd port could be configured to a second interface to work around this.', ""I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.""]",NA,0,"So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.)" +24112,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",1420756871,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.","So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.) + +The sshd port could be configured to a second interface to work around this. I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""So this won't work behind misc-web-lb until after the gerrit dependency on using sshd on the same interface is happening (since misc-web-lb redirects all backend traffic to port 8080.)"", 'The sshd port could be configured to a second interface to work around this.', ""I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster.""]",NA,0,"I'm not sure if it is worth a lot more cycles of work, but it would be nice to have all these misc services behind a centrally configured ssl termination cluster." +24113,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I'll test this out with setting up the misc web to handle it and locally hacking my /etc/hosts, not changing dns",1420753193,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I'll test this out with setting up the misc web to handle it and locally hacking my /etc/hosts, not changing dns","I'll test this out with setting up the misc web to handle it and locally hacking my /etc/hosts, not changing dns",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'll test this out with setting up the misc web to handle it and locally hacking my /etc/hosts, not changing dns""]",NA,0,"I'll test this out with setting up the misc web to handle it and locally hacking my /etc/hosts, not changing dns" +24114,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I'd suggest we test and use the misc-web-lb for this, since it means one less certificate and therefore less general overhead (since we already have the commitment to maintain misc-web-lb).",1420742761,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I'd suggest we test and use the misc-web-lb for this, since it means one less certificate and therefore less general overhead (since we already have the commitment to maintain misc-web-lb).","I'd suggest we test and use the misc-web-lb for this, since it means one less certificate and therefore less general overhead (since we already have the commitment to maintain misc-web-lb).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'd suggest we test and use the misc-web-lb for this, since it means one less certificate and therefore less general overhead (since we already have the commitment to maintain misc-web-lb).""]",NA,0,"I'd suggest we test and use the misc-web-lb for this, since it means one less certificate and therefore less general overhead (since we already have the commitment to maintain misc-web-lb)." +24115,"Chrome warns about insecure certificate on gerrit.wikimedia.org","It is relevant for #code-review either way, so we definitely should then",1420740618,"PHID-USER-3neel27i7dyu62jbbx2l","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","It is relevant for #code-review either way, so we definitely should then","It is relevant for #code-review either way, so we definitely should then",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['It is relevant for #code-review either way, so we definitely should then']",NA,0,"It is relevant for #code-review either way, so we definitely should then" +24116,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I don't remember to be honest. We could certainly test it.",1420730863,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I don't remember to be honest. We could certainly test it.","I don't remember to be honest. We could certainly test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I don't remember to be honest."", 'We could certainly test it.']",NA,0,"We could certainly test it." +24116,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I don't remember to be honest. We could certainly test it.",1420730863,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I don't remember to be honest. We could certainly test it.","I don't remember to be honest. We could certainly test it.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I don't remember to be honest."", 'We could certainly test it.']",NA,0,"I don't remember to be honest." +24117,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#961213, @Chad wrote: +> We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?",1420730328,"PHID-USER-hovi6c77qompv5qd7gtz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#961213, @Chad wrote: +> We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?","QUOTE +QUOTE + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-25,"True","['QUOTE\nQUOTE\n\n\nWith normal HTTP proxying by Varnish I can imagine that.', 'But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?']",NA,0,"QUOTE\nQUOTE\n\n\nWith normal HTTP proxying by Varnish I can imagine that." +24117,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#961213, @Chad wrote: +> We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?",1420730328,"PHID-USER-hovi6c77qompv5qd7gtz","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#961213, @Chad wrote: +> We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?","QUOTE +QUOTE + + +With normal HTTP proxying by Varnish I can imagine that. But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-25,"True","['QUOTE\nQUOTE\n\n\nWith normal HTTP proxying by Varnish I can imagine that.', 'But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?']",NA,0,"But has VCL return(pipe) been attempted as well, such that Varnish acts as simple TCP proxy for the remainer of the TCP connection?" +24118,"Chrome warns about insecure certificate on gerrit.wikimedia.org","@mark, it sounds like we need to buy a certificate to make this go away, is that something you would approve?",1420730192,"PHID-USER-3neel27i7dyu62jbbx2l","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","@mark, it sounds like we need to buy a certificate to make this go away, is that something you would approve?","SCREEN_NAME, it sounds like we need to buy a certificate to make this go away, is that something you would approve?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['SCREEN_NAME, it sounds like we need to buy a certificate to make this go away, is that something you would approve?']",NA,0,"SCREEN_NAME, it sounds like we need to buy a certificate to make this go away, is that something you would approve?" +24119,"Chrome warns about insecure certificate on gerrit.wikimedia.org","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",1420674377,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves.', ""The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time)."", 'It can very easily use a star or combined cert.']",NA,0,"We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves." +24119,"Chrome warns about insecure certificate on gerrit.wikimedia.org","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",1420674377,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves.', ""The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time)."", 'It can very easily use a star or combined cert.']",NA,0,"It can very easily use a star or combined cert." +24119,"Chrome warns about insecure certificate on gerrit.wikimedia.org","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",1420674377,"PHID-USER-oetk6bbl6omm354ejz3b","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.","We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves. + +The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time). It can very easily use a star or combined cert.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","['We tried putting it behind misc-web-lb but we had problems with the git protocol behaving through the proxy if memory serves.', ""The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time)."", 'It can very easily use a star or combined cert.']",NA,0,"The only reason we bought it it's own cert was because we wanted to stop using *.wikimedia.org on misc services (and if memory serves we bought several similar ones at the time)." +24120,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",1420671474,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","[""So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue."", ""- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)."", ""We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning."", ""I've CC'd Chad so perhaps he can reply back with why it needs its own."", ""(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)""]",NA,0,"So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue." +24120,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",1420671474,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","[""So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue."", ""- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)."", ""We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning."", ""I've CC'd Chad so perhaps he can reply back with why it needs its own."", ""(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)""]",NA,0,"- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)." +24120,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",1420671474,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","[""So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue."", ""- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)."", ""We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning."", ""I've CC'd Chad so perhaps he can reply back with why it needs its own."", ""(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)""]",NA,0,"We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning." +24120,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",1420671474,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","[""So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue."", ""- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)."", ""We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning."", ""I've CC'd Chad so perhaps he can reply back with why it needs its own."", ""(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)""]",NA,0,"I've CC'd Chad so perhaps he can reply back with why it needs its own." +24120,"Chrome warns about insecure certificate on gerrit.wikimedia.org","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",1420671474,"PHID-USER-xy6c3ul27f336aaedx2d","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)","So we have two options (that I see): + +- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue. + +- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments). + +We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning. I've CC'd Chad so perhaps he can reply back with why it needs its own. (If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-26,"True","[""So we have two options (that I see):\n\n- Push gerrit behind misc-web-lb, so it uses the wildcard certifiate (globalsign) and doesn't have this issue."", ""- Order a new certificate for gerrit (since we don't use RapidSSL for any updated deployments)."", ""We purchased a gerrit.wikimedia.org certificate per Chad's request on old RT#4976, and I know he has explained why its better on its own cert, but I cannot find said reasoning."", ""I've CC'd Chad so perhaps he can reply back with why it needs its own."", ""(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)""]",NA,0,"(If it no longer does, we can put behind misc-web; if it does I'll create a procurement ticket for it.)" +24121,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",1420001052,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?","I agree with this task being a relatively high priority. + +I discussed this issue withSCREEN_NAME earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-27,"True","['I agree with this task being a relatively high priority.', 'I discussed this issue withSCREEN_NAME earlier today.', 'The warning in Chrome is unsightly.', ""He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?"", 'en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?']",NA,0,"I agree with this task being a relatively high priority." +24121,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",1420001052,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?","I agree with this task being a relatively high priority. + +I discussed this issue withSCREEN_NAME earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-27,"True","['I agree with this task being a relatively high priority.', 'I discussed this issue withSCREEN_NAME earlier today.', 'The warning in Chrome is unsightly.', ""He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?"", 'en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?']",NA,0,"I discussed this issue withSCREEN_NAME earlier today." +24121,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",1420001052,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?","I agree with this task being a relatively high priority. + +I discussed this issue withSCREEN_NAME earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-27,"True","['I agree with this task being a relatively high priority.', 'I discussed this issue withSCREEN_NAME earlier today.', 'The warning in Chrome is unsightly.', ""He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?"", 'en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?']",NA,0,"The warning in Chrome is unsightly." +24121,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",1420001052,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?","I agree with this task being a relatively high priority. + +I discussed this issue withSCREEN_NAME earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-27,"True","['I agree with this task being a relatively high priority.', 'I discussed this issue withSCREEN_NAME earlier today.', 'The warning in Chrome is unsightly.', ""He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?"", 'en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?']",NA,0,"en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?" +24121,"Chrome warns about insecure certificate on gerrit.wikimedia.org","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",1420001052,"PHID-USER-hyfm4swq76s4j642w46x","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","I agree with this task being a relatively high priority. + +I discussed this issue with @Krenair earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue. @Dzahn: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?","I agree with this task being a relatively high priority. + +I discussed this issue withSCREEN_NAME earlier today. The warning in Chrome is unsightly. He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe? + +en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-27,"True","['I agree with this task being a relatively high priority.', 'I discussed this issue withSCREEN_NAME earlier today.', 'The warning in Chrome is unsightly.', ""He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?"", 'en.wikipedia.org and lists.wikimedia.org both seem unaffected by this issue.SCREEN_NAME: it feels like gerrit.wikimedia.org is already using its own certificate... does a new one need to be purchased or could we just fix the current one?']",NA,0,"He says we just need a new certificate for gerrit.wikimedia.org that doesn't rely on outdated algorithms, maybe?" +24122,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?",1419256887,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?","QUOTE +QUOTE + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-28,"True","[""QUOTE\nQUOTE\n\nThe screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL."", '?']",NA,0,"?" +24122,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?",1419256887,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?","QUOTE +QUOTE + +The screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL. ?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-28,"True","[""QUOTE\nQUOTE\n\nThe screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL."", '?']",NA,0,"QUOTE\nQUOTE\n\nThe screenshot doesn't make it look like that is the actual issue but instead that it comes from RapidSSL." +24123,"Chrome warns about insecure certificate on gerrit.wikimedia.org","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +",1419256546,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-28,"True","['ways to solve this:\n\n- resolve T18\n- buy a new cert\n- move gerrit behind misc-web varnish??', '(without caching)']",NA,0,"ways to solve this:\n\n- resolve T18\n- buy a new cert\n- move gerrit behind misc-web varnish??" +24123,"Chrome warns about insecure certificate on gerrit.wikimedia.org","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +",1419256546,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +","ways to solve this: + +- resolve T18 +- buy a new cert +- move gerrit behind misc-web varnish?? (without caching) +",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-28,"True","['ways to solve this:\n\n- resolve T18\n- buy a new cert\n- move gerrit behind misc-web varnish??', '(without caching)']",NA,0,"(without caching)" +24124,"Chrome warns about insecure certificate on gerrit.wikimedia.org",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +but we don't want to copy that cert to the gerrit host.",1419255849,"PHID-USER-fo56wm4wxiwpoofn2xdu","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment",">>! In T76562#846225, @Seb35 wrote: +> The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature. + +but we don't want to copy that cert to the gerrit host.","QUOTE +QUOTE + +but we don't want to copy that cert to the gerrit host.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-28,"True","[""QUOTE\nQUOTE\n\nbut we don't want to copy that cert to the gerrit host.""]",NA,0,"QUOTE\nQUOTE\n\nbut we don't want to copy that cert to the gerrit host." +24125,"Chrome warns about insecure certificate on gerrit.wikimedia.org","The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature.",1418492302,"PHID-USER-2nopae2cxuamwcbndaih","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature.","The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-29,"True","['The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature.']",NA,0,"The certificate *.wikimedia.org used on phabricator.wikimedia.org and other sites can be used; it has a SHA-256 signature." +24126,"Chrome warns about insecure certificate on gerrit.wikimedia.org","Also see {T73156} about another Chrome warning for Gerrit.",1417615582,"PHID-USER-hgn5uw2jafgjgfvxibhh","PHID-TASK-bw55vakzcnxdtorfihta","task_subcomment","Also see {T73156} about another Chrome warning for Gerrit.","Also see {T73156} about another Chrome warning for Gerrit.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-31,"True","['Also see {T73156} about another Chrome warning for Gerrit.']",NA,0,"Also see {T73156} about another Chrome warning for Gerrit." +24747,"Graphics on the login and create account forms are not SVG","Graphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.",1420746433,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yhbcve5g2wopseezdanf","task_description","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.","Medium",50,NA,NA,"open","True","c3",1,"True","False",-25,"True","['Graphics on the login and create account forms are not SVG.', 'Graphics on the login and create account forms are not SVG.', ""And that's terrible."", 'There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.']",FALSE,0,"Graphics on the login and create account forms are not SVG." +24747,"Graphics on the login and create account forms are not SVG","Graphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.",1420746433,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yhbcve5g2wopseezdanf","task_description","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.","Medium",50,NA,NA,"open","True","c3",1,"True","False",-25,"True","['Graphics on the login and create account forms are not SVG.', 'Graphics on the login and create account forms are not SVG.', ""And that's terrible."", 'There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.']",FALSE,0,"Graphics on the login and create account forms are not SVG." +24747,"Graphics on the login and create account forms are not SVG","Graphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.",1420746433,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yhbcve5g2wopseezdanf","task_description","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.","Medium",50,NA,NA,"open","True","c3",1,"True","False",-25,"True","['Graphics on the login and create account forms are not SVG.', 'Graphics on the login and create account forms are not SVG.', ""And that's terrible."", 'There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.']",FALSE,0,"There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form." +24747,"Graphics on the login and create account forms are not SVG","Graphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.",1420746433,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yhbcve5g2wopseezdanf","task_description","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in `resources/src/mediawiki.special/images` that are used in login form or account creation form.","Graphics on the login and create account forms are not SVG./n/nGraphics on the login and create account forms are not SVG. And that's terrible. + +There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.","Medium",50,NA,NA,"open","True","c3",1,"True","False",-25,"True","['Graphics on the login and create account forms are not SVG.', 'Graphics on the login and create account forms are not SVG.', ""And that's terrible."", 'There are four large-ish drawings and one tiny icons in CODE that are used in login form or account creation form.']",FALSE,0,"And that's terrible." +24748,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995825,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"Thanks,SCREEN_NAME-WMF!" +24748,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995825,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png." +24748,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995825,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"contributors-icon.svg probably changed during the design process." +24748,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995825,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/9e7e9b76bdf504f0867e2239ff84efc322eb1298/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided)." +24749,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995756,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"Thanks,SCREEN_NAME-WMF!" +24749,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995756,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png." +24749,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995756,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"contributors-icon.svg probably changed during the design process." +24749,"Graphics on the login and create account forms are not SVG","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).",1424995756,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Thanks, @Pginer-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/glyph-people-large.png +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-lock.png (just a lock, we have another in SVG at https://www.mediawiki.org/wiki/File:Locked_icon.svg) +* https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki.special/images/icon-contributors.png (this is the one that probably changed from the one you provided).","Thanks,SCREEN_NAME-WMF! + +It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png. + +contributors-icon.svg probably changed during the design process. + +The ones we're still looking for are: + +* URL +* URL (just a lock, we have another in SVG at URL +* URL (this is the one that probably changed from the one you provided).",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-18,"True","['Thanks,SCREEN_NAME-WMF!', 'It looks like edits-icon.svg matches icons-edit.png, and pages-icon.svg matches icon-pages.png.', 'contributors-icon.svg probably changed during the design process.', ""The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided).""]",NA,0,"The ones we're still looking for are:\n\n* URL\n* URL (just a lock, we have another in SVG at URL\n* URL (this is the one that probably changed from the one you provided)." +24750,"Graphics on the login and create account forms are not SVG","I have found [[ https://www.dropbox.com/s/oz1cjgfqxmhsxce/Account-Creation-Mockup.psd?dl=0 | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.",1424949860,"PHID-USER-c47vnc2yxmwfvvc4367q","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I have found [[ https://www.dropbox.com/s/oz1cjgfqxmhsxce/Account-Creation-Mockup.psd?dl=0 | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.","I have found [[ URL | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-18,"True","['I have found [[ URL | the following mockup ]] in the design folder.', ""I extracted the three icons that appear in the mockup as SVG:\n\n{F47553}\n\n{F47554}\n\n{F47555}\n\nIf those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.""]",NA,0,"I have found [[ URL | the following mockup ]] in the design folder." +24750,"Graphics on the login and create account forms are not SVG","I have found [[ https://www.dropbox.com/s/oz1cjgfqxmhsxce/Account-Creation-Mockup.psd?dl=0 | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.",1424949860,"PHID-USER-c47vnc2yxmwfvvc4367q","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I have found [[ https://www.dropbox.com/s/oz1cjgfqxmhsxce/Account-Creation-Mockup.psd?dl=0 | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.","I have found [[ URL | the following mockup ]] in the design folder. I extracted the three icons that appear in the mockup as SVG: + +{F47553} + +{F47554} + +{F47555} + +If those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.",NA,NA,NA,NA,NA,"True","c3",1,"False",NA,-18,"True","['I have found [[ URL | the following mockup ]] in the design folder.', ""I extracted the three icons that appear in the mockup as SVG:\n\n{F47553}\n\n{F47554}\n\n{F47555}\n\nIf those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them.""]",NA,0,"I extracted the three icons that appear in the mockup as SVG:\n\n{F47553}\n\n{F47554}\n\n{F47555}\n\nIf those are not the icons, please provide a screenshot with the icons you are looking for, and I'll try to find them." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"Munaf was kind enough to reply." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"He also said they might be on Google Drive." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"P.S." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"Munaf says hi." +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,":)" +24751,"Graphics on the login and create account forms are not SVG","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",1421283396,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee), @HowieF or @Pginer-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)","Munaf was kind enough to reply. He said the vector versions were originally in a PSD, but he couldn't find it. He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them. He also said they might be on Google Drive. + +P.S. Munaf says hi. :)",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-24,"True","['Munaf was kind enough to reply.', ""He said the vector versions were originally in a PSD, but he couldn't find it."", 'He mentioned that Steven Walling (also no longer a WMF employee),SCREEN_NAME orSCREEN_NAME-WMF might have them.', 'He also said they might be on Google Drive.', 'P.S.', 'Munaf says hi.', ':)']",NA,0,"He said the vector versions were originally in a PSD, but he couldn't find it." +24752,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",1421210577,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.""]",NA,0,"He was my teammate on E3 when we were working on this project." +24752,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",1421210577,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.""]",NA,0,"See URL ." +24752,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",1421210577,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.""]",NA,0,"I'm pretty sure they were designed by Munaf Assaf." +24752,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",1421210577,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I've emailed him just in case he still has them and is able to dig them up.""]",NA,0,"He no longer works here, but I've emailed him just in case he still has them and is able to dig them up." +24753,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",1421210565,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I'll email him just in case he still has them and is able to dig them up.""]",NA,0,"He was my teammate on E3 when we were working on this project." +24753,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",1421210565,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I'll email him just in case he still has them and is able to dig them up.""]",NA,0,"See URL ." +24753,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",1421210565,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I'll email him just in case he still has them and is able to dig them up.""]",NA,0,"I'm pretty sure they were designed by Munaf Assaf." +24753,"Graphics on the login and create account forms are not SVG","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",1421210565,"PHID-USER-dw53c5cb2qfhyemej57o","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See https://gerrit.wikimedia.org/r/#/c/30637/ . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.","I'm pretty sure they were designed by Munaf Assaf. He was my teammate on E3 when we were working on this project. See URL . + +He no longer works here, but I'll email him just in case he still has them and is able to dig them up.",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","[""I'm pretty sure they were designed by Munaf Assaf."", 'He was my teammate on E3 when we were working on this project.', 'See URL .', ""He no longer works here, but I'll email him just in case he still has them and is able to dig them up.""]",NA,0,"He no longer works here, but I'll email him just in case he still has them and is able to dig them up." +24754,"Graphics on the login and create account forms are not SVG","@SPage, @Mattflaschen, do you remember who created these, and can you hunt them down for the original vector files?",1420746586,"PHID-USER-wkpnidxoctuhawexig5p","PHID-TASK-yhbcve5g2wopseezdanf","task_subcomment","@SPage, @Mattflaschen, do you remember who created these, and can you hunt them down for the original vector files?","SCREEN_NAME,SCREEN_NAME, do you remember who created these, and can you hunt them down for the original vector files?",NA,NA,NA,NA,NA,"True","c3",1,"True",NA,-25,"True","['SCREEN_NAME,SCREEN_NAME, do you remember who created these, and can you hunt them down for the original vector files?']",NA,0,"SCREEN_NAME,SCREEN_NAME, do you remember who created these, and can you hunt them down for the original vector files?" diff --git a/dsl/human_sampling.R b/dsl/human_sampling.R index 1d3b9e9..6efee1b 100644 --- a/dsl/human_sampling.R +++ b/dsl/human_sampling.R @@ -1,23 +1,45 @@ library(tidyverse) -main_csv <-"~/analysis_data/092925_unified_phab.csv" +main_csv <-"~/analysis_data/100325_unified_phab.csv" main_df <- read.csv(main_csv, header = TRUE) -set.seed(123) # For reproducibility +set.seed(1871) # For reproducibility sampled_df <- main_df %>% group_by(source) %>% - mutate(sampled_TaskPHID = TaskPHID %in% sample(unique(TaskPHID), 30)) %>% + mutate(sampled_TaskPHID = TaskPHID %in% sample(unique(TaskPHID), 35)) %>% ungroup() %>% filter(sampled_TaskPHID) %>% select(-sampled_TaskPHID) -sentence_level_sample <- sampled_df |> - mutate(cleaned_sentences = str_extract_all(olmo_cleaned_sentences, "(?<=')[^']+(?=')")) |> +labeling_sampled_df <- sampled_df %>% + group_by(source) %>% + mutate( + verification_sample = if_else( + TaskPHID %in% sample(unique(TaskPHID), min(7, length(unique(TaskPHID)))), 1L, 0L + ) + ) %>% + ungroup() + +sentence_level_sample <- labeling_sampled_df |> + mutate( + cleaned_sentences = lapply( + olmo_cleaned_sentences, + function(x) { + m <- str_match_all(x, "'([^']*)'|\"([^\"]*)\"")[[1]] + # Both columns 2 and 3 may exist, but only one will be filled for each match + vals <- c(m[,2], m[,3]) + vals <- vals[vals != "" & !is.na(vals)] + return(vals) + } + ) + )|> unnest(cleaned_sentences)|> filter(cleaned_sentences != ", ") |> - select(-olmo_sentence_categories, -starts_with("normalized"), -starts_with("gerrit")) + select(-olmo_sentence_categories, -starts_with("normalized"), -contains("gerrit")) + +table(sentence_level_sample$verification_sample) (nrow(sentence_level_sample) / 293) * 1.5 -#write.csv(output_df, "100125_human_info_sample.csv", row.names = FALSE) \ No newline at end of file +write.csv(sentence_level_sample, "100625_human_info_sample.csv", row.names = FALSE) diff --git a/mgaughan-rstudio-server_29985545.out b/mgaughan-rstudio-server_29985545.out new file mode 100644 index 0000000..3d6d0a9 --- /dev/null +++ b/mgaughan-rstudio-server_29985545.out @@ -0,0 +1,17 @@ +1. SSH tunnel from your workstation using the following command: + + ssh -N -L 8787:n3439:58519 mjilg@klone.hyak.uw.edu + + and point your web browser to http://localhost:8787 + +2. log in to RStudio Server using the following credentials: + + user: mjilg + password: Kyq6AGP0kRtXvXeoXReZ + +When done using RStudio Server, terminate the job by: + +1. Exit the RStudio Session ("power" button in the top right corner of the RStudio window) +2. Issue the following command on the login node: + + scancel -f 29985545