Glitch alert: Invalid warning being attached to threads

[C C]

There's a spurious "Caution: Old Thread" warning that is being attached to new topics. It requires multiple edits of playing around with the Prefix labels to finally get rid of it.

EDIT: Hah! I see this very thread is currently sporting it, so the problem is self-evident. I'm leaving it as evidence.

2nd EDIT: Apparently it's only temporary. Returning to the posts later, the advisory disappears.

[C C]

I still notice it intermittently appearing again on threads that others start. Sometimes it's there initially, then you reload or return later and it's gone.

[stryder]

I still notice it intermittently appearing again on threads that others start. Sometimes it's there initially, then you reload or return later and it's gone.

The original usage for this was down to how the site was setup.

I originally wanted to lock all threads after a year from being added to, however some of the members mentioned that sometimes they like to interact with an old thread rather than starting a new one. So instead of automatically locking them, I dropped a Javascript addition into the thread based upon the thread posters date. Unfortunately the javascript code used isn't particular brilliant it could of been tidied and tightened further. So it does behave odd with some threads. It shouldn't effect the threads too much although it can always be removed.

It's likely due to changes in security of browser practices that I haven't currently caught up with.

[stryder]

I still notice it intermittently appearing again on threads that others start. Sometimes it's there initially, then you reload or return later and it's gone.

The original usage for this was down to how the site was setup.

I originally wanted to lock all threads after a year from being added to, however some of the members mentioned that sometimes they like to interact with an old thread rather than starting a new one.  So instead of automatically locking them, I dropped a Javascript addition into the thread based upon the thread posters date.  Unfortunately the javascript code used isn't particular brilliant it could of been tidied and tightened further.  So it does behave odd with some threads.  It shouldn't effect the threads too much although it can always be removed.

It's likely due to changes in security of browser practices that I haven't currently caught up with.

Okay did think I had a fix, seems to not be the case I'll removed the offending bit of code.

[stryder]

Fun Fact:
Scivillage.com is now indexed by Bing! While that might not seem particular important to anyone, it's something that has bugged me for years. Bing for some reason dropped indexing the site some years back and I could never put a finger on what exactly it was causing it to assume there was an issue with the site.

I tried many different things, such as resubmitting manually to their index even asking the ChatGPT to no avail.

Since the removal of the piece of Javascript for the "Caution Old Thread" message... Bing is now indexing. So I guess it was checking the website core code for alterations (and possible security risk?!?) rather than seeing it bespoken.

[C C]

Fun Fact:
Scivillage.com is now indexed by Bing!  While that might not seem particular important to anyone, it's something that has bugged me for years.  Bing for some reason dropped indexing the site some years back and I could never put a finger on what exactly it was causing it to assume there was an issue with the site.

I tried many different things, such as resubmitting manually to their index even asking the ChatGPT to no avail.

Since the removal of the piece of Javascript for the "Caution Old Thread" message... Bing is now indexing.  So I guess it was checking the website core code for alterations (and possible security risk?!?) rather than seeing it bespoken.

Holy smoke. It's also showing up on DuckDuckGo now. I had given up on that ever happening, like Klaatu stepping out of a flying saucer in Washington, D.C.