Skin talk:Foreground

@Cavila: Is this your skin? I have noticed that there are some strings not localized in Spanish:

• "Actions" (page menu, it should be "Acciones")
• "Search" (search button, it should be "Buscar")
• "Search..." (text box, it should be "Buscar...")
• "Recent changes" (site menu, it should be "Cambios recientes")
• "Help" (site menu, it should be "Ayuda")

If you could add them or let me know how to add them that would be great. Micru (talk) 22:33, 4 August 2014 (UTC) Reply

Hiya Micru, no it isn't. Foreground is the joint creation of Garrick van Buren and Jamie Thingelstad. I don't know if and to what extent support for Spanish is handled natively by the skin. Of course, MediaWiki comes with language settings of its own (you may also want take a look at the Universal Language Selector), but I guess you already knew that.

See also GitHub, where most of the discussion about the skin seems to take place. Hope that helps! Cavila (MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7) 11:35, 5 August 2014 (UTC) Reply

Hi there

I'm using the extension "Visual Editor", and I was able to confirm operation at Vectoy skin, but I can not work with Foregroiund skin on.

According to HELP, and I tried to modify Foregroud skin, but it could not be made to correspond to the Foreground skin.

Is there any plan to correspond to "Visual Editor" in future version up of foregroud skin ?

I want to ask all means if none.

Thanks 153.177.124.178 13:47, 3 September 2014 (UTC) Reply

Hi.

I had the same issue, and it worked for me. contact me and I will send you the code if still relevant. Wess (talk) 10:21, 4 December 2014 (UTC) Reply

Thank you, Wess.

I will contact you. Papamanman2 (talk) 13:09, 7 January 2015 (UTC) Reply

@Wess Since integration with VisualEditor will more and more become an issue or better spoken a requirement it will probably be very nice if you could provide a patch at GitHub. [[kgh]] (talk) 15:49, 7 January 2015 (UTC) Reply

Thank you for your reply.

I tried again.

• Mediawiki: 1.23.7
• Foreground: Hutchy68/patch-2
• Visual Editor: 0.1

But I couldn't solve some problems.

• drop down lists(ex. Header list) are cut in the middle
• contents of save pop-up window is not displayed

I consider that Foreground css and Visual Editor css are colliding.

But I can't identify the location of the problem.

Could you please show the location of the modification?

Thank you. Papamanman2 (talk) 00:53, 11 January 2015 (UTC) Reply

I am so sorry for not seeing your comments. I would be pleased to share it on github but I need some learning for that. If you'll send me your email I will be happy to share the code (only the template php is required). Wess (talk) 19:18, 8 March 2015 (UTC) Reply

This is what I succeeded for tonight, I am not very common with Github's interface but I guess it fulfills the current need:

https://github.com/Wiki-Org/Forground-VisualEditor-patch Wess (talk) 19:55, 8 March 2015 (UTC) Reply

I am so sorry for not replied to you comment, I didn't check this board.

And thank you for your help.

I tried to apply your patch to my mediawiki(Japanese Language).

But it din't work.

Maybe the cause is not php file, but is css.

I modified skin css, and it worked well with the exception of the part.

There are still some bug, but I will wait for product version of Visual Editor.

Thank you so much. 111.89.36.155 00:29, 28 April 2015 (UTC) Reply

Hi, we have had some troubles to with getting Visual Editor to work on Foreground, The patch from Wess and setting the LocalSettings.php. (Version MW 1.25), any help would be greatly appreciated. 65.49.14.74 (talk) 18:06, 19 August 2015 (UTC) Reply

The patch was integrated in patch-7 branch: https://github.com/paladox/foreground/tree/patch-7. Also - make sure to declare the skin as VE enabled in LocalSettings (does VE works with Vector?) Wess (talk) 08:50, 24 August 2015 (UTC) Reply

Hi, I'm having multiple issues with this skin. All this these issues are for Foreground skin.

Issue 1:

I'm using Visual Editor for my skin, I do not get the Edit feature, just edit source and cannot use Visual Editor on Foreground skin.

If I switch to Monobook, I get:

Error loading data from server: 0: parsoidserver-http: HTTP: 0.

Here's my understanding of how this should have been done:

Download VisualEditor/UniversalLanguageSelector/Parsoid extensions.

Add the following lines to Local.php:

For Visual Editor:

require_once "$IP/extensions/VisualEditor/VisualEditor.php";
// Enable by default for everybody
$wgDefaultUserOptions['visualeditor-enable'] = 1;
// Don't allow users to disable it
$wgHiddenPrefs[] = 'visualeditor-enable';
// OPTIONAL: Enable VisualEditor's experimental code features
#$wgDefaultUserOptions['visualeditor-enable-experimental'] = 1;

// URL to the Parsoid instance
 // MUST NOT end in a slash due to Parsoid bug
 // Use port 8142 if you use the Debian package
 $wgVisualEditorParsoidURL = 'http://localhost:8000';

For Language Selector:

require_once "$IP/extensions/UniversalLanguageSelector/UniversalLanguageSelector.php";

For Parsoid:

wfLoadExtension( 'Parsoid' );

I have also used the Foreground Patch from: https://www.mediawiki.org/wiki/Skin%20talk%3AForeground#c-Wess-2014年12月04日T10%3A21%3A00.000Z-153.177.124.178-2014年09月03日T13%3A47%3A00.000Z

But it doesn't seem to work.

Issue 2:

I can't seem to get a Dynamic Drop Down menu/link hover with multiple submenus.

http://www.dynamicdrive.com/dynamicindex1/anylinkcss.htm (Demo #3) and under News related.

I have no clue where to start with this and would greatly appreciate the help.

Issue 3:

I can't seem to understand how to set up the SocialProfile extension.

I downloaded it, added it to extensions folder and went to LocalSettings.php and added:

require_once("$IP/extensions/SocialProfile/SocialProfile.php");

I'm using an online file manager right now and help would be greatly appreciated. LearningThis (talk) 01:33, 12 August 2015 (UTC) Reply

I updated Mediawiki 1.25 to 1.26.

But, When I displayed foreground skins, there shows some warning at the top of the display.

"style module should define its position explicitly"

Moreover, there are css or javascript trouble. I cant click menu links.

I researched the cause, and i know that as for version 1.26 custom skins needs "skin.json" which define its positions.

Is there any plan to update Foreground skin forcorresponding 1.26? Or, is there any modification to solve this problem?

Thanks. Papamanman2 (talk) 12:56, 1 December 2015 (UTC) Reply

I presume that you are using version 1.1.0 of Foreground. Try to use develop (master) and see what is happening. It will be nice if you could report back if it is working for you. [[kgh]] (talk) 22:33, 1 December 2015 (UTC) Reply

Thank you for your reply.

I tried develop version, but problem still remains.

Probably, the problem comes from the old skin format of foreground. Same problems are reported in other custom skins. [1] Papamanman2 (talk) 23:06, 1 December 2015 (UTC) Reply

Well there is an issue at GitHub now. Position is defined explicitly in the version I linked so there is some other problem. Once again an utterly poor migration guide for breaking changes. I am sorry that the trouble persists. [[kgh]] (talk) 00:21, 2 December 2015 (UTC) Reply

Thank you so much.

Ok, I understood there may be another problem upgrading from 1.25 to 1.26.

I will try again. Papamanman2 (talk) 01:22, 2 December 2015 (UTC) Reply

Keeping fingers crossed. [[kgh]] (talk) 09:13, 2 December 2015 (UTC) Reply

Could you try if this patch is working for you? [[kgh]] (talk) 16:34, 2 December 2015 (UTC) Reply

Thank you, Kghbln.

Now I downgraded to 1.25, because there were many troubles which I could not solve containing except Foreground skin for emergency.

But, in few days I will try again your patch and report the result.

So, could you please wait for a days?

Thanks. Papamanman2 (talk) 23:31, 4 December 2015 (UTC) Reply

Well this is not my patch, but I asked for help getting it. Yeah, I guess a couple of days are ok. :) Hopefully you get out of the other troubling issues, too. [[kgh]] (talk) 23:35, 4 December 2015 (UTC) Reply

I tried again, and use foreground development version which applied the patch.

The warning messages comes to be not displayed. Thank you.

But fatal bug still remains.

When user clicks the menu buttons, the pull down menu don't appear.

Is there any way to solve it ? Papamanman2 (talk) 00:44, 6 December 2015 (UTC) Reply

Hmm, thanks for testing. I am not sure what is happening. Sit tight! [[kgh]] (talk) 18:46, 8 December 2015 (UTC) Reply

@Papamanman2 could you retry from the develop branch since there have been some changes with fixes such as mw 1.26 and mw 1.25 compat fixes.

Also please try using mw 1.26 when checking out the develop branch.

Do you mind pasting the error you see either from your error log or from what you see on your display.

The error you see may help us track down and fix the problem.

Could you also upload a screenshot on when the error shows. Paladox (talk) 18:57, 8 December 2015 (UTC) Reply

Keeping fingers crossed. Does this version (develop (master)) work for you?

Edit: Oops, I did not see paladox post before. [[kgh]] (talk) 23:09, 8 December 2015 (UTC) Reply

Thank you so much, @Paladox and @Kghbln.

I tried again new develop(master) version, error message doesnt appear. but the same fatal error still remain which drop down menus do not appear when user clicks.

I could not specified the cause of this bug. Because I do not know the bug comes from upgrade itself or foreground skins. I installed many modules and modifications.

If I have vanilla environment, It will be appeared. but I only have production. environment.

So I will give up upgrade to 1.26 for the time being. When I hear that other person succeed in constructed 1.26 & foreground skin, or foreground 1.2 released, I will try again. Papamanman2 (talk) 01:37, 10 December 2015 (UTC) Reply

Well, I think it is time to look at the servers error log and see what it says the time somebody clicks something like you mentioned. I should have asked for this much earlier. So this may be related to foreground or foreground is fixed now and you have other issues that must be fixed. In either way there is not chance to find out without knowing the error. So have a look at the error log since at this point since we cannot help at all. [[kgh]] (talk) 10:12, 10 December 2015 (UTC) Reply

Vanilla it works, doesn't on production sounds like caching is the issue. Please make sure you clear the cache of whatever you are using, files, apc, db, etc. Hutchy68 (talk) 12:27, 10 December 2015 (UTC) Reply

I cleared cache, so the bug must be comes from my customization or update problem.

It may take many times to remove my bugs, But, I am saved that I know foreground(dev) it self corresponds to 1.26.

I can close this topic.

Thank you, Kghbln and Hutchy68. Papamanman2 (talk) 08:07, 11 December 2015 (UTC) Reply

No to forget Paladox. Thanks for participating and providing input as well as testing. Still I recommend to look at the server error log to tackle your issues. [[kgh]] (talk) 12:34, 11 December 2015 (UTC) Reply

if you do customisation could you paste what you have. Like eg if you customise using mediawiki: I am not sure what you call it or what foreground uses but something like mediawiki:common.css or mediawiki:common.js or mediawiki:foreground.css or mediawiki:foreground.js it may be because you have some css overriding the css in foreground. Paladox (talk) 13:22, 11 December 2015 (UTC) Reply

Also do you have a link to your website. Paladox (talk) 15:54, 11 December 2015 (UTC) Reply

Kghbln, I didnt forget the thank to Paladox. I just thank to comment by comment.

Anyway I want to thank again all people who helped me.

In the last week, I struggle to update the server from php 5.5 to HHVM.

Today, I updated 1.25 to 1.26 again. But the situation became worse.

The Screen come to be filled corrupted text. Of course skin never displayed. it may be comes from Immature configuration of HHVM.

Paladox, Yes, I customized common.css, foreground css, foreground.php. But I tried Vanilla Foreground. So the cause may be common css.

But now I still have other bugs comes from upgrade to 1.26. For example if user access to category page, server error occurs.

And sorry to tell you my web site links.

There are so many trouble with upgrading to 1.26, and the Priority of upgrading to 1.26 is not top. So I just wait for the time being, till the preparation of upgrade circumstances become enough.

Thank you. Papamanman2 (talk) 01:37, 14 December 2015 (UTC) Reply

Just for reference here is the load order of MediaWiki:Common.css/.js and Skin specific css/js

1. File .css and .js from an extension or skin
2. MediaWiki:Common.css and Common.js
3. MediaWiki:Foreground.css and Foreground.js
4. User/foreground.css and User/foreground.js (if this is enabled on your wiki)

It might help if you do a new install of MW 1.26 into a subdomain with a new database just to check your server against MW 1.26. Then you can identify if is it MW or your server.

It can also be a scripting resource time out issue so your update isn't fully completing. I run a full web server within my LAN for testing purposes. Mainly so I can check issues with PHP running in FastCGI just like the majority of shared host configurations. My first install of MW 1.26 was dying with lots of errors because the default PHP scripting timeout is set at 30 seconds. I had to up to the script time to 60 seconds and start over. I don't know anything about HHVM, but I would think they probably use the standard script timeout defaults.

You might also want to check the HTML header outputs from HHVM just to make sure the encoding is correct. Corrupted text and garbled output sounds like an encoding issue. If it is just in the page's content then a database encoding issue might be the cause.

Good luck with your upgrade. Hutchy68 (talk) 15:05, 17 December 2015 (UTC) Reply

Hi, Hutchy68.

I am so sorry for reply.

After all, I abandoned introduction of HHVM because of instability in my server, and introduced PHP7.

This was stabler rather than HHVM. I installed HHVM(dev) from source to Centos6.7. This way was so complicatied, so there was some problem in installation of HHVM. On the other hand, I installed PHP7 by yum installation.

Yesterday, I upgraded to foreground skin and MW1.26.2. Because there was some changes in PHP parameters of localsettings.php , many trouble was occured. But I could have solved almost bugs.

Thank you! Papamanman2 (talk) 05:43, 5 May 2016 (UTC) Reply

Glad to read that it is now working for you! Since PHP 5.5 or 5.6 I do not see a reason for utilizing HHVM in standard situations since the cost as described by you seems to outweigh the benefit if there is one. However, that's another story. [[kgh]] (talk) 08:17, 5 May 2016 (UTC) Reply

MediaWiki 1.25.1 serves blank pages after loading this skin. Noloader (talk) 15:23, 3 July 2016 (UTC) Reply

So it seems the top level folder should be named `Foreground` rather than `foregorund-master` or `foreground`. In addition, `foreground.php` ***must*** be named `Foreground.php`.

It seems like these are changes that should already be present in the sources. Users should not have to tinker with names to make this work. Noloader (talk) 15:28, 3 July 2016 (UTC) Reply

Please update the translations (mark the translations), the link to the mailing list is incorrect in the German version. Zabien (talk) 10:23, 22 August 2016 (UTC) Reply

I guess it is quite useless to ask for this on the skin's or exension's pages since the people dealing with marking pages for translations will most likely not read this. I believe it is better to contact one of them directly to get help. Cheers [[kgh]] (talk) 14:59, 24 August 2016 (UTC) Reply

@Kghbln, you get me every time. So true. I did so now here. Thanks for that pointer. Zabien (talk) 19:22, 25 August 2016 (UTC) Reply

Yes Done Shirayuki (talk) 22:19, 25 August 2016 (UTC) Reply

Hi

With Foreground skin i can do for example :

Lear more</span>

For a clickable button in Skin Foreground How to do ?

Thanks 185.156.173.58 (talk) 10:20, 15 November 2017 (UTC) Reply

Excuse me

The code use is

<span class="label" style="padding: 0.6rem 1.2rem 0.7rem 1.2rem;
 border-radius: 4px;
 font-size: 1rem;
 line-height: 1;
 white-space: nowrap;
 cursor: default;
 color:#fbfbfb; 
 background:#3498db">En savoir plus</span>

Thanks 185.156.173.58 (talk) 10:26, 15 November 2017 (UTC) Reply

Sorry i cannot put the code. Thanks 185.156.173.58 (talk) 10:28, 15 November 2017 (UTC) Reply

Typ this. Cheers [[kgh]] (talk) 14:03, 15 November 2017 (UTC) Reply

How use the SCSS Variables for <blockquote> with Foreground ?

Example : for Foundation 4

/* We use these to style blockquotes */
$blockquote-font-color:lighten($header-font-color,30%);
$blockquote-padding:em-calc(920019);
$blockquote-border:1pxsolid#ddd;
$blockquote-cite-font-size:em-calc(13);
$blockquote-cite-font-color:lighten($header-font-color,20%);
$blockquote-cite-link-color:$blockquote-cite-font-color;

I use MediaWiki version 1.27.3, Foreground 1.2.0. and in LocalSettings.php

# HTML Autorisation du code html avec balise <html>...</html>
## Restreindre aux utilisateurs de confiance
$wgRawHtml = true;

Thanks 194.187.249.30 (talk) 22:20, 28 November 2017 (UTC) Reply

Hmm, I think you misunderstand the difference between SCSS and CSS perhaps. SCSS requires a compiler and some other things. Foreround doesn't have an on the fly SCSS preprocessor to create CSS. You must change the CSS or override it in `MediaWiki:Foreground.css` for changes in the <blockquote> styling. Hutchy68 (talk) 00:32, 20 December 2017 (UTC) Reply

Hi!

I'm using MW 1.29.2, SMW 2.5.5 and Foreground 2.0 (have the same problem with FG 1.2) - the small icons are appearing as small square boxes, not showing the small images on the dropdown menus. It seems like letters and numbers inside those squares (FO 85, FO BF, FO DO, FI 28).

Any ideas?

Regards, Pål 51.175.121.98 (talk) 21:47, 6 December 2017 (UTC) Reply

Looks like you ran into the issue covered here (Icons Are Broken) [[kgh]] (talk) 23:16, 6 December 2017 (UTC) Reply

Hi I’m Joe Rossi 2607:FB90:511C:D5F0:E8A0:D7B5:163:2B2F (talk) 05:02, 7 December 2017 (UTC) Reply

Thanks! I tried to add .htaccess with different suggested content, but with no luck. Then I tried the Tweeki-skin and when using that skin, the icons are not broken. 51.175.121.98 (talk) 11:42, 8 December 2017 (UTC) Reply

No idea what is happening. Probably time to post to the mailing list referring to this thread. [[kgh]] (talk) 14:02, 8 December 2017 (UTC) Reply

Yes, please join and post to the mail list. A link to the site? Even if you don't have Foreground as default, just make sure it is installed. Thanks. Hutchy68 (talk) 00:14, 20 December 2017 (UTC) Reply

Please,

When will release the next version stable.

Thanks 77.154.204.244 (talk) 16:47, 8 December 2017 (UTC) Reply

I am using 2.1.0-alpha in production on two wiki for half a year now without issues relating to stability. Indeed the official release could be done. I always wanted to propose some CSS changes. Need to do this sooner than later. [[kgh]] (talk) 16:51, 8 December 2017 (UTC) Reply

Yes, it is overdue. Have some issues to address and I need to create a RFC on dropping IE 8 support completely. Hutchy68 (talk) 00:35, 20 December 2017 (UTC) Reply

Is it possible to keep the searchfield in the header, even on small screens? In the basic settings the searchfield is placed in the menu, which can be reached through the hamburger icon. I think it would be more useful for me, if it is placed between sitelogo and hamburger-icon. Is there any way to do this? Bingenberger (talk) 19:05, 4 January 2018 (UTC) Reply

I do not think so but it is probably worth trying to ask via the mailing list. [[kgh]] (talk) 11:13, 6 January 2018 (UTC) Reply

hi,

i'm not seeing my logo on upper-left, that's visible with other skins.

How to fix?

thx Johnywhy (talk) 23:27, 21 January 2018 (UTC) Reply

Hi, how can I change the font and size of the content? I tried to add something to MediaWiki:Common.css following these instructions Project:Support desk/Flow/2013/12#h-[RESOLVED]_How_to_change_my_Wiki_font_size?-2013年12月16日T06:07:00.000Z but it didn't work. Also, is it normal that I can't find MediaWiki:Foreground.css? Thank you! 70.79.57.220 (talk) 03:39, 2 April 2018 (UTC) Reply

The two icons are covered by this skin (icons of echo extension), notifications and messages, those two icons are just fine on vector skin, plus this skin doesn't fully support rtl language 2001:8F8:1E23:1DCA:381A:B122:270A:4DD9 (talk) 21:09, 2 August 2020 (UTC) Reply

there is another issue with hidden-catlinks, always showing, 2001:8F8:1E23:DE9:918:3F3C:9736:5CAB (talk) 08:04, 9 August 2020 (UTC) Reply

I'm trying to make Foreground available in a Mediawiki 1.34.4 installation. Foreground comes from GitHub sources. However, we have to use Master because there is no REL1_34 tag (most other skins have the a REL1_34 tag). Loading the skin results in:

Fatal error: Uncaught ExtensionDependencyError: Foreground is not compatible with the current MediaWiki core (version 1.34.4), it requires: >= 1.35.0. in /var/www/html/w/includes/registration/ExtensionRegistry.php:334 Stack trace:
#0 /var/www/html/w/includes/registration/ExtensionRegistry.php(186): ExtensionRegistry->readFromQueue(Array)
#1 /var/www/html/w/includes/Setup.php(143): ExtensionRegistry->loadFromQueue()
#2 /var/www/html/w/includes/WebStart.php(81): require_once('/var/www/html/w...')
#3 /var/www/html/w/index.php(41): require('/var/www/html/w...')
#4 {main} thrown in /var/www/html/w/includes/registration/ExtensionRegistry.php on line 334

Noloader (talk) 01:21, 13 December 2020 (UTC) Reply

Check out version v2.3.0 to mitigate. [[kgh]] (talk) 09:30, 13 December 2020 (UTC) Reply

Thanks @Kghbln.

I'm also seeing the same problem with <tt>REL1_35</tt>:

<syntaxhighlight lang='text'>Updating /var/www/html/w/skins/Foreground/

HEAD is now at 778484f Merge pull request #384 from Hutchy68/circleci-nameLink Already up-to-date. error: pathspec 'REL1_35' did not match any file(s) known to git.</syntaxhighlight>

Maybe the Foreground skin can add expected tags? 71.179.5.32 (talk) 22:38, 16 December 2020 (UTC) Reply

I do not really think that REL1_35 is an expected tag. This is for extensions and skins of WMF only. There are extensions around that have REL_35 but will definitively not work for the branch. To my experience it is always best to follow the strategy of the programmer. [[kgh]] (talk) 10:25, 17 December 2020 (UTC) Reply

I feel really ignorant but I have tried everything I know to do to change the font for the Actions button. Can someone please share with me the CSS to style the Actions button? Thank you in advance. LeeMChildress (talk) 18:19, 28 February 2021 (UTC) Reply

Something like this "MediaWiki:Foreground.css" should work:

a#actions-button {
 color: blue;
 background: red;
}

and

.f-dropdown li a {
 color: blue;
 background: red;
}

and

ul#actions.f-dropdown {
 background: red;
}

Change colors as required. Not that you also will have to manipulate the pseudo classes like "hover", "active", etc. [[kgh]] (talk) 22:26, 28 February 2021 (UTC) Reply

Hi, I'm running both Echo and Flow in my 1.34.x MW site using Foreground v2.3.0.

By default Foreground places the Echo and Flow Notification and Alert icons below the "navwrapper" div in a separate "echo-notifications" div as follows:

!-- If user is logged in output echo location -->
<div id="echo-notifications">
<div id="echo-notifications-alerts"></div>
<div id="echo-notifications-messages"></div>
<div id="echo-notifications-notice"></div>
</div>

My question is.. how can I get these items moved to the <div id="navwrapper"> at the top of the page.

In other words.. Is there a way to do this that does not involve making local edits to Foreground.skin.php [1]?

[1] https://github.com/jthingelstad/foreground/blob/develop/Foreground.skin.php Revansx (talk) 20:28, 24 March 2021 (UTC) Reply

Skin page lists "Full support of Font Awesome (v4.5)", but Font Awesome seems to be at v4.7. Not sure how complex font awesome is, but is it possible that Foreground does support Font Awesome 4.7 and the skin page is out of date? Revansx (talk) 13:57, 25 March 2021 (UTC) Reply

When I change the font used on my wiki to Times New Roman, it seems tiny in comparison with Arial... what is the best way to increase the font size slightly throughout the whole wiki? Thanks. (First posted on Project:Support desk/Flow/2021/10#h-How_to_change_font_size_throughout_wiki-2021年10月17日T21:29:00.000Z but I guess it's better to ask here seeing as I'm using the Foreground skin rather than Vector.) Jonathan3 (talk) 11:10, 18 October 2021 (UTC) Reply

I compromised and used Georgia in the end. It has serifs, which I want, but is about the same size as Arial so I won't need to adjust any CSS. Jonathan3 (talk) 10:23, 20 October 2021 (UTC) Reply

Why don't you want to use CSS ? With the /Mediawiki:Common.css pages (or /Mediawiki:Foreground.css for the skin only), it's very simple to change your site's font. Nanash (talk) 21:19, 26 September 2023 (UTC) Reply

This was two years ago now, but from memory it was easy to change the font, but really hard to change the font size. I think this was because its hard coded into the Foreground CSS in dozens of places. And because Times New Roman just seems to be smaller at the same point size compared with Arial or Georgia. It wasn't any underlying philosophy of not wanting to use CSS: it was just that I hadn't found it as easy as I had hoped. I managed it in the end by fiddling with the rem font-size of various HTML elements (making some >1 and some <1). Jonathan3 (talk) 11:53, 27 September 2023 (UTC) Reply

Ha. I don't have any problems with MediaWiki:Common.css. You really should take up CSS... It allows you to modify almost anything in any way ;)

Don't forget to format in "em" and not in "px". And try !important if not working. It works for titles, body, buttons, etc.

Eg :

/* Formatage des titres */

h1

{

font-size: 1.875em !important;

font-weight: 500;

}

h2

{

font-size: 1.5em;

}

h3

{

font-size: 1.1em;

font-weight: 600;

}

h4

{

font-size: 1.1em;

} Nanash (talk) 23:33, 27 September 2023 (UTC) Reply

Good for you. I used rem rather than em but took a similar approach. Jonathan3 (talk) 12:53, 28 September 2023 (UTC) Reply

P.S. What I had hoped for at the beginning was a way of adding one line of CSS to increase the font size site-wide to, let's say, 110%. It was a while ago now, but I think that worked for some elements and not others, which meant I had to target each element separately. Jonathan3 (talk) 13:01, 28 September 2023 (UTC) Reply

Ha ok. I get it. You can apply any attribute (font size, font family, background,...) to the whole page using the html operator (the page) * (all selectors) like this to Mediawiki:YourSkin.css :

html * {

font-size: 105% !important;

}

That said, using universal selector is not recommended. It may slow down the site, it may conflict with certain elements and values that are too high may "break" the page. Nanash (talk) 20:39, 28 September 2023 (UTC) Reply

I'm setting up a new wiki 1.38.2 & the columns have stopped working for text. Instead of the text wrapping, it creates a scroll bar to have the text content pass the column. Hopefully someone is still maintaining this skin. Christharp (talk) 17:13, 3 August 2022 (UTC) Reply

It looks like there is some development in https://phabricator.wikimedia.org/diffusion/SFOR/history/master/

but I am not sure if somebody prepares new release... Radouch (talk) 14:48, 9 July 2023 (UTC) Reply

I wanted to update my installation from MW 1.39 to 1.40 (and download the latest version of the skin).

When updating, all the thumbnails disappeared. The images were displayed "raw", without formatting.

The wikicode is correct. And when testing the installation with the Vector skin, there were no problems. It only existed with the Foreground skin. As he ignore the styling code for images.

As I want to keep this skin, I went back to the old version.

That said, one day I'll have to update my MW... Does anyone have any idea what the problem is? Nanash (talk) 21:14, 26 September 2023 (UTC) Reply

Hi ! Were you able to resolve this problem?

I have the same with MW 1_41 and Foreground.

I solved the problem temporarily with Mediawiki:Foreground.css. Momo50WM (talk) 06:55, 19 January 2024 (UTC) Reply

Hi.

No, I didn't solve the problem with foreground. So I switched to the tweeki skin, which is much more practical for my use. Nanash (talk) 00:14, 23 January 2024 (UTC) Reply

Hi,

Thanks for this great skin.

Since upgrade to MW 1.41, action button and navigation bar items are not working anymore.

Javascript console shows me this error :

La ressource à l’adresse « /mediawiki/load.php?lang=fr&modules=startup&only=scripts&raw=1&skin=foreground » a été bloquée en raison d’un type MIME (« text/html ») incorrect (X-Content-Type-Options: nosniff).

When opening the URL in Firefox, i get :

[6152c6b74483b46c7689fac2] /mediawiki/load.php?lang=fr&modules=startup&only=scripts&raw=1&skin=foreground Error: Class "ResourceLoaderSkinModule" not found

Do you have any idea ?

Thanks very much 2A01:E0A:89F:2530:D71C:C209:E4B9:8ED0 (talk) 19:57, 17 July 2024 (UTC) Reply

Sorry, was due to another extension that wasn't up to date.

Works great now ! 2A01:E0A:89F:2530:D71C:C209:E4B9:8ED0 (talk) 10:59, 18 July 2024 (UTC) Reply

I 'm using foreground (branch REL1_42) on mediawiki 1.42, with a linux apache server. Foreground is in a directory called foreground but it references fonts in a directory called Foreground. So I tried to rename the directory, which triggered an error.

I had to create a Foreground directory with an assets symlink to the foreground/assets directory, so that icons would display...

There might be a correction somewhere to correct that behavior...

Thanks for everything Loizbec (talk) 09:34, 2 October 2024 (UTC) Reply

@Loizbec: The directory should be called Foreground. What error do you get when you call it that? It'd be better to fix that error, rather than renaming it to foreground. Sam Wilson 11:27, 2 October 2024 (UTC) Reply

foreground configuration error

MediaWiki is unable to load the skin foreground. Please check that the skin's name is correct and all of its files are properly installed.

Details:

 Error reading /var/www/html/w/skins/foreground/skin.json. filemtime(): stat failed for /var/www/html/w/skins/foreground/skin.json.

1. 0 /var/www/html/w/includes/GlobalFunctions.php(90): ExtensionRegistry->queue()
2. 1 /var/www/html/w/LocalSettings.php(192): wfLoadSkin()
3. 2 /var/www/html/w/includes/Setup.php(215): require_once('...')
4. 3 /var/www/html/w/includes/WebStart.php(85): require_once('...')
5. 4 /var/www/html/w/index.php(50): require('...')
6. 5 {main}

 Fatal error: Error Loading extension. Unable to open file /var/www/html/w/skins/foreground/skin.json: filemtime(): stat failed for /var/www/html/w/skins/foreground/skin.json in /var/www/html/w/includes/registration/MissingExtensionException.php on line 96

Loizbec (talk) 13:37, 2 October 2024 (UTC) Reply

I'm sorry I have bothered you with that... It was my wfLoadSkin that was in lower case (it worked with v_1.35). Loizbec (talk) 13:39, 2 October 2024 (UTC) Reply

@Loizbec: No worries. It changed, and was not backwards compatible. Seemed worth breaking things, to align Foreground with other skins. Might've been the wrong choice! :-) Sam Wilson 22:53, 2 October 2024 (UTC) Reply

IGNORE, see below Hi: I'm using the Foreground skin on my wiki here: https://skalchemist.cloud/mediawiki/index.php/Main_Page

MediaWiki vs 1.41.1

When I go to the printable version, all internal wiki links have an extra EDIT code displayed, e.g.

Tabletop Roleplaying Games[edit (/mediawiki/index.php? title=Main_Page&action=edit&section=1)]

This is only in the printable version. Is there something I can do in the Print.CSS that would make that stop showing up? Or can someone explain to me why that is happening?

EDIT: I've found this: https://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_disable_external_links_from_showing_in_the_printable_version_of_a_page? That has some code that allegedly can be added to the Print.CSS to make this stop. However, its not working on my pages. Is Foreground preventing this somehow? Is there a setting I can change?

EDIT2: after some concentrated digging and experimentation, I found this seemed to work when added to my Print.CSS a[href]:after { content: " (" attr(href) ")"; }

So problem solved, ignore the question.

I'm using MW1.43 and Foreground 4.0.0 but think this was a problem for me in the past with other versions. I can use MediaWiki:Common.css as expected, and also MediaWiki:Vector.css and similar pages for other skins, but just not MediaWiki:Foreground.css. Nothing I save there takes effect. On the page itself, this usual warning does NOT appear:

Note: After publishing, you may have to bypass your browser's cache to see the changes.

• Firefox / Safari: Hold Shift while clicking Reload, or press either Ctrl-F5 or Ctrl-R (⌘-R on a Mac)
• Google Chrome: Press Ctrl-Shift-R (⌘-Shift-R on a Mac)
• Edge: Hold Ctrl while clicking Refresh, or press Ctrl-F5.

And the content is in normal text rather than monospace. I think the wiki just doesn't realise it's a CSS page. What's up? Thanks. Jonathan3 (talk) 13:06, 8 January 2026 (UTC) Reply

I found out what the problem was. It wasn't to do with Foreground at all but, with some embarrassment, I'll keep this here for future searchers. I'd originally created the page without the "." before "css", so had to move it. The page content model, which I'd never heard of before, was still wikitext. It was simple to change to CSS and works now. Here's the relevant manual page: Help:ChangeContentModel. Jonathan3 (talk) 13:13, 8 January 2026 (UTC) Reply