Community

So when's the next release?

General Discussion

Suggested Topics

  • tallshipT

    Couldn't find a ready to go topic to jump in on - this is really kewl stuffs!

    General Discussion
    1 Votes
    3 Posts
    179 Views
    gotwfG

    The obvious clue bat here is that Flarum is based on PHP glue scripts. So you're always going to suffer that. No matter what. Mitigate? Sure. To various degrees. But yer' still sufferin'. NodeJS makes sense. Especially modern times. Warts? Indubitably. But as do all things. Take the good with the not so good.

    tl;dr?? NodeBB scales really, really, really well! 😜

    And is kinda' fun to work with. Cuz the devs are at the least, tolerable, and other times... pretty cool, even. 😎 🕶

    I would suggest you explore db backend options. In particular, MongoDB and PostgreSQL. Investigate scaling the system. Then ponder doing similarly w/Flarum. No contest fer' me. But, as w/all things, your mileage may vary....

    Have fun! 🐕 🌴 🌴

    Edit: P.S.; Asciidoc rules! Markdown drools!

  • MJM

    Is there a way to see guest IP’s and is there a way to ban them?

    Solved General Discussion
    0 Votes
    9 Posts
    2142 Views
    barisB

    https://github.com/NodeBB/NodeBB/issues/6311 🔜

  • B

    Average user can't upload vidoes

    General Discussion
    0 Votes
    6 Posts
    1632 Views
    Lara JohnsonL

    I too have problem with uploading and could you find a solution for this

  • AnimalA

    Meta tags with 'og' support ?

    Unsolved General Discussion
    1 Votes
    1 Posts
    835 Views
    AnimalA

    Hello

    Was wondering about how to support open-graph og meta tags, while posting url's

    In facebook, whatsapp etc, when a url is pasted in composer, it automatically pulls/displays title, image etc.

    How can I do that in nodebb ?

    Thanks in advance !

  • PitaJP

    Plugin button doesn't show plugin page

    General Discussion
    0 Votes
    5 Posts
    1391 Views
    PitaJP

    git rev-parse HEAD returns aa116e6b4d2f42731729db01f28875494988a684

    I've looked through the Chrome dev console in the network section and it seems that ajaxify is receiving 304: Not modified responses, and gets stuck on opacity:0. A very weird functionality. All of the elements are loaded in, but they are all invisible. Very odd.

    There is an Uncaught Error: Mismatched anonymous define() module error that occurs on page load in ajaxify.

    Okay, I guess never mind. One of the external sources I was including was causing the problem. I removed the define call and now it's working.

Copyright © 2023 NodeBB | Contributors