Follow

Happy “Don’t Forget to Update the Copyright Notice on Your Website” Day!

@imuggle It’s just a wallpaper I found on the Web years ago. No idea where it came from now. Here you go!

@bens @DazeEnd I think it’s less of a legal thing and more for visitors to get the sense the site is still being maintained.

@DazeEnd I don’t run any websites anymore, but back then it was always just programmatic the current year.

@Mpwg I can’t put JavaScript in the footer of my WordPress theme. (It gets stripped out.) I could of course modify the theme, but that would take a lot longer than the 60 seconds it takes to manually change the copyright notice each year.

@DazeEnd There is some dispute over whether the year should be this year or the year the site was created. I don’t know the right answer but most answers I see online seem to agree you only need the year the site was created.

@jsit I’ve always taken the approach of brand created year - current year e.g. 2003 - 2023 as depending on your country the year can imply when copyright takes effect from so changing it to current year only can actually be worse.

@DazeEnd
Or make that bit of the code update server-side so you don't need to update it manually?

@jamesthomson

@edaross @jamesthomson I can’t put JavaScript in the footer of my WordPress theme. (It gets stripped out.) I could of course modify the theme, but that would take a lot longer than the 60 seconds it takes to manually change the copyright notice each year.

@prsn Doesn’t work in my WordPress theme. I could of course modify the theme, but that would take a lot longer than the 60 seconds it takes to manually change the copyright notice each year.

@DazeEnd I’m no lawyer, but I’ve always wondered about this practice: Is it actually legal?

If you’ve made no changes to the content itself, can you just slap a new date on there? Does changing the date itself constitute a change that allows you to claim that the work was “made” in the new year?

@DazeEnd @jamesthomson Thanks for the reminder! I've now updated it to 2023... from 2019. (This has motivated me to actually dig out the syntax to do it automatically in Jekyll, so that's a plus.)

@DazeEnd I thought I was clever enough to auto this but heck, what a good reason to make some git commits on the new year!

@DazeEnd

Code for the Lazy Person who can add JavaScript to their CMSs templating system (Its 2023 why do you use something that doesn't allow for this‽)

<p>Copyright © Ted Tschopp <script>document.write(new Date().getFullYear())</script>. All Rights Reserved</p>

@TedT I can’t put JavaScript in the footer of my WordPress theme. (It gets stripped out.) I could of course modify the theme, but that would take a lot longer than the 60 seconds it takes to manually change the copyright notice each year.

@DazeEnd
1. Make a backup of your theme.
2. Goto Appearance > Theme Editor in your Wordpress dashboard. Select functions.php in and add the following code at the end.

```php
//Allow shortcodes in widgets
add_filter ('widget_text', 'do_shortcode');

function year_shortcode () {
$year = date_i18n ('Y');
return $year;
}
add_shortcode ('year', 'year_shortcode');
```

3. Then goto your footer and add:

```Wordpress
Copyright © [year] Charles Perry. All rights reserved.

@TedT Thanks, but I know know my way around WordPress. I’m no stranger to modifying themes and writing plugins.

@irdodd I can’t put JavaScript in the footer of my WordPress theme. (It gets stripped out.) I could of course modify the theme, but that would take a lot longer than the 60 seconds it takes to manually change the copyright notice each year.

Sign in to participate in the conversation
mastodon.cloud

Everyone is welcome as long as you follow our code of conduct! Thank you. Mastodon.cloud is maintained by Sujitech, LLC.