<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BuddyPress.org | gvdsleen | Mentions</title>
	<link>https://buddypress.org/members/gvdsleen/activity/mentions/</link>
	<atom:link href="https://buddypress.org/members/gvdsleen/activity/mentions/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed mentioning gvdsleen.</description>
	<lastBuildDate>Sat, 04 Apr 2026 15:01:02 +0000</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">767443b06e545fa4e8197eaed4df6c97</guid>
				<title>pcwriter posted on the forum topic How to make pages like Groups, Forums, members and updates only accessible to members? in the group How-To and Troubleshooting</title>
				<link>http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-pages-like-groups-forums-members-and-updates-only-accessible</link>
				<pubDate>Tue, 01 Feb 2011 10:59:30 +0000</pubDate>

									<content:encoded><![CDATA[<p><a href="http://buddypress.org/community/members/gvdsleen/" rel="nofollow ugc">@gvdsleen</a> Once BP1.3 is released, this issue should be resolved as it will use WP pages for components. You will then be able to use s2member&#8217;s page access restrictions for components like Members. In the meantime, you can protect any component directory from unauthorized member levels by editing its index.php template. Add the following just after [&#8230;]</p>
]]></content:encoded>
				
				
							</item>
		
	</channel>
</rss>