After upgrade from 1.5.x to 1.6.0, New Topic does not work

Anjin

I pulled all the plugins out, restored them one by one. And things started working right.

Anjin

@pitaj no errors, client or server side. Just button no workie.

Anjin

@anjin and... its not working again. Was stable for a short period. No errors, no warnings, just the New Topic button does not work.

PitaJ

@anjin by "does not work" do you mean it doesn't open the composer? Are you using the default composer? Does the reply button still work?

Shard

If this is what I did to myself, the composer plugin got disabled. Doublecheck that.

suparomana

@Anjin I have exactly the same problem. I did the upgrade to 1.6.0 a view days ago. Today I got a bugreport that no topics can replied and now new topics can be opened.

@PitaJ Right, the composer doesn't appear. I'm using the redactor-composer.

I discovered one another strange thing. The path to the site-logo was wrong. It was NodeBB/public/uploads/system/ and not /assets/uploads/system/. I had to upload the logo again and afterwards the path was correct. I don't know if the path was wrong since the upgrade to 1.6.0 or today.

suparomana

After my last post I wanted to reinstall all plugins, but I found a few more problems:

The redactor-plugin doesn't appear in the installed list of plugins. I'm pretty sure that nobody uninstalled the plugin! How could this happen? I tried to reinstall it, but nothing changed. The "new topic" and "answer"-Buttons still does not work
I can not uninstall all plugins. I have nodebb-plugin-emoji-one and nodebb-plugin-emoji-extended installed. I can uninstall one of the two plugin, but when I want to uninstall the second, the first appears again. I tried to do a restart of nodebb between the uninstalls but it is the same. here is the log for further information:

io: 2 on [ { type: 2,
    nsp: '/',
    id: 1,
    data:
     [ 'admin.plugins.toggleInstall',
       { id: 'nodebb-plugin-emoji-one', version: '1.2.1' } ] } ]
2/10 15:45:23 [28015] - verbose: [plugins/uninstall] added 3 packages and removed 6 packages in 25.515s

io: 2 on [ { type: 2, nsp: '/', id: 2, data: [ 'meta.rooms.leaveCurrent' ] } ]
io: 2 emit [ 'disconnecting', 'transport close' ]
io: 2 emit [ 'disconnect', 'transport close' ]
io: 2 emit [ 'checkSession', 2 ]
io: 2 on [ { type: 2, nsp: '/', id: 0, data: [ 'admin.getSearchDict', {} ] } ]
io: 2 on [ { type: 2,
    nsp: '/',
    id: 1,
    data:
     [ 'admin.plugins.toggleInstall',
       { id: 'nodebb-plugin-emoji-extended', version: '1.1.1' } ] } ]
2/10 15:46:21 [28015] - verbose: [plugins/uninstall] added 3 packages, removed 2 packages and moved 2 packages in 10.147s

io: 2 on [ { type: 2, nsp: '/', id: 2, data: [ 'meta.rooms.leaveCurrent' ] } ]
io: 2 on [ { type: 2,
    nsp: '/',
    id: 3,
    data:
     [ 'admin.plugins.toggleInstall',
       { id: 'nodebb-plugin-emoji-one', version: '1.2.1' } ] } ]
2/10 15:46:55 [28015] - verbose: [plugins/uninstall] added 1 package, removed 4 packages and moved 2 packages in 11.45s

io: 2 on [ { type: 2, nsp: '/', id: 4, data: [ 'meta.rooms.leaveCurrent' ] } ]
io: 2 emit [ 'disconnecting', 'transport close' ]
io: 2 emit [ 'disconnect', 'transport close' ]
io: 2 emit [ 'checkSession', 2 ]
io: 2 on [ { type: 2, nsp: '/', id: 0, data: [ 'admin.getSearchDict', {} ] } ]
io: 2 on [ { type: 2,
    nsp: '/',
    id: 1,
    data:
     [ 'admin.plugins.toggleInstall',
       { id: 'nodebb-plugin-emoji-extended', version: '1.1.1' } ] } ]
2/10 15:56:11 [28015] - verbose: [plugins/uninstall] added 3 packages, removed 2 packages and moved 2 packages in 12.854s

maybe the problem with new topics is located in the plugin-system..

I will try ./nodebb reset to disable all the plugins and post more information later on.

suparomana

after ./nodebb reset I tried to uninstall the plugins, but the problem of the uninstall/install-loop still exists as described in my last post.

I tried to activate the default composer to test if the "new topic"- and/or the "answer"-buttons are working again, but they are still out of order. But now i get a new 404 on pageload:

http://mydomain.com/assets/templates/composer.tpl?v=g6qg3shgt2k

I'm quite lost and don't know what to do and how i can get my forum up again.

Is there a possibility to downgrade back to 1.5.3 again?

Thanks for any help!

PitaJ

Make sure that you don't have npm@5. It causes the issues you seem to be having with plugins uninstalling.

Run npm -v and if it's version 5, then run npm i -g npm@4, that should fix it.

suparomana

Hi @pitaj,

thanks! Yes I have npm 5.0.3 installed. I try to downgrade npm but I'm struggling with the .npmrc and the right npm config for my webspace. I'm in communication with support of my hoster.

Do you think, that the switch to npm@4 will fix the problems regarding "new topics" and "answers"?

Thanks!

PitaJ

@suparomana it will fix the issue of plugins uninstalling. npm@5 is incompatible with NodeBB at the moment.

suparomana

@pitaj and what do you think about the issue with new topics and answers? Do you have any idea on that?

@Anjin Did you have the same issues with installing/uninstalling plugins?

julian

@suparomana I believe we should resolve the npm issues before addressing the issue with the composer not working...

suparomana

Hi @julian, hi @PitaJ ,

finally I could downgrade npm to Version 4.6.1. I reinstalled all plugins and the persona theme, but I can still not open new topics or answer on topics. When I try it with the standard composer plugin I only get a 404 for the composer.tpl, as posted in a former post. With redactor activated I get an error in the browser console:

client.js:105 Uncaught TypeError: Cannot read property 'composeRouteEnabled' of undefined
    at client.js:105
    at dispatch (jquery.js:5206)
    at g.handle (jquery.js:5014)
    at Object.trigger (jquery.js:8201)
    at jquery.js:8269
    at Function.each (jquery.js:362)
    at D.fn.init.each (jquery.js:157)
    at D.fn.init.trigger (jquery.js:8268)
    at postTools.js:222
    at y (postTools.js:374)

Any Idea what I could do? Can I downgrade nodebb to 1.5.3?

Thanks for any help!

PitaJ

@suparomana have you tried running ./nodebb stop && ./nodebb build && ./nodebb start?

suparomana

@pitaj yes, I tried ./nodebb build several times, but I always used ./nodebb dev to start.

I tried it once more as you said. ./nodebb start aborted with the message to run ./nodebb upgrade. After the upgrade and another ./nodebb start I can post and answer again!

I don't know why an how, but it works again. hopefully not only for a short time.

Thanks for you help!