Page MenuHomePhabricator

mwEmbed is hosted on prototype.mw, meaning that it does not support https
Closed, DeclinedPublic

Description

Hi,

It there anything against moving mwEmbed to commons / meta instead of prototype?

If it's only about having people to do the job, I'm considering to ask for editinterface rights for other security fixes related to https, so maybe I could do this too.

Best regards,


Version: unspecified
Severity: normal

Details

Reference
bz32457

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 12:07 AM
bzimport set Reference to bz32457.

mdale wrote:

mwEmbed presently makes use of a custom loading framework. So it would not be easy to just "move it over" to commons. We are working on ~native~ support for mwEmbed in an extension called Timed Media Handler see bug 27699

After we deploy TMH I can look at porting the other mwEmbed components ( video editor ) over to the new gadget system.

--michael

  • Bug 34520 has been marked as a duplicate of this bug. ***

prototype.wikimedia.org is going to get killed soon (see bug 41433).
Does the issue of missing https:// still applies to a currently supported testing server (labsconsole?)?

Native support for mwEmbed via TMH is in place now (see bug 27699).

(In reply to comment #1 by Michael Dale)

After we deploy TMH I can look at porting the other mwEmbed components ( video
editor ) over to the new gadget system.

Michael: Is that still desirable or is this a WONTFIX?

Assuming this is obsolete now as prototype.* is going to die soon.
We won't fix issues on prototype anymore.

Jérémie: If this is still a problem on labsconsole etc, please file a new report against MediaWiki extensions > TimedMediaHandler. Thanks!