I have install the discourse-jitsi
but no option is available in the editor to add jitsi conference
AI-generated summary
Users are reporting that the discourse-jitsi component is not working — specifically, no option appears in the editor to insert a Jitsi conference. Arkshine identified the root cause: a compile error in the theme component due to a duplicate declaration of themePrefix, which is already available in the component context. This issue stems from a recent PR (#20) and was resolved by Arkshine via PR #21. The fix was merged by pmusaraj, and isaac confirmed readiness to close the issue. Other users, including JammyDodger and merefield, expressed appreciation for the quick resolution and noted the benefit of having a dedicated topic for this official theme component. The issue is now resolved and ready for closure.
There is an error:
[THEME 81 ‘Discourse Jitsi’] Compile error: SyntaxError: “/discourse/theme-81/discourse/components/modal/insert-jitsi: Identifier ‘themePrefix’ has already been declared. (11:7)\n\n 9 | import DModal from "discourse/components/d-modal";\n 10 | import TextField from "discourse/components/text-field";\n> 11 | import themePrefix from "discourse/helpers/theme-prefix";\n | ^\n 12 | import i18n from "discourse-common/helpers/i18n";\n 13 | export default class InsertJitsi extends Component {\n 14 | @tracked” (discourse/components/modal/insert-jitsi.gjs)
themePrefix function is already available in a component context, and the error happens because the import tries to overwrite that. This is related to the latest PR #20.
EDIT: made a PR 
4 Likes
As it’s an official theme component (especially one with a tag set up 
) having a dedicated topic is 
. It saves me having to split topics off later.
3 Likes
Ah, great! Good to hear!
3 Likes
Thanks so much for the fix, @Arkshine, it is now merged.
2 Likes
Thanks @Arkshine, are we good to close this off?
2 Likes
This topic was automatically closed after 2 days. New replies are no longer allowed.