Comments on: Podcast Clean Up: WordPress 101 Permalink Power https://libsyn.com/blog/podcast-clean-up-wordpress-101-permalink-power/ Wed, 27 Mar 2013 01:30:04 +0000 hourly 1 https://wordpress.org/?v=6.7.2 By: Elsie https://libsyn.com/blog/podcast-clean-up-wordpress-101-permalink-power/#comment-212 Wed, 04 Jan 2012 19:17:04 +0000 http://bloggy.libsyn.com/?p=963#comment-212 Very interesing. Thanks Daniel for the wisdom. 

elsie escobar
412 206 9642
elsiesyogakula.com
elsieescobar.com
@yogeek

]]>
By: Daniel J. Lewis https://libsyn.com/blog/podcast-clean-up-wordpress-101-permalink-power/#comment-213 Wed, 04 Jan 2012 13:29:13 +0000 http://bloggy.libsyn.com/?p=963#comment-213 I've seen mixed opinions on revealing the date. Some themes (or just peoples' choices) hide the posted date. This is terribly annoying when the author is not a good writer and they use relative terms and never reveal an absolute date.

Some people feel that a post with a date will seem outdated after a while. I personally disagree. Especially with technical information, I want to know when the post was written so I can figure out whether it's still relevant.

I think it's more important to have the date on the page than in the URL.

And adding a date won't allow WordPress to use the exact same slug, such as:

2011/top-ten-apps
2012/top-ten-apps

Instead, WordPress would turn it into:

2011/top-ten-apps
2012/top-ten-apps-2

]]>
By: Elsie https://libsyn.com/blog/podcast-clean-up-wordpress-101-permalink-power/#comment-211 Wed, 04 Jan 2012 05:26:30 +0000 http://bloggy.libsyn.com/?p=963#comment-211 Thanks for the info Daniel! Do you think it's beneficial to have the year? I often search for the date on people's posts to see how current the article is, especially if I'm searching for the most up to date information. What do you think?

]]>
By: Daniel J. Lewis https://libsyn.com/blog/podcast-clean-up-wordpress-101-permalink-power/#comment-210 Mon, 02 Jan 2012 22:11:04 +0000 http://bloggy.libsyn.com/?p=963#comment-210 Having the year can be nice, but it's certainly no longer required with WordPress 3.3. There used to be a performance penalty to /%postname%/, but they fixed that in WordPress 3.3.

]]>