Backup/export/import Preferences

Contribute UX

AI-generated summary

The discussion focuses on the ability to backup, export, and import user preferences in Discourse. jidanni suggests that end-users should be able to easily export and import their preferences across different sites, and have a backup in case a site goes down.

jidanni discovers that the option to download preferences is available, but is concerned that the language used (“Request archive”) implies that an administrator’s intervention is required. JammyDodger suggests that changing the text to “Download All” might give a more automated feel.

awesomerobot explains that the text was changed to “Request archive” because the download process takes time, and the user is notified when the file is ready. jidanni proposes simplifying the language and adding checkboxes to allow users to select what they want to download.

Additionally, jidanni suggests creating a “diet version” of the preferences.json file that only includes user-set preferences, and allowing users to import preferences. robbie.morrison asks about the current state of exporting and importing site configurations in machine-readable form, and seeks a better method than taking screenshots of settings.

Key suggestions:

  • Simplify the language for downloading preferences
  • Add checkboxes to allow users to select what to download
  • Create a “diet version” of preferences.json
  • Allow users to import preferences
  • Improve the method for exporting and importing site configurations
1

Sure, admins backup, export, import settings all the time, Export and import site settings .

But what about the little guy, the end user?

Certainly the preferences I use on site A, I probably also want to use on site B, or even C.

Plus what if a site goes kaboom? Sure would like to have a backup of my Preferences.

And one should find such functionality right there in the standard app, and not have to hunt around for some third party version.

Hmm seems you can even have some central sync authority..

1 Like
User born after 1904
Allow API use by regular users, not just admins
2

There is the ability to download your own stuff. :+1: It’s been a function we’ve been quite pleased with for some time. :slight_smile:

We’re trialling a new nav menu here on Meta, and you can find that option in https://meta.discourse.org/my/preferences

image
image570×496 7.3 KB

And if you are on a site that’s not using it yet, you can find it under ‘Activity’:

Untitled
Untitled1380×778 73.2 KB

1 Like
3

Sounds great, I wonder why I didn’t remember it when I saw it.

Ah ha, because it says “request archive”.

Sounds like I have to ask the administrator for something.

So even though I haven’t pushed it (the button) yet, but it sounds like I will be drawing the attention of some Administrators maybe.

(I mean here we are in the ux group so I’m to give you all my ux impressions. I wouldn’t want to skimp on those.)

Sure I bet it’s just some kind of timer or something but it still sounds kind of scary.

1 Like
4

I think it did have different text on it until fairly recently? I think it was ‘Download All’.

Would something like that give a more ‘automated’ feel to it?

2 Likes
5

Yeah feedback on the language is welcome. It was updated to “request” instead of “download” because the download isn’t instant when you click the button. Depending on how much activity your account has it may take the system a few minutes to prepare the file for download (and you receive a message once it’s ready).

2 Likes
6

Make “Request archive” just be a simple unnamed download icon button.

And after

Download an archive of your account activity and preferences.

just mention “you’ll get notified when it’s ready.”

And, many users just want their preferences not their activity, and many others want the opposite. So do consider not gluing them together. Have separate downloads. Or have all three buttons, A, P, A+P.

Okay, there’s certainly many categories in the zip.
Perhaps just have a bunch of checkboxes so that user can configure what he’s about to download.

And wait a second, what about importing preferences in?

1 Like
7

Okay the preferences.json… is so packed with stuff that we didn’t actually generate ourselves. So maybe there ought to be a second diet version that only contains things that we set ourselves when editing our preferences.

Actually Facebook, Google, etc. all allow users to pick and choose what stuff they want in the archive that will be produced. Some even have an index.html in the archive to make it “more friendly” than just a bunch of files.

1 Like
8

The first URL in the original posting points to a topic which points to unmaintained uploader code.

At the moment, I am giving some advice to a colleague on establishing a new discourse instance.

What is the state‑of‑play regarding exporting site configurations in machine and human‑readable form? And importing site configurations in machine‑readable form.

At the moment and under admin rights, I am reduced to taking a set of screenshots of my  ☰ ▸ Admin ▸ Settings .. Only show overridden, stripping these together in GIMP, and forwarding the resulting PNG to my friend for viewing. Kinda clumsy.

Any help with a better method much appreciated.