Project:Village Pump/Flow/2023/11

This page is only for discussing issues related to MediaWiki.org website.

To get help with MediaWiki software, ask on Project:Support desk.

cant create page

New here. why can't I create webpage "comunicação não violenta" in portuguese brazil? says its not allowed edition for new users Afbdreds2 (talk) 02:16, 9 November 2023 (UTC)

Because you're on entirely the wrong website. This website is for documentation of the software, not other topics. See Project:Scope * Pppery * _{it has begun} 02:17, 9 November 2023 (UTC)

What is a private paste ?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Look on page Login_problems just before section For_developers, sentence 'you need to use a private paste'.

question 1: What is a private paste ?

Link leads to https://phabricator.wikimedia.org/paste/edit/form/36/ which shows following restrictions although I am logged in Phabricator) :

Access Denied: Restricted Edit Configuration
You do not have permission to view this object.
Users with the "Can View" capability:

    This object has a custom policy controlling who can take this action.

Question 2: Why are these restrictions for ? Who can use this function ? Where to request these rights ? Are they useful for 'normal' users ?

Thanks --Christian 🇫🇷 FR (talk) 11:12, 12 November 2023 (UTC)

People (developers) who signed an NDA with Wikimedia. The data described in that section is privileged and thus needs to be stored privileged. When handled incorrectly, it could allow a third person to impersonate another user on a Wikimedia website. That entire section is only for experienced MediaWiki developers. —TheDJ (Not WMF) (talk • contribs) 15:04, 12 November 2023 (UTC)

Ok, but it is in section for 'users' and not for 'developpers' so I have only added the restriction. Thanks. -- Christian 🇫🇷 FR (talk) 19:47, 12 November 2023 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

New option for local development

Hi all, I'd like to share a new way to set up a local development environment for MediaWiki: Local development quickstart.

The purpose of the quickstart guide is to provide the shortest, simplest path to running MediaWiki locally for people who don't want to use Docker. The goal is to eventually replace the Local installation section on How to become a MediaWiki hacker with a link to the quickstart guide. For more background information, see T347347 on Phabricator.

If you're interested in helping test the quickstart guide, please share your feedback on the talk page or on the Phabricator task. For feedback about MediaWiki development environments in general, I've started a comparison of available options and key pages on Project:Development environments. APaskulin (WMF) (talk) 23:08, 21 November 2023 (UTC)

Thanks to @Timo Tijhof (WMF) for all his help with this project! I've documented his excellent copy-to-clipboard gadget on Project:Code samples. APaskulin (WMF) (talk) 23:45, 21 November 2023 (UTC)

This is looking REALLY good. Very readable. Hope to test it soon. —TheDJ (Not WMF) (talk • contribs) 09:52, 23 November 2023 (UTC)

Update from Fontawesome 5 to 6 Pro

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hello everyone, I took over a project from a colleague this week and have the following problem when updating from Fontawesome 5 to Fontawesome 6. I would like to add that I am a complete newcomer to the Mediawiki world. Since this is a local environment, I don't have an official website for you. Key data:

MediaWiki 1.39.5 (e53adb1)

06:49, 7 Apr 2022

PHP 8.1.25 (fpm-fcgi)

MariaDB 10.5.19-MariaDB-0+deb11u2

ICU 67.1

Debian Distribution

Nginx

We use our own icons, which are integrated via gitlab. If I now install Fontawesome 6 Pro and integrate it into my main.scss:

$fontAwesomeFont:'Font Awesome 6 Pro';

@import 'variables';

@import 'sp-sass/scss/style';

@import 'fontawesome-pro/scss/brands';

@import 'fontawesome-pro/scss/duotone';

@import 'fontawesome-pro/scss/light';

@import 'fontawesome-pro/scss/regular';

@import 'fontawesome-pro/scss/solid';

@import 'fontawesome-pro/scss/v4-shims';

@import 'fontawesome-pro/scss/fontawesome';

@import 'glyphicons/glyphicons/glyphicons';

@import 'glyphicons/halflings/glyphicons-halflings';

@import 'spicons';

@import 'modules/sidebar';

@import 'wiki';

@import 'modules/content';

@import 'modules/searchForm';

and recompile the assets, the custom icons are no longer displayed. I found a place in the source code that causes problems: .fa-slash-back::before If I delete this, everything works. I have no idea why this is happening and hope you can help me. I hope I could give you enough information. Michael brilz (talk) 10:12, 22 November 2023 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Convert Style.css to Scss

Hello everyone, I am new to the world of MediaWiki and have a question about SCSS. So far I have only been able to find limited information on this topic. My specific question is: Is it possible to convert my Styles.css template into an SCSS file? If so, what is the best way to do this?

Many thanks in advance for your help! Michael brilz (talk) 09:06, 23 November 2023 (UTC)

Since all CSS is SCSS, you can just save your CSS file as a .scss file and it will be SCSS. Is there a certain application you have in mind? I'm struggling to understand why this would be helpful, but I'm not a very smart person. —Justin (koavf)❤T☮C☺M☯ 09:37, 23 November 2023 (UTC)

If you weren't smart, you wouldn't be here :) The point is. We have a very large collection of CSS code and templates on our wiki page under Templates:Style.css, Templates:Styles-min769.css etc.. My colleague thinks that the page would be faster if the whole thing was implemented with Scss or Sass. As I am a newcomer to Mediawiki and the world of CSS preprocessors, I have to familiarise myself first. Michael brilz (talk) 09:57, 23 November 2023 (UTC)

This is another not-so-great answer, but you can look thru tickets at Phabricator such as those found here: https://phabricator.wikimedia.org/search/query/ktexKDhOVZs1/#R or here: https://phabricator.wikimedia.org/search/query/srWzSOQOZOnX/#R or here: https://phabricator.wikimedia.org/search/query/pAisUpvFM8MG/#R to get an idea of what kind of discussion has occurred with using precompilers and which requests are open. That may help give you some understanding, in addition to what I hope is a more instructive answer from someone else. —Justin (koavf)❤T☮C☺M☯ 10:07, 23 November 2023 (UTC)

@Koavf Thank you for your help Michael brilz (talk) 10:34, 23 November 2023 (UTC)

MediaWiki has many different css files and places where you can put/use them. Each location has their own benefits, downsides and capabilities.

Templates:Style.css Templates:Styles-min769.css. makes it sound like you might be using Extension:TemplateStyles. In that case, NO, you cannot currently use sass/scss/less for templatestyles. But when using TemplateStyles, you are also not using pure css, you are using a sanitised version of css, which adds prefixes and css property allowlists. TemplateStyles are useful for a limited amount of styling. Think of them as styles that go with a html web component or a vue component or a subset of pages.

You can't go faster than pure css as scss itself gets processed and turned INTO css. At most you might argue that it is faster for development.

Extensions CAN use less (similar to, but different from sass). When working with extensions, I advise you to read ResourceLoader/Developing with ResourceLoader. MediaWiki has its own asset manager called Resource Loader which predefines the asset bundles and allows for code segmenting and on demand loading and postprocessing of resources, that you will have to integrate with when writing extension logic. —TheDJ (Not WMF) (talk • contribs) 14:09, 23 November 2023 (UTC)

Some general principles:

1. Styling and layout for the non-content parts of pages, goes into the skin
2. Small adaptations to an existing skin go into MediaWiki:skinname.css
3. Styling for the widgets (buttons etc) can be done as a seater OOUI theme (OOUI is the widget and design set used by MediaWiki)
4. Styling for content goes either into MediaWiki:Common.css (loaded on every single page)
5. Or if it is only used by specific templates, into TemplateStyles.
6. Styling for your own customer functionality goes into Extensions.
7. Styling for custom functionality used only by some users goes into Extension:Gadgets —TheDJ (Not WMF) (talk • contribs) 14:16, 23 November 2023 (UTC)

Add 'convenient-discussions' tag

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hello! Can you please add a tag for ConvenientDiscussions so that edits are marked not in the description, but in a normal way?

Example: commons:MediaWiki:Tag-convenient-discussions, commons:MediaWiki:Tag-convenient-discussions-description. Iniquity (talk) 16:53, 27 November 2023 (UTC)

Shouldn't we just convert this wiki to DiscussionTools instead? Jdforrester (WMF) (talk) 00:24, 28 November 2023 (UTC)

This is (finally) not an either/or situation. Both CD and DT build on wikitext talk pages (with some basic requirements about the wikitext, like having proper signatures), so the preference is per-user rather than per-page (unlike LQT and Flow, which, once turned on on a page, were forced on everyone). Supporting CD doesn’t happen “instead of” converting the wiki to DT; in fact, the conversion is needed to make CD really usable here. Tacsipacsi (talk) 01:06, 28 November 2023 (UTC)

Yes, but there are already some "regular" pages here, for example Manual_talk:FAQ/ru or Talk:Reading/Web/Desktop Improvements :) But in any case, yes, this wiki will eventually need to be disconnected from the Flow. Iniquity (talk) 12:11, 28 November 2023 (UTC)

Supporting CD doesn’t happen “instead of” converting the wiki to DT; in fact, the conversion is needed to make CD really usable here.

And yet this is asking for special support for a hack that isn't the way forward? Jdforrester (WMF) (talk) 14:10, 28 November 2023 (UTC)

This is not a hack, it's just to make the tool insert normal tags, and not do it in the edit descriptions :) https://www.mediawiki.org/w/index.php?title=User_talk:Iniquity/test&diff=prev&oldid=6216920 Iniquity (talk) 14:16, 28 November 2023 (UTC)

I dont see any harm in creating a tag description for any tag people are actually using. Bawolff (talk) 03:30, 29 November 2023 (UTC)

Yes, but there are already some "regular" pages here

I know, this is why I wrote make CD really usable here and not make CD usable here. As long as this wiki is full of Flow boards, CD (and DT) is of limited – but non-zero – use.

a hack that isn't the way forward

In addition to not being a hack, why wouldn’t it be the way forward? The way forward is relying on wikitext talk pages, not forcing everyone to use DiscussionTools. The very idea behind the Talk pages project is acknowledging that people have come to rely on wikitext on talk pages and all the tools built around that, and they shouldn’t be forced into using a new tool (but rather they should have a free choice between DT and other tools). Tacsipacsi (talk) 00:55, 30 November 2023 (UTC)

I likewise see no reason not to go ahead with this - it's just a few clicks for an admin and then will work forevermore. I don't see the point myself either, but if people do then more power to them. * Pppery * _{it has begun} 01:30, 30 November 2023 (UTC)

As I understand it, this does no harm, and resolves the thread, so I've boldly created the requested pages, copying (+ `c:`) the strings from Commons over to MediaWiki:Tag-convenient-discussions-description and MediaWiki:Tag-convenient-discussions. –Quiddity (talk) 01:43, 30 November 2023 (UTC)

Thanks everyone! :) Iniquity (talk) 01:46, 30 November 2023 (UTC)

@Quiddity, can you please create 'convenient-discussions' tag here: Special:Tags? I didn't check and we forgot about it :( Iniquity (talk) 21:44, 14 December 2023 (UTC)

Done Bawolff (talk) 23:32, 14 December 2023 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.