While perusing some websites, looking at html code, I saw something interesting:
A company had used Javascript to update the copyright date of its website using Javascript. This is the code.
|
1 |
Copyright © 2005-<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" data-wp-preserve="%3Cscript%20type%3D%22text%2Fjavascript%22%3Edocument.write(new%20Date().getFullYear())%3B%3C%2Fscript%3E" data-mce-resize="false" data-mce-placeholder="1" class="mce-object" width="20" height="20" alt="<script>" title="<script>" /> This Company. All rights reserved. |
Of course, as a Force.com developer, I prefer to use Visualforce and Apex over Javascript (as it makes the client thinner -
thick clients are not my preferred modus operandi).
This is the Visualforce version of the above code; it requires no Apex controller nor extension, and will always display the current year.
|
1 |
Copyright © 2005-{!year(today())} This Company. All rights reserved. |
Feel free to use this snippet in your Visualforce pages (including Sites) to ensure that on January 1, you won't look foolish for failing to (shudder) manually
update the footer in your site template.
Happy coding!
RSS Feed
My footer does as you suggest… but I thought to read up on it just now:
It seems that you don’t need a year on a copyright statement as any content always gets life+70 years, regardless of whether it has a copyright statement. The statement is useful though as it states clearly that you own the content.
Adding the current year may not be helpful: if someone looks at a stolen copy of your content alongside your content, your content may look like the stolen one as it will be dated the current year.
http://stackoverflow.com/questions/2390230/do-copyright-dates-need-to-be-updated