Project:Current issues

Jump to: navigation, search

About this board

This page is for discussing issues related to site. To get help with MediaWiki software, ask on Project:Support desk.
By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
Le nain23 (talkcontribs)


Je viens d'installer mediawiki-1.29.1 et je ne vois pas ou je peux changer de skins, pouvez m'aider SVP

Ciencia Al Poder (talkcontribs)

See Manual:$wgDefaultSkin

Reply to "changer de skins"

Some updates about Recent Changes pages

Trizek (WMF) (talkcontribs)


As you may already know, the Collaboration team has created a Beta feature. This feature is on your wiki since few months: "New filters for edit review". You can activate it in your Beta preferences.

What is this feature again?

This feature improves Special:RecentChanges and Special:RecentChangesLinked. It adds new features that ease vandalism tracking and support of newcomers:

  • Filtering - filter recent changes with easy-to-use and powerful filters combinations.
  • Highlighting - add a colored background to the different changes you are monitoring. It helps quick identification of changes that matter to you.

You can know more about this project by visiting the quick tour help page.

What's new?

Since the release, we have fixed small bugs and improved the interface. We have also released a way to bookmark your favorite configurations of filters.

We plan to add more new features! The full list is on this Phabricator page (in English) but here are the most important ones:

  • Filters for Namespaces and tagged edits and, later, filters for Categories and Usernames; they will help you to patrol specific changes more accurately
  • Redesign navigation by using an improved time selector and better integrated navigation options
  • Add live updates
  • Have a more clear interface by putting community-defined 'related links' into a collapsible panel

This last change is about links displayed on top of the RecentChanges (see how they look like on your wiki). We do that change because we have discovered that those links are not that much used. Also, they sometimes take a lot of space on small screens. To help people to focus on recent changes patrolling, we will hide those links, with an option to show them. We have created some examples to show you how it will look like. If you like to see those links all the time, you will have to click on the link to show them and they will remain open. We welcome your feedback about this change.

Most of this information was already introduced in the Collaboration monthly newsletter. Please subscribe to get regular updates!

You can ping me if you have questions.

All the best --, Trizek (WMF) (talk) 10:27, 6 July 2017 (UTC)

Reply to "Some updates about Recent Changes pages"
Dvorapa (talkcontribs)

In outdated strings to translate here on for Czech language there are still messages like Help:Links or Help:Preferences. Whatever I change them to or however I edit them, they are still listed as outdated and I can not make them OK. How are we supposed to change them in order not to be outdated anymore?

Ciencia Al Poder (talkcontribs)

When editing the page directly there's a warning saying the namespace differs from the original. So basically you should leave the Help: namespace as is.

Dvorapa (talkcontribs)

My warning on edit page is "Namespace changed from the definition". This message is nonsense to me per my english understanding. But if it means something like "Namespace differs from the original", then the error message should be more clear I think.

Ciencia Al Poder (talkcontribs)

Yeah, I read the Spanish translation and it says something more similar to "Namespace differs from the original"

Dvorapa (talkcontribs)

Where can I change that nonsense text?

Dvorapa (talkcontribs)

Czech translation is similar nonsense. Just a translation of its origin

Dvorapa (talkcontribs)

I've asked on translatewiki, I hope they'll help

Reply to "Namespace changed from definition"

The Newsletter extension is now enabled in

Qgil-WMF (talkcontribs)

Hi, after a long long journey... Special:Newsletters!

The Newsletter extension is a tool to facilitate subscription and delivery of newsletters hosted on MediaWiki-based sites. You can learn more about this extension at Help:Extension:Newsletter.

Any newsletters within the scope of can be created. In previous discussions it was agreed to only allow administrators to create newsletters. Once a newsletter is created, their publishers can announce new issues at will without requiring administrators anymore.

If you want to create a newsletter and you need an administrator to do it, just reply here specifying:

  • the name of the newsletter
  • a short description, allowing this newsletter to be recognized in a list with all the newsletters
  • a wiki page for its home
  • at least one publisher ( username)

If you want to report problems, request features, or get involved in the project, please check MediaWiki-extensions-Newsletter in Phabricator.

IKhitron (talkcontribs)

Hello. Congratulations, great job! As always, hewiki can help in finding rtl errors. And there always are rtl errors. So, we'd like to create a newsletter, meanwhile in mediawiki, and one day it will move to hewiki, when available. The notifications will be redirections to upcoming sections in he:project:news. So all notificatons will come from mediawiki to hewiki using Echo interwiki system, and will appear on rtl to subscribers. I created this news project, and publish about 80% of messages there for users, every time there is some interesting new mediawiki engine feature, for example. So naturally, I'll write the notifications. So, could you please create a new newsletter: 1. הפומפיה (the grater in hebrew) 2. עדכונים שוטפים על ידיעות חדשות בדף ויקיפדיה:חדשות (ongoing updates about new issues on wikipedia:news) 3. Sorry, what do you mean in home page? I should create something here in mediawiki? In which namespace? 4. User:IKhitron Thank you very much.

Qgil-WMF (talkcontribs)

Hi @IKhitron, thank you for your interest. There is one problem: interwiki prefixes like he:project:news are not supported yet (see phab:T174664). I recommend you to wait until that is solved. Also, the idea of "migrating later to Hebrew Wikipedia" is not clear either (phab:T110645 is where we discuss interwiki / multiwiki support). Would it be an option for you to start testing in I'm sorry for not having better answers currently.

IKhitron (talkcontribs)

Hello, Qgil-WMF. I think I did not explain myself well. I do not talk about an hewiki newsletter, but a mediawiki one. Local. It's issues will be wikilinks to hewiki in regular wikicode, that's all. There isn't something that doesn't allow to create it just now. And I did not talk about technical migration. One day when the extension will be deployed on other wikis, we'll ask the subscribers to subscribe once more, locally. So, could you do this now, please? Thank you very much.

N3 Thanks for phab link, I don't need it, because I don't need interwiki service, as I said.

Qgil-WMF (talkcontribs)

> It's issues will be wikilinks to hewiki in regular wikicode

This is not supported now. The extension will not accept a syntax like "he:project:news". This is exactly what phab:T174664 is about.

IKhitron (talkcontribs)

Maybe I did not understand, Qgil-WMF. But I still think we are talking about different things. I'm not talking about interwiki link in notification - there will be regular mw:homepageofnewsletter#something link there. If somebody clicks and comes to this page, they'll find the interwikilink there, in the text (of the issue), on regular wikitext content model page. Thank you.

Qgil-WMF (talkcontribs)

Alright, sorry, now I understand. The main page is required. It is where you explain what the newsletter is about so users can decide whether they are interested in subscribing, and any other details you want to add. Newsletter issues point to pages, and they don't take into account #sections. In wikitext pages sections are pure representational, and things are prone to go wrong if someone edits the sections (as opposed to renaming pages, which by default leaves redirects). A simple option would be to use Flow topics for new announcements, from the discussion page of the newsletter main page. Each Flow topic is a page indeed.

IKhitron (talkcontribs)

Thank you. Very well, Qgil-WMF. Looks good for me. So the main page could be the flow border, and subscribe button will be added to the description, or I need a wikitext page as the main one and flow page for issues?

Qgil-WMF (talkcontribs)

You need a main wikitext page, otherwise you will not have a discussion page to refer to.  :)

IKhitron (talkcontribs)

Great. So, I'll create a page and ask to convert its talk page to flow. So, it's the same question I asked at the beginning: In which namespace should I create the main page? I don't know this wiki structure. And "User" is not a good idea. Thank you very much.

Qgil-WMF (talkcontribs)

A page in the main namespace is ok. You will get the Flow page automatically. There is no need to request anything.

IKhitron (talkcontribs)

Thank you for your kind recomendations. Done.

Could you, please, create a new newsletter:

  1. הפומפיה
    (the grater in hebrew)
  2. עדכונים שוטפים על ידיעות חדשות בדף ויקיפדיה:חדשות
    (ongoing updates about new issues on wikipedia:news)
  3. הפומפיה
  4. User:IKhitron

Thank you very much.

Qgil-WMF (talkcontribs)

@IKhitron YesY Done Newsletter:הפומפיה

As a first publisher not involved in the development or testing of the Newsletter extension, your feedback is highly appreciated.

IKhitron (talkcontribs)

Thank you very much.

Sorry for the time I spent you.

Three points:

  • I think you can make a summary of our conversation (flow, main namespace and much more) and put it on the project page, so these questions will not be asked every time.
  • You thought I'm talking about interwiki newsletter at the beginning. I didn't. I didn't even think it's possible, otherwise you would not deploy this extension on any wiki, even here on mediawiki. Just once on meta, and it could be enough for all wikis.
  • But all this made me find a bug in Flow: it does not work well on Timeless. So it's an adventage. :-)

Thank you again.

MarcoAurelio (talkcontribs)

Congratulations to all those who made Newsletter possible. Looking forward testing and trying to better the extension. Regards.

Reply to "The Newsletter extension is now enabled in"
Nemo bis (talkcontribs)

We've been using the translate extension for a while now on this wiki, which definitely needs more multilingual support, so I think we should greatly expand its usage, by deciding where to start. The aim is to reach more MediaWiki users (rather than developers); benefits have to be balanced by costs, and in some areas the extension is easier to use than in others (or even easier than continuing with {{Languages}} and so on). Some ideas:

  1. Most viewed pages: I've done some, but they often need an update/revamp in English too.
  2. Configuration variables: hundreds of them have the corresponding Manual: page translated and can be assumed of interest. The pages use a common pattern and most important info is in the template, so – in principle – translations can be moved to the new system (semi)automatically.
  3. Help pages would be the most useful in theory, but those we have here are very specific and limited. It makes no sense to translate most of them, because the "real help pages" and their translations are in fact on Meta or scattered among Wikipedias (or other Wikimedia projects.
Leucosticte (talkcontribs)

About #3: What about the users of non-WMF wikis? Wouldn't translated help pages be helpful for them?

Nemo bis (talkcontribs)

Yes but one should first move the up-to-date and complete English pages here from Meta and other wikis (finding a solution for licensing problems and also convincing them not to keep outdated copies around), which is not going to happen.

Leucosticte (talkcontribs)

You may be right. I think it was a mistake to insist on public domain Help pages, and that we are reaping the harmful consequences of that decision. But to fix it would require acknowledging that a mistake was made, and sometimes people are resistant to that.

HappyDog (talkcontribs)

I disagree - PD help pages are a very good idea. However, it is a mistake to think they will be of any real use until we provide a workable method of distibuting them. I think it is a fairly safe assumption that if there was an easy way to import the default help pages into your local wiki, in the appropriate language(s), then that would be sufficient encouragement for the current pages to be tidied up (if, indeed, that is necessary - I haven't looked at them for a while) and, more importantly, widely translated.

I don't think think the solution here is to import existing non-English help content from elsewhere, or to try and encourage a translation drive for the help content, without having an export process in place.

Nemo bis (talkcontribs)

Seems we can all agree on this, so we're left with #1 and #2 for now.

Nemo bis (talkcontribs)

So... no interest/ideas/suggestions on those two points (priority pages and manual pages)?

Leucosticte (talkcontribs)

I'm afraid translation isn't my area of expertise. It's been noted that "English is the working language of the Internet", though, and my attitude toward those who seek to administer websites tends to be, learn English or GTFO. But you seem to be on the right track as far as prioritization is concerned; focus on the most-viewed pages first.

Nemo bis (talkcontribs)

Configuration settings summaries have over 23 thousands translations for the Configure extension; it would be nice to find a way to use them on wiki. I've opened bugzilla:43380 to see what's technically feasible.

Qgil-WMF (talkcontribs)

I'm not familiar with the Translate extension, although I'm looking for an excuse to finally give it a try.  :) Is it possible to promote a set of pages where translation is prioritized? Using a category, for instance.

Trying to translate the whole is pointless and actually counterproductive, but there is a bunch of pages that would really welcome more translations, and a formal request to be translated. It would be useful for the project and for translator to identify those, and if possible get those nice stats telling that Japanese is 100% up to date, Italian is 83%, Arabic is 12% and so on.

There are two types of translatable pages based on motivation:

  1. Promotion: local languages are good to reach out to new users and contributors. Homepage, the hubs, How to contribute, the local Groups (mainly in their respective native languages)...
  2. Support: essential pages for users of MediaWiki and our technical infrastructure. The most basic and required pages of the manual, how bugzilla works how to get developer access...

Maybe it's worth having both translatable categories separate? Maybe some languages make total sense for Promotion but less so for Support (no specific examples, although I can imagine Indic or Latin languages speakers needing those translations more for Promotion than Support, since the average sysadmin / developer of those languages is used to deal with English documentation).

It is clear that the deeper you get into both categories the clearer is the need to manage some English, at least in our current reality. We could probably define a VERY LIMITED set of pages translatable here and now in both categories and then consider the addition of new pages based on actual need.

And I agree with Nemo that those pages need a review in the canonical English version before making big calls for translation. But maybe this is a feature? It forces us to go through identified pages, mark them as translatable progressively and giving more time to translators to deal with new content. For instance, we could start focusing in How to contribute and Help:Formatting, and do a first test with these pages.

This post was posted by Qgil-WMF, but signed as Qgil.

Nemo bis (talkcontribs)

Yes, it's possible to "categorize" requests for translations, see for instance m:Special:AggregateGroups. It's also possible to define priority languages and even to disable translations in some languages, but this makes little sense on this wiki. In general, people will always translate what they're interested in, not what you'd most like to have translated, therefore if something would use translations it should be translatable, while for focused translation recruitement you can have a specific priority group of translatable pages.

In short, I don't like that "very limited" in all caps, unless you consider (like me) that e.g. 600 configuration settings pages (out of ten thousands content pages) would be a "very limited" set of translatable pages. ;-) Specific pages ready for translation should made translatable immediately: I'll comment on those two on talk.

Qgil-WMF (talkcontribs)

Ok, got your point. I just find useful to have a set of pages identified for volunteer translators without own itch or agenda. "I want to start translating MediaWiki content to Catalan: where should I start? Thank you."

This post was posted by Qgil-WMF, but signed as Qgil.

Nemo bis (talkcontribs) was updated; the Help: and Manual: pages in the top-1000 list should probably be made translatable. Who's willing to help me?

Qgil-WMF (talkcontribs)

Thank you for this useful link!

This post was posted by Qgil-WMF, but signed as Qgil.

This comment was hidden by Elitre (WMF) (history)
Vetonhaxhi (talkcontribs)

DJVU files not displaying after upload ? (talkcontribs)

djvu files not display

This comment was hidden by Seb35 (history)
Reply to "Translate extension"
Dvorapa (talkcontribs)

Please mark Manual:Pywikibot/Installation, Manual:Pywikibot/Version table and Manual:Pywikibot/i18n for translation

Jdforrester (WMF) (talkcontribs)

Done. Note that I had to drop some of the comments from the middle one as you can't re-use translation marker numbers.

SteveStx (talkcontribs)

Hello everyone!

Since a short time, i've the phenomen that the editor inserts [[File:xxxx.filetype]] instead of [[Datei:xxxx.filetype]].

Since my wiki is formerly used in German languge, this is a problem, so most of the images are only shown as links, which are not working.

My Questions:

1) Where can i set the inser languge of the editor to makje him always produce "Datei:" links?

2) Can i set the Wiki to accept both "File:" and "Datei:" as Image-Links?



Reply to "Image insert mixed Datei: and File:"

Beta feature: advanced filters and more options for Watchlists, starting September 5

Trizek (WMF) (talkcontribs)


As you may already know, the Global Collaboration team has created a Beta feature. This feature is on your wiki since few months: "New filters for edit review". You can activate it in your Beta preferences.

What is this feature again?

This feature improves Special:RecentChanges and Special:RecentChangesLinked. It adds new features that ease vandalism tracking and support of newcomers:

  • Filtering - filter recent changes with easy-to-use and powerful filters combinations, including filtering by namespace or tagged edits.
  • Highlighting - add a colored background to the different changes you are monitoring. It helps quick identification of changes that matter to you.
  • Bookmarking to keep your favorite configurations of filters ready to be used.
  • Quality and Intent Filters - those filters use ORES predictions. They identify real vandalism or good faith intent contributions that need help.

You can know more about this project by visiting the quick tour help page.

What's new?

On September 5, the Beta feature will have a new option. Watchlists will have all new features available on Recent Changes Beta now.

If you have already activated the Beta feature "New filters for edit review", you have no action to take. If you haven't activated the Beta feature "New filters for edit review" and you want to try the filters on Watchlists, please go to your Beta preferences on September 6. It will not be possible to try the filters only on Recent Changes or only on Watchlist.

Please also note that later in September, some changes will happen on Recent Changes. We will release some features at the moment available in Beta as default features. This will impact all users, but we will provide an option to opt-out. I'll recontact you with a more precise schedule and all the details very soon.

You can ping me if you have questions.

Jnanaranjan sahu (talkcontribs)

@Trizek (WMF) Is there any option to disable it by default or for any user? Some of the users don't like it as it has been activated for all.

Trizek (WMF) (talkcontribs)

You can opt out of the new filters by going to the "Opt out" section at the bottom of Special:Preferences#mw-prefsection-rc on the wikis you are active on. How ever, like any new change, you should give a chance to that new interface: maybe you will get used to it and find the new features we have added very useful.

Jnanaranjan sahu (talkcontribs)

Thank You @Trizek (WMF). I am already using it since many days, but some user are not interested. Though I have suggested them to use the new feature but they are not convenient for them due to slow internet or something.

GeoffreyT2000 (talkcontribs)

In MediaWiki 1.29, there is a new feature called user group expiry. Shouldn't the page Manual:User groups table then be updated? The previous schema summary should say {{TNT|MW version|version=1.22|version2=1.28}} and the current one (with a new column named "ug_expiry") should say {{TNT|MW version|version=1.29|comment=and after}}. The "fields" section should also be updated to include the new feature.

Legoktm (talkcontribs)

Please update it since you know what changed and when :)

This comment was hidden by (history)
GeoffreyT2000 (talkcontribs)

I gone ahead and made the changes myself.

Seb35 (talkcontribs)

And marked for translation. Thanks for the updates!

DA95 (talkcontribs)

hi everyone

My problem: I wanted to upload a picture (png.) from my computer into my wikipage.

Everything looks good until i get this:

We could not determine whether this file is suitable for Wikimedia Commons. Please only upload photos that you took yourself with your camera, or see what else is acceptable. See the guide to make sure the file is acceptable and learn how to upload it on Wikimedia Commons.

I've got the permission to use this picture, it shows nothing sexualthere is nothing violent or anything at all in it. What should i do?


Ciencia Al Poder (talkcontribs)

Looking at task T146938, it looks like a filter used to prevent newbie users from uploading files to commons directly from other wikis (from the visual editor of a wiki different from commons). You should be able to upload it from commons: and then link to it from your page.

Reply to "unable to put a picture into my wiki"