Just found this thread and wanted to say thanks for updating the hover text.

Over at mangolass.it (managed by @scottalanmiller) we have long had problems with search just completely sucking.

Has anyone ever looked into the feasibility of adding the ability to have tags on individual posts and not just on topics?

@djcyry there is never a reason not to use SSL anymore. The benefit is that the data flowing between my device and your server is encrypted and no one can just slurp up all the data at a random router along the way and see my my stuff.

Yeah most forums are public and such, but not all.

@dannydk6-0 in admin ports. Settings -> Posts

@scottalanmiller said in Tags for posts in addition to topics:

Tags on posts could be pretty useful, I agree.

With the way some topics change course midstream tags on post would be awesome over there.

The mangolassi.it community has a thread with nearly 55800 posts.

This community had nothing imported. The community was formed 4 years ago on NodeBB.

May 9, 2014  /  Water Closet

What Are You Doing Right Now

@jaredbusch said in What Are You Doing Right Now: @thwr said in What Are You Doing Right Now: @jaredbusch said in What Are You Doing Right Now: Linking no this topic over on the NobeBB community. Because? Number of posts? Yeah some started a thread a...

created a pull request on the instructions.
https://github.com/NodeBB/nodebb-english/pull/68

sorvani created this issue in NodeBB/nodebb-english

closed updated the instructions to work on CentOS 7 #68

@Kowlin said:

@exodo any reason you want a option to disable it?

Maybe not a disable, but instead make a max participant value. If the forum admin sets it to 2, then it would be no different than now.

I really want the feature. I cannot count the number of times I have had a chat going and then had to either backfire things to another person, or take it to another medium (Skype/hangouts) in order to get a group chat going.

Switch to master and see if the problem goes away.
git checkout master

See this: https://community.nodebb.org/topic/9904/fresh-install-error-cannot-login-register-js-reference-error

@NodeForumGod said in So Is NodeBB stable?:

So Is NodeBB stable?

I installed it at one time and it stops moments later.

It made me feel not so trusting it.

Is the software stable? Or Am I doing it wrong?

You are doing something wrong for sure.

I have been running nodeBB for two years or so for my D&D Campaign.

Also the Mangolassi.it community has been running it for nearly 3 years. They have a shit ton of traffic and posts daily.

@JaredBusch said in How can I migrate from redis to postgresql/mongodb:

Found a pull request for nodebb-plugin-import that gives it postgresql capability.

Well, it seem that I cannot install v1.12.1 as required by this plugin.

npm never successfully builds.

[[email protected] nodebb]$ sudo -u nodebb ./nodebb setup
package.json not found.
Populating package.json...
OK
Dependencies outdated or not yet installed.
Installing them now...

npm notice 
npm notice New minor version of npm available! 8.3.1 -> 8.12.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.2
npm notice Run npm install -g [email protected] to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/pg
npm ERR!   [email protected]"^7.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer [email protected]"^8" from [email protected]
npm ERR! node_modules/pg-cursor
npm ERR!   [email protected]"^2.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/nodebb/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nodebb/.npm/_logs/2022-06-18T01_31_52_584Z-debug-0.log
Error installing dependencies!
message: Command failed: npm install --production
stdout: null
stderr: null
/opt/nodebb/src/cli/package-install.js:54
		throw e;
		^

Error: Command failed: npm install --production
    at checkExecSyncError (node:child_process:828:11)
    at Object.execSync (node:child_process:902:15)
    at Object.installAll (/opt/nodebb/src/cli/package-install.js:45:9)
    at Object.<anonymous> (/opt/nodebb/src/cli/index.js:60:18)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 1461,
  stdout: null,
  stderr: null
}
[[email protected] nodebb]$ 

Built just fine to v2.2.0 though.

[[email protected]lisk nodebb]$ sudo -u nodebb ./nodebb setup
Dependencies outdated or not yet installed.
Installing them now...

npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

added 922 packages, and audited 923 packages in 2m

76 packages are looking for funding
  run `npm fund` for details

5 high severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
OK

2022-06-18T01:40:58.599Z [1600] - info: NodeBB Setup Triggered via Command Line

Welcome to NodeBB v2.2.0!

This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
Press enter to accept the default setting (shown in brackets).

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Still, maybe one of those can be updated and adapted?

Found a pull request for nodebb-plugin-import that gives it postgresql capability.
https://github.com/akhoury/nodebb-plugin-import/pull/240

So I think I will try that an use the "vanilla" import and see what works.

That is a project for the weekend when beer is involved.

ahwayakchih created this issue in akhoury/nodebb-plugin-import

open fix: support PostgreSQL (added with NodeBB v1.10.x) #240

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Yeah, but I'd thought I remembered seeing a free one

In our conversation from News Year's Day 2021.

https://community.nodebb.org/post/80835

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Found this 3rd party script here, fwiw:

There are others. None of them have been updated in 2+ years.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

My bad. Seems NodeBB folks offer this for a small fee:

They have for years. I first asked this question years ago when they switched to mongo as default.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

are you not already using PostgreSQL

No, in 2015, the install options were redis or mongo, with redis the actual default. I didn't feel the need to use Mongo as my site would never be large and redis could easily handle it.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

By "normal", are you referencing PHP and MariaSQL here?

By normal, I mean not using the normal NodeBB options that are default today. That means Ubuntu and Mongo according to the docs. https://docs.nodebb.org/installing/os/ubuntu/

Been a year or so since I last posted about this, but now I really need to get off of CentOS 7. I can easily reinstall everything on Fedora 36, but I would like to also get off of redis since the project has changed since I first set this up.

Do I need to give up on NodeBB and move to Discourse or some other backend? I'm not a large site operator, but I've been with NodeBB since version 0.9 or so (November 2015). I like the platform, but I do not like not being on a "normal" design anymore.

Redis was the primary back then, but no longer. I think it would be better if I could convert my system to stay in line with the current install design of NodeBB.

I mean, I an on git v1.19.x (currently 1.19.7) and things still work fine. But for how long will it still work well? Obviously, I need to get off of CentOS 7 because it is causing issues due to old package versions.

@pitaj said in Remove login button:

@jaredbusch you could try something like this in your custom css in the ACP:

a[href="/login"] {
  display: none !important;
}

That did it.

so as a quick test, a little searching in the persona theme source login, I found I could refine it to this.

https://github.com/NodeBB/nodebb-theme-persona/search?q=guest+login

Then I added a quick inline style command to hide it in those 6 returned locations.

Then there were two place in /templates/partials/menu.tpl that referenced /login. I did the same there.

Would this be simple enough for a theme setting? Obviously not as an inline style.. that was simply the easilet/quickest way to see if hiding those elements worked.

Rebuilt and gone.

@pitaj said in Remove login button:

Easiest way is probably too hide it with CSS.

That is what I was assuming I would need to do. Was hoping though.

Any pointer on the best way to handle it, that will survive upgrades, before I try and break things?