Closed Sweetdevil144 closed 4 months ago
I think this is related to changes in the underlying libraries over the last couple years. See this post for discussion and possible solutions: https://stackoverflow.com/questions/32686195/shinydashboard-some-font-awesome-icons-not-working
@Sweetdevil144 If you get things working, please submit a pull request with your updates
Thanks for the suggestions @mdietze . I'll check out the above link and remind you of the progress on the same.
Hey,
Sorry for the late response on this issue.
I found the fontawesome
R package (https://github.com/rstudio/fontawesome), which could fix our icon issues in the Pecan Status Board. It offers updated icons and better Shiny compatibility. Might be worth a try for a smoother integration.
Any suggestions @mdietze ?
Yeah, give it a try. If it works submit a PR.
Update on errors :
icon("clock",verify_fa=FALSE)
with icon("clock",lib="font-awesome")
at all instances wherever the error was indicated.main
branchFollowing error logs were displayed
Browsing http://127.0.0.1:5071
The `name` provided ('clock-o') does not correspond to a known icon
The `name` provided ('square-s') does not correspond to a known icon
The `name` provided ('square-e') does not correspond to a known icon
The `name` provided ('square-C') does not correspond to a known icon
Sorry! Server not responding.
Sorry! Server not responding.
Warning: Error in : id variables not found in data: Workflow_id
52: stop
51: melt_check
50: melt.data.frame
48: module
43: callModule
42: moduleServer
41: mod_workflows_satus_server
40: server
3: runApp
2: print.shiny.appobj
1: <Anonymous>
Error : id variables not found in data: Workflow_id
square-s
to simple square
combined with lib=font-awesome
, yet these old logs were displayed.R/app_server.R
OR R/mod_workflows_status.R
.Opening the PR related to same
For the Second (New) error logs, I wanted to clear two more things :
After setting up
pecan-status-board
, I tried running the app on my RStudio Platform. However, I've been facing some server errors with following error logs displayed while the screen stays over in loading scenario.Command :
Logs :