In T215046#4972989, @chasemp wrote:

I have not encountered anyone who has told me that our account creation process or requiring an account is preventing them from participating.

In T175072#4815209, @Aklapper wrote:

Worth to check again once we've deployed https://secure.phabricator.com/T12588 / https://secure.phabricator.com/T12278 in our instance.

For the records, the problem still happens after the Phabricator (2019-02-20) update, as https://secure.phabricator.com/T13091

I cannot reproduce the problem anymore after the Phabricator (2019-02-20) update with https://phabricator.wikimedia.org/maniphest/query/1TDNmKbr02bw/?after=165203.PHID-PROJ-nuz724p235zffwqwhsqa

In T198661#4854654, @Aklapper wrote:

Should test again in our instance once we've pulled a new version from upstream as https://secure.phabricator.com/D19951 got merged on 20190103.

Hi @Bhavanatwr, thanks for taking the time to report this!
Unfortunately this report lacks some information. If you have time and can still reproduce the problem: Please add a more complete description to this report.
That can be a clear list of specific steps to reproduce the situation, as little details sometimes matter, so that nobody needs to guess how you performed each step, describing actual results and expected results after performing the steps to reproduce, providing a link to a public website where the issue can be seen, if you see the same behavior when you are not logged in, information about your web browser(s), MediaWiki version information (if it is not on a Wikimedia wiki), etc.
You can edit the task description by clicking Edit Task.
Ideally, exact and clear steps to reproduce should allow any other person to follow these steps (without having to interpret those steps) and see the same results. Problems that others can reliably reproduce can get fixed faster. Thanks!

Please see and follow https://www.mediawiki.org/wiki/Manual:How_to_debug/Login_problems and report back here. Thanks!

The problem is not really that it is night somewhere on this planet, but finding people who can do SWAT deployments. Feel free to ask in #wikimedia-tech [ https://www.mediawiki.org/wiki/MediaWiki_on_IRC | on Freenode IRC] but I'd say it's unlikely as it's so short-term.

@C.Suthorn: Is this basically T63487: Sharing a Wikimedia Commons file description on Twitter should use a Twitter card ?

Problem does not happen in Firefox 65 on Fedora29. (For future reference, please include browser information when filing CSS issues - thanks!)

@Elephanthunter: Please read https://www.mediawiki.org/wiki/Bug_management/Phabricator_etiquette and stick to technical arguments instead of getting personal in the initial version of your last comment. Thanks a lot.

I do not know what this bug report is about, what "box for title" and where to see a letter G.

Please associate at least one project with this task. This will allow others to see this task when looking at the workboard. Thanks.

@JoHammer: I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!).
Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task.
Please claim this task again when you plan to work on it (via Add Action... → Assign / Claim in the dropdown menu) - it would be welcome! Thanks for your understanding!

This is not a place to play.

https://meta.wikimedia.org/wiki/Surveys implies that Qualtrics is currently used.

All subtasks closed, what is left here? Resetting assignee as the account @egalvezwmf is not active anymore.

This task seems to be about CE Insights 2016, hence closing as obsolete as it is 2019 now. Feel free to reopen this task if I misunderstood.

No reply from @jeblad hence resetting status

Quick request to everyone: Please do not post general development environment issues or questions about Phabricator itself in this task, as that's unrelated to the very topic of this task. See https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback,_questions_and_support - thanks a lot!

Someone has to do it, and you assigned this task to yourself so I guess you will create these projects. :P

Closing as invalid as no code changes in Babel have taken place. Glad you found the reason!

Thanks for reporting this, however Wikimedia cannot do anything about problems on other websites. Please report problems on that website to the maintainers of that website, so they can fix their broken website. Please point them to https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin which has more information how they can fix their broken website.

Thanks for reporting this, however Wikimedia cannot do anything about problems on other websites. Please report problems on that website to the maintainers of that website, so they can fix their broken website. Please point them to https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin which has more information how they can fix their broken website.

Removing Language-Team as this has nothing to do with the Language Team (see description) and it is up to each team what they plan to work on

Thanks for reporting this, however Wikimedia cannot do anything about problems on other websites. Please report problems on that website to the maintainers of that website, so they can fix their broken website. Please point them to https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin which has more information how they can fix their broken website.

Thanks for reporting this, however Wikimedia cannot do anything about problems on other websites. Please report problems on that website to the maintainers of that website, so they can fix their broken website. Please point them to https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin which has more information how they can fix their broken website.

I'm afraid of overengineering here and the tag name sounds very broad and misleading without reading its tag description...

Thanks for taking a look at the code!

unrelated to wikimedia websites hence adjusting project tags. See https://www.mediawiki.org/wiki/Localisation for pointers.

In T115537#4774355, @Aklapper wrote:

No open tasks are being tracked in this Tracking task. Can this task be closed nowadays? If not, which specific subtasks are missing?

Does this problem also happen with other web browsers? Which ones have you tried? Which exact Safari version is used? Please also answer the questions in https://phabricator.wikimedia.org/T211693#4815760

@Puneethchanda: I am resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!).
Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task.
Please claim this task again when you plan to work on it (via Add Action... → Assign / Claim in the dropdown menu) - it would be welcome! Thanks for your understanding!

@Theklan: Could you reply to T191396#4842449 please? Thanks!

Nice catch, thanks! Does that make this ticket obsolete and https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/CodeMirror/+/421349/ declined?

Any chance you could track down / identify the exact string to change in https://phabricator.wikimedia.org/diffusion/ECOL/browse/master/i18n/th.json ?

@jeblad: Cannot reproduce (anymore?) on https://no.wikipedia.org/wiki/Ulv?veaction=edit&debug=true and the aforementioned gadget got removed in
https://no.wikipedia.org/w/index.php?title=MediaWiki:Gadgets-definition&type=revision&diff=19183810&oldid=18749188&diffmode=source - is this still an issue?

lgtm too; could probably be resolved? (And big thanks!)

@Naveenpf : ping? ^

I assume the recent silence realistically makes this task "declined"? :-/

@Siacali: Which exact Graph and JsonConfig versions/branches is this about? Did Yurik explicitly agree to be the assignee of this task?

(Context link: "Restricting anon and newbie contributions " under https://meta.wikimedia.org/wiki/Limits_to_configuration_changes#Underlying_issues )

If this still happens: Has anyone else managed to reproduce this problem with that specific image?

Zhou is not around anymore and there are no news yet (if there were, they'd be mentioned here) unfortunately. Someone with time and resources would need to pick this up again and find someone with time and resource in Legal.

Anyone having an idea where to discuss such a policy? engineering@? Asking as I'm afraid that this ticket could get stuck (though the questions in the last line of T212911#4854118 also sound valid to me).

(@srodlund: Are you sure you wanted to completely remove this task (and the four ones) from the Developer-Advocacy workboard, instead of just moving it to a different column which is not in the past?)

@Jrbranaa: Could you elaborate please?

Which specific and non-theoretical problem is created by the "excess of lines"?

Uhm. Has it been considered to not give different and separate codebases the very same names instead, to avoid ambiguity and confusion?

In T215106#4945684, @Romaine wrote:

Nothing seems to have happened, we are still waiting...

Hi @Tw2019, thanks for taking the time to report this!
Is the MultimediaViewer extension installed, and in which exact version?
When you click on the first link directly, can you access the image and is the image displayed in your web browser? If it is not displayed, what is displayed / which exact error message is shown?
Does this problem also happen with another browser (which browser)?
Have you tried to bypass your browser cache?