Could not find icon : <acf-icon-name> (ACF issue after theme updates)

Support
#1

After installing Pro updates, I get a bunch of notices like this one. One for each icon that is used on the site:

Example: Could not find icon : star-half-alt @ /wp-content/themes/pro/cornerstone/assets/svg/font_awesome/solid/star-half-stroke.svg

On the frontend all icons are gone and I have to go in and switch the used icon categories off and back on to get the icons to show on the frontend again. This happens after each Pro update.

It’s set to use SVGs. All caches cleared after updates. It only happens on the one site I’ll mention in the secure note.

#2

Hello @JvP,

Thanks for writing to us.

This warning appears because Font Awesome v6 renamed legacy icon keys (e.g., star-half-alt became star-half-stroke). During updates, Cornerstone looks up cached icon paths, and stale transients cause it to miss the SVG file until toggling categories forces an index rebuild.

I would suggest you go to Cornerstone->Settings->Cache->Clear Cache.

Cornerstone-‹-TEST-—-WordPress-10-07-2026_12_49_AM
Cornerstone-‹-TEST-—-WordPress-10-07-2026_12_49_AM834×874 75.4 KB

Hope it helps
Thanks

#3

After every Pro update?

#4

Hello @JvP,

It is always best practice to clear all levels of cache—including the theme style cache, caching plugins, server object cache, and CDN—after an update to ensure new code and assets render properly.

Thanks

#5

I know, and I do that. However on this site the issue keeps popping up.

#6

Hello @JvP,

This is a temporary visual issue that will not affect your website’s functionality or data. Clearing the cache should immediately resolve it and allow everything to render as expected.

Thanks

#7

This keeps happening after each Pro update. Clearing the CS cache and the site’s various other caches does not work to immediately restore the icons on the frontend. Only on this specific site. Could be a server side issue maybe.

#8

Hello @JvP,

It might be related to a server-side issue since standard page caching or plugin clearing often fails to flush server-level object caches. You may contact your hosting provider to clear the server object cache, then clear your browser cache and check it again.

Thanks