Yes, and presumably you can apply to every available Theme so this can’t be switched off? (to address @sarahann concern about this approach).
I could use display: none but it might now be as secure as we need it to be. And I figured it would be helpful to have a discussion on how to remove / change Discourse UI templates.
إعجابَين (2)
It’s tricky to do properly, unfortunately. For a big customer of ours who needs functionality removed, my approach has been to hide the elements with CSS and remove the controller side actions by using add_to_class to overwrite the methods with an error in plugin.rb.
9 إعجابات
I have a same problem. I’m working on plugin with topic, and I have to change the html structures but it’s impossible with only CSS. So I was tried to overwrite template but changes never applied.
So do you have find any solution for that?
You can override any template in the application if you like (although outlets are always preferred!). How were you doing it? did you confirm the name is exactly the same as the template you are replacing?
3 إعجابات
I tried to override the “list/topic-list-item.raw.hbs” template, but even though I removed all of the content in template, the topic items still appearing as original, any changing in override template never worked.
Please help me what I was wrong.
See: https://github.com/SamSaffron/discourse-simple-theme for an example of how it is done.
4 إعجابات
Hello,
When I run the command git grep “plugin-outlet” – “*.hbs” in my Linux Terminal, nothing shows up. Any ideas why? Thanks for your help!
Caveat: This is a sysadmin answer, not a plugin developer answer, and I can’t guess what you might have done before you did your git command.
Did you add it to git? What about
grep -r plugin-outlet .
إعجابَين (2)
Building on Jay’s shoulders here, you can of course focus on the specific file type:
grep -r "plugin-outlet" --include \*.hbs
3 إعجابات
Is there anything you need to consider differently if the plugin outlet looks like this?
{{plugin-outlet name="users-top" connectorTagName="div" args=(hash model=model)}}
do the connectorTagName and args attributes mean that plugin developers have particular constraints or extra accesses when using these outlets?
Yes you are meant to work with the API that the outlets establish.
In the users-top you are passed a model which you can use, and the connector will be rendered with a div in this case.
إعجابَين (2)
لم أعثر على {{plugin-outlet}}. لقد وجدت بعض المكونات بنفس الاسم. هل هي نفسها؟
إعجاب واحد (1)
أعتقد أن كود Discourse قد تغير وأن الدليل قديم.
أبحث عن هذا المثال:
وجدت هذا بدلاً من ذلك:
وباستخدام مكون السمة المذهل هذا (deprecated) Plugin outlet locations theme component يمكنني رؤية منفذ المكون هذا حيث يجب أن يكون:
للإجابة على سؤالك، تخميني هو أنه نفس الشيء، ولكن بصيغة جديدة.
3 إعجابات
لقد وجدت أيضًا هذا الوسم. هل يمكن لأحد أن يؤكد أنهم جميعًا متماثلون؟
{{~raw-plugin-outlet name="topic-list-after-title"}}
المرجع الأكثر حداثة للمنافذ الإضافية موجود هنا:
سأحاول تحديث المنشور الأصلي هنا في الأيام القليلة القادمة.
5 إعجابات
تم تحديث المنشور الأصلي (OP) بالصيغة الجديدة، ورابط للتوثيق الكامل
6 إعجابات
أعتقد أنه يجب تحديث الأمر إلى:
git grep "<PluginOutlet" -- "*.gjs"
يشير هذا الرابط إلى “مهمل” (deprecated).
تعديل: وجدت الرابط لإنشاء طلب سحب (PR) تحت المنشور العلوي، لذلك قمت بإنشاء طلب سحب.
إعجاب واحد (1)
تم استبداله بـ:
https://meta.discourse.org/t/introducing-discourse-developer-toolbar/346215?u=merefield
إعجابَين (2)