Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups
    1. Home
    2. oplik0
    • Profile
    • Following 2
    • Followers 2
    • Topics 3
    • Posts 134
    • Best 75
    • Groups 5

    oplik0

    @oplik0

    Plugin & Theme Dev Community Rep

    121
    Reputation
    107
    Profile views
    134
    Posts
    2
    Followers
    2
    Following
    Joined Last Online
    Website wieloswiat.pl

    oplik0 Unfollow Follow
    Users with 50 posts Translator Gamers Community Rep Plugin & Theme Dev

    Best posts made by oplik0

    • RE: Show categories vertically in Persona
      .category-children-item {
        display: flex;
        float: none !important;
      }
      

      seems to do the trick.

      EDIT:
      after looking a bit at the topic @crazycells linked and looking at this for a few more minutes I think the better solution would be:

      .categories .category-children {
        display: flex;
        flex-direction: column;
      }
      

      It doesn't affect how it works, but not using !important is the improvement here 🙂

      Oh, and if you want some distance between the items just add margin-top or margin-bottom to .categories .category-children-item.

      posted in Technical Support
      oplik0
      oplik0
    • RE: Help Needed on Markdown

      It is possible, but you need nodebb-plugin-markdown 8.11.1 or higher, while package.json has the exact version of this plugin selected, so unless you installed your NodeBB recently, you have to either upgrade NodeBB if you're on master branch (git fetch;git reset --hard origin/master;./nodebb upgrade), switch to master branch, wait for next minor 1.13 version or install it manually via npm install nodebb-plugin-markdown@latest - with the last option being the easiest.

      In that version a plugin for markdown-it was added that adds parts of multimarkdown syntax - specifically, better table syntax. You will be able to create multiline tables like this:

      | header1 | header2 | header3 | header4 |\
      | units   | units   | units   | units   |
      |:-------:|:-------:|:-------:|:-------:|
      | data1   | data2   | data3   | data4   | 
      

      When you add \ at the end of a row markdown parser will now interpret it as a multiline row and merge it with the one below. So this example table will look like this:
      multiline table example

      There is more to this syntax than just merging two rows (for example single cells spanning multiple rows or columns) and you can find the documentation of this plugin here

      posted in Feature Requests
      oplik0
      oplik0
    • RE: phpBB NodeBB Flarum Laravel.io who is better Forum?

      @鄭宇佋 A less biased answer would be - they aren't entirely equivalent, and the choice is a combination of specific needs and preferences that IMO can't be generalized to "x is better in general".

      phpBB is the oldest forum, and as such it embodies the older style of forums from before social media made things like tags, real time interactions, feeds etc. popular. However, it is probably the most feature rich of all offerings if you have time and knowledge to set it up.

      Flarum (and I think the Laravel community software too? Never used it :V) is a simpler forum that is tag-based. You can nest tags once in Flarum, but only once and it seems to more encourage a feed approach where your main page is filled with topics sorted in some way and you use tags to go somewhere if you're looking for something specific. This is in contrast to the "classical" structure I mentioned, where you will have subforums/categories that you can infinitely nest and the idea is that the user first goes to the category that will have the topics that will be interesting to them.

      However, NodeBB and Discourse are both somewhere closer to the middle, but on the opposite sides. In both you will find categories and tags, but from what I've seen the emphasis is different - NodeBB is categories that can have tags, Discourse is tags that can have categories 🙂

      Of course, there are a lot of other differences. As mentioned, more modern software is better at doing stuff real-time. Notifications, chats (Discourse and NodeBB have some form of private conversations built in. Flarum and phpBB have extensions that add it), loading new posts without reloads etc.
      AFAIK NodeBB is the only one of these using WebSockets (socket.io)
      Discourse uses some custom polling based protocol.
      Flarum actually doesn't do much live stuff by default (just kilke phpBB), but it does have notifications that can use officially-supported pusher extension to work.

      One major difference though - phpBB, Flarum and Laravel.io are PHP-based, so you can make them work on generally cheaper shared web hosting, meanwhile Discourse and NodeBB will require a server that can run Ruby or Node respectively - for example a Linux VPS.

      Which one is better depends on what you want then.
      Laravel.io seems to be most limited in terms of customization, unless there are some undocumented features on that front. So if there are any things you don't like about the way it looks or feels - don't choose it.
      If you like the Flarum tag structure and don't mind it lacking some things (well, it's a beta after all), it seems like the most performant option.
      phpBB? If you are willing to buy/develop some modern theme and spend time to configure it, sure. Otherwise I wouldn't recommend it.
      The decision between NodeBB and Discourse is harder, and while I prefer NodeBB, I'd say it's mostly down to your preferences, specifics of what you want to use the forum for and the preference for technology stack (Node, Express, MongoDB/Redis/Postgres + no major js framework outside of jQuery on front-end for NodeBB vs Ruby on Rails, Postgres + Ember.js on front-end for Discourse).

      Some unfortunately older topics on this (some will have much more recent replies, so might be useful to read them; I tried to include topics from meta-forums of other forum software and user forums based on software in question):

      • https://community.nodebb.org/topic/1835/which-is-better-nodebb-or-discourse
      • https://community.nodebb.org/topic/10827/why-i-chose-to-use-nodebb-over-phpbb-discourse-mybb-and-other-forums
      • https://discuss.flarum.org/d/2056-flarum-vs-nodebb
      • https://discuss.flarum.org/d/6952-how-is-flarum-different-from-discourse-and-other-forums
      • https://discuss.flarum.org/d/676-what-are-the-advantages-of-flarum-over-discourse
      • https://meta.discourse.org/t/which-is-better-discourse-or-flarum/71726
      • https://what.thedailywtf.com/topic/23993/nodebb-vs-discourse-showdown (just for context - this forum migrated to NodeBB from Discourse in 2016)
      • https://gamingexodus.com/t/nodebb-current-forum-vs-discourse/3012 (here there was a migration in the opposite direction in 2018)
      • https://www.reddit.com/r/webdev/comments/415nlp/discourse_flarum_nodebb_oh_my/
      • https://forums.linuxmint.com/viewtopic.php?t=231767&start=20

      Obviously remember that the answers will be biased essentially everywhere - here, towards NodeBB. On Discourse forums, towards Discourse. On Flarum - towards Flarum. Etc.

      posted in General Discussion
      oplik0
      oplik0
    • [nodebb-widget-discord-embed] Embed a Discord chat in a widget using TitanEmbeds

      A simple widget for embedding a Discord chat (not just an invite and a list of user online, like what Discord gives by itself) using TitanEmbeds.

      My main reason for creating this instead of just using a html widget with the iframe was the option to give guests their forum username by default (so with correct settings on TitanEmbeds they can be logged in as a guest with their username automatically).

      When creating the widget you need to input the embed/server ID from TitanEmbeds and you'll be able to configure almost all settings available for the iframe embed (default channel, theme, language, etc.).

      To install just find the widget in the plugin manager or use npm install nodebb-widget-discord-embed.

      Source code can be found here

      posted in NodeBB Plugins
      oplik0
      oplik0
    • RE: Google Recaptcha v3 not working

      v3 is not just "a better reCAPTCHA" and it is not replacing v2.

      v3 only offers "invisible" reCAPTCHA, but even if Spam Be Gone supported that (it doesn't yet) it still wouldn't work because it passes different data.
      reCAPTCHA v2 is binary - either user is a robot or not.
      v3 doesn't just pass "true||false" but instead passes a score from 0.0 to 1.0 and it's up to the application to determine what score is a success. It also never shows user a challenge as it's not supposed to interrupt the user in any way.

      So to sum it up: for Spam Be Gone to support v3 would mean changing the way it handles reCAPTCHA and I'm not even sure if it's a good idea. v3 is supposed to continuously chceck if user is a bot without interruptions, so it's best used for frequent user actions like posting or login, not for things like registration that happen once per user and it's not a big deal if it interrupts user with a challenge. So I'd say it'd be better for Spam Be Gone to extend its functionally to use v3 on login and posting, and leave v2 on the registration page.

      posted in Technical Support
      oplik0
      oplik0
    • RE: Do not allow users to leave from certain group

      It's already been added some time ago and will be in 1.13.0:
      https://github.com/NodeBB/NodeBB/commit/1796b65d34e5762e95e1bd305d3bc90983059811
      The original issue on GitHub:
      https://github.com/NodeBB/NodeBB/issues/7770

      alfazaz created this issue in NodeBB/NodeBB

      closed Disable user to quit a group (permission) #7770

      0 julianlam committed to NodeBB/NodeBB
      feat: option to restrict group leaving, closes #7770
      posted in Feature Requests
      oplik0
      oplik0
    • RE: How to highlight this button?
      .moderator-tools .fa-ellipsis-v:before{
        content: "some text";
      }
      

      This will replace these three dots, but if you want to keep them you can also do

      .moderator-tools .fa-ellipsis-v:after{
        content: "some text";
      }
      

      Note though, that in the second case it will look ugly without any additional styling - I'd recommend adding at least padding-left or margin-left.

      You can of course style these pseudoelements in any way you want to. So for example you can create this menu that no one will miss:
      07df93e4-78a7-4c15-94f0-3f783b479c7f-image.png
      0df47693-ec67-43e7-85fe-b141a2ccdbda-image.png
      by using this css:

      .moderator-tools .fa-ellipsis-v:before{
        content: "menu";
        margin-left: -10px;
        color: #FF00FF;
        background-color: #FFFF00;
        font-size: 2rem;
        border-radius: 3px;
        font-weight: bolder;
        text-transform: capitalize;
        font-family: "Comic Sans MS", cursive, sans-serif;
      }
      
      posted in General Discussion
      oplik0
      oplik0
    • RE: snowing theme

      It's really easy - it's just one script added to <head>: https://github.com/nextapps-de/snowflake
      So just go to Appearance>Custom Content>Custom Header in ACP and add this: <script src="https://cdn.jsdelivr.net/gh/nextapps-de/snowflake@master/snowflake.min.js"></script>

      posted in Technical Support
      oplik0
      oplik0
    • RE: "Forum Terms of Use" and text formatting

      Markdown works for me. Before 1.13 I needed HTML there tho (this commit changed it). Now it's parsed like a post - so whatever you use for text formatting for users should work.

      posted in Feature Requests
      oplik0
      oplik0
    • RE: Update Schamper's Shoutbox

      You can try creating a PR, but I doubt it will get you anywhere since last commits there were on 2018 and that was a PR too. The creator was last online on this forum in 2017, so I doubt he'll help you here.
      Making a fork is probably the best idea here, since it's unlikely you'll get your changes to the main repo.

      posted in NodeBB Plugins
      oplik0
      oplik0

    Latest posts made by oplik0

    • RE: NodeBB + MongoDB + Scaling (k8s)

      The main issue from what I understood is actually lack of a maintained MongoDB equivalent of this: https://github.com/socketio/socket.io-redis

      There are a few old packages based on the official redis one, but they were last published a few years ago. I think NodeBB team was looking at this fork recently (2 PRs made by 2 NodeBB staff members): https://github.com/lklepner/socket.io-adapter-mongo - and I guess it is the most recent one - but it also seems kinda abandoned.

      So for now it seems that unless NodeBB takes on maintaining an adapter, redis will have to remain a requirement.

      posted in Technical Support
      oplik0
      oplik0
    • RE: PWA not work (NodeBB 1.16.2)

      It was fixed after 1.16.2 release, so wait until 1.17.0 is released or update to a beta version (or master branch)

      posted in Technical Support
      oplik0
      oplik0
    • RE: Is there any mobile client for nodebb

      @sharonyue

      BTW, why do I have a browser window? Is it because Iam using Android, or I am running nodebb 1.14?

      It's because you're running 1.14 actually. The actual scripts for installable PWA only appeared in 1.15.
      However, browsers are confusing so they also offer the option to "add to home screen" any website, but instead of actually considering its manifest for how it's supposed to run and using the service worker properly it will be just an icon to open that website in the browser.

      I would've recommended checking this website to see how it's supposed to work, but it seems to be broken in 1.16.2 unfortunately (mentioned in this issue - service worker was moved to its own directory so only paths starting with /assets/src/ are in its scope.)

      EDIT: while it was mentioned in the issue #9193, it wasn't the main focus. I commented on it on #9127, solution to which actually broke the service worker

      posted in General Discussion
      oplik0
      oplik0
    • RE: phpBB NodeBB Flarum Laravel.io who is better Forum?

      @鄭宇佋 A less biased answer would be - they aren't entirely equivalent, and the choice is a combination of specific needs and preferences that IMO can't be generalized to "x is better in general".

      phpBB is the oldest forum, and as such it embodies the older style of forums from before social media made things like tags, real time interactions, feeds etc. popular. However, it is probably the most feature rich of all offerings if you have time and knowledge to set it up.

      Flarum (and I think the Laravel community software too? Never used it :V) is a simpler forum that is tag-based. You can nest tags once in Flarum, but only once and it seems to more encourage a feed approach where your main page is filled with topics sorted in some way and you use tags to go somewhere if you're looking for something specific. This is in contrast to the "classical" structure I mentioned, where you will have subforums/categories that you can infinitely nest and the idea is that the user first goes to the category that will have the topics that will be interesting to them.

      However, NodeBB and Discourse are both somewhere closer to the middle, but on the opposite sides. In both you will find categories and tags, but from what I've seen the emphasis is different - NodeBB is categories that can have tags, Discourse is tags that can have categories 🙂

      Of course, there are a lot of other differences. As mentioned, more modern software is better at doing stuff real-time. Notifications, chats (Discourse and NodeBB have some form of private conversations built in. Flarum and phpBB have extensions that add it), loading new posts without reloads etc.
      AFAIK NodeBB is the only one of these using WebSockets (socket.io)
      Discourse uses some custom polling based protocol.
      Flarum actually doesn't do much live stuff by default (just kilke phpBB), but it does have notifications that can use officially-supported pusher extension to work.

      One major difference though - phpBB, Flarum and Laravel.io are PHP-based, so you can make them work on generally cheaper shared web hosting, meanwhile Discourse and NodeBB will require a server that can run Ruby or Node respectively - for example a Linux VPS.

      Which one is better depends on what you want then.
      Laravel.io seems to be most limited in terms of customization, unless there are some undocumented features on that front. So if there are any things you don't like about the way it looks or feels - don't choose it.
      If you like the Flarum tag structure and don't mind it lacking some things (well, it's a beta after all), it seems like the most performant option.
      phpBB? If you are willing to buy/develop some modern theme and spend time to configure it, sure. Otherwise I wouldn't recommend it.
      The decision between NodeBB and Discourse is harder, and while I prefer NodeBB, I'd say it's mostly down to your preferences, specifics of what you want to use the forum for and the preference for technology stack (Node, Express, MongoDB/Redis/Postgres + no major js framework outside of jQuery on front-end for NodeBB vs Ruby on Rails, Postgres + Ember.js on front-end for Discourse).

      Some unfortunately older topics on this (some will have much more recent replies, so might be useful to read them; I tried to include topics from meta-forums of other forum software and user forums based on software in question):

      • https://community.nodebb.org/topic/1835/which-is-better-nodebb-or-discourse
      • https://community.nodebb.org/topic/10827/why-i-chose-to-use-nodebb-over-phpbb-discourse-mybb-and-other-forums
      • https://discuss.flarum.org/d/2056-flarum-vs-nodebb
      • https://discuss.flarum.org/d/6952-how-is-flarum-different-from-discourse-and-other-forums
      • https://discuss.flarum.org/d/676-what-are-the-advantages-of-flarum-over-discourse
      • https://meta.discourse.org/t/which-is-better-discourse-or-flarum/71726
      • https://what.thedailywtf.com/topic/23993/nodebb-vs-discourse-showdown (just for context - this forum migrated to NodeBB from Discourse in 2016)
      • https://gamingexodus.com/t/nodebb-current-forum-vs-discourse/3012 (here there was a migration in the opposite direction in 2018)
      • https://www.reddit.com/r/webdev/comments/415nlp/discourse_flarum_nodebb_oh_my/
      • https://forums.linuxmint.com/viewtopic.php?t=231767&start=20

      Obviously remember that the answers will be biased essentially everywhere - here, towards NodeBB. On Discourse forums, towards Discourse. On Flarum - towards Flarum. Etc.

      posted in General Discussion
      oplik0
      oplik0
    • RE: message history in group chat

      Is it really most?
      First, WhatsApp, Signal and other encrypted communicators work that way for a reason. They can't read old messages because they don't have the keys to decrypt the old messages, even if for some reason they'd have access to their ciphertext form - which they also don't, as at least with Signal messages aren't even stored on the server after being delivered.
      So seeing message history from before joining would require getting other clients in the group to replay their messages just for the new person to even have access to them.

      By contrast, services that aren't E2EE and store messages on the server don't have either of these problems - so for example Messenger can easily just fetch a new member the old messages, and it does so.
      NodeBB isn't ent-to-end encrypted, and is entirely server based with AFAIK no local storage for messages at all - I don't think they're even cached in any way. So there isn't a technical limitation to implementing this.

      posted in Technical Support
      oplik0
      oplik0
    • RE: Which is the nodebb community theme

      You can actually use NPM to install from a specific branch of a GitHub repo. Just do npm install NodeBB/nodebb-theme-persona#timeline-style

      Right now the version in package.js on this branch is the same as on the main branch (10.3.16) so it should work without any changes to NodeBB package.json (not sure if the version of installed theme is checked at the startup, but with the same version it doesn't matter)

      Edit: but as Julian said it's work in progress and, so it may be buggy. Also, I'm not sure if NPM will update it from its registry automatically on your next nodebb upgrade or if you'll have to manually install it back.

      posted in Technical Support
      oplik0
      oplik0
    • RE: Which is the nodebb community theme

      It's this branch of Persona. Here is the (still work in progress from what I understood) PR: https://github.com/NodeBB/nodebb-theme-persona/pull/512

      julianlam created this issue in NodeBB/nodebb-theme-persona

      closed Timeline-style design for a topic's posts #512

      posted in Technical Support
      oplik0
      oplik0
    • RE: Postgres question

      @julian

      the database abstraction layer is fairly stable, we haven't had to make many changes to it at all for years.

      There definitely were changes to the database abstraction layer for Postgres with the latest one being less than a month ago: https://github.com/NodeBB/NodeBB/commits/master/src/database/postgres

      Though I get that you mean that there wasn't any big refactor or breaking changes not connected to general NodeBB update (like upgrade to socket.io 3, zscan etc.).
      In 2020 there were only 10 commits there and all were changes that applied to all databases.

      posted in General Discussion
      oplik0
      oplik0
    • RE: snowing theme

      It's really easy - it's just one script added to <head>: https://github.com/nextapps-de/snowflake
      So just go to Appearance>Custom Content>Custom Header in ACP and add this: <script src="https://cdn.jsdelivr.net/gh/nextapps-de/snowflake@master/snowflake.min.js"></script>

      posted in Technical Support
      oplik0
      oplik0
    • RE: Testing stage in GitLab pipeline

      NodeBB tests require database setup beforehand.
      I recommend just checking out how NodeBB currently does it with GitHub Actions or how it was done earlier with TravisCI

      I haven't used GitLab CI much, but I think the services part is pretty similar to GitHub Actions - there are some setup differences (per job variables instead of per service env for example), but I think just adapting the service configuration to GitLab syntax will be better than the bash based install from TravisCI

      posted in NodeBB Development
      oplik0
      oplik0