Skip to content

[NODEBB] Reply Button/arrow answer

Solved Customisation
25 2 11.6k 1
  • wrote on last edited by DownPW
    #2

    @downpw said in [NODEBB] Reply Button/arrow answer:

    .composer .title-container .composer-submit {
    border-radius: 0px 5px 5px 0px !important;
    }

    Hmmm. If I delete !important on code

    .composer .title-container .composer-submit {
       border-radius: 0px 5px 5px 0px ;
    }
    

    It seems to be good for the arrow :
    6b07cbf8-aaf5-411c-9538-67d0fd4d3fb0-image.png

    But the Reply Button went back to how it was before 😞 :
    05296857-48bc-41ea-9200-28d19cf54013-image.png

    the 2 buttons are linked to the same CSS variables but I can’t tell them apart

  • @downpw said in [NODEBB] Reply Button/arrow answer:

    .composer .title-container .composer-submit {
    border-radius: 0px 5px 5px 0px !important;
    }

    Hmmm. If I delete !important on code

    .composer .title-container .composer-submit {
       border-radius: 0px 5px 5px 0px ;
    }
    

    It seems to be good for the arrow :
    6b07cbf8-aaf5-411c-9538-67d0fd4d3fb0-image.png

    But the Reply Button went back to how it was before 😞 :
    05296857-48bc-41ea-9200-28d19cf54013-image.png

    the 2 buttons are linked to the same CSS variables but I can’t tell them apart

    wrote on last edited by
    #3

    @downpw Something like this should work

    button.btn.btn-primary.composer-submit {
        border-top-right-radius: 4px !important;
        border-bottom-right-radius: 4px !important;
    }
    
  • phenomlab phenomlab has marked this topic as solved on
  • DownPW DownPW has marked this topic as unsolved on
  • wrote on last edited by DownPW
    #4

    @phenomlab

    I’m so sorry, It seem we have the same problem 😞

    Just this :

    button.btn.btn-primary.composer-submit {
        border-top-right-radius: 4px !important;
        border-bottom-right-radius: 4px !important;
    }
    

    Its’ ok for Submit Button when I reply to on existant topic
    54629c01-c5eb-4d11-b4de-dc43462b701d-image.png

    But it’s not Ok when I create a New Topic (When you have the arrow button at the right of the Submit Button) :

    0393d71b-f011-43c1-9086-346605eedfb0-image.png

    13a482d1-2587-498a-b1a5-736cdf73659d-image.png

  • @phenomlab

    I’m so sorry, It seem we have the same problem 😞

    Just this :

    button.btn.btn-primary.composer-submit {
        border-top-right-radius: 4px !important;
        border-bottom-right-radius: 4px !important;
    }
    

    Its’ ok for Submit Button when I reply to on existant topic
    54629c01-c5eb-4d11-b4de-dc43462b701d-image.png

    But it’s not Ok when I create a New Topic (When you have the arrow button at the right of the Submit Button) :

    0393d71b-f011-43c1-9086-346605eedfb0-image.png

    13a482d1-2587-498a-b1a5-736cdf73659d-image.png

    wrote on last edited by phenomlab
    #5

    @downpw Yes, I see what you mean. I’d “cheat” a little here and use some positioning to create a faux effect. This should do it

    .btn-group>.btn:last-child:not(:first-child), .btn-group>.dropdown-toggle:not(:first-child) {
      margin-left: -3px;
    }
    .btn-group>.btn:not(:first-child):not(:last-child):not(.dropdown-toggle):hover {
      border-top-right-radius: 0px;
      border-bottom-right-radius: 0px;
    }
    button.btn.btn-primary.composer-submit:hover {
        border-top-right-radius: 4px !important;
        border-bottom-right-radius: 4px !important;
    }
    .btn .caret {
      margin-left: 2px;
    }
    .btn-group>.btn:not(:first-child):not(:last-child):not(.dropdown-toggle) {
      border-radius: 0px;
      border-top-right-radius: 4px;
      border-bottom-right-radius: 4px;
      margin-left: 0px;
    }
    

    It’ll look like this on a reply post

    ea6a7331-a2a9-42c7-93d4-60443f4296fb-image.png

    And like this on a new post

    b0f44193-63db-4c3d-8c98-a85c7344d849-image.png

    I’ve set the CSS here on Sudonix so you can see it in action. Give it a try.

  • wrote on last edited by DownPW
    #6

    @phenomlab

    Yes.

    Just your mouse over on Submit button when you reply to a topic to fix :

    818eb504-86e7-4ebf-bc0b-8466637811ff-image.png

    Result is great, I will test tonight.
    I’m at work at the moment.

  • @phenomlab

    Yes.

    Just your mouse over on Submit button when you reply to a topic to fix :

    818eb504-86e7-4ebf-bc0b-8466637811ff-image.png

    Result is great, I will test tonight.
    I’m at work at the moment.

    wrote on last edited by
    #7

    @downpw Great. Let me know when back, as I’ll need access to your VM for the fonts issue we need to work on

  • wrote on last edited by DownPW
    #8

    I edit my post just one Fix for reply button on mouse over

    Ok for Font tonight at 17h00 😉

  • I edit my post just one Fix for reply button on mouse over

    Ok for Font tonight at 17h00 😉

    wrote on last edited by
    #9

    @downpw said in [NODEBB] Reply Button/arrow answer:

    I’m edit my post just one Fix for reply button on mouse over

    😕 thanks - completely missed that. I’ll amend the original post.

  • wrote on last edited by
    #10

    Ok wait for fix and test after ^^

  • Ok wait for fix and test after ^^

    wrote on last edited by
    #11

    @downpw Updated the original post, and applied CSS here so you can test.

  • wrote on last edited by
    #12

    Great 😉

  • wrote on last edited by
    #13

    It worked on my default theme. 🙂
    It seem to have border effect on my custom themes 😞

  • It worked on my default theme. 🙂
    It seem to have border effect on my custom themes 😞

    wrote on last edited by
    #14

    @downpw do you have anything in your custom CSS that is overriding this ?

  • wrote on last edited by DownPW
    #15

    Lot of variable. Hard to debug… a little lost
    I’ve been on it for 2 hours !!

    for default theme I must add this for delete border to Reply Putton on topic

    .btn-primary {
        color: #fff;
        background-color: #337ab7;
        border-color: transparent;
    }
    
  • Lot of variable. Hard to debug… a little lost
    I’ve been on it for 2 hours !!

    for default theme I must add this for delete border to Reply Putton on topic

    .btn-primary {
        color: #fff;
        background-color: #337ab7;
        border-color: transparent;
    }
    
    wrote on last edited by
    #16

    @downpw why do you need to delete the border ?

  • wrote on last edited by
    #17

    Because it is visible

    beaee397-4637-4609-b223-7a5b6b0d5034-image.png

  • Because it is visible

    beaee397-4637-4609-b223-7a5b6b0d5034-image.png

    wrote on last edited by
    #18

    @downpw I see. Another hack here is to set the border colour to be the same as the background colour.

  • wrote on last edited by DownPW
    #19

    @downpw said in [NODEBB] Reply Button/arrow answer:

    .btn-primary {
    color: #fff;
    background-color: #337ab7;
    border-color: transparent;
    }

    .btn-primary {
        color: #fff;
        background-color: #337ab7;
        border-color: #337ab7;
    }
    
  • @downpw said in [NODEBB] Reply Button/arrow answer:

    .btn-primary {
    color: #fff;
    background-color: #337ab7;
    border-color: transparent;
    }

    .btn-primary {
        color: #fff;
        background-color: #337ab7;
        border-color: #337ab7;
    }
    
    wrote on last edited by
    #20

    @downpw and does that not work ?

  • wrote on last edited by DownPW
    #21

    Yes that work too 🙂
    I must do work on bug on other custom CSS


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
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlab
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Error install plugin

    Solved Customisation plugin nodebb
    8
    1
    1 Votes
    8 Posts
    6k Views
    DownPW
    @pobojmoks Not WP plugin but nodeBB but it a known bug
  • [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] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    5k Views
    phenomlab
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.
  • [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] CSS Style Sheets SelectBox

    Locked Solved Customisation css
    112
    24 Votes
    112 Posts
    63k Views
    phenomlab
    @DownPW as discussed in PM Seems to have been solved with the new JS code that you added allowing the version CSS file change!! Cache problem therefore with the JS of the Switcher theme Based on this, I will close this thread and reference https://sudonix.com/topic/207/nodebb-help-for-my-custom-css/27
  • NodeBB Design help

    Solved Customisation
    8
    3
    2 Votes
    8 Posts
    4k Views
    phenomlab
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.