Componente de tema de texto de espaço reservado do modelo de tópico

Personalização Componente de tema
1

Texto de Espaço Reservado do Modelo de Tópico componente de tema

Este componente de tema permite que você exiba Modelos de Tópico como espaços reservados (marca d’água) em vez de texto de modelo editável.

Isso permite que você forneça instruções personalizadas como um espaço reservado para cada tópico.

Por exemplo:

Este é o texto normal de espaço reservado (marca d’água).

image
image922×259 4.35 KB

NB: Você já pode alterar isso em todo o site alterando o texto personalizado

Vá para Admin >> Personalizar >> Texto

Em seguida, pesquise o texto que você vê na tela.
Uma pesquisa por “BBCode” deve fornecer o que você deseja:

Em seguida, altere os valores de js.composer.reply_placeholder para o texto de espaço reservado que deseja exibir

Você também pode definir um Modelo de Tópico em cada categoria

No diálogo Editar Categoria, selecione Modelos de Tópico. Você pode adicionar um modelo personalizado para sua categoria.

image
image654×722 17.2 KB

Isso funciona bem, MAS o usuário precisa excluir o texto do modelo antes de poder começar a digitar sua postagem.

Este componente de tema permite que você exiba o texto do modelo de tópico como um texto de espaço reservado (marca d’água) em vez do texto editável. Basta clicar na caixa e começar a digitar.

Pode ser configurado para exibir todos os Modelos de Tópico como espaços reservados, ou você pode fazê-lo caso a caso, adicionando um indicador [placeholder] ao Modelo de Tópico.

image
image721×578 16.4 KB

Instalar o componente de tema

:hammer_and_wrench: Repositório Git: https://github.com/naidihr/discourse-topic-template-placeholders

:thinking: Como instalo um Tema ou Componente de Tema?

Créditos

Obrigado a @merefield por refatorar o elemento JQuery para usar o framework Ember e o núcleo do Discourse.

Observe que a versão atualizada foi testada apenas para funcionar nas versões do Discourse a partir de 2.4.1. Se você estiver em uma versão anterior do Discourse, tente a versão original, que foi testada na versão 2.3.10.
Repositório da versão original: https://github.com/naidihr/discourse-topic-template-placeholders_original

35 curtidas
How to Add Category-specific Message Above Topic Editor
Template for replies
How can I add labels in create topic form fields?
Is there an option to trigger a guidelines prompt for the first few posts a user does?
Reply Template
Have users complete form when creating a topic?
Discourse Category Headers theme component
Quote formatting of support category template
I need two different placeholders on new topic and reply body fields
Rotating Composer Placeholder
New lines in the composer's reply placeholder?
Something like shortcodes for Discourse?
2020: The Year in Review
Can a user block a user group?
Js.composer.reply_placeholder applies to New Topics as well as Replies
I there a way to setup a template (placeholder) in the topic creation editor
[PAID] extra input fields for new topic
2

PS development note. I had to do a JQuery hack to get this to work as a theme component. If it is possible to update the placeholder via the model - I would be grateful of you would let me know.

8 curtidas
3

You can try something like this

<script type="text/discourse-plugin" version="0.8">
  api.modifyClass("model:composer", {
    applyTopicTemplate() {
      this._super(...arguments);

      Ember.run.schedule("afterRender", () => {
        // do your work here
      });
    }
  });
</script>

This should allow you to add some custom logic when Discourse applies category topic templates.

That said, this type of way of writing stuff is a bit outdated. I would also recommend that you give this a read if you plan to spend a lot time on Discourse themes. It makes life much easier.

9 curtidas
4

Great idea for a Theme Component!

I’ve gone ahead and submitted a PR to do the following:

  • removes need for jQuery
  • removes need to worry about timing (use Ember framework & Discourse core, don’t fight them)
  • modifies the Composer Model to help achieve the result (as you rightly suggested)

I won’t be upset if you don’t merge it, but hope it helps to see another way of doing things :slight_smile:

(I can’t promise there are no bugs, but happy to follow up on any ! :cowboy_hat_face: )

9 curtidas
5

Thanks Robert. I’ve merged that PR. Much appreciated :+1:

2 curtidas
6

This is literally what I was looking for! You are a god! :bowing_man: :shallow_pan_of_food: :bowing_woman:
Please accept this humble emoji offering. :canned_food:

1 curtida
7

FYI this only works if you first go to the category and create a new topic. If you try to create a new topic from the latest page and then select a category from the dropdown the text doesn’t display.

2 curtidas
8

That’s expected? That’s how Topic Template functionality normally works. The Topic Template won’t be considered in the latter case.

But yeah, imho, that could be improved in even vanilla Discourse without this TC to support your latter case. I have personally found it annoying that users are not presented with the Template if they go the second route.

This TC is just piggybacking off of core so …

9

Maybe we’re talking about different things, but this is how it works for me…

1 curtida
11

This might be due to some other reason because it works here on Meta. if you go to /latest, open the composer and then select the marketplace category you get the template we have for that.

4 curtidas
12

Yep weird. Sorry I think it might have been resolved. This was nagging me for ages but seems to work now.

Ok that presents a new challenge. Haha.

4 curtidas
13

Hi Robert - I tested it after the merge and it was working - but it no longer is for me? This is with the override setting - not using the [placeholder]. Please can you check with your build as well?

Also on my original version - it did work the same if you started a new Topic from the latest page and then select the category.

I may need to roll back…?

14

I’m looking at it now. Give me a little while.

15

OK PR for fix raised: FIX: change the placeholder & template when switching selected Category by merefield · Pull Request #2 · naidihr/discourse-topic-template-placeholders · GitHub

It is now taking the Category from the Composer selection. Now that’s done, it seems to work in all situations, but please confirm.

2 curtidas
16

Hi Robert, I merged that last PR and updated to the latest theme component version in but it is still showing the template text for default by me, even though I have “display all topic templates as placeholders” set. I am on Discourse 2.4.1. Any more thoughts?

2 curtidas
17

That works, but it also doesn’t work at all if display all topic templates as placeholders is turned on, even if I’m in the category. Regretting volunteering for this now? :stuck_out_tongue_winking_eye:

2 curtidas
18

No problem guys. We just iterate. :). I’ll take a look.

Update: PR https://github.com/naidihr/discourse-topic-template-placeholders/pull/3

When checking out remember to refresh the page if you change a setting.

2 curtidas
19

Great Robert. That last PR has fixed it. Also when starting a topic from the latest or category pages. All looking good now. Thank you for taking the time to look at this. Very neat solution _super job :wink::+1:

3 curtidas
20

No problem. A pleasure. Sorry my initial testing should have been more thorough. Thanks for your patience.

I think we are on a good track right now, hopefully!

Keep coming up with more great ideas and putting them into practice!

3 curtidas
21

Howdy folks! We love the idea of this theme component!

I just tried to install it on our discourse instance but I’m running into some trouble here.
It seems that when enabled on the theme, it breaks some of the styling already in the theme.
For example, the buttons at the user drop down:

image
image630×262 11.5 KB

become like this when enabled:

image
image680×230 21.4 KB

In addition to this, the placeholder doesn’t appear to work, both with 'Display all your Topic Templates as placeholders (watermark text)' enabled, and disabled.

It could be that our discourse instance is v2.3.10?

I’ve taken a look at the code here and can’t discern why our styling would be messy.

We rely on another team to manage and update our discourse instance & it’s a bit of a big task to get that done.

I’m hoping for a quick tip to potentially fix this, but, if it boils down to our discourse version that’s fine too!

Thanks in advance :smiley: