Want to use Sudonix themes ?

[phenomlab]

@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.

[DownPW]

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

keep for now this code

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

[phenomlab]

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

[DownPW]

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;
}

[phenomlab]

@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.

[cagatay]

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

[phenomlab]

@cagatay In your CSS, locate the block starting

.category-card .text-muted.timeago

And remove

margin-left: -180px;

[cagatay]

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.

[phenomlab]

@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.

[cagatay]

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

[phenomlab]

@cagatay you are already using it.

[cagatay]

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.

[phenomlab]

@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.

[cagatay]

This situation does not affect google indexing, does it?

[phenomlab]

@cagatay Not to my knowledge.