can't access extend->plugin

Bug Reports
  • when I click extend->plugin try to access , it always loading.
    and I just upgrade 1.6.x to 1.7.x


    anyone can tell me why ?

    2018-01-04T07:20:06.213Z [16198] - error:  TypeError: Cannot create property 'id' on string '['
        at Object.Plugins.normalise (/root/nodebb/src/plugins.js:230:19)
        at Request._callback (/root/nodebb/src/plugins.js:221:11)
        at Request.self.callback (/root/nodebb/node_modules/request/request.js:186:22)
        at Request.emit (events.js:159:13)
        at Request.<anonymous> (/root/nodebb/node_modules/request/request.js:1163:10)
        at Request.emit (events.js:159:13)
        at IncomingMessage.<anonymous> (/root/nodebb/node_modules/request/request.js:1085:12)
        at Object.onceWrapper (events.js:254:19)
        at IncomingMessage.emit (events.js:164:20)
        at endReadableNT (_stream_readable.js:1062:12)
        at process._tickCallback (internal/process/next_tick.js:152:19)
    2018-01-04T07:20:06.216Z [16198] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    2018-01-04T07:20:06.219Z [16198] - info: [app] Database connection closed.
    2018-01-04T07:20:06.220Z [16198] - info: [app] Web server closed to connections.
    2018-01-04T07:20:06.220Z [16198] - info: [app] Shutdown complete.
    [cluster] Child Process (16198) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    2018-01-04T07:20:06.873Z [16799] - info: Initializing NodeBB v1.7.3 http://my website url
    2018-01-04T07:20:08.388Z [16799] - info: [] Restricting access to origin: http://mysiteurl:*
    2018-01-04T07:20:08.632Z [16799] - info: Routes added
    2018-01-04T07:20:08.635Z [16799] - info: NodeBB Ready
    2018-01-04T07:20:08.637Z [16799] - info: Enabling 'trust proxy'
    2018-01-04T07:20:08.640Z [16799] - info: NodeBB is now listening on:
  • This seems to happen when is down or inaccessible, should give a better error message and not crash. Can you give it a try?

  • I think its possible, my server on china and I can't access the nodebb website without shadowsock proxy, so I think the nodebb official staff should try someway to let the chinese know such good product.

  • There actually used to be a couple active Chinese members, and I think there is / was a whole Chinese NodeBB forum hosted somewhere.

  • I can’t tell how active it is, but anyway:

Suggested Topics

  • plugin question and awnser

    Bug Reports
    0 Votes
    2 Posts

    What is your nodebb and plugin version?

  • 0 Votes
    6 Posts

    @baris Thanks for the heads-up, v0.5.12 has been deprecated for the version mismatch issue, so v0.5.11 should be the recommended version

  • broken plugin

    Bug Reports
    0 Votes
    2 Posts

    The developer appears to be active. You should open a new issue on their github if you are having problems.

  • 0 Votes
    1 Posts

    Noticed they do not work on my 0.7.2 atm

    I've enabled topic thumbnails? and file upload (mite help reproduce the bug)

    Thank you. ❤

    should prolly also mention topic thumbnail upload file option gave me this nice big red error message 😞 something to do with MSIE i think

  • 0 Votes
    1 Posts

    I'm not sure if it's just me, but I thought I'd mention it.

    I'm using @Schamper's shoutbox plugin and noticed if I deactivate the plugin without removing the widgets first there will be an empty object listed in on the page in the section where the widget would have been. So, I tested it with the widget-essentials too and it does the same thing...

    I'm on 0.5.1. Here is how you can duplicate:

    Drop any widget into a widget section (aka sidebar or MOTD) Deactivate the plugin that contains the widget Go to the page where the widget would have been and you should see
    the text '[Object object]' where the widget would have been Go to the ACP > Extend > Widgets section and the widget won't be listed where you added it.

    What makes this really confusing #4 because you can't get rid of it. It only reappears when you activate the plugin that had the widget again.

    Has anyone else experienced this?

    And if you added some custom widget sections in your theme.js (like a sidebar for topics.tpl in the vanilla theme), and changed the theme...god help you...but seriously, if you did do that hit me up and I'll tell you how to fix it.