I had back this problem a 2nd time 2 days ago, I don't know if it's related but I was doing iptables FW settings on the VM, I had nodeBB running, and also redis and from my computer desktop redis desktop manager connected to DB.
Then I made a mistake in iptables, blocked all redis port (even local), saying nodebb unable to connect to redis (so as redis desktop manager) then when I openned back 6379 port, all data was gone, not sure if it's related, just an information.
SOLVED Potential issue with GDPR consent page ("export posts" crashes nodebb)
-
Hi,
My setup: Version: 1.9.2 (synced with master).
Pressing "export uploaded content" creates an empty zip file - maybe the user should get a message instead? (anyway this is a minor issue)
Pressing "export posts" crashes nodebb:
error: TypeError: Cannot read property 'content' of null
at /nodebb/src/controllers/user.js:122:32
at Array.map (native)
at /nodebb/src/controllers/user.js:121:20
at /nodebb/node_modules/async/dist/async.js:1126:9
at iteratorSymbol (/nodebb/node_modules/async/dist/async.js:473:16)
at iteratorCallback (/nodebb/node_modules/async/dist/async.js:1050:13)
at /nodebb/node_modules/async/dist/async.js:958:16
at /nodebb/node_modules/async/dist/async.js:1123:13
at iteratorSymbol (/nodebb/node_modules/async/dist/async.js:473:16)
at next (/nodebb/node_modules/async/dist/async.js:5315:29)
at /nodebb/node_modules/async/dist/async.js:958:16
at /nodebb/src/posts.js:107:4
at nextTask (/nodebb/node_modules/async/dist/async.js:5310:14)
at next (/nodebb/node_modules/async/dist/async.js:5317:9)
at /nodebb/node_modules/async/dist/async.js:958:16
at fireFilterHook (/nodebb/src/plugins/hooks.js:114:11)Not sure how to go about fixing this...
JJ. -
Latest master should fix the latter. For the former, perhaps you actually have no uploads mapped to your user? What do you see in the uploads page in your user profile?
-
Its working perfectly now thank you so much!
A comment is generated: "[user/export/uploads] Collating uploads for uid..." when pressing "export uploaded content". Not sure if this is left intentionally.
Anyway, all good now thanks!
-
@JJSagan Yes, that is normal, just an informative echo to indicate that the process has started.
