Hi there,
It appears that the template tool (
) is broken on our topic creator. We are able to access it when we go into safe mode, though.
AI-generated summary
In a support thread titled “Template Button not working,” putty reports that the template tool (
) is broken in their topic creator, though it works in safe mode. pfaffman suggests checking the JavaScript console for errors and suspects a deprecated plugin like “canned replies.” JammyDodger advises using different safe modes to isolate whether a plugin or theme/theme component is causing the issue, especially those affecting the composer. putty confirms they don’t use the suspected plugin and continues troubleshooting. pfaffman follows up asking if any JavaScript errors are visible. putty reports that disabling themes/theme components in safe mode resolves the issue and identifies a specific composer-modifying component — authored internally — as the culprit, promising to investigate further. Heliosurge adds that on their instance, the issue was linked to theme components ‘scrollable content’ and ‘md-composer extras.’ The issue appears to stem from theme components interfering with the composer, not core functionality or deprecated plugins. Community collaboration successfully narrowed the cause to a custom theme component, highlighting the value of safe mode diagnostics and console error checks.
I had a client with the same problem. I think it was the deprecated “canned replies” plugin. Have a look in the Javascript console and you should see an error.
To narrow it down, you could use the different flavours of safe mode to isolate it to a plugin or a theme/theme component.
Do you have any likely candidates that influence the composer in any way?
Unfortunately we don’t use this plugin. The hunt continues!
You donj’t see any errors in the javascript console?
Disabling the themes/theme components in safe mode seems to resolve it.
I was able to narrow down which component modifies the composer. Disabling that resolved the problem. It looks like someone on my team is the author, so I’ll see if they can figure out what specifically broke it.
Thank you @pfaffman & @JammyDodger for the help!
On mine it seemed to be caused by Customization > Theme component 'scrollabke content" & ‘md-composer extras’