<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Efficient permalink strategies for WordPress</title>
	<atom:link href="http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/</link>
	<description>WordPress, web development, and world domination.</description>
	<lastBuildDate>Sat, 11 Feb 2012 20:29:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19719</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: ajaimesv (Andres Jaimes)</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-175502</link>
		<dc:creator>ajaimesv (Andres Jaimes)</dc:creator>
		<pubDate>Tue, 22 Mar 2011 05:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-175502</guid>
		<description>Sí, por esto los permalinks de wordpress debe ser post_id o post_id/postname... http://tinyurl.com/cyensm</description>
		<content:encoded><![CDATA[<p>Sí, por esto los permalinks de wordpress debe ser post_id o post_id/postname&#8230; <a href="http://tinyurl.com/cyensm" rel="nofollow">http://tinyurl.com/cyensm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: firedune (Benavente Patricio)</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-175500</link>
		<dc:creator>firedune (Benavente Patricio)</dc:creator>
		<pubDate>Sun, 20 Mar 2011 04:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-175500</guid>
		<description>Efficient permalink strategies for WordPress http://tinyurl.com/cyensm</description>
		<content:encoded><![CDATA[<p>Efficient permalink strategies for WordPress <a href="http://tinyurl.com/cyensm" rel="nofollow">http://tinyurl.com/cyensm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L?m bàn v? c?u trúc link trong Wordpress – H? Trúc Blog</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-175355</link>
		<dc:creator>L?m bàn v? c?u trúc link trong Wordpress – H? Trúc Blog</dc:creator>
		<pubDate>Thu, 10 Feb 2011 11:42:56 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-175355</guid>
		<description>[...] http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks" rel="nofollow">http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-175348</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 09 Feb 2011 20:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-175348</guid>
		<description>This inefficient URL parsing scheme is why you should avoid doing large sites in WP. We have a client with over 500 pages and the regular expressions that WP has to parse for every page load are well over 1meg of text. In fact, WP is getting so slow due to its size that it barely lets us delete any pages... the irony. Why not create a simple look up table of URL to page/post like Drupal does? Regular expressions are definitely not the best approach, and having to serialize them every page load is worse. This is not a problem &#039;every CMS&#039; has, only WP.</description>
		<content:encoded><![CDATA[<p>This inefficient <acronym title='Uniform Resource Locator'><span class='caps'>URL</span></acronym> parsing scheme is why you should avoid doing large sites in <acronym title='WordPress'><span class='caps'>WP</span></acronym>. We have a client with over 500 pages and the regular expressions that <acronym title='WordPress'><span class='caps'>WP</span></acronym> has to parse for every page load are well over 1meg of text. In fact, <acronym title='WordPress'><span class='caps'>WP</span></acronym> is getting so slow due to its size that it barely lets us delete any pages&#8230; the irony. Why not create a simple look up table of <acronym title='Uniform Resource Locator'><span class='caps'>URL</span></acronym> to page/post like Drupal does? Regular expressions are definitely not the best approach, and having to serialize them every page load is worse. This is not a problem &#8216;every <acronym title='Content Management System'><span class='caps'>CMS</span></acronym>&#8217; has, only <acronym title='WordPress'><span class='caps'>WP</span></acronym>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angie</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-174936</link>
		<dc:creator>Angie</dc:creator>
		<pubDate>Sun, 02 Jan 2011 01:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-174936</guid>
		<description>The Wordpress Codex still shows that structure in several of its examples of custom permalinks. There is a note about it not being a good structure to use but it is below the examples. I hope they remove them because it&#039;s confusing!</description>
		<content:encoded><![CDATA[<p>The WordPress Codex still shows that structure in several of its examples of custom permalinks. There is a note about it not being a good structure to use but it is below the examples. I hope they remove them because it&#8217;s confusing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Référencement WordPress &#8211; Opimiser vos permaliens &#124; Haka Référencement</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-174640</link>
		<dc:creator>Référencement WordPress &#8211; Opimiser vos permaliens &#124; Haka Référencement</dc:creator>
		<pubDate>Thu, 23 Dec 2010 13:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-174640</guid>
		<description>[...] Nous vous déconseillons d’utiliser ces 3 structures car même si elles sont optimisées pour le référencement, elles vont ralentir fortement le temps de chargement de vos pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] Nous vous déconseillons d’utiliser ces 3 structures car même si elles sont optimisées pour le référencement, elles vont ralentir fortement le temps de chargement de vos pages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Canonical URL&#8217;s, Optimized Permalinks &#124; Cordobo</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-174482</link>
		<dc:creator>Canonical URL&#8217;s, Optimized Permalinks &#124; Cordobo</dc:creator>
		<pubDate>Fri, 17 Dec 2010 16:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-174482</guid>
		<description>[...] the new permalink structure is in some cases faster because of the way wordpress stores the URL information in the database (see further: Efficient permalink strategies for WordPress) [...]</description>
		<content:encoded><![CDATA[<p>[...] the new permalink structure is in some cases faster because of the way wordpress stores the URL information in the database (see further: Efficient permalink strategies for WordPress) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dougal</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-172650</link>
		<dc:creator>Dougal</dc:creator>
		<pubDate>Mon, 29 Nov 2010 17:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-172650</guid>
		<description>Remember, the problem discussed here only applies when the configured permalink structure causes ambiguity between matching permalinks for posts and pages. Under most normal circumstances, the WordPress rewrite rules are very efficient.</description>
		<content:encoded><![CDATA[<p>Remember, the problem discussed here only applies when the configured permalink structure causes ambiguity between matching permalinks for posts and pages. Under most normal circumstances, the WordPress rewrite rules are very efficient.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress : Optimiser vos permaliens &#124; Haka Référencement</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-172614</link>
		<dc:creator>WordPress : Optimiser vos permaliens &#124; Haka Référencement</dc:creator>
		<pubDate>Mon, 22 Nov 2010 14:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-172614</guid>
		<description>[...] Nous vous déconseillons d’utiliser ces 3 structures car même si elles sont optimisées pour le référencement, elles vont ralentir fortement le temps de chargement de vos pages. [...]</description>
		<content:encoded><![CDATA[<p>[...] Nous vous déconseillons d’utiliser ces 3 structures car même si elles sont optimisées pour le référencement, elles vont ralentir fortement le temps de chargement de vos pages. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://dougal.gunters.org/blog/2009/02/04/efficient-wordpress-permalinks/#comment-172598</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Thu, 18 Nov 2010 19:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/?p=1431#comment-172598</guid>
		<description>I think this discussion is obsolete. Why not do away with &quot;permalinks&quot; in the DB?


In my opinion, the whole concept of storing &quot;permalinks&quot; - a hardcoded link for each page in a database is mad! Even if WP had a mapping table (post &lt;=&gt; link) the server must still look through potentially thousands of records with each request. On top of that comes the headache if anything needs to be changed at some point.


I&#039;m puzzled as to why WP doesn&#039;t just use some general rewrite rules that you can specify and which are mapped to querystring parameters, just like in .htaccess. The same rules could be applied in a function to create the URLs for display on the site.


Say you had a CMS for shops. Each shop was a post. The shops had products that was also posts. Here is an example in the syntax used by htaccess, but rules could be handled by the WP parsing function just the same:


RewriteRule ^/shops/([0-9]+)/products/([0-9]+)/*$ /index.php?post_id=$2&amp;post_type=products [L,I]
RewriteRule ^/shops/([0-9]+)/products/*$ /index.php?page_id=1248&amp;shop_id=$1 [L,I]
RewriteRule ^/shops/([0-9]+)/*$ /index.php?post_id=$2&amp;post_type=shops [L,I]
RewriteRule ^/shops/*$ /index.php?page_id=56 [L,I]


Nothing besides a few rules would ever need to be stored in the DB, and requests would be lightning fast.</description>
		<content:encoded><![CDATA[<p>I think this discussion is obsolete. Why not do away with &#8220;permalinks&#8221; in the DB?</p>
<p>In my opinion, the whole concept of storing &#8220;permalinks&#8221; &#8211; a hardcoded link for each page in a database is mad! Even if WP had a mapping table (post &lt;=&gt; link) the server must still look through potentially thousands of records with each request. On top of that comes the headache if anything needs to be changed at some point.</p>
<p>I&#8217;m puzzled as to why WP doesn&#8217;t just use some general rewrite rules that you can specify and which are mapped to querystring parameters, just like in .htaccess. The same rules could be applied in a function to create the URLs for display on the site.</p>
<p>Say you had a CMS for shops. Each shop was a post. The shops had products that was also posts. Here is an example in the syntax used by htaccess, but rules could be handled by the WP parsing function just the same:</p>
<p>RewriteRule ^/shops/([0-9]+)/products/([0-9]+)/*$ /index.php?post_id=$2&amp;post_type=products [L,I]<br />
RewriteRule ^/shops/([0-9]+)/products/*$ /index.php?page_id=1248&amp;shop_id=$1 [L,I]<br />
RewriteRule ^/shops/([0-9]+)/*$ /index.php?post_id=$2&amp;post_type=shops [L,I]<br />
RewriteRule ^/shops/*$ /index.php?page_id=56 [L,I]</p>
<p>Nothing besides a few rules would ever need to be stored in the DB, and requests would be lightning fast.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: dougal.gunters.org @ 2012-02-12 02:45:50 by W3 Total Cache -->
