<?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: Misadventures in MP-WP setup, the sad work-in-progress post</title>
	<atom:link href="http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/</link>
	<description>The search for invariants</description>
	<pubDate>Sat, 07 Mar 2026 21:04:00 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-2368</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Wed, 12 Apr 2023 01:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-2368</guid>
		<description>@Cristi: You can hope all you want, but if you want to make progress you'd &lt;a href="http://ossasepia.com/2023/02/17/how-are-things-moving-in-eulora2/#comment-29175" rel="nofollow"&gt;still&lt;/a&gt; be better advised to ask questions and be specific.</description>
		<content:encoded><![CDATA[<p>@Cristi: You can hope all you want, but if you want to make progress you'd <a href="http://ossasepia.com/2023/02/17/how-are-things-moving-in-eulora2/#comment-29175" rel="nofollow">still</a> be better advised to ask questions and be specific.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cristi</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-2367</link>
		<dc:creator>Cristi</dc:creator>
		<pubDate>Mon, 10 Apr 2023 08:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-2367</guid>
		<description>I hope I can install MP-WP.</description>
		<content:encoded><![CDATA[<p>I hope I can install MP-WP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-459</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 09 Mar 2021 03:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-459</guid>
		<description>&lt;blockquote&gt;you know how to make a new line in a footnote ?&lt;/blockquote&gt;

I'm not sure how the obvious answer didn't occur to either of us at the time - I guess the non-documentation situation really is &lt;em&gt;that bad&lt;/em&gt; - but at any rate: you can indeed use explicit br and p tags if you're that sort of a masochist, but then again you can just hit "Return" like a normal person. Once for line break, twice for paragraph break, all the same whether in footnotes, body text or comments.</description>
		<content:encoded><![CDATA[<blockquote><p>you know how to make a new line in a footnote ?</p></blockquote>
<p>I'm not sure how the obvious answer didn't occur to either of us at the time - I guess the non-documentation situation really is <em>that bad</em> - but at any rate: you can indeed use explicit br and p tags if you're that sort of a masochist, but then again you can just hit "Return" like a normal person. Once for line break, twice for paragraph break, all the same whether in footnotes, body text or comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-375</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 01 Dec 2020 19:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-375</guid>
		<description>I finally got around to switching footnotes to the standard double-parentheticals from prior &#60;fn&gt; and &lsqb;[ special-snowflakeisms, for both Fixpoint and Dorion Mode where I had propagated the configuration. I went to some lengths to make sure everything came out right -- easy enough for his, while my own turned up fun meta-instances like &lt;a href="http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/?b=yet%20another%20worry&#038;e=code.#select" rel="nofollow"&gt;this one&lt;/a&gt; to be escaped -- but I'd appreciate the note should you find anything amiss.

The procedure was, roughly:

1. Make a SQL dump for backup purposes. Search and manually replace things that conflict with the new delimiter. For instance,
&lt;blockquote&gt;&lt;code&gt;mysql mpwp_db_name -e "select id from posts where post_content like '%((%';"&lt;/code&gt;&lt;/blockquote&gt;

2. Edit wp-content/plugins/footnotes.php, find the preg_match_all call, and replace the opening and closing delimiter options in its regex with ones that cover both your old and new delimiters (following the pattern it already uses for allowing &#60;footnote&gt;).

3. Bulk replace the old with new delimiters, for instance:
&lt;blockquote&gt;&lt;code&gt;mysql mpwp_db_name -e "update posts set post_content = replace(replace(post_content, '&#60;fn&gt;', ' &lpar;('), '&#60;/fn&gt;', '))')"&lt;/code&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>I finally got around to switching footnotes to the standard double-parentheticals from prior &lt;fn> and &lsqb;[ special-snowflakeisms, for both Fixpoint and Dorion Mode where I had propagated the configuration. I went to some lengths to make sure everything came out right -- easy enough for his, while my own turned up fun meta-instances like <a href="http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/?b=yet%20another%20worry&#038;e=code.#select" rel="nofollow">this one</a> to be escaped -- but I'd appreciate the note should you find anything amiss.</p>
<p>The procedure was, roughly:</p>
<p>1. Make a SQL dump for backup purposes. Search and manually replace things that conflict with the new delimiter. For instance,</p>
<blockquote><p><code>mysql mpwp_db_name -e "select id from posts where post_content like '%((%';"</code></p></blockquote>
<p>2. Edit wp-content/plugins/footnotes.php, find the preg_match_all call, and replace the opening and closing delimiter options in its regex with ones that cover both your old and new delimiters (following the pattern it already uses for allowing &lt;footnote>).</p>
<p>3. Bulk replace the old with new delimiters, for instance:</p>
<blockquote><p><code>mysql mpwp_db_name -e "update posts set post_content = replace(replace(post_content, '&lt;fn>', ' &lpar;('), '&lt;/fn>', '))')"</code></p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Selection and other sundries for MP-WP &#171; Fixpoint</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-271</link>
		<dc:creator>Selection and other sundries for MP-WP &#171; Fixpoint</dc:creator>
		<pubDate>Mon, 11 May 2020 05:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-271</guid>
		<description>[...] Mircea Popescu's Wordpress, which amount to an approximation of the changes I've been running since initial setup of Fixpoint, reground to build upon subsequent improvements by billymg and Diana [...]</description>
		<content:encoded><![CDATA[<p>[...] Mircea Popescu's Wordpress, which amount to an approximation of the changes I've been running since initial setup of Fixpoint, reground to build upon subsequent improvements by billymg and Diana [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-8</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 29 Oct 2019 18:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-8</guid>
		<description>I should have asked, yes. Thinking back on it, at the time &lt;a href="http://ossasepia.com/2020/04/20/ossasepia-logs-for-14-Sep-2019#1002493" rel="nofollow"&gt;I was optimizing&lt;/a&gt; along a different line than you - finding which version would be most manageable to inspect internally in the event that I had to - I wasn't all that motivated to pursue a specific version just because it was known to work in your environment. Though writing this, it sounds dumb because the cost to ask was minimal and potential benefits of sharing a common version unexplored.

Glad to move on from this one. Except ugh, I found two mismatched sub-list items ("I later find where they're hidden", "Apache has a mod_remoteip"); I'll just make an update to fix those.</description>
		<content:encoded><![CDATA[<p>I should have asked, yes. Thinking back on it, at the time <a href="http://ossasepia.com/2020/04/20/ossasepia-logs-for-14-Sep-2019#1002493" rel="nofollow">I was optimizing</a> along a different line than you - finding which version would be most manageable to inspect internally in the event that I had to - I wasn't all that motivated to pursue a specific version just because it was known to work in your environment. Though writing this, it sounds dumb because the cost to ask was minimal and potential benefits of sharing a common version unexplored.</p>
<p>Glad to move on from this one. Except ugh, I found two mismatched sub-list items ("I later find where they're hidden", "Apache has a mod_remoteip"); I'll just make an update to fix those.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Coman</title>
		<link>http://jfxpt.com/2019/misadventures-in-mp-wp-setup-the-sad-work-in-progress-post/#comment-7</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Mon, 28 Oct 2019 22:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=40#comment-7</guid>
		<description>"found DC's post; didn't find the tarballs in question from upstream or gentoo mirrors" - so why not simply comment there at that post, at that time and simply ask maybe I would share the tarballs?  

Otherwise tbh I think in this particular case the format works great to convey precisely the ...mess that there is. And at any rate, your time is really way better spent on more useful things than cleaning all this installation-mess up (without a clearly fixed, unchanging environment, the installation will still remain a mess, no matter how clean the new recipe).</description>
		<content:encoded><![CDATA[<p>"found DC's post; didn't find the tarballs in question from upstream or gentoo mirrors" - so why not simply comment there at that post, at that time and simply ask maybe I would share the tarballs?  </p>
<p>Otherwise tbh I think in this particular case the format works great to convey precisely the ...mess that there is. And at any rate, your time is really way better spent on more useful things than cleaning all this installation-mess up (without a clearly fixed, unchanging environment, the installation will still remain a mess, no matter how clean the new recipe).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
