Font Awesome Icons Randomly Stopped Working

JayGervais
Kilo Sage

Hi there, 

The font awesome icon kit used randomly stopped working on all of our instances. In the console I am getting a 403 error. When I go into the portal base theme, in the list section for JS Includes, the icon kit is included as a JS Include. After opening it, when clicking the URL, it shows XML with Access Denied. I am not sure what happened or why this stopped working but it happened randomly and is affecting all of our platforms.

If you have any idea how to troubleshoot this or what the issue might be, I appreciate your insight.

Cheers, 

Jay

1 ACCEPTED SOLUTION

Willem
Giga Sage
Giga Sage

Hi Jay,

 

A few things you can try:

Include

  • This article mentioned it should be in the CSS Include:

https://www.servicenowelite.com/blog/2017/11/15/service-portal-custom-font

  • If you include it using attachment, make sure the attachment is still there and has not changed.

 

Security

Can you check this security rule:

yourinstance.service-now.com/sys_security_acl_list.do?sysparm_query=name%3Dsp_theme%5EORname%3Dsp_css%5Eoperation%3Dread

Should contain the role Public.

 

 

Other things you can check

- With your browser's developers tools, see if there is any error showing when loading the glyph picker.

- Check in the Style Sheet that references to attached files are valid (https://<your instance>.service-now.com/sp_css.do?sys_id=e3a01fce375100103c80dc1873990ebe).

- Verify that you have only one "fontawesome.min" Style Sheet.

- licensing on font-awesome kit

https://community.servicenow.com/community?id=community_article&sys_id=55e62d7fdbafb70813b5fb2439961...

 

View solution in original post

3 REPLIES 3

Willem
Giga Sage
Giga Sage

Hi Jay,

 

A few things you can try:

Include

  • This article mentioned it should be in the CSS Include:

https://www.servicenowelite.com/blog/2017/11/15/service-portal-custom-font

  • If you include it using attachment, make sure the attachment is still there and has not changed.

 

Security

Can you check this security rule:

yourinstance.service-now.com/sys_security_acl_list.do?sysparm_query=name%3Dsp_theme%5EORname%3Dsp_css%5Eoperation%3Dread

Should contain the role Public.

 

 

Other things you can check

- With your browser's developers tools, see if there is any error showing when loading the glyph picker.

- Check in the Style Sheet that references to attached files are valid (https://<your instance>.service-now.com/sp_css.do?sys_id=e3a01fce375100103c80dc1873990ebe).

- Verify that you have only one "fontawesome.min" Style Sheet.

- licensing on font-awesome kit

https://community.servicenow.com/community?id=community_article&sys_id=55e62d7fdbafb70813b5fb2439961...

 

Thanks Willem. The issue ended up being with the licencing on our font-awesome kit. I appreciate your help.

You are welcome! I will add it to the list, next time someone needs it 🙂