-
Notifications
You must be signed in to change notification settings - Fork 361
Editor icons are not loading #475
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
Comments
Yes, please use the new v3.0.0-beta.0 version and include the following in the assets section in the angular.json:
|
worked for me |
I fix the issue installing awesome fonts or something like that. I couldn't find the dependency in the documentation, but the dev of the package talk about it in an issue like this one. |
this worked for me too, thx:> |
If the above solutions don't work for you, you can try what I did.
that's all. |
this also worked for me. |
i run this cli but still the icons are not showing. what am i missing? |
Same issue, I use --base-href and the application is trying to look at parent path and fails In index.html file add this
|
@veer05 temporary solution worked for me, thanks |
This might be obvious but also check that your font was not set to a white color by accident by some framework - in that case the fonts are actually loaded but you might be fooled into thinking they are not present. |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
Good morning everyone, it worked perfectly. |
I fixed this by adding the font, and it worked initially. But when I added a glob in angular.json to include icons in my build, they still wouldn’t show up when running locally. Another issue was that my app has a baseUrl, so all assets load from there, but the FontAwesome files were being served internally from the library, which broke the pathing. To solve this, I forked the library and added the Angular @fortawesome/angular-fontawesome package. Now, the icons load consistently with the rest of the assets, and this issue won’t reoccur. Until my PR gets merged, I’ve uploaded it to my npm registry for anyone interested: npm i @mhaseebtariq/angular-editor. I’m also using it in production at my company. Once the PR is approved, you can switch back to the original package—credit, of course, goes to the original author. This is just a quick fix! |
I had the same issue and this worked for me: add this object in angular.json file in assets: (as it is in the docs)
and add this style in styles.scss file:
|
::ng-deep got deprecated so if you are using later versions, that fix may not work |
@mohaseebtariq |
@Farzane2630 @mohaseebtariq can you please tell me how you implement in Angular 18 Please help me to solve this issue in Angular 18
I have make the changes according to you but it's not working for Angular 18 |
@durgeshsamcomtechnobrains when you build the project do you see the font files in the build folder? |
|
@mohaseebtariq Thanks a lot, |
@durgeshsamcomtechnobrains ,How do you fix that? |
@AravindM-Contus you just need to change in 2 files |
Hi, I am facing an issue. This change works on localhost, but when I deploy the build, it does not work in production. Has anyone faced this issue? I need help. ![]() ![]() ![]() |
@meetitexpert |
I am trying on Angular-14 and angular-editor-2.2.0-beta.0. The Editor icons are not loading.

Also, I could see these errors in the console. And I guess this is due to the removal of the CDN link in the latest merge.

Kindly let me know the workaround if any.
The text was updated successfully, but these errors were encountered: