@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix content: <http://purl.org/rss/1.0/modules/content/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<https://lhero.org/portfolio/lh-membership/>
  a sioc:Post ;
  dc:title "Member addresses" ;
  dcterms:identifier 155315 ;
  dc:modified "2026-11-22T01:44:25Z"^^xsd:dateTime ;
  dc:created "2026-11-22T01:44:25Z"^^xsd:dateTime ;
  sioc:link <https://lhero.org/portfolio/lh-membership/member-addresses/> ;
  sioc:has_creator <https://lhero.org/author/1/#account> ;
  sioc:has_container <https://lhero.org/#posts> ;
  content:encoded """<ul class="lh_portfolio-meta"><li><strong>Part of:</strong> <a href="https://lhero.org/portfolio/lh-membership/">LH Membership</a></li></ul>
<p class="wp-block-paragraph">Addresses are stored by LH Addresses, once for the network, and each site sees only the addresses it holds (its uses). LH Addresses does not know what a member is, so LH Membership answers for it (<code>includes/lh-membership-addresses-class.php</code>, since 2.110.0).</p>



<h2 class="wp-block-heading">Who is a member</h2>



<p class="wp-block-paragraph">A user holding any member-type term on the site: membership of the organisation, not an account or an editor role. Another site&#8217;s membership is read straight from that site&#8217;s own term tables, so no blog switch is needed.</p>



<h2 class="wp-block-heading">Filters answered</h2>



<ul class="wp-block-list">
<li><code>lh_addresses_site_can_read</code>: true when the viewer holds the member-data capability on the site (<code>promote_users</code>, filter <code>lh_membership_return_member_data_capability</code>) and the subject is a current member, or a former one: someone the site holds or has held an address use for. A former member&#8217;s site then sees only what it holds, the last address it was given.</li>



<li><code>lh_addresses_carry_use_on_move</code>: when a member changes address, a site&#8217;s use moves to the new address only while they are a current member. The member&#8217;s own book always follows.</li>
</ul>



<h2 class="wp-block-heading">Clubs get their members&#8217; addresses</h2>



<p class="wp-block-paragraph">Since 2.111.0, when a user is given a member type on a site (<code>set_object_terms</code>), the site gets a residential use (filter <code>lh_membership_return_club_address_use_type</code>) on the member&#8217;s own residential address. A site that already holds a current residential address for them keeps it; a site holding a replaced address, i.e. a former member who rejoins, is given the current one. Leaving ends nothing.</p>



<p class="wp-block-paragraph">Existing members were given the same way by a one-off job, <code>lh_membership_address_uses_backfill</code>: single cron events on the main site once LH Addresses&#8217; own backfill is done, 100 members per run (filter <code>lh_membership_return_address_uses_backfill_batch_size</code>), site by site in ID order, under a five-minute network lock, retrying five minutes later on a failed query. Progress is in the network option <code>lh_membership-address_uses_backfill</code> (site_id, last_user_id, given, skipped, failed, done, completed_at). Members with no address of their own are skipped.</p>
"""^^rdf:XMLLiteral ;
  sioc:content """Part of: LH Membership
Addresses are stored by LH Addresses, once for the network, and each site sees only the addresses it holds (its uses). LH Addresses does not know what a member is, so LH Membership answers for it (includes/lh-membership-addresses-class.php, since 2.110.0).



Who is a member



A user holding any member-type term on the site: membership of the organisation, not an account or an editor role. Another site&#8217;s membership is read straight from that site&#8217;s own term tables, so no blog switch is needed.



Filters answered




lh_addresses_site_can_read: true when the viewer holds the member-data capability on the site (promote_users, filter lh_membership_return_member_data_capability) and the subject is a current member, or a former one: someone the site holds or has held an address use for. A former member&#8217;s site then sees only what it holds, the last address it was given.



lh_addresses_carry_use_on_move: when a member changes address, a site&#8217;s use moves to the new address only while they are a current member. The member&#8217;s own book always follows.




Clubs get their members&#8217; addresses



Since 2.111.0, when a user is given a member type on a site (set_object_terms), the site gets a residential use (filter lh_membership_return_club_address_use_type) on the member&#8217;s own residential address. A site that already holds a current residential address for them keeps it; a site holding a replaced address, i.e. a former member who rejoins, is given the current one. Leaving ends nothing.



Existing members were given the same way by a one-off job, lh_membership_address_uses_backfill: single cron events on the main site once LH Addresses&#8217; own backfill is done, 100 members per run (filter lh_membership_return_address_uses_backfill_batch_size), site by site in ID order, under a five-minute network lock, retrying five minutes later on a failed query. Progress is in the network option lh_membership-address_uses_backfill (site_id, last_user_id, given, skipped, failed, done, completed_at). Members with no address of their own are skipped.
""" ;
  sioc:topic <https://lhero.org/?taxonomy=author&term=cap-1>, <https://lhero.org/?taxonomy=lh_object_key&term=lh-portfolio_doc_20261121t150500-lh-membership-member-addresses> .

<https://lhero.org/author/1/#account> rdfs:seeAlso <https://lhero.org/author/1/?feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=author&term=cap-1> rdfs:seeAlso <https://lhero.org/?taxonomy=author&term=cap-1&feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=lh_object_key&term=lh-portfolio_doc_20261121t150500-lh-membership-member-addresses> rdfs:seeAlso <https://lhero.org/?taxonomy=lh_object_key&term=lh-portfolio_doc_20261121t150500-lh-membership-member-addresses&feed=lhrdf&format=turtle> .
