<?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/"
	xmlns:georss="http://www.georss.org/georss" 
	>
<channel>
	<title>
	Comments on: LH Knowledge Base	</title>
	<atom:link href="https://lhero.org/portfolio/lh-knowledge-base/feed/" rel="self" type="application/rss+xml" />
	<link>https://lhero.org/portfolio/lh-knowledge-base/</link>
	<description>Digital Sovereignty for everyone</description>
	<lastBuildDate>Sat, 07 Nov 2026 00:32:54 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-knowledge-base/#comment-1537944</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Sat, 07 Nov 2026 00:32:54 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=148407#comment-1537944</guid>

					<description><![CDATA[Removes the status visibility re-sync added in 1.9.1. It did not fix the missing root index.md and log.md listings for signed-in users; that was fixed in LH Archived Post Status 3.13.0. No change in behaviour.]]></description>
			<content:encoded><![CDATA[<p>Removes the status visibility re-sync added in 1.9.1. It did not fix the missing root index.md and log.md listings for signed-in users; that was fixed in LH Archived Post Status 3.13.0. No change in behaviour.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-knowledge-base/#comment-1537940</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Fri, 06 Nov 2026 23:39:51 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=148407#comment-1537940</guid>

					<description><![CDATA[Knowledge base visibility now follows whoever is signed in for the request, even when they are recognised after WordPress has loaded (application passwords, MCP connections and similar). Previously visibility was fixed when the plugin loaded, so for those requests the root index.md and log.md left out every entry, and entry links fell back to ?post_type= URLs.]]></description>
			<content:encoded><![CDATA[<p>Knowledge base visibility now follows whoever is signed in for the request, even when they are recognised after WordPress has loaded (application passwords, MCP connections and similar). Previously visibility was fixed when the plugin loaded, so for those requests the root index.md and log.md left out every entry, and entry links fell back to ?post_type= URLs.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
