<?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 for Brass Blogs Web Design</title>
	<atom:link href="http://brassblogs.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://brassblogs.com</link>
	<description>Web Design located in Simsbury (a suburb of Hartford) CT</description>
	<lastBuildDate>Mon, 05 Dec 2011 17:35:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on wp_logout_url()&#8230;. AGH!!! by Shelly</title>
		<link>http://brassblogs.com/cms-platforms/wordpress/wp_logout_url-agh#comment-571</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Mon, 05 Dec 2011 17:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=285#comment-571</guid>
		<description>And Alex, that&#039;s why I recommended NOT changing core, and simply placing this fix in your functions.php.  You should never mess with core.  but when you have to, this is the proper way to do it.</description>
		<content:encoded><![CDATA[<p>And Alex, that&#8217;s why I recommended NOT changing core, and simply placing this fix in your functions.php.  You should never mess with core.  but when you have to, this is the proper way to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on wp_logout_url()&#8230;. AGH!!! by Shelly</title>
		<link>http://brassblogs.com/cms-platforms/wordpress/wp_logout_url-agh#comment-570</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Mon, 05 Dec 2011 17:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=285#comment-570</guid>
		<description>David - sorry it took so long to get back to you on your question.  Been crazy busy here.  

First off, it&#039;s PHP, not Javascript.  

Secondly, the &quot;function wp_logout_url($redirect=&#039;&#039;)&quot; line sets up the function, where a variable ($redirect) defaults to nothing. That way, if the function is used with no input given as a value for $redirect, it won&#039;t throw up an error that a required parameter is missing. 

wp_logout_url(), anyway, is WordPress core, not the fixed function. So if you want any more explanation than that, you&#039;d probably have to contact the WordPress dev team for why they chose to do it that way. But the most likely reason is what I have above - so you can have a defined variable (for use elsewhere) and the definition of that variable - by default - is nothing.</description>
		<content:encoded><![CDATA[<p>David &#8211; sorry it took so long to get back to you on your question.  Been crazy busy here.  </p>
<p>First off, it&#8217;s PHP, not Javascript.  </p>
<p>Secondly, the &#8220;function wp_logout_url($redirect=&#8221;)&#8221; line sets up the function, where a variable ($redirect) defaults to nothing. That way, if the function is used with no input given as a value for $redirect, it won&#8217;t throw up an error that a required parameter is missing. </p>
<p>wp_logout_url(), anyway, is WordPress core, not the fixed function. So if you want any more explanation than that, you&#8217;d probably have to contact the WordPress dev team for why they chose to do it that way. But the most likely reason is what I have above &#8211; so you can have a defined variable (for use elsewhere) and the definition of that variable &#8211; by default &#8211; is nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on wp_logout_url()&#8230;. AGH!!! by Tung</title>
		<link>http://brassblogs.com/cms-platforms/wordpress/wp_logout_url-agh#comment-569</link>
		<dc:creator>Tung</dc:creator>
		<pubDate>Mon, 05 Dec 2011 05:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=285#comment-569</guid>
		<description>Having the same problem, but with BuddyPress. Glad someone figured it out before I had to digg into the code!</description>
		<content:encoded><![CDATA[<p>Having the same problem, but with BuddyPress. Glad someone figured it out before I had to digg into the code!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on wp_logout_url()&#8230;. AGH!!! by lån, alex</title>
		<link>http://brassblogs.com/cms-platforms/wordpress/wp_logout_url-agh#comment-567</link>
		<dc:creator>lån, alex</dc:creator>
		<pubDate>Mon, 29 Aug 2011 14:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=285#comment-567</guid>
		<description>Hey. Great tip thanks! Would love to see WP update core tho since i really dont like messing with it in case i forget to fix it again after i update or smth.</description>
		<content:encoded><![CDATA[<p>Hey. Great tip thanks! Would love to see WP update core tho since i really dont like messing with it in case i forget to fix it again after i update or smth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on wp_logout_url()&#8230;. AGH!!! by David</title>
		<link>http://brassblogs.com/cms-platforms/wordpress/wp_logout_url-agh#comment-566</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 14 Jul 2011 22:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=285#comment-566</guid>
		<description>Great post, but I have a little question.

In the second of code where it has:

function wp_logout_url($redirect = &#039;&#039;) 

In the parameters it has an assignment instead of a variable, why? (I&#039;m sort of a nooby in JavaScript myself).</description>
		<content:encoded><![CDATA[<p>Great post, but I have a little question.</p>
<p>In the second of code where it has:</p>
<p>function wp_logout_url($redirect = &#8221;) </p>
<p>In the parameters it has an assignment instead of a variable, why? (I&#8217;m sort of a nooby in JavaScript myself).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back End Instructions &#8211; official release by Shelly</title>
		<link>http://brassblogs.com/blog/back-end-instructions-official-release#comment-564</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Thu, 07 Jul 2011 20:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=274#comment-564</guid>
		<description>Yes, it appears I&#039;m correct.  it&#039;s *possible* to remove the permalink slug from the instructions post, but the difficulty of doing it (and the possible collisions and dangers that could affect the rest of the site) it&#039;s simply not worth trying to do. Doing so would basically use the custom post type for something it&#039;s not supposed to be used for.

An alternative method would be to simply force any user who accidentally happen upon an instruction on the front end to be logged in.  Actually there&#039;s several things you could do.  if you dont&#039; want them to be seen *at all* on the front end, you can create a custom post type template file and make the custom post type do whatever you like.  Force people to log in to see it first (and compare the logged-in user&#039;s level to the level given in the custom post type) ir simple have a default message that says &quot;you can&#039;t see this&quot; or something. (maybe make it a fake 404 page.)

Those are some viable workarounds :)</description>
		<content:encoded><![CDATA[<p>Yes, it appears I&#8217;m correct.  it&#8217;s *possible* to remove the permalink slug from the instructions post, but the difficulty of doing it (and the possible collisions and dangers that could affect the rest of the site) it&#8217;s simply not worth trying to do. Doing so would basically use the custom post type for something it&#8217;s not supposed to be used for.</p>
<p>An alternative method would be to simply force any user who accidentally happen upon an instruction on the front end to be logged in.  Actually there&#8217;s several things you could do.  if you dont&#8217; want them to be seen *at all* on the front end, you can create a custom post type template file and make the custom post type do whatever you like.  Force people to log in to see it first (and compare the logged-in user&#8217;s level to the level given in the custom post type) ir simple have a default message that says &#8220;you can&#8217;t see this&#8221; or something. (maybe make it a fake 404 page.)</p>
<p>Those are some viable workarounds <img src='http://brassblogs.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back End Instructions &#8211; official release by Stephan</title>
		<link>http://brassblogs.com/blog/back-end-instructions-official-release#comment-563</link>
		<dc:creator>Stephan</dc:creator>
		<pubDate>Thu, 07 Jul 2011 20:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=274#comment-563</guid>
		<description>Thank you!</description>
		<content:encoded><![CDATA[<p>Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back End Instructions &#8211; official release by Shelly</title>
		<link>http://brassblogs.com/blog/back-end-instructions-official-release#comment-562</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Thu, 07 Jul 2011 16:30:15 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=274#comment-562</guid>
		<description>Well, they are using the WordPress custom post type.  Custom Post Types are generally made to be used on the front-end of the site.  So generally, if someone has the URL to the page, it would be visible on the front end.  But if you don&#039;t link to them from anywhere on the site, they should not be found - save from someone actually knowing exactly where they are located.

Someone already reported to be that they are coming up in the search results.  I&#039;ve fixed that issue (it&#039;s in the upcoming release) - so once you upgrade there shoudn&#039;t be anyone actually viewing them from the front end (not unless you provide direct links to them)  I dont&#039; know that there&#039;s any method of preventing them from actually being seen on the front end (whether you know what the URL is or not) - because, as I said before, these are using the custom post type system that WordPress provides.  I don&#039;t know that there&#039;s any method of removing permalinks from posts. But I&#039;ll look into it.</description>
		<content:encoded><![CDATA[<p>Well, they are using the WordPress custom post type.  Custom Post Types are generally made to be used on the front-end of the site.  So generally, if someone has the URL to the page, it would be visible on the front end.  But if you don&#8217;t link to them from anywhere on the site, they should not be found &#8211; save from someone actually knowing exactly where they are located.</p>
<p>Someone already reported to be that they are coming up in the search results.  I&#8217;ve fixed that issue (it&#8217;s in the upcoming release) &#8211; so once you upgrade there shoudn&#8217;t be anyone actually viewing them from the front end (not unless you provide direct links to them)  I dont&#8217; know that there&#8217;s any method of preventing them from actually being seen on the front end (whether you know what the URL is or not) &#8211; because, as I said before, these are using the custom post type system that WordPress provides.  I don&#8217;t know that there&#8217;s any method of removing permalinks from posts. But I&#8217;ll look into it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back End Instructions &#8211; official release by Stephan</title>
		<link>http://brassblogs.com/blog/back-end-instructions-official-release#comment-561</link>
		<dc:creator>Stephan</dc:creator>
		<pubDate>Thu, 07 Jul 2011 16:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=274#comment-561</guid>
		<description>Hi,

it is a real great Plugin. I have only one problem/question: The Instructions shall be visible only to Backend-Users. Unfortunately with there Permalink they are reachable in the Frontend as well.
I tried to set it to private or password protected but then they won&#039;t show up in the Backend anymore. Is there any way to solve that or am I just blind?!?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>it is a real great Plugin. I have only one problem/question: The Instructions shall be visible only to Backend-Users. Unfortunately with there Permalink they are reachable in the Frontend as well.<br />
I tried to set it to private or password protected but then they won&#8217;t show up in the Backend anymore. Is there any way to solve that or am I just blind?!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Back End Instructions &#8211; official release by Shelly</title>
		<link>http://brassblogs.com/blog/back-end-instructions-official-release#comment-553</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Tue, 07 Jun 2011 12:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://brassblogs.com/?p=274#comment-553</guid>
		<description>Actually, yes there is.  (I noticed that too!) I&#039;m working on the next release and that&#039;s in my &quot;to do&#039;s&quot; for it :)</description>
		<content:encoded><![CDATA[<p>Actually, yes there is.  (I noticed that too!) I&#8217;m working on the next release and that&#8217;s in my &#8220;to do&#8217;s&#8221; for it <img src='http://brassblogs.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

