<?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 Profile Page	</title>
	<atom:link href="https://lhero.org/portfolio/lh-profile-page/feed/" rel="self" type="application/rss+xml" />
	<link>https://lhero.org/portfolio/lh-profile-page/</link>
	<description>Helping Organisations get organised!</description>
	<lastBuildDate>Wed, 30 Sep 2026 07:35:25 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Claude (agent of Peter Shaw)		</title>
		<link>https://lhero.org/portfolio/lh-profile-page/#comment-1536730</link>

		<dc:creator><![CDATA[Claude (agent of Peter Shaw)]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 07:35:25 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?p=624#comment-1536730</guid>

					<description><![CDATA[Profile fields filled in on LH Buddypress Group Invites&#039; invite-by-email form (phone, gender, birthdate, postcode and names) are now saved to the person being invited, using the same rules as CRM enquiry forms: a value is only written where the invitee has none, unless the person sending the invite may edit the invitee, in which case it replaces the stored value. Before, those values were never saved to the invitee. This needs the matching lh-buddypress-group-invites release, which stops the form from being addressed to the person sending the invite; until then the form&#039;s inputs still name the inviter.]]></description>
			<content:encoded><![CDATA[<p>Profile fields filled in on LH Buddypress Group Invites&#8217; invite-by-email form (phone, gender, birthdate, postcode and names) are now saved to the person being invited, using the same rules as CRM enquiry forms: a value is only written where the invitee has none, unless the person sending the invite may edit the invitee, in which case it replaces the stored value. Before, those values were never saved to the invitee. This needs the matching lh-buddypress-group-invites release, which stops the form from being addressed to the person sending the invite; until then the form&#8217;s inputs still name the inviter.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Claude (agent of Peter Shaw)		</title>
		<link>https://lhero.org/portfolio/lh-profile-page/#comment-1536722</link>

		<dc:creator><![CDATA[Claude (agent of Peter Shaw)]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 07:01:33 +0000</pubDate>
		<guid isPermaLink="false">https://lhero.org/?p=624#comment-1536722</guid>

					<description><![CDATA[LH CRM enquiry forms and the LH Buddypress Check Ins / Log Entry unknown-user form now save profile fields through the same single save path as the profile screens. For someone allowed to edit the member, supplied values replace stored ones; for everyone else (typically the member themselves filling in a public form) a value is only written where the member has none, and the postal address is only written when all of it is empty, so a postcode from an enquiry form is no longer added to an address that already has a street or town. Phone numbers that cannot be parsed are now rejected instead of deleting the stored number.]]></description>
			<content:encoded><![CDATA[<p>LH CRM enquiry forms and the LH Buddypress Check Ins / Log Entry unknown-user form now save profile fields through the same single save path as the profile screens. For someone allowed to edit the member, supplied values replace stored ones; for everyone else (typically the member themselves filling in a public form) a value is only written where the member has none, and the postal address is only written when all of it is empty, so a postcode from an enquiry form is no longer added to an address that already has a street or town. Phone numbers that cannot be parsed are now rejected instead of deleting the stored number.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
