Can't logout in v0.7.3

Bug Reports

Suggested Topics


  • 0 Votes
    1 Posts
    209 Views

    NodeBB Version:
    1.10.2.
    (I have no more developer information about the used NodeBB as i am not a administrator)

    Exact steps to cause this issue:

    Open a existent thread Go with Tab key to 'Topic Tools' button Hit Cursor-Down Sub-menu opens Hit Cursor-Down Cursor stucks in item 'Lock Topic', next item in sub-menu is not selected

    What you expected:
    I expected to reach all menu items in sub-menu with Cursor-Down key as in other buttons sub-menues

    What happened instead:
    Cursor stucks in first item of sub-menu and next items can not be selected

    Additional:
    Submenu items reachable by mouse
    Keyboard access is needed for accessibility

    Sub-menu items of 'Topic Tools' not reachable by keyboard · Issue #7100 · NodeBB/NodeBB

    NodeBB version: 1.10.2. (I have no more developer information about the used NodeBB as i am not a administrator) Exact steps to cause this issue: Open a existent thread Go with Tab key to 'Topic Tools' button Hit Cursor-Down Sub-menu ope...

    favicon

    GitHub (github.com)

    A webdev in our company said:

    This is because NodeBB uses a hidden class to hide the opposite value (lock/unlock) so focus is lost when going over the hidden element.
    .
    This could be fixed by using a hidden attribute on the <li> element but the toggleClass code is in NodeBB core not the theme code.

    There is a need to fix this because accessibility by keyboard is important for some disabled or without-mouse users.

  • Pagination settings don't take

    Bug Reports
    6
    0 Votes
    6 Posts
    1k Views

    @teh_g said in Pagination settings don't take:

    @pichalite said in Pagination settings don't take:

    @dangeruss @PitaJ Don't think that's a bug. User settings won't let you use a number bigger than the number in ACP -> Settings -> Pagination.

    Sounds like a warning needs to appear if you go higher than that value!

    Wait so if I set a setting higher than that in ACP settings then it should work?

    Edit. Seems to have worked. Would be nice to have a max setting in ACP, so that the default settings are not also the max.

  • That's a bug

    Bug Reports
    3
    0 Votes
    3 Posts
    1k Views

    redis.

    The problem probably happened because we were in two people using the panel at the same time, and something went wrong.

    Apart from that, the server accepted a string ( "{category: cid}"**** or something similar ) in the place of a number, maybe some pre-checks on the incoming data should have been done.

    Now i resetted all and the problem is solved, so sorry if i can't give much infos but i am not practical with redis and node.js.

    **** EDIT:
    when writing that without the space a wild number appears, is that normal?

  • 0 Votes
    8 Posts
    3k Views

    Leave your feedback here, and we'll address it 🙂

    [composer] tags placeholder should include instructions · Issue #1618 · NodeBB/NodeBB

    Maybe: Separate tags with commas How does other software message this to users? (Too lazy to do research right now) Original thread: https://community.nodebb.org/topic/1634/0-4-3-problems-getting-tags-working#12225

    favicon

    GitHub (github.com)

  • 0 Votes
    8 Posts
    3k Views

    That warning means that someone is running a very old version of NodeBB's client side code (and simply hasn't refreshed, or hasn't cleared their browser cache). So not to worry 🙂