Skip to content

NodeBB Theme/Skin Switcher

Solved Customisation
38 2 17.5k 1
  • @phenomlab tried it, CSS class is still not showing. 😞

    wrote on last edited by
    #29

    @Teemberland can you remove all JS and leave the custom CSS with just the basic body class and let me know if that works?

  • @Teemberland can you remove all JS and leave the custom CSS with just the basic body class and let me know if that works?

    wrote on last edited by
    #30

    @phenomlab that doesn’t work either.

  • @phenomlab that doesn’t work either.

    wrote on last edited by
    #31

    @Teemberland ok, there’s definitely something wrong here. Are you sure there’s no errors in the console or you don’t have any script blockers running in your browser that could be interfering with execution?

  • @Teemberland ok, there’s definitely something wrong here. Are you sure there’s no errors in the console or you don’t have any script blockers running in your browser that could be interfering with execution?

    wrote on last edited by Teemberland
    #32

    @phenomlab correct. No console error or script blockers.
    EDIT:
    It shouldn’t matter what theme I use, correct? I’m currently using Slick theme.

    EDIT #2: I added my CSS rule to a widget. I can now see it on the page. Perhaps this is my only work around at this point.

  • @phenomlab correct. No console error or script blockers.
    EDIT:
    It shouldn’t matter what theme I use, correct? I’m currently using Slick theme.

    EDIT #2: I added my CSS rule to a widget. I can now see it on the page. Perhaps this is my only work around at this point.

    wrote on last edited by
    #33

    @Teemberland can you switch to Persona and see if the issue exists there as well ? I know that the Slick theme does have some issues.

  • @Teemberland can you switch to Persona and see if the issue exists there as well ? I know that the Slick theme does have some issues.

    wrote on last edited by
    #34

    @phenomlab BINGO! It does work in Persona. Unfornately, we have to use our custom Slick theme per my company’s request.

    I guess for now I have to put the styles in a widget for it to work. Unless you can think of something else?

  • @phenomlab BINGO! It does work in Persona. Unfornately, we have to use our custom Slick theme per my company’s request.

    I guess for now I have to put the styles in a widget for it to work. Unless you can think of something else?

    wrote on last edited by
    #35

    @Teemberland thought as much. I personally don’t use Slick for anything because of the issues it has. However, it’s abundantly clear that this theme doesn’t seem to recognize or inline any css from the ACP which is bizarre.

    The good thing is that there’s nothing wrong with your NodeBB installation, but as you say, you have to use Slick, so the only way this will work is to embed the CSS in a widget. Whilst this works, here be dragons. If you decide to change the theme or have to reset it, the widgets are all removed and placed into the drafts section - you have to put these back manually.

    My last remaining suggestion would be to minify the CSS once you have it finalized as it’s presence in the widget could well affect page load speed.

  • phenomlab phenomlab has marked this topic as solved on
  • @Teemberland thought as much. I personally don’t use Slick for anything because of the issues it has. However, it’s abundantly clear that this theme doesn’t seem to recognize or inline any css from the ACP which is bizarre.

    The good thing is that there’s nothing wrong with your NodeBB installation, but as you say, you have to use Slick, so the only way this will work is to embed the CSS in a widget. Whilst this works, here be dragons. If you decide to change the theme or have to reset it, the widgets are all removed and placed into the drafts section - you have to put these back manually.

    My last remaining suggestion would be to minify the CSS once you have it finalized as it’s presence in the widget could well affect page load speed.

    wrote on last edited by
    #36

    @phenomlab Thanks! I’ll make sure the company is aware of this.

    Thank you for putting up with me, @phenomlab ! I really appreciate all your help. You can mark this as resolved for now.

  • @Teemberland thought as much. I personally don’t use Slick for anything because of the issues it has. However, it’s abundantly clear that this theme doesn’t seem to recognize or inline any css from the ACP which is bizarre.

    The good thing is that there’s nothing wrong with your NodeBB installation, but as you say, you have to use Slick, so the only way this will work is to embed the CSS in a widget. Whilst this works, here be dragons. If you decide to change the theme or have to reset it, the widgets are all removed and placed into the drafts section - you have to put these back manually.

    My last remaining suggestion would be to minify the CSS once you have it finalized as it’s presence in the widget could well affect page load speed.

    wrote on last edited by
    #37

    @phenomlab by the way, I fixed the issue in Slick. I just copied this code from Persona to my header.tpl in Slick.

    {{{if useCustomHTML}}}
    {{customHTML}}
    {{{end}}}
    {{{if useCustomCSS}}}
    <style type="text/css">{{customCSS}}</style>
    {{end}}}
    

    It used to looke like this:

    <!-- IF useCustomHTML -->
    {{customHTML}}
    <!-- END -->
    <!-- IF useCustomCSS -->
    <style type="text/css">{{customCSS}}</style>
    <!-- END -->
    
  • @phenomlab by the way, I fixed the issue in Slick. I just copied this code from Persona to my header.tpl in Slick.

    {{{if useCustomHTML}}}
    {{customHTML}}
    {{{end}}}
    {{{if useCustomCSS}}}
    <style type="text/css">{{customCSS}}</style>
    {{end}}}
    

    It used to looke like this:

    <!-- IF useCustomHTML -->
    {{customHTML}}
    <!-- END -->
    <!-- IF useCustomCSS -->
    <style type="text/css">{{customCSS}}</style>
    <!-- END -->
    
    wrote on last edited by
    #38

    @Teemberland great spot ! You should create a PR for that so they can include it in the official repository.

    Just be aware that any subsequent releases will overwrite your fix without the PR.


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • 2 Votes
    1 Posts
    639 Views
    No one has replied
  • Skins

    Solved Customisation skins
    4
    1 Votes
    4 Posts
    2k Views
    phenomlab
    @OT Yes, I know. Here’s the article. I just finished it https://sudonix.org/topic/542/swatch-theme-changer Please try this in test first before you deploy to live.
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • fading in /tags page

    Solved Customisation nodebb
    32
    1
    30 Votes
    32 Posts
    13k Views
    DownPW
    Fix working perfectly
  • [NodeBB] greeting message

    Solved Customisation css nodebb javascript
    2
    1
    3 Votes
    2 Posts
    2k Views
    phenomlab
    @pwsincd welcome to sudonix, and thanks for the comments. What your looking for is here https://sudonix.com/topic/195/nodebb-welcome-message/3?_=1648295651358
  • NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    33
    4 Votes
    33 Posts
    16k Views
    DownPW
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • [NODEBB] Stats

    Unsolved Customisation plugin stats script
    20
    1
    2 Votes
    20 Posts
    6k Views
    JAC
    @phenomlab said in [NODEBB] Stats: @jac or I land up fixing it I wouldn’t put it past you
  • NodeBB metadata

    Solved Configure nodebb
    4
    2 Votes
    4 Posts
    2k Views
    JAC
    @phenomlab said in NodeBB metadata: @jac Are you sure ? https://www.google.co.uk/search?q=site%3Astockportcounty.fans&sxsrf=AOaemvLwnaZL-PliU_2dBOg_Eo1pMVhBjg%3A1638982328139&source=hp&ei=uOKwYeatBcOsad3yp7AE&iflsig=ALs-wAMAAAAAYbDwyLBSDcG5XYoFCKwQFhgz94wTxOcV&ved=0ahUKEwjm6dX71NT0AhVDVhoKHV35CUYQ4dUDCAk&uact=5&oq=site%3Astockportcounty.fans&gs_lcp=Cgdnd3Mtd2l6EAM6BAgjECc6CwgAEIAEELEDEIMBOg4ILhCABBCxAxDHARCjAjoRCC4QgAQQsQMQgwEQxwEQowI6BQguEIAEOggIABCABBCxAzoFCAAQgAQ6CAguELEDEIMBOgsILhCABBDHARCvAToICC4QgAQQsQM6BQgAELEDOgsILhCABBDHARDRAzoLCAAQgAQQsQMQyQM6BQgAEJIDUABYySZg0CdoAHAAeACAAW2IAa0NkgEEMjMuMpgBAKABAQ&sclient=gws-wiz Fair enough 🤪🤪.