Comments on: Keep an Up-To-Date Copyright Notice on Your WordPress Blog

By: Updating the Copyright on your WP Blog | Writing Success

Updating the Copyright on your WP Blog | Writing Success — Mon, 05 Jan 2009 15:51:53 +0000

[...] shows, the correct copyright will accompany it. I’m not a techie, so I’ll refer you to Keep an Up-To-Date Copyright Notice on Your WordPress Blog on BloggingTips for more information on how to write the [...]

By: Greg@Mendham Real Es

Greg@Mendham Real Es — Mon, 05 Jan 2009 13:29:29 +0000

This is really cool! thanks a lot for the heads up and for the valuable information.

By: Dennis Edell

Dennis Edell — Sat, 03 Jan 2009 13:26:03 +0000

This is awesome, thanks! I think I'll wait 'till I upgrade though.

By: Aravind Jose T.

Aravind Jose T. — Sat, 03 Jan 2009 12:54:34 +0000

Thanks for the heads up.

But, I see a 2008 right there, in the footer, here !!

By: Luis

Luis — Sat, 03 Jan 2009 10:03:45 +0000

Nice post. I like the code functions you are using for automatic insertion of the copyright years. I chose to do it manually, I just opened my footer.php and changed the dates accordingly. Is true that we can forget to do this but the lesser code the better, I hate to bloat my WordPress themes mainly because I'm not a PHP expert.

Thanks for all you do. Luis.

By: Rajeev Edmonds

Rajeev Edmonds — Sat, 03 Jan 2009 08:32:13 +0000

This is awesome. Though I have blogger blogs, but I may need this in future when I'll shift to self hosted blog. Bookmarked…

By: jim

jim — Sat, 03 Jan 2009 00:24:56 +0000

I agree with Rarst on the point of code vs. static HTML. Granted, with caching, it's not a big deal, but ever little bit counts right? Speed kills!

By: Billy Mabray

Billy Mabray — Fri, 02 Jan 2009 16:37:13 +0000

Ha! Yeah, you're right about the "copyright copyright" thing. I see it that way so much that I just copied it without thinking about it.

This is all based on standard PHP and WP functions — none of which are going away anytime soon. You should always be a little wary of 3rd party code, but in this case I'm pretty confident it will hold up and not damage anything.

By: Rarst

Rarst — Fri, 02 Jan 2009 16:15:09 +0000

On topic – personally I prefer simple edit once a year to having bunch of extra code around. I would probably use it if it was WordPress native stuff, but the less third party things the less is probability of something going wrong.