-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export individual styles #526
Comments
Maybe we can add a new button to export styles listed in the manager so you can use the filter feature to select which styles to be exported. |
If you do a quick edit to an existing style (I realize the recommended method is a separate "helper" style) is there still really not any way at all to export the actual individual style CSS data to a file? Coming from the userscript world this has always been a pretty trivial task to save/maintain backups of individual styles/scripts, so I'm hoping I've just overlooked the Stylus method. TIA! |
Hi @CollinChaffin! In the new manager layout PR I've been working on (not too much lately 😿), you will be able to export selected styles. It will also allow bulk actions, like deleting, updating, etc, on those selected styles. |
Don't believe his lies. The "new manager layout PR" is a myth. A fairy tale passed down through the generations. "Backups" are currently just the whole DB. While you're not exactly able to export individual stylesheets to files, exporting to Mozilla format may be less convenient, but it's in the same ballpark. At least it'll convert multi-sectioned styles to a single block of code you can copy/paste to save to a file and copy/paste to import. |
How do you do that? I don't see a button anywhere to do it. |
They're in the side bar on traditional edit pages. Usercss styles are already a self-contained format, with a single block of code you can copypasta. |
Merging into #1339. |
The Wiki is clear that individual styles can't be exported, so I'm requesting that as a new capability.
(I searched and don't see any existing requests for this, open or closed.)
The text was updated successfully, but these errors were encountered: