Bug Report

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

@crazycells you are right 🙂 thank you.

@eeeee said in restarting nodebb on boot:

can I just run nodebb under nodemon for auto restarts?

It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

@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

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

And now, after all this time 😕 I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block 🤦

.tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; }

And, add this below to make it more specific.

.emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }

@phenomlab said in NodeBB Footer:

@jac and you. Hope all is well and you recover quickly

Thanks pal 😁🤝🏻

@DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.

@phenomlab yes, i can understand. it is working now 🙂