+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Plugin changed CSS permanently (/t-plugin-changed-css-permanently)
Plugin changed CSS permanently - Bling7777 - 2025-03-04
Hi all,
I have been messing with some plugins (this and this) in my Jellyfin that didn't work for me. So I uninstalled them.
But now I'm stuck with some permanent CSS changes. I have an additional 360px padding-top (see attached image).
I tried restarting Jellyfin, redeploying docker, cleaning cache, running in another browser...
I even tried to remove some hanging .XML from /config/plugins/configurations/ - without any apparent change.
Could someone point me in the right direction on how to solve this, please?
Thanks in advance!
RE: Plugin changed CSS permanently - Efficient_Good_5784 - 2025-03-04
If it's actual CSS code, you need to find the "branding.xml" file and delete the code inside of it.
This file should be in the config folder. On Docker, it's the config folder inside of the top-most config folder.
If that doesn't fix the issue, most likely it's a caching issue somewhere.
RE: Plugin changed CSS permanently - Bling7777 - 2025-03-04
Thanks for the reply, @Efficient_Good_5784.
It didn't work, unfortunately. Where should I look for interface cache?
Or is there a way to backup all the important configs from my instance (transcoding, language, profiles) and redeploy the whole thing?
RE: Plugin changed CSS permanently - Efficient_Good_5784 - 2025-03-04
To redeploy, it depends on how you installed Jellyfin.
All you need to do is copy and transfer the config directory to the new install.
RE: Plugin changed CSS permanently - Bling7777 - 2025-03-04
Copying the config directory didn't even let me connect to the "same Jellyfin server". It made me delete and add again the same server.
When I did, none of my configurations were in place.
Anyway, I did something right and got rid of the weird padding.
You're probably right with the cached thing. Too bad I couldn't find what was it.
Thank you for the help!