Thanks guys, after updating and a hard refresh it is now working as expected!
「いいね！」 2
Just started testing this component; thanks! I’d curious about adding Placeholder text to private messages. Has anyone tried that?
Private messages have the same default placeholder text as Topic posts. It can be changed by the site administrators under the admin settings Customize > Text. Search for js.composer.reply_placeholder - as shown at the top of this thread.
If you use this component to customise the placeholder text for each Topic Category, the default placeholder text should only apply to the Private Messages.
「いいね！」 1
This theme component is really cool. I’ve been trying to find a way to give my users a little more guidance when they create a topic, and would like to make the experience more like completing a form.
Right now, this theme component makes it so that all text that is preloaded in a topic is a single placeholder. So, once a user types anything in the topic composer, all of the placeholder text goes away.
Would it be possible to have it so that there are different placeholders on the page? For example, the topic template could load a separate placeholder for:
“Name”
“Location”
“Issue”
So that when the users types in their name, the other placeholders for Location and Issue stay there, until the user types in their spots too?
The default Discourse Topic Template Text stays whilst the user is typing. It sounds like that is what you need?
The Placeholder Approach:
What I (and others?) would be looking for would behave more like placeholders in a form (meaning with separate form elements).
The basic default behavior now would allow me to list out different sections of the form, like what I wrote (“name”, “location”, and “issue”), but the default template behavior has the same problems as noted before–markdown makes it confusing and user can break it easily.
I think the ideal would be like a normal form, where there is a placeholder for each section (name, location, and issue), but (here’s the difference) the sections would behave independently. So when the user clicks on the name section, the placeholder “name” disappears, but the other sections stay until the user clicks on those too.
I could imagine this being possible (?) with jquery. Each section would have to have its own div with id, and then jquery would allow showing or removing the text of that particular id when the user clicks on it. This would require adding divs into the textarea, however, and I’m not sure how to do that.
I’m investigating that here.
The Template Approach
Probably an alternative would be that the section headers don’t “disappear” when the user clicks. So the section headers (example: Name, Location, and Issue) would be text that would stay on the page. To make it more form-like, compared to the current template default:
- The section header text could not be edited by the user (ie,
contenteditable="false") - The section break points could not be removed by the user
- There would be space below the section header where it’s clear the user can type. In the current default template, they’d have to go to where the text is, hit
return, to create space to type.
Perhaps this is the easier way to do it?
I found this setting only apply on first post not working.
It doesn’t work if I want all posts in a topic have the same placeholder and deactivate the setting. I get a standard placeholder in this case.
Any possibility of having a placeholder specific to replies (not the first post in a topic)? I’m hoping to give users more guidance on what can be in a reply, and a placeholder that pops up in a reply would be helpful.
「いいね！」 4
返信の場合にのみ、プレースホルダーテキストが複数行ある場合にのみ機能することがわかりました。コードが少し複雑なため、理由はまったくわかりません。
追伸
その間、ブラウザのコンソール警告を停止するための小さなPRを提出しました。
「いいね！」 2
Nathan、マージありがとうございます。
「いいね！」 2
プレースホルダーテキストが表示されない問題が発生しています。何が足りないのでしょうか？
テンプレート：
コンポーネント設定
プレースホルダー/テンプレートテキストが表示されない
「すべてのトピックテンプレートをプレースホルダーとして表示」のチェックを外した場合
テンプレートが編集可能なテキスト（プレースホルダーテキストではない）として表示される
テンプレートテキストを編集すると [placeholder] が含まれる
テンプレートテキストが消える/プレースホルダーテキストがない
これは、プラグイン/コンポーネントがインストールされていないクリーンな Discourse インストール（Discourse 3.4.0）で行っています。
このテーマコンポーネントは機能しなくなったようです。
「いいね！」 3
このコンポーネントは私には動作しなくなりました。
ああ、まあ、動作していないことは確認できます。おそらく、Discourse の最近の大きな変更が原因でしょう。
「いいね！」 1
こんにちは、更新の希望はありますか？
こんにちは 
このテーマコンポーネントを復活させ、最新のDiscourseと互換性を持たせるためのPRを作成しました 
「いいね！」 5
@Donさん、ありがとうございます。プルリクエストをマージしました。動作するかテストしてください。
「いいね！」 2