NodeBB - Created pages not found?

[JAC]

@jac I’ve deleted them and re -created them.

Once in widgets it seems like the old widgets (created pages) are still there with a capital letter which was the first one I created.

It needs to work without a capital letter, but it won’t show as a page without it? I wonder if you can take a look?

Many thanks

[JAC]

@jac Works fine with the capital letter here as soon as you remove the capital letter (although that’s now the created page) it shows this.

[phenomlab]

@jac I’ll have a look at this later.

[phenomlab]

@jac I’ve had a look at this, and he reason as to why this fails is because the slug specified starts with a capital letter. Under Windows, there is no distinction, but under Linux (which is what your VPS is running), this matters in the sense that you can use the same wording but different cases allows you to treat them as separate pages.

To work around this, the “Path To Page” value should always be in lower case. I’ve changed these so they should work now

It would be pretty rare for a URL to contain uppercase letters. If you do a Google search for anything you’ll notice the URL returned is always lower case as that’s the industry standard.

[JAC]

@phenomlab said in NodeBB - Created pages not found?:

@jac I’ve had a look at this, and he reason as to why this fails is because the slug specified starts with a capital letter. Under Windows, there is no distinction, but under Linux (which is what your VPS is running), this matters in the sense that you can use the same wording but different cases allows you to treat them as separate pages.

To work around this, the “Path To Page” value should always be in lower case. I’ve changed these so they should work now

It would be pretty rare for a URL to contain uppercase letters. If you do a Google search for anything you’ll notice the URL returned is always lower case as that’s the industry standard.

Absolutely, I’d changed them to lower case and they still returned a page not found message. However when I entered a capital letter at the start the page then was showing fine.

[JAC]

@jac said in NodeBB - Created pages not found?:

@phenomlab said in NodeBB - Created pages not found?:

@jac I’ve had a look at this, and he reason as to why this fails is because the slug specified starts with a capital letter. Under Windows, there is no distinction, but under Linux (which is what your VPS is running), this matters in the sense that you can use the same wording but different cases allows you to treat them as separate pages.

To work around this, the “Path To Page” value should always be in lower case. I’ve changed these so they should work now

It would be pretty rare for a URL to contain uppercase letters. If you do a Google search for anything you’ll notice the URL returned is always lower case as that’s the industry standard.

Absolutely, I’d changed them to lower case and they still returned a page not found message. However when I entered a capital letter at the start the page then was showing fine.

Looks like it is working now mate, thanks very much. I will find and re-add the fixtures code.

[phenomlab]

@jac Ok. Good.

[JAC]

@phenomlab said in NodeBB - Created pages not found?:

@jac Ok. Good.

I think when the links from the Nav bar drop-down are clicked the page loads but the football content (table) for example doesn’t load.

Could this be because it’s asked to open in a new tab? Although this doesn’t load either.

[JAC]

@jac however on more digging I’ve found that if you go directly to the link then the table shows up no issues.

[phenomlab]

@jac Yes, this is likely to be an issue with how the script is being called. I’m guessing the page loads when accessed directly, but not via the forum itself ?

EDIT - suspicion confirmed. The page loads without issue if accessed directly.

Checking

[phenomlab]

@jac this should work now. It’s a little primitive, and means the page has to load twice, but it’ll work as desired. Essentially, the below code when added to each widget will force the page to reload directly

<script>
$(window).on('action:ajaxify.end', function (data) {
    location.reload();
});
</script>

[JAC]

@phenomlab said in NodeBB - Created pages not found?:

@jac this should work now. It’s a little primitive, and means the page has to load twice, but it’ll work as desired. Essentially, the below code when added to each widget will force the page to reload directly

<script>
$(window).on('action:ajaxify.end', function (data) {
    location.reload();
});
</script>

Brilliant, thank you very much Mark!

Will try this again now. Not been on here much as the Mrs has Covid so we are all off not feeling great.

[phenomlab]

@jac Sorry to hear that. Hope everything’s ok.

[JAC]

@phenomlab said in NodeBB - Created pages not found?:

@jac Sorry to hear that. Hope everything’s ok.

Thanks Mark, appreciate it.

Fortunately for now it’s just a temperature and a barking cough.

So I’ve got my son at home too as we are awaiting his PCR result to see if he can go back into school. It’s a strange one, if his result comes back as negative he’s allowed back into school , but I have to stay off even though my lateral flow results were negative despite feeling unwell all week it was only on Tuesday night that the Mrs had similar symptoms to me and did a test and was negative on all three just be sure.

[phenomlab]

@jac A strange setup indeed. I have one of my team at work who has tested positive and needs to self-isolate.

[JAC]

@phenomlab definitely strange, as I’ve had the result back today from the PCR test done on Wednesday and it’s positive despite 3 lateral flow tests being negative.

[phenomlab]

@jac Yeah, not surprised. I’ve heard numerous stories of multiple LF tests showing as negative, when a PCR is positive.

[JAC]

@phenomlab absolutely, seems a pointless exercise really for many to do the lateral flow test for it to be falsely negative to then go in work etc and spread it when being genuinely positive.

[phenomlab]

@jac Exactly. Hard point to argue.