Composant de thème Texte d'espace réservé du modèle de sujet

[Rhidian (Rhidian Bramley)]

Texte d’espace réservé du modèle de sujet composant de thème

Ce composant de thème vous permet d’afficher les modèles de sujet comme des espaces réservés (filigranes) plutôt que comme du texte de modèle modifiable.

Cela vous permet de fournir des instructions personnalisées en tant qu’espace réservé pour chaque sujet.

Par exemple :

Ceci est le texte d’espace réservé (filigrane) normal.

NB : Vous pouvez déjà modifier cela à l’échelle du site en changeant le texte personnalisé

Allez dans Admin >> Personnaliser >> Texte

Ensuite, recherchez le texte que vous voyez à l’écran.
Une recherche de « BBCode » devrait vous donner ce que vous voulez :

Ensuite, modifiez les valeurs de js.composer.reply_placeholder pour le texte d’espace réservé que vous souhaitez afficher

Vous pouvez également définir un modèle de sujet dans chaque catégorie.

Dans la boîte de dialogue Modifier la catégorie, sélectionnez Modèles de sujet. Vous pouvez ajouter un modèle personnalisé pour votre catégorie.

Cela fonctionne bien, MAIS l’utilisateur doit supprimer le texte du modèle avant de pouvoir commencer à rédiger son message.

Ce composant de thème vous permet d’afficher le texte du modèle de sujet comme un texte d’espace réservé (filigrane) plutôt que comme du texte modifiable. Il vous suffit de cliquer dans la zone et de commencer à taper.

Il peut être configuré pour afficher tous les modèles de sujet comme des espaces réservés, ou vous pouvez le faire au cas par cas en ajoutant un indicateur [placeholder] au modèle de sujet.

Installer le composant de thème

Dépôt Git : https://github.com/naidihr/discourse-topic-template-placeholders

Comment installer un thème ou un composant de thème ?

Crédits

Merci à @merefield pour la refactorisation de l’élément JQuery afin d’utiliser le framework Ember et le noyau de Discourse.

Veuillez noter que la version mise à jour a été testée uniquement pour fonctionner sur les versions de Discourse à partir de 2.4.1. Si vous utilisez une version antérieure de Discourse, essayez la version originale, qui a été testée sur la version 2.3.10.
Dépôt de la version originale : https://github.com/naidihr/discourse-topic-template-placeholders_original

[Rhidian (Rhidian Bramley)]

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.

[Johani (Joe)]

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.

Split up theme Javascript into multiple files

Complex theme javascript can be split into multiple files, to keep things nicely organised. To use this functionality, simply add files to the /javascripts folder in your theme directory. Currently, these files can not be edited from the Discourse UI, so you must use the Theme CLI or source the theme from git. Javascript files are treated exactly the same as they are in core/plugins, so you should follow the same file/folder structure. Theme files are loaded after core/plugins, so if the filen…

[merefield (Robert)]

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

remove use of jquery and avoid use of timeout

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

[Rhidian (Rhidian Bramley)]

Thanks Robert. I’ve merged that PR. Much appreciated

[sunjam (james.network)]

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

[davidkingham]

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.

[merefield (Robert)]

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 …

[davidkingham]

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

[Johani (Joe)]

@merefield

RESULT: Composer is NOT populated with the Template

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.

[merefield (Robert)]

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.

[Rhidian (Rhidian Bramley)]

@merefield

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

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…?

[merefield (Robert)]

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

[merefield (Robert)]

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.

[Rhidian (Rhidian Bramley)]

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?

[davidkingham]

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?

[merefield (Robert)]

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.

[Rhidian (Rhidian Bramley)]

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

[merefield (Robert)]

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!

[Ryan_NR (Ryan)]

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:

become like this when enabled:

---

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