With Piwigo 12 (and also in 11), we now have an automatic link to the configuration page of the plugin, with pattern admin.php?page=plugin-<pluginID>. It supposes:
the plugin has an admin.php file at the root of the plugin directory
the plugin ID (ie folder name) has no dash in its name
We have 2 (very popular) plugins having a dash in their ID : piwigo-videojs and piwigo-openstreetmap. Renaming a plugin ID is very complicated due to upgrade issues. So I propose to have a specific processing for those 2 (and strongly discourage to use a dash in plugin ID for future plugins)
With Piwigo 12 (and also in 11), we now have an automatic link to the configuration page of the plugin, with pattern `admin.php?page=plugin-<pluginID>`. It supposes:
1. the plugin has an `admin.php` file at the root of the plugin directory
2. the plugin ID (ie folder name) has no dash in its name
We have 2 (very popular) plugins having a dash in their ID : piwigo-videojs and piwigo-openstreetmap. Renaming a plugin ID is very complicated due to upgrade issues. So I propose to have a specific processing for those 2 (and strongly discourage to use a dash in plugin ID for future plugins)
<!-- github-sync-id:1091181724 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
With Piwigo 12 (and also in 11), we now have an automatic link to the configuration page of the plugin, with pattern
admin.php?page=plugin-<pluginID>. It supposes:admin.phpfile at the root of the plugin directoryWe have 2 (very popular) plugins having a dash in their ID : piwigo-videojs and piwigo-openstreetmap. Renaming a plugin ID is very complicated due to upgrade issues. So I propose to have a specific processing for those 2 (and strongly discourage to use a dash in plugin ID for future plugins)