<?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: Disabling the Plugin/Theme editor 3.0</title>
	<atom:link href="http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/</link>
	<description>WordPress multisite how to - making sense of the network feature from what was wordpress mu</description>
	<lastBuildDate>Thu, 26 Jan 2012 22:51:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Richard Matthews</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-9813</link>
		<dc:creator>Richard Matthews</dc:creator>
		<pubDate>Mon, 05 Jul 2010 02:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-9813</guid>
		<description>Hey Guys, 

I&#039;ve got a question about security and usability for my WP3 Multi-Site install. 

I&#039;m running a pretty well moderated community site, with the ability for users to keep &#039;Journals&#039; - our custom name for blogs. But WPMS defaults all new users as Admins of any blogs they create. What would be ideal for us is if they could default to simply Editors for their own blogs. 

Do you know if this is possible?</description>
		<content:encoded><![CDATA[<p>Hey Guys, </p>
<p>I&#8217;ve got a question about security and usability for my WP3 Multi-Site install. </p>
<p>I&#8217;m running a pretty well moderated community site, with the ability for users to keep &#8216;Journals&#8217; &#8211; our custom name for blogs. But WPMS defaults all new users as Admins of any blogs they create. What would be ideal for us is if they could default to simply Editors for their own blogs. </p>
<p>Do you know if this is possible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deepanshu Goel</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-9645</link>
		<dc:creator>Deepanshu Goel</dc:creator>
		<pubDate>Thu, 24 Jun 2010 03:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-9645</guid>
		<description>Thanks a lot.

one simple line in wp-config.php does make a lot sense in view of security.</description>
		<content:encoded><![CDATA[<p>Thanks a lot.</p>
<p>one simple line in wp-config.php does make a lot sense in view of security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrea</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-9129</link>
		<dc:creator>andrea</dc:creator>
		<pubDate>Wed, 16 Jun 2010 19:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-9129</guid>
		<description>Remove the temptation to try, and even with permissions - what if you miss some?</description>
		<content:encoded><![CDATA[<p>Remove the temptation to try, and even with permissions &#8211; what if you miss some?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-9123</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 16 Jun 2010 17:29:11 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-9123</guid>
		<description>I assumed file permissions would be the standard way to work around this.

Removing the editor link does make things a little smoother looking in the backend though I spose.</description>
		<content:encoded><![CDATA[<p>I assumed file permissions would be the standard way to work around this.</p>
<p>Removing the editor link does make things a little smoother looking in the backend though I spose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mercime</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8816</link>
		<dc:creator>mercime</dc:creator>
		<pubDate>Sun, 13 Jun 2010 23:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8816</guid>
		<description>Ron, thank you for this plugin. I already had an enable plugin/theme editor in mu-plugins when I upgraded dev install to WP 3.0 trunk and saw two links to each editor :-) Agreed with you 100% that theme&amp; plugin editors should not be enabled even for Site/Super Admins in production/live installs.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Ron, thank you for this plugin. I already had an enable plugin/theme editor in mu-plugins when I upgraded dev install to WP 3.0 trunk and saw two links to each editor <img src='http://wpmututorials.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Agreed with you 100% that theme&amp; plugin editors should not be enabled even for Site/Super Admins in production/live installs.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8096</link>
		<dc:creator>Donald</dc:creator>
		<pubDate>Mon, 03 May 2010 08:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8096</guid>
		<description>Great plugin!  Almost exactly what I wanted.  Added 

$cap == &#039;delete_plugins&#039; &#124;&#124; $cap == &#039;activate_plugins&#039; 

to the function to disable activation or deactivation of all plugins.

This in addition to the &quot;disable plugin updates&quot; plugin works perfect, thanks!</description>
		<content:encoded><![CDATA[<p>Great plugin!  Almost exactly what I wanted.  Added </p>
<p>$cap == &#8216;delete_plugins&#8217; || $cap == &#8216;activate_plugins&#8217; </p>
<p>to the function to disable activation or deactivation of all plugins.</p>
<p>This in addition to the &#8220;disable plugin updates&#8221; plugin works perfect, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8035</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Sun, 18 Apr 2010 02:30:13 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8035</guid>
		<description>The plugin goes in the wp-content/mu-plugins folder. In a new 3.0 install, you need to create the folder.</description>
		<content:encoded><![CDATA[<p>The plugin goes in the wp-content/mu-plugins folder. In a new 3.0 install, you need to create the folder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ipstenu</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8022</link>
		<dc:creator>Ipstenu</dc:creator>
		<pubDate>Wed, 14 Apr 2010 17:01:42 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8022</guid>
		<description>I put this in my /plugins folder on my MultiSite blog and went to activate it only ... it&#039;s not there.  So I remembered that dropins for Multi Site go in the wp-content folder, not plugins. I went and put it there and still nothing.  I even went and checked that I (as super-admin) could still edit themes and plugins and I can.

This is 3.0-Beta with the nightly build from the 13th.</description>
		<content:encoded><![CDATA[<p>I put this in my /plugins folder on my MultiSite blog and went to activate it only &#8230; it&#8217;s not there.  So I remembered that dropins for Multi Site go in the wp-content folder, not plugins. I went and put it there and still nothing.  I even went and checked that I (as super-admin) could still edit themes and plugins and I can.</p>
<p>This is 3.0-Beta with the nightly build from the 13th.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8018</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Wed, 14 Apr 2010 05:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8018</guid>
		<description>If someone hacks their way onto the super admin list, then they have access to the theme/plugin files. In the case of the theme editor, it defaults to the active theme on the current blog. The rest of the hack script would be pretty easy writing.</description>
		<content:encoded><![CDATA[<p>If someone hacks their way onto the super admin list, then they have access to the theme/plugin files. In the case of the theme editor, it defaults to the active theme on the current blog. The rest of the hack script would be pretty easy writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ovidiu</title>
		<link>http://wpmututorials.com/plugins/disabling-the-plugintheme-editor-3-0/#comment-8011</link>
		<dc:creator>Ovidiu</dc:creator>
		<pubDate>Mon, 12 Apr 2010 23:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://wpmututorials.com/?p=362#comment-8011</guid>
		<description>dumb question, but why disable the editors for the Super Admin? Or am I simply confused by the new terms? Isn&#039;t the Super Admin = the global admin, as opposed to a blog-admin (aka a user that signs up for a blog and becomes its admin?)</description>
		<content:encoded><![CDATA[<p>dumb question, but why disable the editors for the Super Admin? Or am I simply confused by the new terms? Isn&#8217;t the Super Admin = the global admin, as opposed to a blog-admin (aka a user that signs up for a blog and becomes its admin?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

