Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Font Awesome 5.0 #62

Open
RickAtFenestra opened this issue Apr 5, 2018 · 3 comments
Open

Feature Request: Font Awesome 5.0 #62

RickAtFenestra opened this issue Apr 5, 2018 · 3 comments

Comments

@RickAtFenestra
Copy link

@RickAtFenestra RickAtFenestra commented Apr 5, 2018

Feature Request

A feature request: upgrade support to the "free" version of Font Awesome 5.x. Thanks for the skin... it is great.

@Hutchy68
Copy link
Owner

@Hutchy68 Hutchy68 commented Apr 18, 2018

Love to upgrade, but this will require some work. What is at issue, open source version vs pro (paid) and the icons available to the open source. Some changed, some did not, some have a different call to render them.

@poVoq
Copy link

@poVoq poVoq commented Apr 19, 2018

Maybe better to stick with Fork-Awesome?:
https://github.com/ForkAwesome/Fork-Awesome

@designnerd
Copy link

@designnerd designnerd commented Apr 6, 2020

We implemented a temporary fix for this by creating a customizations folder in the MW directory, then placing the FontAwesome5 basic (free) set items we downloaded there, then added the following workaround in LocalSettings.php:

Load Theme Customizations

$wgResourceModules['ourtheme-customizations'] = array(
'styles' => "/fontawesome-5-8-2/css/all.css", // Stylesheet to be loaded in all skins
'scripts' => "", // Script file to be loaded in all skins
'localBasePath' => "$IP/customizations/",
'remoteBasePath' => "$wgScriptPath/customizations/"
);
function efCustomBeforePageDisplay( &$out, &$skin ) {
$out->addModules( array( 'ourtheme-customizations' ) );
}

Then in the CSS:

#yourElement {
content: "\f0f3";
font-family: "Font Awesome\ 5 Free";
font-weight:900;
}

Not an ideal way to do it but it gets the job done as a temporary workaround. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants