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
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).
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?
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.
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.