[Bug]: Plugin option defaults no longer auto-populate when enabled.

[MykeHalk]

Contact Details

No response

What happened?

I recall default plugin config options used to auto-populated when installed and enabled. Currently, plugins require manual addition of options to /etc/pwnagotchi/config.toml or else they crash due to missing options.

The only option that auto-populates is the main.plugins.PLUGIN_NAME.enabled = true.

Version

2.9.5.2

3rd Party Hardware

No

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[wpa-2]

just run
sudo cp /etc/pwnagotchi/default.toml /etc/pwnagotchi/config.toml

easy edit down the line then.

[MykeHalk]

@wpa-2 Im confused, how does that address the plugins failing to auto-populate? If anything that will just reset my current configuration to default. From what I recall most plugins have defined defaults and __init__.py should automatically populate them into config.toml? What happened to that?

EDIT:
Also, even if i did cp the the default.toml to config.toml it wouldn't solve my issue because of custom plugins. Options for those are not included in the defaults.

[wpa-2]

Which plugin are you referring to, as every one I tried that happens.
If the plugin isn't setup right that's hardly the fault of pwnagotchi right ?

[MykeHalk]

What do you mean? I'm referring to every plugin. If you would like an example that you can test, install aluminum-ice's fork, add a custom plugin, and enable it and it will automatically populate the plugin's config options into config.toml.

For some reason jayofelony's fork does not do this, or the functionality has been broken at some point and requires bisection.

[taboo8614]

I have also noticed that when adding new plugins I must hunt down a guide that also gives me all the options to add to my config.toml file otherwise they fill my logs with errors.

[jayofelony]

I've never seen it auto populate config options for a custom installed plugin. Which plugin are you referring to?