Console error after upgrade to 2.1.0

Unsolved Technical Support

Suggested Topics


  • Steam SSO (1.18)

    Unsolved Technical Support
    1 Votes
    11 Posts
    451 Views
  • 0 Votes
    10 Posts
    2k Views

    @fais3000 what was the actual error message you got? This shouldn't be happening any more.

  • 0 Votes
    1 Posts
    154 Views

    Is there any way to migrate wbb 3.1 to nodebb?

  • 0 Votes
    1 Posts
    587 Views

    I first noticed this when I ran into issues with jquery not executing on the ACP, but now with a separate installation, on a totally different server, I'm seeing it again.

    I can see clearly that jQuery or javascript isn't executing, but the browser console remains totally blank.

    In the previous case, another user here was able to display the contents from his browser console, but mine stayed blank.

    This time around, the lavender theme's masonry script isn't executing, but there's no output from my browser console. Thoughts?

    NOTE

    I am running this directly from an IP address without a FQDN. Could this be part of the issue?

    UPDATE

    I started up nodebb in dev mode and watched the terminal, but I'm not getting any errors or warning after the site loads. I'm totally stumped why masonry.js isn't loading. It's not even showing up in the console's resources, but there was no error thrown either in the client or the terminal.

  • 0 Votes
    1 Posts
    683 Views

    I have attempted to install the emailer-mailgun plugin and end up with an error. When I install from the ACP an ENOENT, open error is displayed, momentarily, referencing a path in the plugin that does not exist. The path error is:

    Error ENOENT, open '/path to my installation/node_modules/nodebb-plugin-emailer-mailgun/node_modules/mailgun-js/node_modules/form-data/node_modules/mime/package.json'

    The form-data directory is not there.

    I am running Nodebb v0.9.3 and the emailer-mailgun plugin is reporting itself as version 1.0.0.

    Has anyone else run into this problem and is there a work around to resolve the problem?

    Thank you.

    Edit: This is a low priority issue. I installed the nodebb-plugin-emailer-local-bobo plugin and was able to configure it to use Mailgun just fine. I am using the SMTP settings as opposed to the API call but that is fine for my usage.