Awesome @baris : i should have a look at your changes !
I think we should be able to display more relevant topics by sorting the results with a good mixed ponderation...

If we look at the newly Suggested Topics on bottom of this post.. they don't really seem to be particularly relevant to our discussion

Excellent work @baris (i noticed the routine maintenance screen)
Here is how i see it :
The category filter is useful in my mind : sometimes it's just what we want because results from other sections of the forum could be totally irrelevant.. (it really depends on how your forum is divided...)
If a category is given, we should be able to filter on the requested category, if not, maybe topics within the same category should just be given a higher weight to sort the requested n results..
What do you think ?

@baris But yes.. you're right : there should be a better way to do this by matching topics on tags and titles at the same time, with some ponderation.. and with a category filter if given...

@baris Thnxx for your explanation ! I got it now : the concat thing
I almost agree with the priority given to tag matching over titles matching..
But what is clearly missing is the category filter !

@baris Well.. it's not !
It seemed like a bug to me too.. at least, not what i expected.
Then i noticed the mention :

If placed on a page other than categoy will pull from all recent posts

I'm glad i discovered that displaying related topics is a feature of the widget-essentials plugin : Is there any plugin to show related or similar topics on topic page?
However, after adding this widget in my topic footer i was really disapointed that the suggested topics weren't really that related as they didn't belong to the same category (forum) of the post in question.
I expected the category filter of the widget to be intended just for that purpose but it doesn't work on topics pages (so what's the point ?):

Thnxx @julian ! and congrats to all the team for all this awesome work on nodebb !!

I'm a little bit puzzled by your answer, and maybe i'm not getting it right.
So, indulge me with a more thorough explanation of my use case :

I've allready have put nginx in front of nodebb with this classic configuration :
https://blog.nodebb.org/introducing-the-build-system-in-v1-4-3/
It handles all the static assets and then call nodebb for the dynamics parts.

So, now, i just have to deal with something like 100-500 old topics (that have been correctly rewritten to our new nodebb urls with a different set of nginx redirect rules) but they are not here anymore, and i want to find redirections to new topics for the part of them that are the most requested..

It's really an SEO thing : we don't want to loose the good rankings the old forum had.
These old topics are have been indexed by google or some old facebook post and they are really frequently requested ...

But i don't see the interest to put these (hundreds?) of special redirections rules inside nginx that handles allready every single request to nodebb ?? That would put a serious (indue) work on him on every request ?

I really dream of a core nodebb plugin that could handle all these 404 inside nodebb when everything else have been tried (so that it would be a very scarce event).

Like i've said before : it's really a use-case of dealing with a post-migration trauma because these 404 will for sure disappear with time and the new google indexations.. but we want to address them now so that we dont loose ranks...
My boss is really watching the 404 pages as they happen, and he could deal with them in the back-office, but for sure he doesn't want to edit the nginx configuration files and me neither when a new 404 is detected...

Hi Everyone !
I was looking for a plugin to handle the 404 errors inside NodeBB.
Instead of redirecting directly to the custom 404 page, i want to be able to try a specific set of rules (using regular expressions) to see if i can find a redirection to a better resource.
I need this plugin because we migrated an old nukephp forum, and some of the ancien posts didn't make it through because they were obsolete in the new context.

I searched through the Install Plugin page, but didn't find anything that could fit my needs.
Does anyone know of a plugin that would be close enough, or what could be the best starting point to write mine ?

Cheers,

@baris Thanks !
You were really quick.
I have a slightly more complete PR here : https://github.com/NodeBB/NodeBB/pull/6185
because it happens on topics too.
Cheers,

@psychobunny Hi there,
As of nodebb v1.7.2, we have a checkbox to disable RSS feeds,
but the link for RSS feeds is still generated in the page head : <link rel="alternate" type="application/rss+xml" href="http://localhost:4567/category/2.rss?uid=3&token=305e32c5-9963-4bab-a4c1-fcdfa9c6c980" />
And following this link leads to a 404.

Hi @julian, thanks for your help : i've put my nginx configuration here : https://gist.github.com/zipang/3d60db9c29cb9a5db7ec3f431d07279b
And then, yes : i correctly updated the url and socket.io origin inside config.json !

Could you point me to the place in the code where the sitemap.xml is generated ?
I'll try to log what happens when he tries to browse topics..

@baris : Thanks !
I was still running nodebb v1.6.1 so i was unable to find the place you mentioned in the ACP.
But after a (difficult) upgrade to v1.7.1, i can now clearly see it :

That should do the job !

Hi there !

I have exactly the same problem (but i don't know if it was related to switching to https as i didn't look at the sitemap before)
There is no absolutely no entry for topics in my sitemap !

https://forum.mathforu.com/sitemap.xml

<sitemapindex>
  <sitemap>
    <loc>https://forum.mathforu.com/sitemap/pages.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://forum.mathforu.com/sitemap/categories.xml</loc>
  </sitemap>
</sitemapindex>

In the backoffice i tried 'Clear the cache for sitemap' but it stayed the same !

Edit :
I'm currently running on NodeBB v1.6.1, so i'll try to update to v1.7.1 and keep you updated on that issue !
Update :
I've upgraded to NodeBB v1.7.1 but nothing changed on that issue.

Hi there !
I have the exact same problematic.
We want to track the fact that the user has successfully confirmed his email after inscription.
I identified the /confirm/ page being the page where the user is directed after his email confirmation, so i can add code like this one in the HEAD section :

if (document.location.pathname.indexOf("/confirm/") === 0) {
    fbq("track", "CompleteRegistration");
}

But it appears to be a very brittle approach as i don't know if the confirmation was really successfull.
So, is your commit a way to know that the registration was successfull via the registered param ?

And.. is there a standard way in the admin panel to add custom code at the end of the page and preferrably after jQuery is loaded to inspect the page content ?

@pitaj Well yes thxxs !
It seems to work this command : pm2 logs nodebb
I'll update this post if i encounter any unwanted behaviours with this solution !

Hi Everyone !

@jcano : Did you have any success with pm2 ?
I have the same exact problematic.
I don't know how to setup nodebb to start with systemctl (we should need a nodebb.service file example)
So i wanted to ressort to pm2 to do the job as i allready use it on the same server to watch other nodejs processes and it does a great job.

So far i've tried all of these commands and they seem to work as expected :

pm2 start app.js --name nodebb
pm2 list
pm2 restart nodebb
pm2 stop nodebb

But now, i don't know how to see the log (./nodebb log doesn't work anymore, or to issue commands like ./nodebb upgrade)

@PitaJ : Is there something else to know, like env variables to setup... ?

@pitaj Thanks a lot : that really makes much more sense now.

I allready had deployed mailgun as a service through the use of an API key and that's what i was looking for !
Now that my domain has been created in the mailgun admin pannel and verified through the propagation of specific DNS records, i can confirm that the SMTP credentials are working and that the mails are being sent !

These clarifications were very helpful indeed !

Thanks a lot for your quick answer !

Do you mean that to use mailgun as my third-party email service provider, i just have to enter my mailgun username and password in these fields ?
Yeah.. i'm a bit confused as i expected that each services would have its own configuration.
And i am even more confused by the fact that the sentence :

An alternative would be to utilise a third-party emailer plugin such as SendGrid, Mailgun, etc. Browse available plugins here.

leads to a broken link... (can you see the {config.relative_path} inside the url ?)

There is a standard page for the configuration of email services, (/admin/settings/email)
but how do we input the required parameters for each individual mail service (gmail, mailgun, ...)

There is no specific input provided for each of them !

my screen capture is in french as it is the langage of my forum instance