Skip to content
Sudonix

Bug Report

Solved Bugs

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

  • crazycellsundefined

    "most votes" ranking option is not respecting the plugin

    Bugs
    5
    3 Votes
    5 Posts
    155 Views
    phenomlabundefined

    @crazycells Agreed. It takes a more sensible approach. Nobody ever upvotes the first post - it’s usually much further down as the conversation progresses.

  • Pandaundefined

    adding some console.log to Nodebb

    Solved Customisation
    4
    1 Votes
    4 Posts
    477 Views
    phenomlabundefined

    @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.

  • cagatayundefined

    Q&A Plugin Changes NodeBB

    Solved Customisation
    25
    6 Votes
    25 Posts
    2k Views
    cagatayundefined

    @phenomlab said in Q&A Plugin Changes NodeBB:

    float: right;
    left: 10px;
    }

    worked thank you 🙂

  • Salaundefined

    Fresher in Nodebb install

    General
    24
    15 Votes
    24 Posts
    2k Views
    phenomlabundefined

    @Hari I’ve been reading a lot about APO. Looks impressive.

  • DownPWundefined

    Plugin reaction Bug

    Solved Customisation
    15
    0 Votes
    15 Posts
    689 Views
    phenomlabundefined

    @DownPW That was going to be my next suggestion 🙂

  • phenomlabundefined

    FIXED: Annoying cosmetic bug on mobile view

    Moved Bugs
    13
    3 Votes
    13 Posts
    708 Views
    phenomlabundefined

    And now, after all this time 😕 I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block 🤦

    .tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; }

    And, add this below to make it more specific.

    .emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }
  • DownPWundefined

    [NODEBB] Help for my custom CSS

    Solved Customisation
    193
    38 Votes
    193 Posts
    30k Views
    DownPWundefined

    OMG make sense

    Thanks dude 🙂

  • RiekMediaundefined

    NodeBB Design help

    Solved Customisation
    8
    2 Votes
    8 Posts
    833 Views
    phenomlabundefined

    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ?

    For the record, this is what I added

    #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; }

    The /categories page seems a bit messed up, so looking at that currently

    EDIT - issued some override CSS in the CATEGORIES widget

    <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style>

    That should resolve the /categories issue.