Movement Communications Specialist at the Wikimedia Foundation
This is my staff account. See @Ckoerner for volunteer stuff.
Profile image licensed under Creative Commons Attribution-Share Alike 3.0 Unported license.
Movement Communications Specialist at the Wikimedia Foundation
This is my staff account. See @Ckoerner for volunteer stuff.
Profile image licensed under Creative Commons Attribution-Share Alike 3.0 Unported license.
In T344479#9391878, @Novem_Linguae wrote:Thanks Chris for that info and for your team's work on this. The Meta-Wiki presence project sounds like a great project that should improve community relations. Couple quick questions:
- Is there still a plan to update https://wikimediafoundation.org/role/staff-contractors/ (rather than just putting it all on-wiki, for example)?
- Approximate timeline for https://wikimediafoundation.org/role/staff-contractors/ to be updated? Two months maybe?
Thanks a lot. Looking forward to your feedback.
Hey everyone, sorry for the delay in responding—it took a bit for this task to make its way to our team. We are working on getting an updated staff listing and org structure as part of a larger project to overhaul the Foundation’s overall presence on Meta. The project, which is being led by the Movement Communications team (the team I’m on), is about building a better front door to the Foundation’s work. It’s based on a longstanding ask from community members for us to clean up our org structure as well as team and department pages (including staff listings) in a way that will better connect you all with the information, resources, and support you need from the Foundation. Take a look here to get a sense of what we’re working on.
I'm seeing other users leaving comments as well. I am resolving this issue given that T348111 is now resolved and our fix is working as intended!
This should be fixed permanently as of T348111. Apologies for the disruption of service.
Ok, I met with our developers earlier this week and now can confirm that this is holding. Resolving this issue as our plugin is working as intended.
After some light testing I think this may be related to another issue we're having on the site. We've implemented a change. Could you please try again and let me know if the site is agreeable for you?
We have our plugin in production. This should resolve the issue. I'm not going to resolve this until I can be sure, but adding a note here for transparency.
Since tags can be added by anyone they run the risk of being messy. :) It looks like someone inadvertently punched lines of text into the tag field. I've removed these and the autocomplete is working better.
Yeah, this is a frustrating situation. Our patch we deployed yesterday hit a snag, but we're addressing the issue and will have a solution eventually.
Thank you @Hurohukidaikon for the report! As mentioned in T345512, this is related to an issue with our translation/multilingual plugin. The site is working as intended now and the pages and posts are loading. If an issue comes up again, please let us know. For now, I'll consider this resolved.
I appreciate folks noticing and alerting us of these issues. There was a bug relating to the translation/multilingual plugin (Polylang) that was causing some issues with the site. See also T345582. We did the old 'turn it off and on again' fix and things are working as intended. I see new posts appearing on Planet Wikimedia as an example (https://en.planet.wikimedia.org)
Where is the code, especially the temporary fix? Maybe volunteers could help if they had access to the code.
This should be handled upstream in WordPress core. There is a task for it in their community and input there is welcome: https://core.trac.wordpress.org/ticket/44610
In doing some cleanup on the diff-blog board I'm revisiting this task. We did this for Diff back in May. For those with access: https://github.com/wpcomvip/wikimedia-blog-wikimedia-org/pull/230
A temporary fix is in place. I have a task on the list with our developers to have a more consistent fix, should be resolved in the next few months.
We have resolved the larger issue with plugins. They should now not be showing banners to non-Admins. Thanks again to @TheDJ for brining this to our attention. For posterity :) see the commit below.
May it be linked to the fact I have the same account on WordPress created separately?
According to T321160#8703886 this is resolved. I'm able to confirm and test as well. Big thanks to @Juandev for making us aware and to @Tgr for pinpointing the cause.
Hmm, looks like OAuth is not having a good day. If folks have an existing account they can request a password reset and login via the WordPress authentication at https://diff.wikimedia.org/wp-login.php
@Bennylin, I'm looking into this now. When you are translating a draft blog post, is the "duplicate" icon highlighted? https://diff.wikimedia.org/wp-content/uploads/2022/05/duplicate-icon.png
A welcome request @Bennylin. I have now added basa Jawa with the language code jv. You should be able to select it from the translation interface.
Thanks for flagging this @Bennylin. This is a bug in the calendar system that came about with a recent software update. We hope to have a patch in place in a few weeks. For the time being, notifications like this or an email to diff@wikimedia.org lets us know, and folks with the right permissions can publish events manually. I've done so for your event. Please reach out if you need to change anything.
We (The folks who help keep Diff running) have been thinking about this idea. Over the last two years we haven't seen much interest from community for creating such a board. Admittedly we as staff also haven't been able to dedicate the time it would take to setup and manage such a board. One set up the right way that would allow for the frequency and diversity of posts as we do now. (Also, the idea of an editorial board was from a different time and the organization has changed since then).
This has been done. We're using the new shiny schema and the message is no longer showing. I have a larger task with our development partners to hide these administrative messages from folks with the contributor role.
I'll have to dig into this one. It's not apparent to me why this is only happening to German and not all languages. The conjunction is a translated string ("und", "y", "et", etc.) so it should be breaking consistency across languages!
This was one of those tasks where I thought, "Gosh, this is going to take a while to dig into and figure out how to solve. I'll probably have to learn how to use the wp-cli search-replace command, build a command to specify the post_content field in the database, test that against our develop instance, and make sure I don't bork the blog. I'll get to it when I have more time."
Thanks for the head's up @TheDJ. Folks with the contributor role shouldn't be seeing these messages intended for admins. I'll see what I can do to remove these notices. For now, the worst thing that could happen is someone updates the events database for me. Which would be surprising. Right now the preflight check doesn't complete (on our dev environment) due to an issue with a few events.
Yes, I can, but probably not until sometime next month. I have a request in with our folks at Human Made who have some hours set aside for supporting Diff then. I'm currently busy with preparations for sharing out the Annual Plan and Wikimania, which is taking up my time at the moment.
I logged into Github today to see if I could give Varnet access and...I don't have admin access. So, could both Greg and I be added as admin to the wikimedia/interconnection-wordpress-theme repo please. (It's possible I didn't act on the invite mentioned in the task above. Apologies.
Related original ask for this repo (that I never got to populating!) T267612
I like this idea if it would make the process less manual than it is currently. I've often found myself spending an entire work day copy/pasting translated text from a Google doc into the Translation interface on-wiki. Given that I'm a monoglot I'm surprised I haven't messed up entire pages (yet).
It's not the canonical repo, just a public mirror. We're working on a better system for sharing and contributing the code behind Diff.
This has been fixed with a recent update to the co-authors plugin. You can now more easily manage multiple authors. See this blog post about the update!
If I understand things correctly, two parts are needed. Commons needs to provide an oEmbed response to requests (such as from WordPress) and WordPress core needs to include oEmbed support for Commons.
An update to our CSS rules broke the calendar interface for a bit. We updated the rules a few weeks ago and things are back to as they should be. :)
Hmm. This seems to be a conflict with the translation plugin. I'll investigate.
Sorry for the delay in responding here. An update to WordPress since this was reported has fixed this issue. The pagination now works as intended.
Thanks @Urbanecm.
I've had my technical questions addressed here and elsewhere. Thanks all for the input.
This is a result of the multilingual software we use on Diff, Polylang. At least in part. It creates a language variant for each taxonomy (categories/tags) when used. This way each category or tag can be written and displayed in the appropriate language (so you don't see a post written in Russian with the English category "Campaigns"). Ideally when editing a post you'd see something like "Campaigns (RU)" or "кампании" in the selection list.
Thanks for trying @Kizule!
see emails sent to assignee on May26 and Jun17
I can confirm that I'm now receiving the digest emails. Thanks y'all for the quick response.
Agreed, this is confusing. The extension we're using for WordPress allows us to have multiple authors, and authors who don't have an account on Diff. It also conflicts with this setting in ways that doesn't give appropriate attribution in the email version of posts. I digress.
My foundation staff account ckoerner@, the other user is kstinerowe@
Note: I am receiving digests for other lists such as wikitech-l and MediaWiki-l.
Thank you both @Urbanecm and @MarcoAurelio
Added a note about Diff on the Wikimedia Blog page on meta. That page now references the News section of wikimediafoundation.org.
@Dsharpe You haven't missed anything. We didn't know if it was best to alert you before we made any purchase as we didn't want to buy something only to have Security say no. If it's normal to proceed as you describe I can talk to my supervisor to make that happen.
As per T249039#6309061, medium requires management level acceptance of the risk.
@Reedy et al, are Brad's license updates satisfactory? Anything else needed from our end?
@MarcoAurelio, I hate to be a bother, but is this something you can assist me with?
We had some CSS concatenation issues that were causing the stylesheet for comments to break. That's been fixed in an update from a few months ago. I'm able to verify it's loading as intended. Resolving.
Brad has made the changes regarding licensing (and is also now subscribed to this task). :) 👋
Hi @Reedy! Let me try my best.
Adding a note here that I've spoken to our developer and he is ready for a security review. As mentioned above, the code can be found at the following repo (let me know if you need access).