@FrankM
Sorry but this does not work at all.
How can a redirection be applied from a webserver that does not recieve the request.

I don't have the old domain anymore, and even I'd have it now, This does not address the issue on the long run.

Hi,

I have to change the domain name of my forum. This render internal links (within posts) broken.

My mongodb version is 3.2.11

I have tried the following db script:

db.collection.updateMany(
  { "objects.content": { $regex: /old.domain.com/ } },
  [{
    $set: { "objects.content": {
      $replaceOne: { input: "$objects.content", find: "old.domain.com", replacement: "new.domain.com" }
    }}
  }]
)

Which lead me to the following error:

2022-06-09T17:24:23.808+0200 E QUERY    [thread1] Error: the update operation document must contain atomic operators :
DBCollection.prototype.updateMany@src/mongo/shell/crud_api.js:568:1

I greatly appreciate if someone could point me how to achieve that.

PS: I am totally illiterate in mongodb.

Thank you all

@julian

basically the question popped while thinking of installing plugin-adsense (which does not worked at all for me btw - 1.11.2)

Is there any off-the-shelf solution to restrict a plugin for a set of group? Or any "easy" solution to do such?

Thanks

Here is a working .service, but I concur with @julian, do not put your nodebb inside the /root folder. Pretty good chance it will ruin your security at some point.

[Unit]
Description=NodeBB
Documentation=https://docs.nodebb.org
After=system.slice multi-user.target mongod.service

[Service]
Type=simple
User=nodebb

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=nodebb

WorkingDirectory=/var/www/nodebb/NodeBB/
ExecStart=/usr/bin/env node loader.js --no-silent --no-daemon
Restart=always

[Install]
WantedBy=multi-user.target

Hi,

Due a massive reorganisation of my category tree I'd like to reset all user to be automatically subscribed to all categories.
I have an adminMongo to manipulate the db
Unfortunately my mongodb skill is close to nothing.

Is there anyone kind enough to share the proper mongodb snippet to achieve such (either adminMongo or cli based.

Thank you

@The-Worms oui

@The-Worms Je voudrais pouvoir coller les derniers topics de la catégorie annonces de manière élégante comme ici.

Juste:
Titre
Contenu

@The-Worms
my theme is persona and this widget - tried it - does not generate such markup at all
has user, date I don't want and miss content i'd like to have
The topic you linked mention html widget for such part.
I have correctly implemented the popular tags widget however
https://aide.prestashop.click

Thanks for you time

@The-Worms
Seems obvious I have misunderstood something trivial on the first widget (said HTML widget based)
How can I have this html fetching n recent post on one specific category and displays them like in this forum home page.

<li>
        <a href="{relative_path}/topic/{topics.slug}">
                <strong>{topics.title}</strong>
                <br />
                {topics.content}
        </a>
</li>

With the HTML widget (or any other widget btw)

On this community forum there is this nice announcement widget
With pinned topic and list of topic per category.

How it is done ?
A step by step will be really appreciated

@julian
Thank you.
I was a little confused by this part of the documentation:

git reset --hard origin/v0.3.x    # Replace v0.3.x with the branch name!

But finally I made it w/o any issue

Excellent job

Hi all,

Here is my situation, I run nodebb 1.6.1 over nodejs v6.11.5
I'd like to migrate.

Is there anyone kind enought to advise me regarding the steps I should run first.
i.e: Do I upgrade my nodejs first, to which version, ...

Thanks for your time.

Ok things get returned to normal but I suspect the is some security at stake here.
Been the only admin I know that nothing get changed from the BO.
User settings was on allowing them to change their skin.
At some point the only scenario I can think of, it that some user action has invaded the default settings.

I have disabled user skin change.

It seems related to the fact I'm not any more in the skin "no-skin", how to return the default setting (non authenticated user to "no-skin")

Hi all,

All a sudden, despite having made no changes on my nodeBB 1.6.1 the front page is exhibiting weird behaviour on display.
https://aide.prestashop.click
If any one could lead me to what cause this and how to fix it, it be greatly appreciated

Best

I finally found the issue, it is related to the timestamp (score) when the user get registered.
I did not realized that my import was generating wrong type of time stamp {score":{"$numberLong":"1454992330000"}} rather than {score":1.509408313172e+12}

I finally run this fixup to cope with my issue:

db.objects.find({_key:"group:registered-users:members"}).forEach(
  function(e){
    db.objects.update(
      {"_id": e._id},
      {"$set": {"score": 0+e.score}}
    )
  }
);

I hate this mongojs thingy

It happens that I setup the minimum password complexity to 2 and user are not able to use password like Ulllll#n
Where:
U mean an uppercase
l mean lowercase
# a special char
n a number

I managed to get the green flag at 16 characters.

Sounds like the 2 complexity level is a bit overkill

Hi,

I have imported my users, topics and posts from my legacy forum within nodebb.
Everything sounded good, but my legacy users are not able to see any content while connected
As a temporary fix, I have added them to a special group (legacy) that fixed the issue.

My question is, is there anyone able to give me hints on the type of record I obviously miss during my "import" ?

What I have populated for each user:

{"_key":"user:<uid>"}
{"_key":"username:uid"}
{"_key":"username:sorted"}
{"_key":"userslug:uid"}
{"_key":"users:joindate"}
{"_key":"email:uid"}
{"_key":"email:sorted"}
{"_key":"group:registered-users:members"}

For the topics (I inserted each topic in an existing category - 2)

{"_key":"topic:<tid>"}
{"_key":"topics:tid"}
{"_key":"cid:2:tids"}
{"_key":"uid:<uid>:topics"}
{"_key":"cid:2:<uid>:tids"}

For posts

{"_key":"post:<pid>"}
{"_key":"posts:pid"}
{"_key":"group:administrators:member:pids"}
{"_key":"uid:<uid>:posts"}
{"_key":"tid:<tid>:posts"}

did you check that your domain resolves to your server? dns?