Is there any way to disable 'register' on the login page?

Solved Configure

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💗

  • 2 Votes
    11 Posts
    88 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?

  • Category For User

    Solved Configure
    11
    12 Votes
    11 Posts
    38 Views

    3.5.1 has now been released. I’ve just deployed it, so safe to do so!

  • Upgrade issues

    Solved Configure
    2
    2 Votes
    2 Posts
    45 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
    47 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.

  • WP / Woocommerce Mystery

    Solved Configure
    23
    12 Votes
    23 Posts
    84 Views

    @Panda said in WP / Woocommerce Mystery:

    Just back to my other question, have you ever used Shopify?
    It insists on a templating language to use any custom js.

    Not personally as never had any need, however, I do know that it uses Liquid for JS templating. It’s written in Ruby and is used to generate dynamic content on shop fronts. There’s zero reason as to why it wouldn’t work with data supplied by 3rd party API’s, although WordPress code won’t natively work for obvious reasons, and as such, this code would need to be re-written.

    The JS part will likely work with minor modification, but not the PHP file in it’s current form.

  • NodeBB: Consent page

    Solved Configure
    16
    4 Votes
    16 Posts
    217 Views

    @DownPW I still do not see any issues.

  • NodeBB: Creating pages

    Solved Configure
    9
    0 Votes
    9 Posts
    73 Views

    OK, I think I have figured out how to place a link in the footer which will click to a new page.

  • 0 Votes
    1 Posts
    141 Views

    I’ve seen plenty of useless error messages over my career in IT, but this one really takes the p…

    After recovering my Ghost blog, I was met with the below error

    sudonix@vps:~/domains/content.sudonix.com/public_html$ ghost start ✔ Checking system Node.js version - found v14.18.1 ℹ Ensuring user is not logged in as ghost user [skipped] ℹ Checking if logged in user is directory owner [skipped] ✔ Checking current folder permissions ✔ Validating config ✔ Checking memory availability ✔ Checking binary dependencies ✖ Starting Ghost: content-sudonix-com A GhostError occurred. Message: Ghost was able to start, but errored during boot with: Cannot read property 'config' of undefined Debug Information: OS: Ubuntu, v20.04.3 LTS Node Version: v14.18.1 Ghost Version: 4.22.4 Ghost-CLI Version: 1.18.0 Environment: production Command: 'ghost start' Additional log info available in: /home/sudonix/.ghost/logs/ghost-cli-debug-2021-11-22T11_29_19_297Z.log Try running ghost doctor to check your system for known issues.

    Now let’s be 100% transparent here. This error message means nothing to nobody, isn’t documented anywhere on the Ghost forums, and is as much use as a chocolate fireguard.

    I was ready to throw in the towel and choose another platform, then it suddenly dawned on me that I’m not using the default Casper theme, but Leibling, which of course, is missing. I downloaded this, and extracted it to the themes directory, and lo and behold…

    sudonix@vps:~/domains/content.sudonix.com/public_html$ ghost start ✔ Checking system Node.js version - found v14.18.1 ℹ Ensuring user is not logged in as ghost user [skipped] ℹ Checking if logged in user is directory owner [skipped] ✔ Checking current folder permissions ✔ Validating config ✔ Checking memory availability ✔ Checking binary dependencies ✔ Starting Ghost: content-sudonix-com ------------------------------------------------------------------------------ Your admin interface is located at: https://content.sudonix.com/ghost/ sudonix@vps:~/domains/content.sudonix.com/public_html$

    Something to bear in mind in case you run across the same issue.

    Shame on 👻 for not being more specific around the true origin of this error.