Customisation

@Panda said in Interesting Widget code, but can’t fetch API:

How did you drop that widget into the post there?
I hadnt seen this BSgenerator anywhere on sudonix site, do you use it somewhere already?

Yes, here

https://sudonix.org/topic/414/corporate-bullshit-generator?_=1687774393044

It’s not a “post” or “topic” in the common sense. It is actually a page in it’s own right and leverages nodebb-plugin-custom-pages. This in turn creates a new “route” which behaves like a page, meaning it is then exposed for widgets.

@Panda said in Interesting Widget code, but can’t fetch API:

Also can you explain more what you mean by calling the code externally. In my API call example, how would I go about doing that?

By this, I mean create all the required code in an external JS file that is reachable by the NodeBB instance - so, in “public” for example - or in my case /public/js. The widget then “calls” that file and because it runs outside of the scope of NodeBB, you just need to return the values to the widget.

Hope this makes sense?

Fix working perfectly 👍 🙂

No no, I said that in the sense that he told me it was simple ^^
I was able to see that this was not the case by targeting the elements he had advised me.

@cagatay this relates to a change the css classes used for the brand header meaning it will now float to the left instead of right.

If you’d like to retain the original behavior, you can add this css class

Further information here

https://community.nodebb.org/topic/17090/manual-build-a-custom-header-in-harmony/19?_=1684069325296

@phenomlab forget it, look likes good with your codes.

@mventures said in NodeBB: Consent policy popup:

How did you implement this consent pop-up?

This is located in /admin/settings/cookies

@mventures said in NodeBB: Consent policy popup:

Does it appear every new day for a user who has accepted it?

No. It places a cookie on the machine of the user who visits the site, and once they accept it, it doesn’t appear again unless you select

0bda6e07-efca-4039-a132-c94060a6fec4-image.png

@eeeee if you’re using the console, you could try

node app.js > app.log 2>&1

This would redirect stdout to a file named app.log and redirect stderr to stdout.

I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log.

Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.

@mventures I’ve not done anything here.

@cagatay ok. You should use a copy of the production database or a completely new one. Never share a database between two instances of NodeBB.

@phenomlab said in Footer bar add center text:

div#console-nav-tab

Ah ok test with bottom: 0px !important; idem

@DownPW very useful tip. Thanks

@Sala ok, but that’s still the same loop which is going to have an impact on the CPU.

@cagatay

Just add margin-left on the element like @phenomlab said to you :

aa08c62b-4223-4cba-8c0f-c73d50474c0d-image.png

Maybe @phenomlab have a better way

@Sala This should look better

e5cec20e-be36-4ee8-9129-fd11ad4656ac-image.png

You can increase the top and bottom padding by increasing the values above.

@cagatay it should be created as soon as you start the instance. See below

https://docs.meilisearch.com/learn/security/master_api_keys.html#communicating-with-a-protected-instance

@cagatay Good question, but one that’s likely best answered by the devs themselves. Could easily be done with a simple jQuery regex but that would really just be painting over rotten wood.

@cagatay ok

@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