You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The academic icons pack is not loading. This means that when the logos should be displayed, there is a blank space instead. This affects a range of academic icons including OSF and Google Scholar.
Examples of where this occurs are visible on the website home page, under the logo next to "What is FORRT?", and in the author lists for Educators' Corner pieces.
To Reproduce
No specific steps, it's just not loading! This is visible on the live site.
Expected behavior
The academic icons should be displayed when called.
Screenshots
In the below screenshots, the OSF logo should be between the Twitter and Github icons.
Home page:
Educators' Corner:
Additional context
This is also occurring on my development server. It might be an issue in themes > academic > data > assets.toml, but I don't know enough about webdev to solve it right now!
The text was updated successfully, but these errors were encountered:
Describe the bug
The academic icons pack is not loading. This means that when the logos should be displayed, there is a blank space instead. This affects a range of academic icons including OSF and Google Scholar.
Examples of where this occurs are visible on the website home page, under the logo next to "What is FORRT?", and in the author lists for Educators' Corner pieces.
To Reproduce
No specific steps, it's just not loading! This is visible on the live site.
Expected behavior
The academic icons should be displayed when called.
Screenshots
In the below screenshots, the OSF logo should be between the Twitter and Github icons.
Home page:
Educators' Corner:
Additional context
This is also occurring on my development server. It might be an issue in themes > academic > data > assets.toml, but I don't know enough about webdev to solve it right now!
The text was updated successfully, but these errors were encountered: