using the standard way to save configuration

[plegall]

I see that configuration is saved in the plugin directory, in the conf.php file. That makes the plugin immediately incompatible with "multiple site" Piwigo :-/ Why not using the standard way to store configuration with Piwigo? You have examples on how to do that with plugin Skeleton https://github.com/Piwigo/Piwigo-Skeleton

[jasperweyne]

During normal usage, the plugin stores the configuration in the same way as the Piwigo skeleton. However, if a problem occurs (this might also happen on the side of the OIDC identity provider), a user may inadvertently lock themselves out when the authorization flow is enabled. By enabling the authorization flow, the native Piwigo login flow is bypassed. This means that, if for some reason the user can't login to their Piwigo installation using the authorization flow, they're permanently locked out of their Piwigo installation.

Therefore, the conf.php file is provided to manually override the database-stored configuration. It's intended for emergency use, as manually editing database values is (usually) more difficult, compared to editing a file on disk. However, if you have another suggestion for this particular use case, let me know!

[plegall]

OK, that's very specific but I think I get it :-)

Instead of storing this configuration in the plugin directory, it should be stored in the local directory.

$conf_filepath = PHPWG_ROOT_PATH.PWG_LOCAL_DIR .'config/openid.inc.php';
if (file_exists($conf_filepath))
{
  include($conf_filepath);
}