Skip to content

Top Ranked Forums

Chitchat

  • Page control arrows for PWA

    Solved Customisation
    27
    25 Votes
    27 Posts
    419 Views

    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems.

    /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android }

    Once you’re in that rabbit hole, it’s impossible to get out of it.

  • Bug Report

    Solved Bugs
    43
    21 Votes
    43 Posts
    889 Views

    @crazycells yep. I get it! Good point.

  • 50 Votes
    146 Posts
    18k Views

    Updated git for above change

    https://github.com/phenomlab/nodebb-harmony-threading/commit/14a4e277521d83d219065ffb14154fd5f5cfac69

  • 1 Votes
    4 Posts
    477 Views

    @eeeee if you’re using the console, you could try

    node app.js > app.log 2>&1

    This would redirect stdout to a file named app.log and redirect stderr to stdout.

    I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log.

    Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.

  • 3 Votes
    17 Posts
    461 Views

    @mventures Ok. No issues

  • 11 Votes
    14 Posts
    610 Views

    @dave1904 excellent news. Thanks for the feedback

  • 0 Votes
    9 Posts
    804 Views

    @downpw I’m inclined to agree with this. There isn’t much else you can do, and provided it works with no odd looking artefacts in other browsers, then ok. The :before and :after are pseudo classes and very well supported across all browsers (except perhaps Internet Exploder, but who uses that these days ?)

  • 10 Votes
    28 Posts
    2k Views

    @marusaky Good post. The real issue with Flarum is that even the most minor of changes requires a extension, which is crazy. With NodeBB, you can make changes on the fly very easily, and without too much effort.

    There is an element of learning when it comes to making changes to any platform, but Javascript is not difficult at all once you get used to it, and there’s also extensive support for jQuery (and hundreds of code snippets on the internet you can easily adapt and tailor to your own needs)

    For years, phpBB used to reign supreme - now it’s incredibly dated, and always did have the most confusing admin panel I’ve ever seen.