• 0 Votes
    13 Posts
    577 Views

    @baris

    Yes it's better !

  • 1 Votes
    18 Posts
    1k Views

    @magnusvhendin Settings->Advanced User

    Obligatory reading: https://github.com/gorhill/uBlock/wiki/Advanced-user-features

    Although it still does allow some stuff I'd rather not see, on balance I tend to favor "Medium Mode" : https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode

    Once you're "in the advanced user" modes, enable various "noop" rules to season to taste. Speaking of which, you probably also should read up "Dynamic Filtering": https://github.com/gorhill/uBlock/wiki/Dynamic-filtering

    For those more visual and auditory learners: youtuber link: https://www.youtube.com/watch?v=2lisQQmWQkY

    Have fun! o/ ๐Ÿ•

  • Login error

    Unsolved Technical Support
    0 Votes
    8 Posts
    889 Views

    @ushi said in Login error:

    When I try to log in, I get such an error message
    "Login failed
    We are unable to connect you to the system, as it has been too long. please try again."
    What to do?

    I'll explain what the problem is,
    Apparently the forum server is too slow and did not load the ssl certificate.
    So you need to change the "http: //" in the url "https: //" and then try to connect again ... (I also translate from Hebrew, maybe you should add a category in Hebrew ...)

  • 0 Votes
    8 Posts
    670 Views

    Thanks @dunlix and @PitaJ for help me. Problem solved only for yours help. Thanks a lot

  • 0 Votes
    4 Posts
    462 Views

    @pitaj I can confirm that this fixed my issue! Thank you!

  • 0 Votes
    4 Posts
    599 Views

    @dogs themes are plugins, so everything you suggested can also be done in their theme.

  • 0 Votes
    2 Posts
    390 Views

    Upgrading NodeBB causes error on startup ยท Issue #9204 ยท NodeBB/NodeBB

    Ref to: error: Error: [[error:group-name-too-long]] on NodeBB Upgrade After upgrading NodeBB 1.13.x to 1.16.1 I received following error: โ†’ [2020/10/13] Create verified/unverified user groups...Error occurred 2021-01-16T13:12:18.178Z [45...

    favicon

    GitHub (github.com)

  • 2 Votes
    1 Posts
    334 Views

    Whats the right way to use third party libraries?

    I tried to do it descriped in the docs:
    https://docs.nodebb.org/development/plugins/libraries/

    But it doenst work.

    I want to use Swiper in my Theme:
    https://swiperjs.com/get-started/

    I tried it with

    "modules": { "swiper.js": "node_modules/swiper/swiper-bundle.min.js" }

    in client.js i used:

    require(['swiper'], function (Swiper) { var mySwiper = new Swiper('.swiper-container', { // Optional parameters direction: 'vertical', loop: true, // If we need pagination pagination: { el: '.swiper-pagination', }, // Navigation arrows navigation: { nextEl: '.swiper-button-next', prevEl: '.swiper-button-prev', }, // And if we need scrollbar scrollbar: { el: '.swiper-scrollbar', }, }) });

    The Javascript from Swiper does not load.

    Can you help me?

    I also treid to import it directly via html

    <link rel="stylesheet" href="https://unpkg.com/swiper/swiper-bundle.min.css"> <script src="https://unpkg.com/swiper/swiper-bundle.min.js"></script>

    and I also copied the contents of:
    https://unpkg.com/[email protected]/swiper-bundle.js

    and createt a file unter /lib/swiper-bundle.min.js. Nothing worked for me. The JS is still not loading...

    Looking forward to your answers! ๐Ÿ™‚

    I fixed it.

    I am sorry. In my development I use grunt. But it seems that I doesnt load new libraries if installen. So I determinated the process Ctrl+C and restarted it using grunt. The librariers are loaded and the third party library works well now using:

    "modules": { "swiper.js": "node_modules/swiper/swiper-bundle.min.js" } require(['swiper'], function (Swiper) { var mySwiper = new Swiper('.swiper-container', { ... ... ... }) }
  • 0 Votes
    5 Posts
    680 Views

    @Varun-Ganesh-D After updating what? Do not know jack about SES but seems whacked to me that updating only NodeBB would result in such. Perchance might some other, more system wide updates also been in the lurking? ๐Ÿค”

    Presuming you have cli access, what returns when thou drivest the following:

    [root@forums ~]# which sendmail
    /usr/sbin/sendmail

    Should be similar to above, and, of course, be in your $PATH.

    Rock on! ๐ŸŽธ

  • 0 Votes
    6 Posts
    707 Views

    @PitaJ thanks
    Resolved

    I removed Oxide Theme, and Custom Home Page Plugin
    Don't know which caused issues. But removed 3-4 last recently added things

  • 0 Votes
    8 Posts
    927 Views

    @tecy No need ๐Ÿ™‚

  • 0 Votes
    5 Posts
    602 Views

    problem solved. i have to import external script with

    require([script], function(name) { })

    It seems that importing scripts in a classic way creates conflicts in nodebb

  • 0 Votes
    2 Posts
    632 Views

    @fortunato I forgot to say that this error doesn't show up when creating a new topic and sometimes it works also in replies. The error in the NodeBB UI is the following: "stream ended unexpectedly"

    6c6ff98f-95d8-4ad4-b402-b7a336cf47e7-image.png

  • 0 Votes
    1 Posts
    320 Views

    Hi,

    Brief details of what is required:

    I have index.html page and index.js file under router. I am showing data from one collection say 'x' on page index.html. All the code related to router.get/post is done in index.js file.

    There is a button 'SubText' on index.html, m applying aggregation for search and storing output in new collection. Till here, everything is working fine.

    Now my requirement is when user clicks on 'SubText' button, after new collection, it should take it to different html page and show data from newly created collection.

    Please can anybody suggest/guide how to do this?

    Please find below the coder:

    Index.js

    var createGroups = function (db, callback) { var pipeline = [ { $match: { $text: { $search: "Error" } } }, {

    $project: { _id: 0, procPath: 1, bkgroundInfo: 1, "result": { $cond: { if: { $gte: [{ $indexOfCP: ["$bkgroundInfo", "Error"] }, 0] }, then: { $substrCP: ["$bkgroundInfo", { $indexOfCP: ["$bkgroundInfo", "Error"] }, 140] }, else: "Not Found" } } } }, { "$out": "SKSNodeColl" }

    ]
    db.aggregate(pipeline).toArray(function (err, result) {
    //assert.equal(err, null);
    console.log(result);
    callback(result);
    });
    };

    router.get('/newColl', function (req, res, next) { MongoClient.connect(url, { useNewUrlParser: true }, function (err, client) { if (err) { console.log(err); throw err; } var db = client.db("mydb"); var collection = db.collection("Users"); console.log("Mongo Connection - New Collection"); createGroups(collection, function (err, result) { console.log("newCollection Created"); var userdetails = path.join(__dirname, "/../views/userdetails.html"); console.log(userdetails); client.close();
    res.sendFile(userdetails);
    }); });
    });

    =====================
    Index.html

    <a href="/newColl"><input type="button" id="resultMatch" value="PatternMatchingResult" tabindex="1"></a>

    userdetails.html //page where I want to show data from new collection.(included ptrnSearch.js in this file in head section: )

    <form id="form1" name="form1" method="post" action="/fetch">
    <input type="hidden" name="id" value="" id="id" />
    <table border="1">
    <tbody>
    <tr>
    <th> ID </th>
    <th> Procedure Path </th>
    <th> Background Description </th>
    <th> Error Pattern </th>
    </tr>
    {% if (data.length) %}
    {% for item in data %}
    <tr>
    <td> {{item['_id']}} </td>
    <td> {{item['procPath']}} </td>
    <td> {{item['bkgroundInfo']}} </td>
    <td> {{item['result']}} </td>
    </tr>
    {% endfor %}
    {% endif %}
    </tbody>
    </table>
    </form>

    ptrnSearch.js //added to userdetails.html page

    router.get('/', function (req, res) { MongoClient.connect(url, function (err, client) { if (err) { throw err; } var db = client.db("mydb"); db.collection('SKSNodeColl').find({}).toArray(function (err, docs) { if (err) { throw err; } res.render('userdetails.html', { data: docs }); client.close(); }); }); });

    ==============================
    Many Thanks

  • 0 Votes
    2 Posts
    652 Views

    I fixed my own issue. Apparently some install scripts fail when run as root (or with sudo). I'm not sure why this is the case, but I got everything to work by running sudo chown -R ralph:www-data /path/to/nodebb && ./nodebb upgrade as a standard user.

  • 0 Votes
    2 Posts
    596 Views

    Did you rebuild and restart, or did you just restart?

    You have to rebuild after installing plugins.

  • 0 Votes
    4 Posts
    924 Views

    Never mind I was accidentally using the $ sign LOL. Was a long night.

  • 0 Votes
    5 Posts
    837 Views

    This may help BUT!!!! it will erase your database:
    If you remove config.json - I believe nodebb will create a new one, and will initialize the forum from scratch.

    Kindly note, I am a user like you, not part of the dev team so my knowledge is limited. I may be wrong, but I actually think this trick will work.

    Good luck!
    JJ

  • 0 Votes
    4 Posts
    3k Views

    The common causes for a session mismatch error are usually one of the following:

    1. Mis-configured URL parameter in your config.json file

    If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.

    2. Improper/malformed cookieDomain set in ACP

    Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:

    Cookie Domain setting

    If this is set, you'll want to revert the setting by editing your database directly:

    Redis: hdel config cookieDomain
    MongoDB: db.objects.update({ _key: "config" }, { $set: "cookieDomain": "" });

    3. Missing X-Forwarded-Proto header from nginx/apache

    If you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure property.

    In nginx, you will need to add the directive like so:

    location / { ... proxy_set_header X-Forwarded-Proto $scheme; ... }