Technical Support

@crazycells thanks you, after couple upgrades and downgrade and upgrade it fixed

@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. [jbusch@obelisk 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! pg@"^7.4.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer pg@"^8" from [email protected] npm ERR! node_modules/pg-cursor npm ERR! pg-cursor@"^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 } [jbusch@obelisk nodebb]$ Built just fine to v2.2.0 though. [jbusch@obelisk 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). [image: 1655517237358-7d8a5a66-30f5-4d65-a5ec-ac395ecd0178-image.png]

@gotwf 9.5 (Ya I know is a very old version )

As @baris has replied in that issue, this is already a feature in the ACP. It sounds like you are looking to disable the "welcome" email, but preserve the existing email confirmation emails, yes? In that case, you'll have to wait until v2.2.0, at which point you can use a plugin to change the template for the welcome email back to verify-email.

@baris Thanks! perfect https://github.com/julianlam/nodebb-plugin-support-forum/pull/14

@julian Maybe a new indicator to know this? So that inspectors can know this too, not just those who have access to ACP

@PitaJ ... without a checkbox but good to know =;^)  thank you.

Something of an update. I've reworked the code, and added some nice looking new color swatches (themes are based off Persona) https://sudonix.com/topic/284/theming-support-in-sudonix

@baris Thanks. I'm using the 18.x train (was previously on 14, so overdue an upgrade )

@razibal thanks for reporting, https://github.com/NodeBB/NodeBB/issues/10692 This started happening after the refactor to change tag storage to be by category https://github.com/NodeBB/NodeBB/pull/8938/files

@mstan — sorry that you haven't received a response. NodeBB doesn't save the Mongo database anywhere specific on the file system, it would be wherever the insulted MongoDB install saves it's data.

@doekia Does this help ? https://stackoverflow.com/questions/38883285/error-the-update-operation-document-must-contain-atomic-operators-when-running

@phenomlab My password consists of upper case letters, numbers and lower case letters.

thanks all for the comments.

Two things you can try Comment out https://github.com/NodeBB/NodeBB/blob/master/public/src/admin/admin.js#L47 Add a true to this if block so it doesn't logout the admin automatically https://github.com/NodeBB/NodeBB/blob/master/src/middleware/admin.js#L148

@baris Which is exactly what I did ! Very odd, but pleased it's fixed, and hope everyone else can benefit from this. Thanks for all the help.

@RandomAnimeGamer what you mean it recommends specifying a port? Here's a quote from the guide: Note: When entering your site URL, make sure it is exactly what you plan on accessing your site at. If you plan on visiting http://example.org to open your forum, then enter exactly http://example.org.

So after doing a lot of digging, I found out that the error was that NGINX needs to be configured for the SSL. This isn't really mentioned in the Ubuntu nodeBB guide, and the NGINX configuration guide linked on it is a dead link. First, I needed to combine my certificate and intermediate certificate (If you have a root certificate, you combine it as well) into one .cert file. This amounted to just copying the intermediate certificate and pasting it after the regular certificate (keeping the "BEGIN" and "END" lines). Then, I inserted the combined key into /etc/ssl/ directly. After doing this, I added my private key to a new folder I created in etc named "keys" (/etc/keys/). Lastly, I referenced my SSL in the "default" file in /etc/nginx/sites-available/default listen 443 ssl default_server; ssl on; ssl_certificate /etc/ssl/zbgamewiki.com_ssl_bundle.cer; ssl_certificate_key /etc/keys/_.zbgamewiki.com_private_key.key; And restarted nginx via sudo systemctl reload nginx

@gslender I didn't play around with Firestore myself, but the bulk of @justmeow's reasoning was in this post

@KnickKnack said in Deleted thread visible for all even if not allowed: the deleted threads appearing in the category listing Non-privileged users should just see "This topic is deleted!" or "This post is deleted!". Their position is kept because it is rather difficult to keep track of the topics/posts based on who can view the post and who cannot.