When first setting up this plugin, I made the grave mistake of uploading all my FA SVGs, via the admin UI. This obviously took forever and I had to do it in batches to avoid having the browser crash, but I eventually managed to do it. The configuration page in the admin panel is understandably unusable, so I've been trying, unsuccessfully, to get rid of those SVGs so I can add only the ones I'm using.
The reason I can't just ignore it is because it's not actually working, but I'm unable to troubleshoot due to the lag.
I've tried:
Disabling and re-enabling
Reinstalling
Uninstalling and reinstalling
Deleting the user/data/fontawesome directory
Deleting the user/config/yaml file
None of those have worked. The only thing that seems to work is removing the SVGs individually in the admin UI, which is obviously impossible due to their sheer number and the amount of lag on that page.
Is there some other layer of cache I'm unaware of that persists after running bin/grav clearcache --all?
When first setting up this plugin, I made the grave mistake of uploading all my FA SVGs, via the admin UI. This obviously took forever and I had to do it in batches to avoid having the browser crash, but I eventually managed to do it. The configuration page in the admin panel is understandably unusable, so I've been trying, unsuccessfully, to get rid of those SVGs so I can add only the ones I'm using.
The reason I can't just ignore it is because it's not actually working, but I'm unable to troubleshoot due to the lag.
I've tried:
user/data/fontawesome
directoryuser/config/
yaml
fileNone of those have worked. The only thing that seems to work is removing the SVGs individually in the admin UI, which is obviously impossible due to their sheer number and the amount of lag on that page.
Is there some other layer of cache I'm unaware of that persists after running
bin/grav clearcache --all
?