The discussion revolves around a user, Stelmsind, trying to customize the preferences page in Discourse by overriding the user/preferences template in the </head> template section. However, they encounter issues with some elements not working properly.
DeanMarkTaylor suggests that the problem might be due to an outdated version of Discourse and a mismatched version of preferences.hbs.
Mittineague points out that the highlighted issues are related to missing text strings for client.en.yml tokens and asks for clarification on what Stelmsind is trying to achieve.
Stelmsind realizes their mistake and apologizes for the noise, explaining that they used an outdated version of preferences.hbs from GitHub.
Stelmsind further explains their goal of integrating Discourse with their main site and acknowledges their current approach is hacky, but plans to make cleaner changes once they have a clearer idea of what they want to achieve.
I’m trying to apply some additional customisation to the preferences page, but I’m having some difficultly. I’ve created this in the ‘’ template section:
<script type='text/x-handlebars' data-template-name='user/preferences'>
contents of 'app/assets/javascripts/discourse/templates/user/preferences.hbs'
</script>
But this doesn’t work 100%. There’s a couple of elements of the preferences page that don’t work properly.. I’ve highlighted them below.
Oh yes, of course! I took the preferences.hbs off of github. It was late and it didn’t occur my addled brain that it might not be the same as in my installation.
Thanks the reply. I’m just starting to explore ways to make discourse seem better integrated with our main site. There are a few areas if overlap, such as dual preferences/profile pages, two notification systems etc.
I’m doing this in quite a hacky way at the moment, as you can see However, once I have a clearer idea of what we want to achieve then I’ll attempt a cleaner set of changes.