Skip to content

Error shows as visitor views post

Moved Configure

  • Getting Eror When Started NodeBB

    Solved Configure
    7
    2 Votes
    7 Posts
    257 Views

    @phenomlab yes i did.

    i deleted one of plugin then it started to work normally.

  • 2 Votes
    11 Posts
    320 Views

    @veronikya said in mongodb replica set:

    The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly
    Solution:
    Edit the /etc/resovel.conf file
    Add 127.0.0.53

    One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?

  • Upgrade issues

    Solved Configure
    2
    2 Votes
    2 Posts
    136 Views

    Use this code

    git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x

    And you will have the latest version without specifying it

    https://docs.nodebb.org/configuring/upgrade/

  • 2 Votes
    9 Posts
    237 Views

    @Panda I see why - if you check the browser console, there’s an error logged there. This is from one of my VM’s

    image.png

    There is a decision tree that pulls the value of the editor theme from the saved browser settings on each load, but that fails if the theme has never been changed, and the user has the default (in your case, you are using light mode, so it serves “flatly” by default, but the editor itself is never set and returns null

    This below code changes that

    /* If savedTheme is undefined it will return null - based on this, we assume that the user has the default theme selected and never changed it, so we'll need to force that here */ if(!savedTheme) { var savedTheme = "flatly"; }

    If you reload your browser and test again, it should work properly.

  • 3 Votes
    16 Posts
    490 Views

    @phenomlab
    Ah, got it working!
    I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters.
    So made the new fork title longer and button responded.

  • 2 Votes
    19 Posts
    579 Views

    @phenomlab Work now 😉

  • 1 Votes
    1 Posts
    630 Views
    No one has replied
  • 0 Votes
    12 Posts
    526 Views

    @jac Not necessarily, no. The domain redirect is purely so that older links that point to the previous domain don’t just spit out a 404 error message when someone tries to access them.

    However, if the domain is seldom used, then why would you need the redirect in the first place (a point which you mentioned below). I’m still struggling to understand why you’d need two sites with the same information if the other domain is rarely used