Skip to content

Want to use Sudonix themes ?

Chitchat
  • @cagatay yes, but I’d reiterate the concerns I’ve raised above in the sense that it may impact the flow of other elements.

    Essentially, this is fm going to be a relatively simple CSS change.

  • Mark hi,
    after upgrading 3.9 i have some problems with my web site.
    Pls see below photos of my problems;

    image.png

    Also recent post and topics options i dont see my header

    image.png

  • @cagatay This will be because of the below changes

    https://community.nodebb.org/topic/18292/nodebb-3.9.0

    It’s related to the brand header section here

    <button type="button" class="btn-ghost-sm d-flex gap-2 dropdown-toggle" data-bs-toggle="dropdown"
    

    It needs to be changed to

    <button type="button" class="btn btn-ghost btn-sm d-flex gap-2 dropdown-toggle" data-bs-toggle="dropdown"
    

    I’ve made this change on your site, but you’ll also need some additional CSS. This ought to do it, and it’s been also applied to your forum.

    .btn-ghost {
        --bs-btn-hover-border-color: var(--bs-body-navbar-active);
        --bs-btn-active-bg: var(--bs-body-navbar-active);
    }
    
  • Of course, I am the same problem I have change the css class button on widget brand Header

    except that I had an offset present on the brand header.

    I did the same manipulations but I cannot remove this shift that we see on the screen.

    Any idea how to remove this @phenomlab ?

    Before :
    daed0cbc-7791-44eb-a1c1-28e4168051e4-image.png

    After upgrade :

    1d3ffc95-51eb-43f6-beef-df34161af0da-image.png

  • @DownPW Is this on your live site, or development? I cannot see any issue?

    EDIT - I see it on your DEV site. Not sure where the additional padding is coming from to be honest, but one quick “fix” would be to target this CSS

    [type=button]:not(:disabled), [type=reset]:not(:disabled), [type=submit]:not(:disabled), button:not(:disabled)
    

    And use this

    [type=button]:not(:disabled), [type=reset]:not(:disabled), [type=submit]:not(:disabled), button:not(:disabled) {
        cursor: pointer;
        margin-top: 0.5rem;
        margin-bottom: 0.5rem;
    }
    

    I think you may have added

    button.btn.btn-ghost.btn-sm.d-flex.gap-2 {
        padding-top: 0.8rem;
    }
    

    Although this isn’t very elegant as padding will in fact make the button much larger.

  • yep in dev, always for test before upgrade prod 😉

    @phenomlab said in Want to use Sudonix themes ?:

    I think you may have added

    button.btn.btn-ghost.btn-sm.d-flex.gap-2 {
    padding-top: 0.8rem;
    }

    Yep you’re right my friends.

    But your method seems better :

    [type=button]:not(:disabled), [type=reset]:not(:disabled), [type=submit]:not(:disabled), button:not(:disabled) {
        cursor: pointer;
        margin-top: 0.5rem;
        margin-bottom: 0.5rem;
    }
    

    Thanks

    EDIT : ha noooo your code broke the “Answer” Button

    96be1a13-ad61-4065-b02d-4ef2b4a85b0c-image.png

    keep for now this code

    button.btn.btn-ghost.btn-sm.d-flex.gap-2 {
    padding-top: 0.8rem;
    }

  • @DownPW that’s because it’s targeting the button type. Just change the post button class.

  • hmm sorry don’t understand

    Edit :

    like this maybe ?

    .btn.btn-ghost.btn-sm:not(:disabled) {
        cursor: pointer;
        margin-top: 0.5rem;
        margin-bottom: 0.5rem;
    }
    
  • @DownPW Yes, that will work fine. What I meant was that the original CSS I provided targets [type=button] so would impact all others on the page in addition to the intended target.

  • @phenomlab i have some problems with my below items when selected this type of tree;

    image.png

  • @cagatay In your CSS, locate the block starting

    .category-card .text-muted.timeago
    

    And remove

    margin-left: -180px;
    
  • Mark hi,

    I know that you also update your own css and js along with nodebb’s updates but mine is old one when we first set it up.

    I would like to your help to use your current css and js codes if its possible?

    Thank you for your helping.

  • @cagatay

    @cagatay said in Want to use Sudonix themes ?:

    I know that you also update your own css and js along with nodebb’s updates

    I do update the CSS and JS here, but it’s not in line with NodeBB releases. All of the code I have written will work with prior releases, with the exception of Chat Threading, which requires a specific hook not present in some early versions. Again, this would still work, but not at full capacity.

    @cagatay said in Want to use Sudonix themes ?:

    mine is old one when we first set it up

    It’s not “old” - it just isn’t the latest code. In fact, the code running on your website is not advertised anywhere else, so in fact, is newer than the Git links in this post.

    @cagatay said in Want to use Sudonix themes ?:

    I would like to your help to use your current css and js codes if its possible?

    Possible, yes, but not yet. There are still some bugs in the code branch I’m using here, and I don’t want to introduce complexities into your installation - particularly when I know they exist, and you’d be left with issues that your users then have to put up with.

  • thank you for your advise Mark.
    may i use your font ? what i have to do for it?

  • @cagatay you are already using it.

  • i have many minor problems shown below photo, how can i fix it?
    Chrome is moving towards a new experience that lets people make an informed choice with respect to third-party cookies.

    image.png

  • @cagatay This isn’t related to NodeBB, but how the Chrome browser itself behaves - see below

    Yes, Google Chrome is shifting towards a more privacy-focused approach, particularly in how it handles third-party cookies. This change is part of a broader industry trend towards improving user privacy and transparency, as seen in regulations like the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

    Key elements of Chrome’s new approach include:

    • Phasing out third-party cookies: Chrome has been working on a plan to phase out third-party cookies entirely, which are often used by advertisers and trackers to follow users across websites. This is part of Google’s Privacy Sandbox initiative.

    • User control and transparency: Chrome will provide users with more detailed options and controls over how third-party cookies are used. This will allow users to make an informed decision about which cookies they want to allow or block, helping them better understand how their data is being used.

    • Privacy Sandbox: Instead of third-party cookies, Google is introducing alternatives, like FLoC (Federated Learning of Cohorts), which aims to deliver relevant ads without exposing individual users’ browsing history to advertisers. FLoC is part of Privacy Sandbox, which focuses on creating new privacy-preserving mechanisms for digital advertising.

    • Better Consent Experiences: Chrome is also expected to improve how websites prompt users to give consent for cookies, reducing “cookie fatigue” and making the process more straightforward.

    This new experience is expected to improve user privacy without entirely disrupting the ad-supported web ecosystem, which depends heavily on tracking technologies.

  • This situation does not affect google indexing, does it?

  • @cagatay Not to my knowledge.


Related Topics
  • Who uses Flarum?

    Chitchat
    22
    7 Votes
    22 Posts
    400 Views

    @Madchatthew I use it here. It is faster, but not sure if that extends to build times.

  • SEO and Nodebb

    Performance
    2
    2 Votes
    2 Posts
    329 Views

    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example

    https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1

    However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts

    https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365

    And also

    https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164

    It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”.

    Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.

  • NodeBB v3 Chat Very Slow

    Moved Performance
    47
    11 Votes
    47 Posts
    4k Views

    @DownPW Seems fine.

  • Custom badges

    Solved Customisation
    103
    49 Votes
    103 Posts
    11k Views

    Perfect 😉

  • How to fix size of photos & videos NodeBB

    Solved Customisation
    7
    3 Votes
    7 Posts
    669 Views

    @crazycells pleasure. Using percentages makes much more sense in this case. It’s the same argument with px vs pt vs em with fonts, margins, padding, etc., in the sense that em is generally preferred over px and pt

    https://stackoverflow.com/questions/609517/why-em-instead-of-px

  • Fresher in Nodebb install

    General
    24
    15 Votes
    24 Posts
    2k Views

    @Hari I’ve been reading a lot about APO. Looks impressive.

  • Error install plugin

    Solved Customisation
    8
    1 Votes
    8 Posts
    615 Views

    @pobojmoks

    Not WP plugin but nodeBB but it a known bug

  • Social icon (Nodebb)

    Solved Customisation
    7
    0 Votes
    7 Posts
    1k Views

    @phenomlab said in Social icon (Nodebb):

    @jac I just tested my theory around using the OG image, and according to the Twitter card validator, it works fine

    73e805e1-997b-41bf-9259-51c5052ca8fc-image.png

    fixed 🙂