Thank you, I didn't try that approach, instead, I realized I can change the settings directly from the code. So I'm baking in my settings into my plugin and setting them in the init.

@PitaJ Ahh... Yeah this was looking fine, but I've encountered a problem with exporting the local login setting. Earlier it was in the config object, but now that has been obsoleted and it's a "group privilege". I find the database structure of groups and their privileges a big confusing. Do you think you could help me figure out how to export that general setting in the current situation?

@Rusdy-MT It seems to me like they have revamped this option. It's now some kind of "group privilege" now. You can toggle it under ACP -> Manage -> Privileges. This came out of nowhere for me as well...

Alright, thanks.

Hmm, I guess that would be the way then. Are the ones in the config object also plugin options, or only general ones?

I'm trying to set up a staging environment, but a lot of my setup depends on my settings. I don't want to have to duplicate them every time I change something. Is there a way to sync all ACP, perhaps in a file?

Edit: I also want to sync the installed plugins, but I can already do that with package.json.

Ok, I'll do that. Thank you!

Hi, I'd like to submit a PR as a feature request for NodeBB. Should I do it on the latest versioned branch, or on master, or...?

Well, there are language files in /public/language. The GDPR text is, as far as I remember, sourced from a few of these entries (the language files are JSON files with a prase identifier, and translation). So if you want to change the wording, you would have to modify these files in your clone of the repo.

Not sure if this is the "best way" since they might be overwritten when you pull the next version (could someone with more knowlede than me confirm this?) but that's a git issue that you should be able to handle once you get to updating.

For example, I see three entries in the file "/public/language/en-US/register.json" that start with "gdpr_". There are probably others but this is a good place to start. Just search those language files for the exact wording.

Also note that to chnag eit you would have to change all of the languages, but if english only is enough for you, that is easier.

Yeah, don't worry, it's not urgent and when I'm setting the specific host URL for my client it works. I just realized that looking at the code, setting "*" will not work. However, I also see now that you added '...Origin-regex' in the latest update, so I guess that is a fine workaround.