when content is not displayed i can see this error in js console
t.match is not a function (nodebb.min.js:9)
this will get me mad... need to downgrade
when content is not displayed i can see this error in js console
t.match is not a function (nodebb.min.js:9)
this will get me mad... need to downgrade
@julian said:
@manuel Sounds like you have an existing NodeBB process running. Make sure there are no orphaned NodeBBs running!
ps aux | grep node
, and thenkill -9
with impunity.
after killing and restarting everything i have this js error in admin
Error: script error for: alerts (require.js:8)
same for the path forum/admin/ loggers|database|events and forum/admin/plugins/ nameplugin
some plugins like local emailer and shoutbox won't work in admin
i still can't see the sidebar in homepage and moreover while navigating through forum when i go back to the home nothing will be loaded (or better, categories are invisible O.o)
i cannot change theme from lavender to vanilla i.e. O.o
@julian said:
@manuel Could you try the latest version of NodeBB (or if you're on v0.4.x branch, update the code in that branch), and run
./nodebb upgrade
again?Please run this command and let me know what it says:
npm ls nodebb-widget-essentials nodebb-theme-vanilla nodebb-theme-lavender
./nodebb stop --> ./nodebb line 31: kill (no such process)
git pull + nodebb upgrade says i have all up to date
[email protected] with lavender 0.0.25-0, vanilla 0.0.19-1, widgets-essentials 0.0.21-0
starting in log mode:
some plugins are using the deprecated "callbacked" method
plugins are marked as deactivated in admin but i can see on forum that emoji, twitter, soundcloud are working like if they are active O.o
the homepage and category sidebars lost theyr widgets that are now gone in drafts sidebar
there are some issues dragging them (they are positioned away from mouse pointer while dragging)
after reconfiguring and saving sidebars it's still not displayed in the homepage and plus the theme is not "running smoothly" and there are some bad looking things (like up/down votes)
i tried switching from firefox 30 to chrome, same situation and same error in websocket connection
i think i have to downgrade to previous version
utils.makeNumbersHumanReadable is not a function (app.js:287)
ctrl+f5 (after several times) solved the .js issue (content not loading in admin), but only in the admin
the forum index still does not display the homepage sidebar, but if i put some widgets in global sidebar they will be displayed
and why after a reset i still have all plugins on? i am using lavender theme.
today i upgraded to 4.0.0 and i have the same issue, plus content not loading when i click menus in admin
i tried to reset and rerun upgrade, this is still not working and i see this error in console
firefox could not establish a connection to server ws://forum.xxxxxxxx.com/socket.io/1/websocket/GzrMxZ8uYBdQX12C21GS. (socket.io.js:2)
utils.makeNumbersHumanReadable is not a function (app.js:287)
digitalocean vm with 1gb ram, ssd disk, 1 cpu
are we far from the release?
yes it works
I'd like a link to the last message in a topic because with the current theme in topics with many messages it will scroll down by 20 messages each time you press the (near # out of #)
@frissdiegurke said:
@manuel It's because I use
nconf.get('url')
to get the domain (in fact this remains from @julian).
I need any way to get the absolute path of NodeBB-root. I guess thenconf.get('url')
is ment to avoid problems with sub-directories (that would appear if I use/
instead).
Since I cannot see any automatic way around this for all use-cases you may just replaceemojiPath=nconf.get("url")+"/plugins/nodebb-plugin-emoji-extended/images"
byemojiPath="/plugins/nodebb-plugin-emoji-extended/images"
within your/nodebb/root/node_modules/nodebb-plugin-emoji-extended/index.js
you'd need to redo this every time I update the plugin until this may get supported.
Maybe a url-prefix field will occur within the ACP/emoji-extended next update
removing nconf.get("url") worked but it was config.json use_port = true
during setup and watching online documentation this effect on urls was not clear to me, sorry
@scuzz have this too but I don't know if he is running nodebb @ 4567 voluntarily
I don't think to have any particular configuration on my server, I've just used the tutorial on github to setup the ngnix proxy
afaik port number is appended only on emoji's urls
@Scuzz said:
@manuel I get the same link to an image no matter where the image is, shoutbox and the forums. They all have the port numbers. I am using nginx too
i run nginx on public ip port 80 and it forwards to nodebb on 127.0.0.1:4567
the only "fix" i could do is to add a listener on 4567 but i don't understand why the emoji plugin adds the port when nodebb does not for all the other urls
i tried a git pull and restarted nodebb, now i have the problem everywhere, so it's the emoji plugin sorry
can some1 move my post to the correct topic please?
@Scuzz this is happening only into the shoutbox
i have an issue with images path for emoticons (i am running nodebb behind nginx )
paths generated by this plugin are like http://xxx.xxx.com:4567/plugins/nodebb-plugin-emoji-extended/images/grinning.png
to be correct the port 4567 should be removed
had to uninstall it too :S
What's the best way to update plugins?
@julian why i don't see notifications for new chats then?
i mean a number up to the chat icon like for "unread" posts
subsequent feature request: add notifications for chats and pm