<?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: Is Joomla 1.5 RC 1 Ready for Search Engine Optimization?</title>
	<atom:link href="http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/feed/" rel="self" type="application/rss+xml" />
	<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/</link>
	<description>Getting Joomla websites to reach their Full Potential by Optimization for Search Engines</description>
	<lastBuildDate>Sat, 24 Jul 2010 20:12:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-3061</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Fri, 21 Sep 2007 20:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-3061</guid>
		<description>@Peter

Changes could be upgrades from a Database point of view, other files coming into the package and removal of others.

It is a RC2 release and there will be a RC3 release...

So the Upgrade paths of RC2 to RC3 and to the first Stable release could become a problem.

Check also the error questions on http://forum.joomla.org/index.php#14 

One of my own reasons not to swith yet is that the SEF Functions of 1.5 are not implemented fully.
Also the small amount of extensions available is a reason not to switch to 1.5 for Live sites, that need to be fast and stable.</description>
		<content:encoded><![CDATA[<p>@Peter</p>
<p>Changes could be upgrades from a Database point of view, other files coming into the package and removal of others.</p>
<p>It is a RC2 release and there will be a RC3 release&#8230;</p>
<p>So the Upgrade paths of RC2 to RC3 and to the first Stable release could become a problem.</p>
<p>Check also the error questions on <a href="http://forum.joomla.org/index.php#14" >http://forum.joomla.org/index.php#14</a> </p>
<p>One of my own reasons not to swith yet is that the SEF Functions of 1.5 are not implemented fully.<br />
Also the small amount of extensions available is a reason not to switch to 1.5 for Live sites, that need to be fast and stable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Muusers - Meeuwsen</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-3060</link>
		<dc:creator>Peter Muusers - Meeuwsen</dc:creator>
		<pubDate>Fri, 21 Sep 2007 19:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-3060</guid>
		<description>Pathos: What will be the changes that you are referring to, that makes you think it&#039;s not wise to run RC2 now?</description>
		<content:encoded><![CDATA[<p>Pathos: What will be the changes that you are referring to, that makes you think it&#8217;s not wise to run RC2 now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-3059</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Fri, 21 Sep 2007 19:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-3059</guid>
		<description>@r4lph

Please check if your .htaccess file is setup the right way and you renamed the file to .htaccess 

Otherwise please first try just using the first option only.
If that works okÃ© you know you have an error in you .htaccess file, or your server does not support the mod_rewrite option on Apache.

P.s. I would suggest not using the 1.5 RC2 version for Live Production sites, as there will be some changes in RC3..</description>
		<content:encoded><![CDATA[<p>@r4lph</p>
<p>Please check if your .htaccess file is setup the right way and you renamed the file to .htaccess </p>
<p>Otherwise please first try just using the first option only.<br />
If that works okÃ© you know you have an error in you .htaccess file, or your server does not support the mod_rewrite option on Apache.</p>
<p>P.s. I would suggest not using the 1.5 RC2 version for Live Production sites, as there will be some changes in RC3..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: r4lph</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-3058</link>
		<dc:creator>r4lph</dc:creator>
		<pubDate>Fri, 21 Sep 2007 17:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-3058</guid>
		<description>when i activate both SEO-functions i cannot reach submenus the first menu-page reloads on click...</description>
		<content:encoded><![CDATA[<p>when i activate both SEO-functions i cannot reach submenus the first menu-page reloads on click&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2613</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 25 Aug 2007 23:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2613</guid>
		<description>@Pathos
Yes. It&#039;s the ItemID number, but I just downloaded the codes yesterday. I may need do it again to see what will happen.</description>
		<content:encoded><![CDATA[<p>@Pathos<br />
Yes. It&#8217;s the ItemID number, but I just downloaded the codes yesterday. I may need do it again to see what will happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2610</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Sat, 25 Aug 2007 21:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2610</guid>
		<description>@Tom
Please check if you have the latest release and not a nightly build.

The number looks like the part that was mentioned before on the developers Blog as the use of the content ItemID as part of the URL to insure the uniqueness off the URL.

Could you check if the 44 is indeed the ItemID number of the content?</description>
		<content:encoded><![CDATA[<p>@Tom<br />
Please check if you have the latest release and not a nightly build.</p>
<p>The number looks like the part that was mentioned before on the developers Blog as the use of the content ItemID as part of the URL to insure the uniqueness off the URL.</p>
<p>Could you check if the 44 is indeed the ItemID number of the content?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2604</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 25 Aug 2007 15:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2604</guid>
		<description>Hi, Hi:

I played Joomla 1.5 RC 1 for a while to see how its SEF works. However, I got some url as &quot;http://www.example.com/home/44-why-number&quot;  instead of &quot;&quot;http://www.example.com/home/why-number&quot; . I was wondering if anyone experienced the same problem? And how can get rid of it? Thanks.

-Tom</description>
		<content:encoded><![CDATA[<p>Hi, Hi:</p>
<p>I played Joomla 1.5 RC 1 for a while to see how its SEF works. However, I got some url as &#8220;http://www.example.com/home/44-why-number&#8221;  instead of &#8220;&#8221;http://www.example.com/home/why-number&#8221; . I was wondering if anyone experienced the same problem? And how can get rid of it? Thanks.</p>
<p>-Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2428</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Fri, 17 Aug 2007 08:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2428</guid>
		<description>@Peter
I&#039;m always on the lookout for improvements of Joomla and SEO, So I will test your Plugin and write some findings.
Good to see some much Dutch people involved with Joomla!

@Sumisha
You have some great extensions and Plugins, currently I have the sh404SEF running on a IIS based website!
Thank you for your work, and I will check  the h1 content stuff also.

I could not get the s version running on 1.5 but that is logical since it is totally different that 10.0.x versions.
I am waiting on the RC 2 also to see if the other stuff as mentioned on the Joomlatwork site will get into it.. 
But it is the same as RC 1, I would like to have more control with a component like sh404SEF.</description>
		<content:encoded><![CDATA[<p>@Peter<br />
I&#8217;m always on the lookout for improvements of Joomla and SEO, So I will test your Plugin and write some findings.<br />
Good to see some much Dutch people involved with Joomla!</p>
<p>@Sumisha<br />
You have some great extensions and Plugins, currently I have the sh404SEF running on a IIS based website!<br />
Thank you for your work, and I will check  the h1 content stuff also.</p>
<p>I could not get the s version running on 1.5 but that is logical since it is totally different that 10.0.x versions.<br />
I am waiting on the RC 2 also to see if the other stuff as mentioned on the Joomlatwork site will get into it..<br />
But it is the same as RC 1, I would like to have more control with a component like sh404SEF.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shumisha</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2426</link>
		<dc:creator>Shumisha</dc:creator>
		<pubDate>Fri, 17 Aug 2007 07:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2426</guid>
		<description>Hi all,
For those who can&#039;t wait for 1.5 to be stable, may I remind you that sh404SEF already provides for the 1.0.X series:
- SEF URL without mod_rewrite
- total control over Title and Meta tags, for any URL
- h1 tags around contentheadings
- multi-lingual URLs as needed
- https base URL for shared-ssl
All of this withouth hacking the core or templates in any way
1.5 is getting better on URL, I am waiting for RC2 to really give feedback, as they say most improvements will be done for this next release.

Regards to all</description>
		<content:encoded><![CDATA[<p>Hi all,<br />
For those who can&#8217;t wait for 1.5 to be stable, may I remind you that sh404SEF already provides for the 1.0.X series:<br />
- SEF URL without mod_rewrite<br />
- total control over Title and Meta tags, for any URL<br />
- h1 tags around contentheadings<br />
- multi-lingual URLs as needed<br />
- https base URL for shared-ssl<br />
All of this withouth hacking the core or templates in any way<br />
1.5 is getting better on URL, I am waiting for RC2 to really give feedback, as they say most improvements will be done for this next release.</p>
<p>Regards to all</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Muusers - Meeuwsen</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2425</link>
		<dc:creator>Peter Muusers - Meeuwsen</dc:creator>
		<pubDate>Fri, 17 Aug 2007 07:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2425</guid>
		<description>Sorry for this shameless post, but some time ago i have created a simple plugin that enables you to optimize just a little bit further by being able to set the page  tag, using the Article Alias.

See: http://www.vak18.com/joomla_plugins/ for information and download.</description>
		<content:encoded><![CDATA[<p>Sorry for this shameless post, but some time ago i have created a simple plugin that enables you to optimize just a little bit further by being able to set the page  tag, using the Article Alias.</p>
<p>See: <a href="http://www.vak18.com/joomla_plugins/" >http://www.vak18.com/joomla_plugins/</a> for information and download.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2423</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Fri, 17 Aug 2007 05:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2423</guid>
		<description>@Gavin

True, I would like to see the same thing, altough most of them are already possible if your Template supports them.
You can then select the css class in your content if your editor supports it.
Or you must af course edit without wysiwig editor :-)

The only way you can have a h1 for your Title is if its incorperated in you template, or to you the Joofox header with is a module that does that.
http://www.antoniodeluca.info/en/services-products/joofox.html

But Joomla 1.5 Templates seem to get better at using these features.
Allgthough it is up to the Templates designers to really get it right (but that is the same with WordPress)</description>
		<content:encoded><![CDATA[<p>@Gavin</p>
<p>True, I would like to see the same thing, altough most of them are already possible if your Template supports them.<br />
You can then select the css class in your content if your editor supports it.<br />
Or you must af course edit without wysiwig editor :-)</p>
<p>The only way you can have a h1 for your Title is if its incorperated in you template, or to you the Joofox header with is a module that does that.<br />
<a href="http://www.antoniodeluca.info/en/services-products/joofox.html" >http://www.antoniodeluca.info/en/services-products/joofox.html</a></p>
<p>But Joomla 1.5 Templates seem to get better at using these features.<br />
Allgthough it is up to the Templates designers to really get it right (but that is the same with WordPress)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2417</link>
		<dc:creator>Gavin</dc:creator>
		<pubDate>Thu, 16 Aug 2007 23:27:01 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2417</guid>
		<description>Thanks for the review. I have played around with 1.5 Beta and have to say it looks really nice and promising. I am considering migrating my 1.0 site to 1.5 but might just hold off a while. It would be good to create a template for 1.5 first.

Which kinda brings me to the next question. In terms of article headings is there an easy way to overwrite the contentheading class and replace it was an h1, h2,h3,h4,h5 tag etc.. One of the best things about wordpress is semantically correct code. Something I&#039;d really like to see incorporated into Joomla.</description>
		<content:encoded><![CDATA[<p>Thanks for the review. I have played around with 1.5 Beta and have to say it looks really nice and promising. I am considering migrating my 1.0 site to 1.5 but might just hold off a while. It would be good to create a template for 1.5 first.</p>
<p>Which kinda brings me to the next question. In terms of article headings is there an easy way to overwrite the contentheading class and replace it was an h1, h2,h3,h4,h5 tag etc.. One of the best things about wordpress is semantically correct code. Something I&#8217;d really like to see incorporated into Joomla.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trond</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2200</link>
		<dc:creator>Trond</dc:creator>
		<pubDate>Fri, 03 Aug 2007 11:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2200</guid>
		<description>This is a very informative article. I&#039;m experienced with both SEO and Joomla and  will be very happy when Joomla will be 100% SEO compliant (out of the box).

Best regards,
Trond - JoomlaSEO.no</description>
		<content:encoded><![CDATA[<p>This is a very informative article. I&#8217;m experienced with both SEO and Joomla and  will be very happy when Joomla will be 100% SEO compliant (out of the box).</p>
<p>Best regards,<br />
Trond &#8211; JoomlaSEO.no</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Laur</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2054</link>
		<dc:creator>Don Laur</dc:creator>
		<pubDate>Thu, 26 Jul 2007 20:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2054</guid>
		<description>Looks good.  I am using the old Open SEF to do what I can in way of SEO.</description>
		<content:encoded><![CDATA[<p>Looks good.  I am using the old Open SEF to do what I can in way of SEO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pathos</title>
		<link>http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/comment-page-1/#comment-2024</link>
		<dc:creator>Pathos</dc:creator>
		<pubDate>Tue, 24 Jul 2007 20:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://pathosseoblog.com/is-joomla-15-rc-1-ready-for-search-engine-optimization/#comment-2024</guid>
		<description>Hi Steve,

The picture in your post does promise more on the SEO part, nice looking features!

I hope its done in the next, or the Stable release or yes, I would be dissapointed..</description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>The picture in your post does promise more on the SEO part, nice looking features!</p>
<p>I hope its done in the next, or the Stable release or yes, I would be dissapointed..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)

Served from: pathosseoblog.com @ 2010-09-04 05:40:29 -->