Hi guys,
you might struggle with the same issue as I do:
We’ve installed various plugins with a lot of settings at admin panel. Discourse settings are pretty well grouped by their kind. Plugins not. We can’t say which option belongs to which plugin. I’d like to suggest a little improvement…
Is it possible to expand / collapse plugin specific options like the details view? (collapsed by default)
Some other ideas:
altering background color (white / gray / white / …)
a thin line between each plugin settings group
In addition to this, I’d like to have some basic information about the plugin on top of each group (1-2 sentences description), latest version and the installed one (date and build version), a link to the offical support site and a link to the plugin author’s site, and if available a shortcut to the docker manager to install updates.
When you click on the settings link for a plugin, it works by filtering the settings based on the plugin name. For example, if you click on the settings for discourse-solved, it will bring you to this URL:
This means that any of a plugins settings that cannot be found through that filter will not be displayed. With the discourse-solved plugin, the setting for accept_all_solutions_trust_level is not displayed when you click on the Settings button.
For starters though we should be more consistent about naming in our plugin site settings. I agree a better structure makes sense here, we can associate the plugin settings with the particular plugin and then always be able to find them regardless of naming.
I really like the idea of allowing you to expand plugin settings directly near the plugin, somewhat similar to how theme settings work.
fAs I understand it, I know of two approaches. One is for a plugin to have its own settings menu under Settings. For a plugins settings to be shown from the Plugins page the settings need to follow the convention of setting names being prefixed with the plugins name.
For example, the setting name for the data explorer plugin begins with “data_explorer_” if it was not so it would not be found from the Plugins page.
I’m guessing the settings are being searched for setting names that begin with the same string as the plugin name. I’m also guessing it would be easiest to make this behavior known to plugin authors and put the onus on them to follow the convention.
이 설정/필터 버튼은 각 플러그인별로 사용 가능한 건가요? 여기 나열된 플러그인 하나만 가지고 있습니다(기본적으로 사전 설치된 몇몇 플러그인이 있고,它们的 설정은 이 플러그인들과 함께 /admin/site_settings/category/plugins에 나열되어 있습니다. 명확한 구분/분리가 없어서 매우 이상하게 느껴졌습니다.)
이미지에서 /admin/plugins 섹션의 유일한 상호작용은 플러그인 링크를 클릭하는 것인데, 이는 해당 플러그인의 GitHub 저장소로 이동합니다. 커뮤니티 관리자가 더 많은 플러그인을 추가할 때 이 부분이 얼마나 지저분하고 체계적이지 않게 될지 걱정됩니다.
제 경우에는 설정 링크 버튼이 없지만, @simon이 제공한 URL 예시를 바탕으로 openid를 사용하여 결과를 필터링할 수 있습니다. 다만 이는 플러그인의 전체 이름이 아니고, 다른 플러그인도 openid를 포함하고 있다면 이 방법이 작동하지 않을 수도 있습니다(openid-connect는 결과를 9개에서 1개로 변경했으며, openid는 로그인 설정에서 관련 없는 2개의 결과를 보여주었습니다).
수정:openid_connect가 올바른 값인 것 같습니다. 이 설정 키들을 기반으로 필터링하는 것으로 보입니다.
