Hi Team,
I have upgraded nodebb to v2.6.1 by merging with master branch from nodebb git. Also updated my npm to v9.2.0 node to v18.12.1.
After successfully ./nodebb setup , when I start it, its shows below error.

2022-12-08T10:14:09.506Z [4567/30680] - error: TypeError: Cannot read properties of undefined (reading 'hasOwnProperty')
at C:\Users\AmodChaubey\Desktop\AngelOne\Smart Forum\smart-api-forum\node_modules\nodebb-plugin-markdown\index.js:107:18
at Array.forEach (<anonymous>)
at C:\Users\AmodChaubey\Desktop\AngelOne\Smart Forum\smart-api-forum\node_modules\nodebb-plugin-markdown\index.js:105:26
at C:\Users\AmodChaubey\Desktop\AngelOne\Smart Forum\smart-api-forum\src\promisify.js:43:65
at _node_internal (node:util:291:10)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2022-12-08T10:14:09.506Z [4567/30680] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
2022-12-08T10:14:09.508Z [4567/30680] - error: Error [ERR_SERVER_NOT_RUNNING]: Server is not running.
at new NodeError (node:internal/errors:393:5)
at Server.close (node:net:1827:12)
at Object.onceWrapper (node:events:627:28)
at Server.emit (node:events:525:35)
at emitCloseNT (node:net:1880:8)
at process.processTicksAndRejections (node:internal/process/task_queues:81:21

Urgently need assistance .

Need to get all post in forum downloaded.. is there a way ?

Hi, after upgrading nodebb to v1.18.6 , dropdowns are not able show categorys..

Hi..
While upgarding NodeBB from v1.15.0 to v1.18.6, getting error,

info: [build] client side styles build started
error: [build] client side styles build failed
error: [build] Encountered error during build step

SyntaxError: Inline JavaScript is not enabled. Is it set in your options? in /node_modules/nodebb-theme-persona-custom-scaf/less/bootstrap/buttons.less on line 51, column 5:
50 pointer-events: none; // Future-proof disabling of clicks
51 .opacity(.65);
52 .box-shadow(none);

Error occurred during upgrade: undefined
(node:6394) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(Use node --trace-warnings ... to show where the warning was created)
(node:6394) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code