Skip to content

Difficult to move posts now, on mobile.

Bugs

Related Topics
  • Test of youtube embeds

    Solved Configure
    14
    11 Votes
    14 Posts
    286 Views

    @phenomlab Perfect!!! Many thanks.

  • 4 Votes
    8 Posts
    480 Views

    @Panda said in Upgrade to NodeBB v3? 2BB or not 2BB, that is the question!:

    So although thats a plugin it has Widget like element and stopped working on the Theme change

    Which is normal based on the widgets being reset when you change themes.

  • 36 Votes
    55 Posts
    5k Views

    @DownPW I see why. The code relies on the existence of

    [component="topic/quickreply/container"]

    However, this by definition means that the below has to be enabled

    aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png

    It will then work

    7fb38631-e0f3-46ef-b652-00929d927b13-image.png

    For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component.

    The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on 🙂

  • NodeBB v3

    Announcements
    2
    3 Votes
    2 Posts
    235 Views

    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.

  • Plugin reaction Bug

    Solved Customisation
    15
    0 Votes
    15 Posts
    948 Views

    @DownPW That was going to be my next suggestion 🙂

  • background color of the footer area

    Solved Customisation
    7
    7 Votes
    7 Posts
    524 Views

    @phenomlab thank you very much 🙂

  • FIXED: Annoying cosmetic bug on mobile view

    Moved Bugs
    13
    3 Votes
    13 Posts
    1k Views

    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; }
  • Display tweets in widget [NodeBB]

    Solved Customisation
    29
    4 Votes
    29 Posts
    3k Views

    @phenomlab brilliant, many thanks Mark 😁