<?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 Membership	</title>
	<atom:link href="https://lhero.org/portfolio/lh-membership/feed/" rel="self" type="application/rss+xml" />
	<link>https://lhero.org/portfolio/lh-membership/</link>
	<description>Digital Sovereignty for everyone</description>
	<lastBuildDate>Sat, 31 Oct 2026 15:31:25 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-membership/#comment-1537819</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Sat, 31 Oct 2026 15:28:26 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=145740#comment-1537819</guid>

					<description><![CDATA[Organisation invitations are kept as history instead of being deleted. Rejection and removal from a site now close the person&#039;s open invitations (mark them accepted) and fire lh_membership_org_team_invite_closed with the reason; deleting a team leaves its invitations in place; only deleting the account deletes them. Approval now joins people only to the teams on invitations it has not processed before, tracked per person and site by the highest invitation ID processed (user option lh_membership-org_invites_processed), so approving someone again does not put them back in teams they have left. An invitation whose team no longer exists is skipped with a warning.]]></description>
			<content:encoded><![CDATA[<p>Organisation invitations are kept as history instead of being deleted. Rejection and removal from a site now close the person&#8217;s open invitations (mark them accepted) and fire lh_membership_org_team_invite_closed with the reason; deleting a team leaves its invitations in place; only deleting the account deletes them. Approval now joins people only to the teams on invitations it has not processed before, tracked per person and site by the highest invitation ID processed (user option lh_membership-org_invites_processed), so approving someone again does not put them back in teams they have left. An invitation whose team no longer exists is skipped with a warning.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-membership/#comment-1537817</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Sat, 31 Oct 2026 12:32:03 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=145740#comment-1537817</guid>

					<description><![CDATA[Organisation invitations replace BuddyPress site invitations. Registration now creates an lh_membership organisation invitation (no team) instead of a bp_members_invitation_manager one, and a team picked at registration or ticked at the consent step becomes that same invitation&#039;s team, so each person has one record per site. The team is optional. Accepting or declining the terms marks the person&#039;s open invitations accepted (open until they respond, accepted once they have). On approval the person joins the team on each of their invitations before the welcome email. Rejection deletes their invitations for the site. The onboarding checks for an outstanding site invitation now read the new class.]]></description>
			<content:encoded><![CDATA[<p>Organisation invitations replace BuddyPress site invitations. Registration now creates an lh_membership organisation invitation (no team) instead of a bp_members_invitation_manager one, and a team picked at registration or ticked at the consent step becomes that same invitation&#8217;s team, so each person has one record per site. The team is optional. Accepting or declining the terms marks the person&#8217;s open invitations accepted (open until they respond, accepted once they have). On approval the person joins the team on each of their invitations before the welcome email. Rejection deletes their invitations for the site. The onboarding checks for an outstanding site invitation now read the new class.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
