Solved New param Topic template in category settings: what it is used for?

Hello,
I discovered a new param in category settings called Topic template.
What is it used for? Can anyone give an example?


Thanks.

This is a default text that will be displayed on a new topic in the text field (see image).

Wow, this is a great feature! Thank you for the reply.

Hi @rich,
I've tried to test this feature but unfortunately got no success.
Please have a look at screenshots:

A Topic template was added to the demo category "Welcome mat".



When I create a new topic in this category, I do not see predefined text in text-area.

Kunena 5.1.5
Crypsis BS3 (no WYSIWYG, but BBCode editor is enabled in template settings)
PHP 7.2.1

I see on your image also not the first column (see image), so I think, the editor is loaded from the cache.
Click on New Topic, then press Strg+F5. If does not help, then empty also the Joomla cache.

Hi rich,

I've cleared browser cache and now all works fine.
Thank you for the tip.

I was surprised with a modal window that appears with two buttons "Replace content / Replace content and keep existing". Would be good to avoid such modal window since if the user is creating a new topic, there is no need to keep the existing (empty) field, so this is an extra action.

Btw, I am using a custom template which does not support this feature.
Can anyone give an URL on Github issue where the Topic template was added or give an advice which template file to investigate?
/components/com_kunena/template/crypsisb3/layouts/topic/ ... (which one is next? edit/default.php ?)

Thanks.

github.com/Kunena/Kunena-Forum/commit/af...f4c24fa64f04a2a8438c
github.com/Kunena/Kunena-Forum/commit/03...f91a741dacb7f9f38e5d
github.com/Kunena/Kunena-Forum/commit/38...45861d2048d499cbfcd6
I'm not sure whether this links help you. There have been some corrections in the meantime, you can find the fixes with the keyword "Topic template" on Git.
github.com/Kunena/Kunena-Forum/issues?q=...template+label%3Abug

I will try.
Thank you again, @rich!