<?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/"
		>
<channel>
	<title>Comments on: mailto:staff</title>
	<atom:link href="http://blog.decaf.de/2009/01/mailto-staff/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.decaf.de/2009/01/mailto-staff/</link>
	<description></description>
	<lastBuildDate>Sun, 05 Feb 2012 13:12:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Malwerick</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-51902</link>
		<dc:creator>Malwerick</dc:creator>
		<pubDate>Thu, 03 Mar 2011 09:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-51902</guid>
		<description>How to settings mailto:staff to see as administrators or editors to WP Dashboard Thanks!</description>
		<content:encoded><![CDATA[<p>How to settings mailto:staff to see as administrators or editors to WP Dashboard Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Schürjohann</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-50869</link>
		<dc:creator>Dirk Schürjohann</dc:creator>
		<pubDate>Fri, 16 Apr 2010 10:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-50869</guid>
		<description>Kent,
thank you for your feedback! I don&#039;t think we can get on roles other than the common WP ones. But — What we can do is split up the recipient list if it contains more than x items. For instance if you come up with a list of 250 recipients you&#039;d get three mailto links (containing 100/100/50 items) instead of one.

Caveats:
1. I don&#039;t find it very usable. The plugin isn&#039;t (conceptual/technichal) appropriate for that huge num of recipients.
2. I&#039;m sorry we can&#039;t do it within some weeks as there&#039;s too much other stuff around.

So, maybe someone else wants to implement the splitting feature?</description>
		<content:encoded><![CDATA[<p>Kent,<br />
thank you for your feedback! I don&#8217;t think we can get on roles other than the common WP ones. But — What we can do is split up the recipient list if it contains more than x items. For instance if you come up with a list of 250 recipients you&#8217;d get three mailto links (containing 100/100/50 items) instead of one.</p>
<p>Caveats:<br />
1. I don&#8217;t find it very usable. The plugin isn&#8217;t (conceptual/technichal) appropriate for that huge num of recipients.<br />
2. I&#8217;m sorry we can&#8217;t do it within some weeks as there&#8217;s too much other stuff around.</p>
<p>So, maybe someone else wants to implement the splitting feature?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-50868</link>
		<dc:creator>Kent</dc:creator>
		<pubDate>Sun, 11 Apr 2010 15:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-50868</guid>
		<description>Hi Dirk, This plugin works better than others for getting the mail out to users, but if I send to subscribers 100+ I get errors. One way around this is to divide users into smaller groups / roles, but &quot;Mail to Staff&quot; does not read other than standard groups / roles.

Is there a way to get the program to include any group / role which is created, instead of just the standard one which come with WP?

I&#039;d really appreciate a reply on this.

Thank You,
Kent</description>
		<content:encoded><![CDATA[<p>Hi Dirk, This plugin works better than others for getting the mail out to users, but if I send to subscribers 100+ I get errors. One way around this is to divide users into smaller groups / roles, but &#8220;Mail to Staff&#8221; does not read other than standard groups / roles.</p>
<p>Is there a way to get the program to include any group / role which is created, instead of just the standard one which come with WP?</p>
<p>I&#8217;d really appreciate a reply on this.</p>
<p>Thank You,<br />
Kent</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Schürjohann</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-50851</link>
		<dc:creator>Dirk Schürjohann</dc:creator>
		<pubDate>Tue, 23 Feb 2010 09:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-50851</guid>
		<description>Thank you, Tech-A! I&#039;ve attached the javascript info.</description>
		<content:encoded><![CDATA[<p>Thank you, Tech-A! I&#8217;ve attached the javascript info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech-A of Kwassl.net</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-50850</link>
		<dc:creator>Tech-A of Kwassl.net</dc:creator>
		<pubDate>Fri, 19 Feb 2010 21:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-50850</guid>
		<description>Hi,
at first, I was disapointed, as I did not get the link on the dashboard. Then I checked the source of the page and saw, this plugin needs JavaScript. Is that somewhere described? Maybe it would be helpfull to include some  part, which tells, some function of the plugin is missing.

Greets Tech-A</description>
		<content:encoded><![CDATA[<p>Hi,<br />
at first, I was disapointed, as I did not get the link on the dashboard. Then I checked the source of the page and saw, this plugin needs JavaScript. Is that somewhere described? Maybe it would be helpfull to include some  part, which tells, some function of the plugin is missing.</p>
<p>Greets Tech-A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Schürjohann</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-44610</link>
		<dc:creator>Dirk Schürjohann</dc:creator>
		<pubDate>Thu, 23 Apr 2009 05:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-44610</guid>
		<description>kaigou, unfortunately RM&#039;s changes are persistent, which means that if you deactivate it all settings stay active. Did you reselect the WordPress native roles for your staff when you dumped RM?

Could you try once again to set yourself back to a regular WP admin and have a look what our plugin does. Still no mailto links to the complete staff means you were definitely right with RM not being the bad guy.</description>
		<content:encoded><![CDATA[<p>kaigou, unfortunately RM&#8217;s changes are persistent, which means that if you deactivate it all settings stay active. Did you reselect the WordPress native roles for your staff when you dumped RM?</p>
<p>Could you try once again to set yourself back to a regular WP admin and have a look what our plugin does. Still no mailto links to the complete staff means you were definitely right with RM not being the bad guy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kaigou</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-44609</link>
		<dc:creator>kaigou</dc:creator>
		<pubDate>Tue, 21 Apr 2009 18:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-44609</guid>
		<description>Apparently the problem isn&#039;t RM -- I checked the assigned #s, which were all correct, and eventually I gave up and deactivated RM. No fix, so I&#039;m guessing RM isn&#039;t the source of the conflict. Any other ideas for where I could look, to troubleshoot?

(You&#039;re right about RM&#039;s defaults, since when I re-activated it, everyone got set to zero, including me -- even when WP itself had everyone listed at appropriate levels. Whoosh, there went my entire admin dashboard, and it wouldn&#039;t come back no matter how much I prodded RM. Lovely.) 

Thanks again!</description>
		<content:encoded><![CDATA[<p>Apparently the problem isn&#8217;t RM &#8212; I checked the assigned #s, which were all correct, and eventually I gave up and deactivated RM. No fix, so I&#8217;m guessing RM isn&#8217;t the source of the conflict. Any other ideas for where I could look, to troubleshoot?</p>
<p>(You&#8217;re right about RM&#8217;s defaults, since when I re-activated it, everyone got set to zero, including me &#8212; even when WP itself had everyone listed at appropriate levels. Whoosh, there went my entire admin dashboard, and it wouldn&#8217;t come back no matter how much I prodded RM. Lovely.) </p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Schürjohann</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-44608</link>
		<dc:creator>Dirk Schürjohann</dc:creator>
		<pubDate>Tue, 21 Apr 2009 06:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-44608</guid>
		<description>Thanks for your feedback, kaigou!

Role Manager shouldn&#039;t be a problem, but can you check the user levels it uses for your staff: by default role manager uses 0 when setting up new roles. I guess you&#039;re admin with 0 level and therefore act as a subscriber (from the plugin&#039;s point of view).

So you should set the user levels in role manager to the wordpress defaults in order to make the plugin (and other plugins tracking the user level) work:

admins 8-10 (default 10)
editors 5-7 (default 7)
authors 2-4 (default 2)
contributors 1
subscribers 0</description>
		<content:encoded><![CDATA[<p>Thanks for your feedback, kaigou!</p>
<p>Role Manager shouldn&#8217;t be a problem, but can you check the user levels it uses for your staff: by default role manager uses 0 when setting up new roles. I guess you&#8217;re admin with 0 level and therefore act as a subscriber (from the plugin&#8217;s point of view).</p>
<p>So you should set the user levels in role manager to the wordpress defaults in order to make the plugin (and other plugins tracking the user level) work:</p>
<p>admins 8-10 (default 10)<br />
editors 5-7 (default 7)<br />
authors 2-4 (default 2)<br />
contributors 1<br />
subscribers 0</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kaigou</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-44607</link>
		<dc:creator>kaigou</dc:creator>
		<pubDate>Mon, 20 Apr 2009 21:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-44607</guid>
		<description>Hey. Great plugin! ...so I&#039;m sure this error must be mine, if I could just figure it out. I&#039;m one of the admins (of 3); I have one editor, 22 authors, and 7 contributors on the site. When I installed the plugin, all I get is the option to mail-to the admins. There&#039;s nothing showing up for any of the other groups (which is actually the most useful part of this plugin&#039;s concept, for me -- 22 people is an awful lot to email at once, manually). 

I&#039;m also using Role Manager, but otherwise I&#039;ve made no adjustments to users, nor have I messed with the admin interface at all. Is there some other setting I need to make sure is switched to the &#039;on&#039; position to see the other groups as email options?

Thanks!</description>
		<content:encoded><![CDATA[<p>Hey. Great plugin! &#8230;so I&#8217;m sure this error must be mine, if I could just figure it out. I&#8217;m one of the admins (of 3); I have one editor, 22 authors, and 7 contributors on the site. When I installed the plugin, all I get is the option to mail-to the admins. There&#8217;s nothing showing up for any of the other groups (which is actually the most useful part of this plugin&#8217;s concept, for me &#8212; 22 people is an awful lot to email at once, manually). </p>
<p>I&#8217;m also using Role Manager, but otherwise I&#8217;ve made no adjustments to users, nor have I messed with the admin interface at all. Is there some other setting I need to make sure is switched to the &#8216;on&#8217; position to see the other groups as email options?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Schürjohann</title>
		<link>http://blog.decaf.de/2009/01/mailto-staff/#comment-44597</link>
		<dc:creator>Dirk Schürjohann</dc:creator>
		<pubDate>Mon, 19 Jan 2009 08:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.decaf.de/?p=909#comment-44597</guid>
		<description>Álvaro, thanks for your feedback!

Concerning your second comment: Where the mailto link occurs is easy to manage. WordPress provides a bunch of »hooks«, and you could use a different one than the current activity box hook. Line 24 in &lt;code&gt;mailto-staff.php&lt;/code&gt;:

This one would be for the profile page of any user:
&lt;code&gt;// actions
add_action(&#039;profile_personal_options&#039;, &#039;mailto&#039;);

This one would be the WP header:
&lt;/code&gt;&lt;code&gt;// actions
add_action(&#039;admin_head&#039;, &#039;mailto&#039;);

And this one would be the WP footer:
&lt;/code&gt;&lt;code&gt;// actions
add_action(&#039;admin_footer&#039;, &#039;mailto&#039;);&lt;/code&gt;

Concerning your first comment: If you want to contact subscribers only, you should remove lines 47-50 (admins) or even better lines 47-62 (admins, editors, authors, contributors). Second, as you need a simple link without user options, you may want to modifiy the HTML structure and dismiss the checkboxes. It&#039;s lines 103-122.</description>
		<content:encoded><![CDATA[<p>Álvaro, thanks for your feedback!</p>
<p>Concerning your second comment: Where the mailto link occurs is easy to manage. WordPress provides a bunch of »hooks«, and you could use a different one than the current activity box hook. Line 24 in <code>mailto-staff.php</code>:</p>
<p>This one would be for the profile page of any user:<br />
<code>// actions
add_action(&#039;profile_personal_options&#039;, &#039;mailto&#039;);

This one would be the WP header:
</code><code>// actions
add_action(&#039;admin_head&#039;, &#039;mailto&#039;);

And this one would be the WP footer:
</code><code>// actions
add_action(&#039;admin_footer&#039;, &#039;mailto&#039;);</code></p>
<p>Concerning your first comment: If you want to contact subscribers only, you should remove lines 47-50 (admins) or even better lines 47-62 (admins, editors, authors, contributors). Second, as you need a simple link without user options, you may want to modifiy the HTML structure and dismiss the checkboxes. It&#8217;s lines 103-122.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

