Reassigning to Kartik since today is my last day at WMF. The patch should be good to go but needs review.

There seems to be an issue running cxserver as a service using upstart. I can ssh into the vagrant instance and start cxserver manually with:

sudo node /srv/cxserver/src/Server.js

If I do that everything works fine, but vagrant provision does not seem to be able to start cxserver as a service using upstart. I believe the conf file is correct and it is very similar to the parsoid conf.

I will add the necessary modules to extension.json tomorrow to bring the file up-to-date.

Do we want to update the titles on the dashboard? Or is what we have now ok? Changing the text for the tabs on the dashboard is a simple change, but we will need Dan to deploy the change after we make it.

Moving to Sprint 83 so it can be done along with the other link related tasks.

I tried setting the local user options separately using ::mediawiki::settings and put the priority at 90 so it would be loaded after the ContentTranslation extension is loaded as suggested in T88665. Does not seem to have had any effect.

@Pginer-WMF: Dan and I revised the titles of the two graphs on the dashboard a few days ago and merged the changes but for some reason the dashboard does not seem to have updated. I will follow up with Dan today to see what is up.

I've looked into what implementing this would require. I think it wouldn't require more than a one day's worth of effort with minimal to moderate changes to the code. If we want to include in sprint 82, I can probably take it. However, it might be considered more of a new feature than a bug so I am also fine if we want to postpone in order to address higher priority issues.

Etherpad:

Yes. It is, I believe.

The schema you mention was set up in June and has never been used. We currently only use the schema that is called just "ContentTranslation." The other schema can be safely deleted. Thanks for the info about naming conventions. We will follow the convention in the future.

All the security related patches are merged and on beta-labs now. Please verify that things are as you need them and if they are resolve this task.

The patch ended up being quite simple and fixes an important bit of functionality. We might want to consider including it in the current release.

It looks like the necessary patch is waiting on review from Amir. Should be available shortly.

@csteipp. To reiterate what Santhosh said, the drafts are only visible to the user who created them and they can be deleted. This would seem to take care of the comments about drafts you made. We already have approval from legal on storing drafts in the db since no one else can see them.

@Pginer-WMF. I want to double check with you when the remove link card should be shown.

The publish to user namespace if we are publishing to the real Wikipedia functionality has not been implemented yet because at the time we did this story we did not have the configuration parameter or any way to detect whether we were publishing to main namespace or user namespace by default.

The point is to insert a link that uses the adapted title as the link text at the caret position; not to make the surrounding text a link. So in your example above, it would insert a link with the text "BBC Radio" wherever the text caret is. This would only be done by clicking "Add link." There would be no automatic link creation when clicking on a source link.

It is still possible to add a link inside another link. Selecting text inside a link does not automatically create a new link now, but if you select text inside a link you get the "Add link" card and clicking on "Add link" inserts a link inside the link.

Patches updated following comments from Krinkle. Code to encode as html entities and decode on the client side removed.

I have modified the communication between cxserver and the front end for MT. Response from the server is now sent as JSON with <,> and " converted to html entities. Decoded on the client.