Can someone clarify the difference between these three Discourse concepts: theme-component, plugin, and pluginAPI. Especially between theme-component and plugin. If I want to customize my forum, how do I know which to build? (sorry if I missed this distinction in the intro , but I’m not seeing it t…

Thanks, guys. This is helpful. I think the key distinction I am picking up: –if you want to change something that is only about what’s on the front end, build a theme. –if you want to change something that requires interaction with the backend, build a plugin. Does that sound right? Here’s a con…

[画像] JQ331: If user is moderator, show the pin button (this is front end) The superficial part might be, but it will involve the backend because it relates to rights and security. You can’t give the front end discretion on what privileges someone has.

[画像] merefield: The superficial part might be, but it will involve the backend because it relates to rights and security. You can’t give the front end discretion on what privileges someone has. Do you mean that programmatically answering “Is this user a moderator of this category” is somethin…

[画像] JQ331: Here, because I need to converse with the backend (probably in (1), maybe also in (3)?), i’d have to use a plugin In a theme, you should be able to know if a user is moderator and also make backend calls if the discourse API exposes an endpoint that you can call from the front-end…

That’s very helpful regarding themes v plugins and also regarding the specific example I mentioned. Thanks. So far my approach to entering changes has been to sort through the specifics of the Discourse code (where is this object defined, what controls this template, where is the logic that handles…

Have you found: How to reverse engineer the Discourse API

I have seen that previously, but I’m taking a closer look now. Thanks for the reminder. Im trying to sort through: –where in the API I would get the info about who the moderator of a given category is (I’m not seeing it in the info returned about categories or users–obviously it has to be somewher…

[画像] JQ331: obviously it has to be somewhere I would look in the database. [画像] JQ331: add a custom field to a topic The database has a posts table and you could add a field there, but then you will be off the ranch and get no support.

Thanks–this is all very helpful. [画像] EricGT: I would look in the database. What database do you mean? To confirm, my idea here would be to use the API to do some of this stuff that might otherwise require a plugin. So, for example, my site itself would be making a call to the API to deter…

[画像] JQ331: What database do you mean? When Discourse is installed per the standard it is in a Docker container . Persistence of data is achieved using a PostgreSQL database. See: Data Explorer Plugin If you have admin rights you can grab one of the backups, it is SQL compressed into a tar.g…

テーマコンポーネント vs プラグイン：違いは何か

開発

EricGT (EricGT) 2020 年 6 月 5 日午後 7:47 9

見つけましたか：Discourse API のリバースエンジニアリング方法

「いいね！」 1

トピック		返信	表示
"theme-component" should be a subcategory instead of a tag Site feedback	16	1594	2022 年 7 月 19 日
About the Customization category Customization	0	55	2026 年 2 月 25 日
Can I use the JSON API instead of building a plugin? Development	3	1043	2020 年 6 月 6 日
Questions about the technical architecture of Discourse Development	18	1796	2024 年 1 月 2 日
Using the JS API Developer Guides plugin-api , explanation , code	20	11867	2026 年 1 月 30 日

テーマコンポーネント vs プラグイン：違いは何か

関連トピック