There is a way to permanently address this. The ending copyright date can be a variable based upon the current year instead of hardcoded. Seems like this would resolve this issue moving forward. The downside is that bets could no longer be placed to see how long it takes to report the year is wrong each January.Can't complain.
We made it 6 days this year.
I think that's a record.
exactlyyour site has the correct date, so obviously it's important to you.
Community platform by XenForo
it was notCommunity software
before?
This site is running the latest version which has the correct year it will be released.Also worth noting, your site has the correct date, so obviously it's important to you.
It changed quite a long time ago now from "Forum software by XenForo" to "Community platform by XenForo".Community platform by XenForo
it was notCommunity software
before?
I believe using a variable for the current year is the way to go.
Don't you still claim copyright in 2022 to v2.2.8 Patch 1? If so, wouldn't it be okay to put in a variable placeholder for the ending copyright date that automatically appears?The copyright on released versions pertains to the year they were released.
The end date does not impact the dates we're claiming the copyright for.Don't you still claim copyright in 2022 to v2.2.8 Patch 1? If so, wouldn't it be okay to put in a variable placeholder for the ending copyright date that automatically appears?
People think the XenForo copyright notice is for their website in general, it isn't. It is just for the XenForo Software which as mentioned above was last updated in 2021, so it is covered by the current copyright notice.
If you want to show the current year, for your website:
Find the phrase:
extra_copyright
ACP: Appearance>Search Phrases
Then in 'Phrase text' add the following:
<br>
Content © Your_domain.com 2(startyear)-<script type="text/javascript">
var today = new Date()
var year = today.getFullYear()
document.write(year)
</script>, all rights reserved
This should still work.
Content © Your_domain.com <startyear>-{{ date($xf.time, 'Y') }}, all rights reserved
Script kiddies are just going to try any public exploit regardless of version; if they don't work, they don't work, and they'll go back to crying in their basement.On a related note, the copyright can be removed for 300 bucks for those not wanting to wait several weeks every year for it to be updated.
I believe using a variable for the current year is the way to go. It's pretty obvious this is an issue that gets brought up every year, yet has no solution other than joking around. Such an easy solution. Also makes it a tiny bit more confusing for hackers to search for old/outdated sites using a google search for the copyright code.
The symbol signifies copyright (right to copy) whether it is registered or not. Unlike R and TM, where one signifies registration of a trademark.Although unless you have actually copyrighted your site, it's meaningless ...
We use essential cookies to make this site work, and optional cookies to enhance your experience.