<?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 Tasks	</title>
	<atom:link href="https://lhero.org/portfolio/lh-tasks/feed/" rel="self" type="application/rss+xml" />
	<link>https://lhero.org/portfolio/lh-tasks/</link>
	<description>Digital Sovereignty for everyone</description>
	<lastBuildDate>Sun, 01 Nov 2026 05:30:47 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-tasks/#comment-1537829</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Sun, 01 Nov 2026 05:30:47 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=147124#comment-1537829</guid>

					<description><![CDATA[Staff can now change a task&#039;s workflow status, release a claim and reset retries in the UI, not only through the edit-task ability (#153082). The block editor&#039;s Task queue panel has a Change status control plus Release claim and Reset retries buttons, saved with Update through a new lh_tasks_workflow REST field, which is only sent when those controls are touched. The front-end task page has a staff form for the same changes, with an optional staff-only note, and staff get a Resolve button on each open subtask in a master task&#039;s checklist. edit_task() now refuses unknown statuses and status or claim changes on a task with no queue record, logs assignment and claim releases, and fires the completed action when it moves a task into Resolved or Closed, so follow-up reminders and notifications clear as they do on every other route. Master tasks still resolve automatically when their last subtask is resolved this way.]]></description>
			<content:encoded><![CDATA[<p>Staff can now change a task&#8217;s workflow status, release a claim and reset retries in the UI, not only through the edit-task ability (#153082). The block editor&#8217;s Task queue panel has a Change status control plus Release claim and Reset retries buttons, saved with Update through a new lh_tasks_workflow REST field, which is only sent when those controls are touched. The front-end task page has a staff form for the same changes, with an optional staff-only note, and staff get a Resolve button on each open subtask in a master task&#8217;s checklist. edit_task() now refuses unknown statuses and status or claim changes on a task with no queue record, logs assignment and claim releases, and fires the completed action when it moves a task into Resolved or Closed, so follow-up reminders and notifications clear as they do on every other route. Master tasks still resolve automatically when their last subtask is resolved this way.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-tasks/#comment-1537771</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Fri, 30 Oct 2026 01:52:39 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=147124#comment-1537771</guid>

					<description><![CDATA[The noindex rule for task pages no longer runs before WordPress has set up its main query. On a request that dies early, such as the fatal-error screen, core still prints robots meta tags, and the check for a task page used to trigger an &quot;is_singular() was called incorrectly&quot; notice there.]]></description>
			<content:encoded><![CDATA[<p>The noindex rule for task pages no longer runs before WordPress has set up its main query. On a request that dies early, such as the fatal-error screen, core still prints robots meta tags, and the check for a task page used to trigger an &#8220;is_singular() was called incorrectly&#8221; notice there.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
