<?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 for my weblog</title>
	<atom:link href="http://www.swart.org.za/wordpress/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.swart.org.za/wordpress</link>
	<description>babblings!</description>
	<lastBuildDate>Tue, 05 Feb 2008 15:31:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by carl</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2220</link>
		<dc:creator>carl</dc:creator>
		<pubDate>Tue, 05 Feb 2008 15:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2220</guid>
		<description>@CiViX

I have only upgrade RHEL 4 servers running Apache 2.0.x to Plesk 8.3 and FrontPage continued working on all of them.

Thinking about your statement, yes, Plesk does not affect mod_frontpage. Plesk only controls Apache&#039;s configuration files.</description>
		<content:encoded><![CDATA[<p>@CiViX</p>
<p>I have only upgrade RHEL 4 servers running Apache 2.0.x to Plesk 8.3 and FrontPage continued working on all of them.</p>
<p>Thinking about your statement, yes, Plesk does not affect mod_frontpage. Plesk only controls Apache&#8217;s configuration files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by CiViX</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2219</link>
		<dc:creator>CiViX</dc:creator>
		<pubDate>Wed, 30 Jan 2008 14:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2219</guid>
		<description>At least one person has reported PLESK 8.3 breaking the new Frontpage-support. This seems unplausible to me as PLESK itself shouldn&#039;t affect mod_frontpage?

Have any of you tried upgrading to PLESK 8.3, and did it screw up Frontpage or did it work fine?</description>
		<content:encoded><![CDATA[<p>At least one person has reported PLESK 8.3 breaking the new Frontpage-support. This seems unplausible to me as PLESK itself shouldn&#8217;t affect mod_frontpage?</p>
<p>Have any of you tried upgrading to PLESK 8.3, and did it screw up Frontpage or did it work fine?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by CiViX</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2218</link>
		<dc:creator>CiViX</dc:creator>
		<pubDate>Sun, 20 Jan 2008 21:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2218</guid>
		<description>Ah, seems the problem was that the httpd-update had overwritten the suexec. I fixed it by following this info: http://kb.swsoft.com/en/1322

(Btw, the upgrade was not to httpd-2.2.6, just from 2.2.3-10 to 2.2.3-11.)</description>
		<content:encoded><![CDATA[<p>Ah, seems the problem was that the httpd-update had overwritten the suexec. I fixed it by following this info: <a href="http://kb.swsoft.com/en/1322" rel="nofollow">http://kb.swsoft.com/en/1322</a></p>
<p>(Btw, the upgrade was not to httpd-2.2.6, just from 2.2.3-10 to 2.2.3-11.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by CiViX</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2217</link>
		<dc:creator>CiViX</dc:creator>
		<pubDate>Sun, 20 Jan 2008 19:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2217</guid>
		<description>Upgraded to apache 2.2.6 and now the Frontpage-support seems to be broken again :-/ Have any of you experienced this or found any fix? Would it be sufficient just to recompile the frontpage-rpm do you think?</description>
		<content:encoded><![CDATA[<p>Upgraded to apache 2.2.6 and now the Frontpage-support seems to be broken again :-/ Have any of you experienced this or found any fix? Would it be sufficient just to recompile the frontpage-rpm do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by Carl Swart</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2216</link>
		<dc:creator>Carl Swart</dc:creator>
		<pubDate>Mon, 31 Dec 2007 10:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2216</guid>
		<description>@CiViX

Sorry but everything on my side is working 100%. It has now been 10 days and all the clients are happy.

The only suggestion I have is to for you to start from the beginning.

Sorry that I can not be of more assistance.</description>
		<content:encoded><![CDATA[<p>@CiViX</p>
<p>Sorry but everything on my side is working 100%. It has now been 10 days and all the clients are happy.</p>
<p>The only suggestion I have is to for you to start from the beginning.</p>
<p>Sorry that I can not be of more assistance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by CiViX</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2215</link>
		<dc:creator>CiViX</dc:creator>
		<pubDate>Thu, 20 Dec 2007 23:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2215</guid>
		<description>The FP Webadmin layout is screwed up. I&#039;m testing in Firefox, but th FP Webadmin looks fine on servers running &quot;original Frontpage-module&quot;, so there must be something wrong with this patched version. I&#039;ve checked and the styles (webadmin.css) and images seem to be in the correct directories with the right permissions...

Anyone figure this out?</description>
		<content:encoded><![CDATA[<p>The FP Webadmin layout is screwed up. I&#8217;m testing in Firefox, but th FP Webadmin looks fine on servers running &#8220;original Frontpage-module&#8221;, so there must be something wrong with this patched version. I&#8217;ve checked and the styles (webadmin.css) and images seem to be in the correct directories with the right permissions&#8230;</p>
<p>Anyone figure this out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by codepoet</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2214</link>
		<dc:creator>codepoet</dc:creator>
		<pubDate>Thu, 20 Dec 2007 21:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2214</guid>
		<description>@carl

Yeah, I managed to get it figured out shortly after my last post here. Ended up needing to delete/re-add the domain into Plesk, not sure what exactly I&#039;d broken, but that made everything start working again.

Thanks,

-Kenneth</description>
		<content:encoded><![CDATA[<p>@carl</p>
<p>Yeah, I managed to get it figured out shortly after my last post here. Ended up needing to delete/re-add the domain into Plesk, not sure what exactly I&#8217;d broken, but that made everything start working again.</p>
<p>Thanks,</p>
<p>-Kenneth</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by Carl Swart</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2213</link>
		<dc:creator>Carl Swart</dc:creator>
		<pubDate>Thu, 20 Dec 2007 03:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2213</guid>
		<description>@codepoet

You are indeed correct. That was part of the problem. The major problem however was that the patches that I made use of literally altered a piece of the mod_frontpage code. When I looked at the original Apache 1.3 code I discovered the problem and re-created the patches.

Have you made sure that all the permissions on the FPSE files are correct by running the set_default_perms.sh script in the /usr/local/frontpage/version5.0/ directory?</description>
		<content:encoded><![CDATA[<p>@codepoet</p>
<p>You are indeed correct. That was part of the problem. The major problem however was that the patches that I made use of literally altered a piece of the mod_frontpage code. When I looked at the original Apache 1.3 code I discovered the problem and re-created the patches.</p>
<p>Have you made sure that all the permissions on the FPSE files are correct by running the set_default_perms.sh script in the /usr/local/frontpage/version5.0/ directory?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Urrgghh &#8230;. FrontPage! by codepoet</title>
		<link>http://www.swart.org.za/wordpress/blog/2007/12/01/urrgghh-frontpage/comment-page-1/#comment-2212</link>
		<dc:creator>codepoet</dc:creator>
		<pubDate>Thu, 20 Dec 2007 01:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.swart.org.za/wordpress/?p=69#comment-2212</guid>
		<description>I&#039;ve found a problem in that patch you linked, that may explain why your FrontPage isn&#039;t working.... 

at about line 840 after applying the patches... there is a part that is invalid... the patch made these changes...

-    ap_table_set(r-&gt;notes,&quot;FPexecfilename&quot;, ap_pstrcat(r-&gt;pool, FPSTUB, NULL));
-    r-&gt;filename = ap_pstrcat(r-&gt;pool, r-&gt;filename, szCgi, NULL);
+    execFilename = apr_pstrcat(r-&gt;pool, FP, szDir, szBuf, szBase, NULL);
+    apr_table_set(r-&gt;notes,&quot;FPexecfilename&quot;, execFilename);

which were not correct for what is being done, the first of those new lines should really be

execFilename = apr_pstrcat(r-&gt;pool, FPSTUB, NULL);
instead of .... FP, szDir, szBuf, szBase... as was incorrectly put in the patch

some of those (szDir/szBase) are uninitialized variables that make random stuff in the log like
&quot;attempt to invoke directory as script: /usr/local/frontpage/version5.0\xa4\xc4\xcf\xbf_\xaf\xbf\xb7\xc0\xc4\xcf\xbf\xe6\xe1\x1f\xb7\x022523\xa5\n&quot;

Now, if only I could figure out why it refuses to accept my password for the FPadmin login, i&#039;d be all set.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found a problem in that patch you linked, that may explain why your FrontPage isn&#8217;t working&#8230;. </p>
<p>at about line 840 after applying the patches&#8230; there is a part that is invalid&#8230; the patch made these changes&#8230;</p>
<p>-    ap_table_set(r-&gt;notes,&#8221;FPexecfilename&#8221;, ap_pstrcat(r-&gt;pool, FPSTUB, NULL));<br />
-    r-&gt;filename = ap_pstrcat(r-&gt;pool, r-&gt;filename, szCgi, NULL);<br />
+    execFilename = apr_pstrcat(r-&gt;pool, FP, szDir, szBuf, szBase, NULL);<br />
+    apr_table_set(r-&gt;notes,&#8221;FPexecfilename&#8221;, execFilename);</p>
<p>which were not correct for what is being done, the first of those new lines should really be</p>
<p>execFilename = apr_pstrcat(r-&gt;pool, FPSTUB, NULL);<br />
instead of &#8230;. FP, szDir, szBuf, szBase&#8230; as was incorrectly put in the patch</p>
<p>some of those (szDir/szBase) are uninitialized variables that make random stuff in the log like<br />
&#8220;attempt to invoke directory as script: /usr/local/frontpage/version5.0\xa4\xc4\xcf\xbf_\xaf\xbf\xb7\xc0\xc4\xcf\xbf\xe6\xe1\x1f\xb7\x022523\xa5\n&#8221;</p>
<p>Now, if only I could figure out why it refuses to accept my password for the FPadmin login, i&#8217;d be all set.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

