Technical Support

@pitaj hmm...looking more closely at this...updating the dependencies might do it. But if not, that one seems to use the Amazon published SDK so it should definitely work. Thanks!

@florian-rubel did you ever figure this one out?

Further update - Problem appears to be fixed. One difference in browser errors is the prepareFooter error: Uncaught ReferenceError: highlight is not defined at HTMLDocument.prepareFooter ((index):3508) Further digging showed that the prepareFooter() is where custom javascript is placed and that was the issue. Custom java script was breaking the page during prepareFooter() which killed the reply functionality (along with a lot of other things). The java script was there to add functionality to highlight.js for syntax highlighting. now to dig into what has changed with highlight.js in the latest version.

You can click on the headers in the table to change the sorting. Inactive filter was just displaying users who haven't logged in the past x months so you can change sorting to last online sorted by ascending and see inactive users.

@baris said in Skin Switcher in User Settings: https://github.com/pichalite/nodebb-theme-slick/commit/c304310f7fbb23a452664d04d81b6b24fed61d0d Thank you!

@dogs This looks kind of cool. Lord knows I am not a fan of systemd but it seems like the most practical choice for NodeBB startup/restart under systemd based systems. Which is pretty much all Linux nowadays. Yeah, I get void, alpine and gentoo exist. Other systems, however.... Seems like this pm2 could be a nice win over trad rc scripts. Or just use something Illumos based and SMF. Maybe Tribblix or Hipster? Oh... snap.... too many folks nowadays favor writing unportable software in the name of "efficiency". Others may just call it lazyness.... In any case, nice find.

@ape if you're using that hook, the routes are mounted to /api/v3, so the definition you provided would end up being accessible at /api/v3/test123

@baris That's it! That was the problem, I changes the directory layout to something more familiar to me. To test the solution I created a directory 'public' and saved a 'tmp.js' to it. I started grunt, changed the file and it recognized the change. Thanks for your help!

Hi, I would like to display a scrollbar to the right of topics. NodeBB already has the scrollbar but it's embedded in the pagination block in the bottom right corner. I tried modifying the code in the scrollbar.tpl file (persona template) but it did not work which is not surprising since the code in there is just an HTML container. Any help would be appreciated.

@waugh have you considered upgrading nodebb to the latest version? I think that will fix your issue

Your vm may have suffered an unclean shutdown. Note "may". In absence of more info, a couple things to try. If you have nodebb set up to be launched via systemd, disable that. And then stop just for good measure and then disable dependencies: systemctl disable nodebb systemctl stop nodebb systemctl disable nginx (sub apache if using apache) systemctl disable mongod (or whatever db backend you're using Then reboot the vm. When it comes back up we're going to restart all that in reverse order, verifying each is up and running before proceeding to next: systemctl status mongod systemctl status nginx systemctl status nodebb Those should now all report "disabled". So let's start them up, verifying each launches w/o error before proceeding to next systemctl start mongod If the startup messages are greek to you or pass by too quickly: systemctl status mongod Should report something very close to this: [root@forums ~]# systemctl status mongod ● mongod.service - MongoDB Database Server Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-03-05 06:57:52 UTC; 1 weeks 6 days ago Docs: https://docs.mongodb.org/manual Process: 457777 ExecStart=/usr/bin/mongod $OPTIONS (code=exited, status=0/SUCCESS) Process: 457762 ExecStartPre=/usr/bin/chmod 0755 /var/run/mongodb (code=exited, status=0/SUCCESS) Process: 457739 ExecStartPre=/usr/bin/chown mongod:mongod /var/run/mongodb (code=exited, status=0/SUCCESS) Process: 457725 ExecStartPre=/usr/bin/mkdir -p /var/run/mongodb (code=exited, status=0/SUCCESS) Main PID: 457824 (mongod) CGroup: /system.slice/mongod.service └─457824 /usr/bin/mongod -f /etc/mongod.conf ‣ 457824 /usr/bin/mongod -f /etc/mongod.conf If that all looks good, try starting nodebb: systemctl start nodebb A status check should look something like this: [root@forums ~]# systemctl status nodebb ● nodebb.service - NodeBB Loaded: loaded (/etc/systemd/system/nodebb.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2021-03-05 06:59:17 UTC; 1 weeks 6 days ago Docs: https://docs.nodebb.org Process: 459055 ExecStart=/usr/bin/env node loader.js (code=exited, status=0/SUCCESS) Main PID: 459071 (node) CGroup: /system.slice/nodebb.service ├─459071 /usr/bin/node /opt/nodebb/loader.js ├─459082 /usr/bin/node /opt/nodebb/app.js If you are getting anything other than "SUCCESS" then stop just be sure: systemctl stop nodebb Then sudo to change to your nodebb user and then go try starting nodebb manually using the "log" flag: cd /where/ever/your/nodebb/lives ./nodebb start -l Then copy/pasta the ensuing spewage so the other gurus in the lurking can deconstruct. Good luck. Once you get this sorted, be sure to re-enable those services else they will not automatically restart after a shutdown/reboot. systemctl enable mongod systemctl enable nginx systemctl enable nodebb I'd even then reboot after that just to be sure all comes back up as expected. Yeah, this is not issue specific but when dealing with unknown glitches it is nice to rule out some low hanging fruit to help isolate.

@pitaj Currently I have problem with google search console.(Couldn't fetch sitemap) → problem with sitemap So I was testing my website with some google tools(testing url in search console, PageSpeed Insights, ...) and search console show error with those files. Just tried to solve my sitemap problem... Still, the problem has not been solved

@dunlix I think it is google's problem https://support.google.com/webmasters/thread/2790050?hl=en just same as my case. answer in this link said Your sitemap can be processed by google ranging from 24 hours to 24 days (even 1 month + in some rare case)

In the event you missed them, I took a couple stabs at some email tutorials. The intent was to provide enough understanding to get you pointed in the right directions rather than get 'er done copy/pasta recipes. Hence, they may or may not be the droids you're looking for: Read first: https://community.nodebb.org/topic/15072/nodebb-email-options Read second: https://community.nodebb.org/topic/15077/nodebb-email-postfix-null-client

@pitaj I meant on a production environment. Thanks though

Welcome email template doesn't append the email footer that has unsubscribe button. Digest email template are working fine with email footer. Does anyone face the same issue?

@julian Thanks for the invitation to contribute. Is there something i should consider regarding the issue / pull request - markup, document structure,...?