Project:Current issues

Jump to navigation Jump to search

About this board

This page is only for discussing issues related to site. To get help with MediaWiki software, ask on Project:Support desk.
Dinoguy1000 (talkcontribs)


Add signage to old TPG team pages and subpages to indicate deprecation

MBinder (WMF) (talkcontribs)

The Technical Program Management Team would like to append a hatnote and historical tag to 118 Team Practices Group pages, as part of deprecating them so that visitors don't mistakenly assume they can still get TPG support (see: I've been investigating AutoWikiBrowser, but I'm a little nervous about using a batch-editing tool when I might break something. Lego suggested I post here as a possible alternative to AWB, where someone might volunteer an existing bot and I can forgo the overkill of creating a new one.

The list of pages:

The hatnote: "The Team Practices Group (TPG) was dissolved in 2017. Any previously TPG-related support is no longer available for request."

This would be followed by

Anyone willing to help me resolve this? :)

Reply to "Add signage to old TPG team pages and subpages to indicate deprecation"

process for deletion of translations

Bdijkstra (talkcontribs)
Ciencia Al Poder (talkcontribs)

Project:Current issues is the best place for this!

Bdijkstra (talkcontribs)
Ciencia Al Poder (talkcontribs)

Done, although I'm not sure that was necessary.

Bdijkstra (talkcontribs)

Thanks. A link to the page appeared in the "Other languages" bar, which was misleading since it was absolutely useless in its state (2 words translated). I suppose deletion was unnecessary if there is a way to hide the translation until it is at least somewhat useful. Is there?

GZWDer (talkcontribs)
MarkAHershberger (talkcontribs)

Done. But I think this should have had some more discussion.

Christoph Jauera (WMDE) (talkcontribs)

Thanks for that, having these page semi-protect is definitely a must.

Jdforrester (WMF) (talkcontribs)

Why is the code written that way? That seems like a massive architectural mistake. Anything trusted even within the Wikimedia cluster like that should be in the MediaWiki namespace at least (and probably locked down to be JSON or whatever content model so only technical admins can edit them).

Christoph Jauera (WMDE) (talkcontribs)

Since the FileImporter replaces/improves tools that the communities used for getting the job done, one very successful tool among those ( the Commonshelper ) was the gauge for the stuff we wanted to achieve with the FileImporter. The config structure and 'files' from that tool were used to have a good starting point for the changes made by the importer.

The relatively simple structure gives an easy way to maintain these by the communities and we see that more as a feature.

Jdforrester (WMF) (talkcontribs)

A gadget having major security holes is a problem, not an excuse to follow it. :-(

MarkAHershberger (talkcontribs)

It seems like we should have some documented guidance for this sort of thing.

Bdijkstra (talkcontribs)

Dharam salvi is adding personal details in various places. Please undo, hide, and perhaps block.

Honischboy (talkcontribs)

It looks like a coyright violation

Jdforrester (WMF) (talkcontribs)
Nemo bis (talkcontribs)

Manual:Installation guide has one section with a 400 words summary, but then links to a "Main installation guide" composed of 4+4 more pages. None of these pages is translatable. Can we consolidate truly important information and make it translatable? Currently one is supposed to find the following logical steps.

  1. Download
  2. Requirements
  3. The actual installation
  4. Misc troubleshooting and alternatives if something went wrong
  5. Configuration
  6. Maintenance
  7. Informative material

The pages in bold are part of the official Template:InstallationNav (which complements Template:MediaWiki Introduction): they are supposed to be the official path and need special care and coordination.

Nemo bis (talkcontribs)
Nemo bis (talkcontribs)

I made Manual:LocalSettings.php translatable and expanded Manual:System administration by merging Manual:Configuration.

  • Manual:System administration could be useful if it becomes a reasonable index/step by step guide/tutoring of the really important pages in Category:MediaWiki for site admins (allowing to remove respective information from the general installation manual), but I'm not sure of its current role.
  • Manual:LocalSettings.php is very visited, but it's quite a mess. I doubt it kept anywhere close up to date, is it currently making a good service to users?
Ciencia Al Poder (talkcontribs)

I wonder what's the purpose of making Manual:LocalSettings.php translatable if you doubt about the usefulness of that page or if you plan/propose to improve/restructure it.

Nemo bis (talkcontribs)

The page is vastly correct and the strings contained in it look rather stable, so it's ok to translate it. It is my impression that some consolidation will be needed for that page (reducing total amount of text around), but not a rewriting.

Nemo bis (talkcontribs)

I've tried to make the essential stuff transcludable, and I've trimmed some more pages.

IMHO the direction is rather clear:

  • always defer to other sites for guides on how to set up PHP etc.;
  • keep all the steps internal to MediaWiki (like installer, config script, LocalSettings.php) in their own, shared manual pages;
  • in all the setup-specific pages, just transclude the former and maintain only:
    • information on packages available and how to use them (debatable, should be on their sites whenever possibles),
    • OS-specific instructions which can't be found anywhere else, like specific paths to put in MediaWiki config or RAM/suhosin requirements and the like. (talkcontribs)

Please, can someone give consideration to Raspberry PI 3, Raspbian GNU/Linux 9, LAMP. Where due to some GNU license issue, mySQL redirects to MariaDB. Need to know how to get superuser on phpMyAdmin (the commands given are for mySQL, and are not the right format for MariaDB. There is no password for root initially for MariaDB, but no direct relationship (it seems) between MariaDB and phpMyAdmin. Might be proven wrong here once I start creating databases in MariaDB.

However this really good documentation, it just doesn't go far enough. Thanks.

Ciencia Al Poder (talkcontribs)

Looks like your question is about MariaDB/phpMyadmin, not MediaWiki. Have you tried asking on a mariaDB forum or stackoverflow?

Reply to "Installation guide consolidation"

Next version of mw missing from navigation (1.31)

5 (talkcontribs)

Go to MediaWiki 1.30, then check the navigation on the right, 1.30 and 1.32 is there, but 1.31 is missing. How am I supposed to easily get to the soon to be released next version without manually searching for it?

Jdforrester (WMF) (talkcontribs)

You aren't "supposed" to get unreleased versions. If they're not released yet, it's because they're not thought to be ready yet.

Ciencia Al Poder (talkcontribs)

Jdforrester: That's nonsense. MediaWiki 1.31 is a Release Candidate. How can people test it to see if there are bugs previous to formal release if it isn't made available?

Also, that's not the object of the question. The box at the top-rigt of the page contains the following items:

The problem is that MediaWiki 1.31 is not appearing there (but 1.32 is!).

Jdforrester (WMF) (talkcontribs)
That's nonsense. MediaWiki 1.31 is a Release Candidate. How can people test it to see if there are bugs previous to formal release if it isn't made available?

Regular end-users are absolutely not the right audience for Release Candidate software. The people looking to test it out are likely expert MediaWiki sysadmins, developers, and others who follow the mediawiki-l mailing list, not the more normal kinds of sysadmins who aren't necessarily expert in how labyrinthine bugs in MediaWiki can be explored.

The problem is that MediaWiki 1.31 is not appearing there (but 1.32 is!).

Wait a week or whatever and it'll appear when it's released. I don't see this as a problem. When 121… asked "How am I supposed to easily get to the soon to be released next version without manually searching for it?", and answer is "you aren't".

(If instead you want to debate having a link to the bleeding-edge master in the list, that's a fine discussion point, but not really the question asked.) (talkcontribs)

If the alpha version is there, the release candidate clearly should be too. It's simply easy navigation between relevant versions.

As for why should someone have easy access, maybe they want to easily see what is the upcoming version either because they are looking to update when it comes out, or are a user looking at the new features for when the wiki they use is updated?

Reply to "Next version of mw missing from navigation (1.31)"
Incnis Mrsi (talkcontribs)
Wargo (talkcontribs)

Topics can be categorized but only in topic Summary.

Reply to "{{Edit request}} and Flow"
GZWDer (talkcontribs)

It seems this page have some deleted pre-2013 edits. Can someone restore them?

Jdforrester (WMF) (talkcontribs)

@Jeroen De Dauw did. I can restore them, but maybe he can explain why he deleted it in the first place?

Jeroen De Dauw (talkcontribs)

I generally don't remember the reasons for edits I made 5+ years ago ;) Why is this even a thing to care about?

Jdforrester (WMF) (talkcontribs)