Removing blue 'moved' tag from post

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
    18 Posts
    97 Views

    @Panda You’ll need to do that with js. With some quick CSS changes, it looks like this

    d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png

    The colour choice is still really hard on the eye, but at least you can now read the text

  • SEO and Nodebb

    Performance
    2
    2 Votes
    2 Posts
    42 Views

    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example

    https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1

    However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts

    https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365

    And also

    https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164

    It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”.

    Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.

  • Adding fileWrite to nodebb code

    Solved Configure
    16
    5 Votes
    16 Posts
    224 Views

    @eveh this might be a question for the NodeBB Devs themselves. In all honesty, I’m not entirely sure without having to research this myself.

  • Link vs Refresh

    Solved Customisation
    20
    8 Votes
    20 Posts
    501 Views

    @pobojmoks Do you see any errors being reported in the console ? At first guess (without seeing the actual code or the site itself), I’d say that this is AJAX callback related

  • 3 Votes
    8 Posts
    266 Views

    @qwinter yep, knew it was there somewhere 😁

  • 0 Votes
    6 Posts
    235 Views

    @jac just checked this again and although the image now shows I am still seeing the error message?

    IMG_20220118_200149.jpg

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

  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    747 Views

    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.