<?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 Buddypress Group Numbers	</title>
	<atom:link href="https://lhero.org/portfolio/lh-buddypress-group-numbers/feed/" rel="self" type="application/rss+xml" />
	<link>https://lhero.org/portfolio/lh-buddypress-group-numbers/</link>
	<description>Digital Sovereignty for everyone</description>
	<lastBuildDate>Wed, 04 Nov 2026 02:57:57 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-buddypress-group-numbers/#comment-1537863</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 01:54:39 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=153227#comment-1537863</guid>

					<description><![CDATA[First release. Splits the Group Numbers xProfile field type out of lh-competitions into a network-activated plugin, so every site (and site_id MCP calls) sees it. A member gets a number (0-999, filterable via lh_bp_group_numbers_number_range) per BuddyPress group, stored as one user meta array under _lh_bp_group_numbers. Public API: get_numbers(), get_number(), set_numbers(), save_submitted_numbers(). Which groups get a number defaults to all of the member&#039;s groups and is narrowed with the lh_bp_group_numbers_group_query_args filter; invited groups plus anything added on lh_bp_group_numbers_pending_groups (built-in optional LH Membership held-teams integration) are listed too; wording is filterable via lh_bp_group_numbers_labels. Includes the wp-admin user-edit Group Numbers table. Saves now merge per group, so clearing one input clears that number and groups not on the form keep theirs; the field also saves from BuddyPress&#039;s wp-admin Extended Profile screen. Until the schema 1 migration is finalised it still registers the legacy lh_comps-meta type and reads _lh_comps-team_numbers as a fallback. Adds the lh-buddypress-group-numbers/migrate-group-numbers ability (report, migrate, finalise).]]></description>
			<content:encoded><![CDATA[<p>First release. Splits the Group Numbers xProfile field type out of lh-competitions into a network-activated plugin, so every site (and site_id MCP calls) sees it. A member gets a number (0-999, filterable via lh_bp_group_numbers_number_range) per BuddyPress group, stored as one user meta array under _lh_bp_group_numbers. Public API: get_numbers(), get_number(), set_numbers(), save_submitted_numbers(). Which groups get a number defaults to all of the member&#8217;s groups and is narrowed with the lh_bp_group_numbers_group_query_args filter; invited groups plus anything added on lh_bp_group_numbers_pending_groups (built-in optional LH Membership held-teams integration) are listed too; wording is filterable via lh_bp_group_numbers_labels. Includes the wp-admin user-edit Group Numbers table. Saves now merge per group, so clearing one input clears that number and groups not on the form keep theirs; the field also saves from BuddyPress&#8217;s wp-admin Extended Profile screen. Until the schema 1 migration is finalised it still registers the legacy lh_comps-meta type and reads _lh_comps-team_numbers as a fallback. Adds the lh-buddypress-group-numbers/migrate-group-numbers ability (report, migrate, finalise).</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Peter Shaw		</title>
		<link>https://lhero.org/portfolio/lh-buddypress-group-numbers/#comment-1537862</link>

		<dc:creator><![CDATA[Peter Shaw]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 01:38:37 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?post_type=lh-portfolio&#038;p=153227#comment-1537862</guid>

					<description><![CDATA[Initial scaffold.]]></description>
			<content:encoded><![CDATA[<p>Initial scaffold.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
