@julian Thank you Julian.
Tried to debug the recentreplies.js and found that it tries to access value of category that is undefined and all other fields of the post is set to null.
The idea is to try fix it in redis before upgrading.
If you would have a chance to advice me a correct direction where I should dig in in order to delete this corrupted data in db it will be super helpful.
Encountered Uncaught Exception: meta is not defined
-
From NodeBB's error.log file comes this entry:
{"level":"error","message":"[app] Encountered Uncaught Exception: meta is not defined","timestamp":"......"}I don't know what the error is associated with. Any body else encountered that error message? Any clues?
-
Can you get it to produce on demand? If so, please try to disable plugins one by one until you find the culprit... it may be that a plugin is depending on
metabeing a global, when it is not. -
That error is coming right after this:
{"level":"error","message":"[plugins/nodebb-plugin-emoji-extended] This plugin's CSS is incorrectly configured, please contact the plugin author.","timestamp":"...."}So it looks like it's connected to that plugin.
-
Could be... or might be a coincidence -- emoji-extended should really use LESS... unless that's an older plugin version you're using?>
-
I'm running Edge, so all plugins should be current.
-
@planner Running v0.2.2-1 of emoji extended. The only error I get is:
warn: [plugins/nodebb-plugin-emoji-extended] "callbacked" deprecated as of 0.4x. Use asynchronous method instead for hook: filter:post.parse -
That means I have to update the plugin separately.
That should not be a problem, but I have to first get NodeBB to work on my site, either from a subfolder or a subdomain. There's too much going on i my head right now that even the smallest problem seems very difficult.
Perhaps you or anybody reading this can help me figure out why. So as not to hijack this thread, I'm starting another one with my main issue at Nginx 502 Bad Gateway and NodeBB subdomain installation.
