Base solution for your next web application

Activities of "TimMackey"

@ismcagdas - The solution you suggested solves the problem. Thank you.

Added the following to angular.json:

"glob": "**/*",
"input": "node_modules/@fortawesome",
"output": "/assets/@fortawesome"

and this to index.html:

<link rel="stylesheet" href="./assets/@fortawesome/fontawesome-pro/css/all.css">

@exInt - solution #3 file is src/index.html. You create the link yourself. My project type is Angular / Core.

@ismcagdas - Please refer to #5527 for installation and usage. The fonts have been working since August with versions 5.6.0 and 6.2.0.

Since my original post I have continued to try more potential solutions:

  1. modified src/index.html <link rel="stylesheet" href="../node_modules/@fortawesome/fontawesome-pro/css/all.css">
    1. removed rel="stylesheet",
    2. replaced href with src,
    3. replaced all.css with all.min.css
  2. added <base href="/"> before any <link .. >
  3. copied the entire @fortawesome folder to src/assets folder and changed index.html to <link rel="stylesheet" href="./assets/@fortawesome/fontawesome-pro/css/all.min.css">.

Item 3. does fix the issue, but isn't an ideal solution, since the 'assets' folder is reserved for modifed vendor-supplied components, and it's another setup setp. It will be OK as an interim solution during development. Still, it begs the question, what changed from 6.2.0 to 6.4.0 that would cause the error message and non-functionality?

Refused to apply style from 'http://localhost:4200/node_modules/@fortawesome/fontawesome-pro/css/all.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

...message is displayed in Chrome Version 71.0.3578.98 browser debug console, and icons are not visible for AspNetZereo release 6.4.0. AspNetZero release 6.2.0 does not display this message and all icons are visible.

I read the other 3 issues related to this, and was unable to apply any of those solutions to solving my issue. Starting with a clean database does not solve the issue either. I've also attempted other solutions found in places like github and stackoverflow - without success. The issue is related to "pro" icons only. Non-pro icons display normally.

What is required to fix this issue?

Thank you for the clarification.

The answer seems to be that the all selections in the User Interface group are unselected.

I'm trying to identify a path for implementation. Could you please answer my questions? Thank you.

You say "However, this is based on the Abp vNEXT framework." What's the catch? I do understand the vNext isn't yet officially released, but that's not a sufficient barrier for creating documentation pages. Unless it really isn't production ready.

Can I use the npm package in the current release of AspNetZero? Is it recommended I use the npm package as a separate solution, independent of my AspNetZero solution? Should I wait until AspNetZero integrates Abp vNEXT framework? And if so, what is the planned release date? It would be helpful if you could identify some possible paths for implementation. Thank you.

Version 6.2.0 Core 2.0 / Angular

Browser width: 1024 pixels:

Browser width: 1025 pixels:

Showing 281 to 290 of 398 entries