<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>fortes.com - Latest Comments in Updating WordPress Plugins for 1.5.1</title><link>http://fortes.disqus.com/</link><description></description><atom:link href="https://fortes.disqus.com/updating_wordpress_plugins_for_151/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 13 Jul 2005 17:55:38 -0000</lastBuildDate><item><title>Re: Updating WordPress Plugins for 1.5.1</title><link>http://fortes.com/2005/05/updating-wordpress-plugins-for-151/#comment-1207737</link><description>&lt;p&gt;Hi Fil!&lt;/p&gt;&lt;p&gt;I'm using WP 1.5.1.3 and I had your postlevel plugin running until I realized that all users apart from me, the admin, cannot view or comment the post. &lt;br&gt;Please apologize if I don't get it right, but does this mean that I can fix the broken single post view of your postlevel plugin myself according to these instructions?&lt;/p&gt;&lt;p&gt;Do you plan to release a new version of it that works with WP 1.5.1 or higher?&lt;br&gt;Your plugin would be the only one which works with the newer WP versions. &lt;br&gt;I used the viewlevel plugin before, but since I've upgraded, it did not work any more. Now I'm using the private category plugin, but this only hides certain posts in overviews and archives. If you know the id or permalink, you can still access it. I made a quick and dirty hack and now it does not the display the content any more, but I'm not that confident with it.&lt;br&gt;Your plugin is the only one which is based on private posts you can access when you're logged in thanks to the plugin. The other ones do it vice versa, these posts are public, but hidden by the plugin. I think your way is more secure.&lt;/p&gt;&lt;p&gt;I'm sure you would make a lot of people very happy for this feature is desperately needed in WP. :-))) Just private posts that can only be seen in the admin area or protected posts which need a password each time are not sufficient. I already postet a feature request at &lt;a href="http://wordpress.org" rel="nofollow noopener" target="_blank" title="wordpress.org"&gt;wordpress.org&lt;/a&gt;...&lt;/p&gt;&lt;p&gt;Sorry for this mass of words. ;-)&lt;br&gt;Greetings! &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jessica</dc:creator><pubDate>Wed, 13 Jul 2005 17:55:38 -0000</pubDate></item><item><title>Re: Updating WordPress Plugins for 1.5.1</title><link>http://fortes.com/2005/05/updating-wordpress-plugins-for-151/#comment-1207736</link><description>&lt;p&gt;Does this work with 1.5.1.3?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shelby</dc:creator><pubDate>Sat, 09 Jul 2005 01:23:30 -0000</pubDate></item><item><title>Re: Updating WordPress Plugins for 1.5.1</title><link>http://fortes.com/2005/05/updating-wordpress-plugins-for-151/#comment-1207735</link><description>&lt;p&gt;underburn: The information on this page is for the developer of whatever plugins you're using. If you know PHP, you can try to edit the plugin yourself using the instructions in this post (if you don't, contact your plugin authors)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fortes</dc:creator><pubDate>Tue, 17 May 2005 01:01:19 -0000</pubDate></item><item><title>Re: Updating WordPress Plugins for 1.5.1</title><link>http://fortes.com/2005/05/updating-wordpress-plugins-for-151/#comment-1207734</link><description>&lt;p&gt;I dont understand what to do in order to fix it, my site is at &lt;a href="http://underburn.com" rel="nofollow noopener" target="_blank" title="underburn.com"&gt;underburn.com&lt;/a&gt; I erased my plugins and tried it again but for some reason its failing on me&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">underburn.com</dc:creator><pubDate>Mon, 16 May 2005 20:34:15 -0000</pubDate></item></channel></rss>