<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>wp-SwimTeam &#187; fields</title>
	<atom:link href="http://www.wp-swimteam.org/tag/fields/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wp-swimteam.org</link>
	<description>A WordPress plugin for swim team management</description>
	<lastBuildDate>Tue, 24 Jan 2012 22:21:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Administrative Fields for Users and Swimmers</title>
		<link>http://www.wp-swimteam.org/2009/05/20/administrative-fields-for-users-and-swimmers/</link>
		<comments>http://www.wp-swimteam.org/2009/05/20/administrative-fields-for-users-and-swimmers/#comments</comments>
		<pubDate>Wed, 20 May 2009 21:07:06 +0000</pubDate>
		<dc:creator>Mike Walsh</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Ideas]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Progress]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[fees]]></category>
		<category><![CDATA[fields]]></category>
		<category><![CDATA[Options]]></category>
		<category><![CDATA[registration]]></category>

		<guid isPermaLink="false">http://www.wp-swimteam.org/2009/05/20/administrative-fields-for-users-and-swimmers/</guid>
		<description><![CDATA[I had a request to support fields that weren’t visible to the end users when they used the system.&#160; I decided to support these “administrative” fields as I have been referring to them by enhancing the optional fields for swimmers and users to be tagged as “user” fields or “administrative” fields. When a field is [...]]]></description>
			<content:encoded><![CDATA[<p>I had a request to support fields that weren’t visible to the end users when they used the system.&#160; I decided to support these “administrative” fields as I have been referring to them by enhancing the optional fields for swimmers and users to be tagged as “user” fields or “administrative” fields.</p>
<p>When a field is defined as “administrative”, only users with WordPress permissions of EDITOR or higher will have the fields visible.&#160; For all other users, they are hidden.&#160; An Admin or Editor can change the value of the field and it will be saved when the user or swimmer data is saved.</p>
<p>The first practical usage of this is with a team that wants to mark registration fees as paid on a per swimmer basis.&#160; Not the sort of thing you would expose to a parent but useful from a logistics perspective.</p>
<p>Both user and administrative fields are available in reports.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wp-swimteam.org/2009/05/20/administrative-fields-for-users-and-swimmers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

