Post Levels Enhancer is a Word Press plugin that provides a visual mouse-accessible menu for Filipe Fortes’s Post Levels plugin.
Current Version: 0.1.1
Last update on May 16, 2005
Changelog:
- v0.1.1 - 2005.05.16 - minor change for compatibility with WP 1.5.1 and PL 0.2.1
- v0.1.0 - 2005.03.21 - initial release - for PostLevels 0.2.0
Requirements:
- WordPress 1.5
- Activated Post Levels plugin 0.2.1 (compatibility with other versions is purely coincidental). Update: I have written a “branch” of Post Levels 0.2.1 which addresses certain issues. See this post for more information.
- JavaScript must be enabled for this plugin to function correctly
Installation:
- Save plugin file as post-levels_enhancer.php in your wp-content/plugins/ directory
- Activate plugin in the Plugins section of WordPress
Usage:
- Go to the Write Post section of WordPress administration panel
- Click the Advanced Editing button (it’s next to the Publish button). A box entitled Post Levels should appear directly underneath the main text-input area.
- Check the Enable box to enable Post Levels and select the appropriate user level for your post. (Note: All users with level equal to, or above the chosen Post Level will be able to see the post.)
- Once you have finished your writing, click the Save button (not Publish). (Note: Saving the post keeps it Private — something needed for Post Levels to work.)
A note on Post Levels
As of this version (v0.2) Post Levels does not recognize registered (user_level=0) users — it only recognizes users with user_level=1 or above. I see that as a drawback, since I would like to give my registered readers access to some private posts, without giving them posting privileges (setting user_level to 1+).
The good news is that this issue is very easy to fix. Here are the instructions:
- Open post-levels.php in your editor of choice (or you can even use WordPress’s built-in plugin editor)
- Find the line that reads
if (!empty($user_level))(if should be close to the top) - Replace that line with this one:
if(isset($user_level)) - Save
Help?
I am getting an error:
Warning: Cannot modify header information - headers already sent by (output started at /home/tekwh0re/public_html/wp/wp-content/plugins/postlvl.php:201) in /home/tekwh0re/public_html/wp/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/tekwh0re/public_html/wp/wp-content/plugins/postlvl.php:201) in /home/tekwh0re/public_html/wp/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/tekwh0re/public_html/wp/wp-content/plugins/postlvl.php:201) in /home/tekwh0re/public_html/wp/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/tekwh0re/public_html/wp/wp-content/plugins/postlvl.php:201) in /home/tekwh0re/public_html/wp/wp-admin/admin.php on line 9
Thanks! =)
Comment by Tek — Thursday, March 24, 2005 @ 14:44
Tek, am I correct in assuming that postlvl.php is my plugin? It just seems odd, since the file is exactly 201 lines, including the tags.
In any case, to double check that it’s my plugin that’s causing the problem, see if disabling it fixes the problem. If it does, make sure that the plugin file does not have any spaces at the top, before the first “<php”.
The only other thing I can suggest at the moment is disabling other plugins to see if PostLevels and PLEnhancer will work by themselves. (Note: if you want to check PLE, you must turn on PL).
Let me know if this helps.
Comment by dima — Thursday, March 24, 2005 @ 21:31
Ah thanks… I am always looking for an extra tab return or break… it was a space.
Working now. Thanks for the plugin! =)
Comment by Tek — Saturday, March 26, 2005 @ 09:37
sure thing
Comment by dima — Saturday, March 26, 2005 @ 13:56
Tek, the plugin works fine with one strange side effect. For the vast majority of forms in the admin, not just “write post”, whenever I submit the form wordpress will do strange things such as return a blank page or a page with only the WP logo and Firefox logo with a link to the support forums.
The form will however submit successfully. Any suggestions?
Comment by Max — Saturday, April 16, 2005 @ 14:06
Sorry Dima, not sure why I addressed that to Tek…
Comment by Max — Saturday, April 16, 2005 @ 14:07
Hi Max.
Please be more specific. Which forms are affected by this bug? The _only_ time the plugin should be included (by WordPress) is when you are in the Advanced Edit form. So if you are having problems with other forms (forms that have nothing to do with posts), then it is probably not a problem with the PLE plugin.
Comment by dima — Saturday, April 16, 2005 @ 16:49
Warning: Cannot modify header information - headers already sent by (output started at /home/pingo1/public_html/wp-content/plugins/post-levels_enhancer.php:201) in /home/pingo1/public_html/wp-admin/admin.php on line 6
Warning: Cannot modify header information - headers already sent by (output started at /home/pingo1/public_html/wp-content/plugins/post-levels_enhancer.php:201) in /home/pingo1/public_html/wp-admin/admin.php on line 7
Warning: Cannot modify header information - headers already sent by (output started at /home/pingo1/public_html/wp-content/plugins/post-levels_enhancer.php:201) in /home/pingo1/public_html/wp-admin/admin.php on line 8
Warning: Cannot modify header information - headers already sent by (output started at /home/pingo1/public_html/wp-content/plugins/post-levels_enhancer.php:201) in /home/pingo1/public_html/wp-admin/admin.php on line 9
Same error
Comment by Ludwig — Wednesday, April 20, 2005 @ 17:32
Sorry for DP, theres no space in either of them
Comment by Ludwig — Wednesday, April 20, 2005 @ 17:33
Ludwig, these are classic “space outside of tags” symptoms. Please double-check that there is absolutely nothing before <?php or after ?>. Even a single white space (’ ’) or a return will cause those warning to pop up.
Comment by dima — Wednesday, April 20, 2005 @ 18:32
Error at the write post screen:
Warning: in_array(): Wrong datatype for second argument in /home/virtual/site145/fst/var/www/html/blog/wp-content/plugins/post-levels_enhancer.php on line 92
Comment by Peter — Wednesday, June 15, 2005 @ 15:17
Peter, do not worry about it. There is no problem. You are only getting that warning because you have never used a custom field in any of your WP posts. As soon as you create one (for example when you use PostLevels for the first time), the warning will go away.
Comment by dima — Wednesday, June 15, 2005 @ 16:14
Cool thanks!
Comment by Peter — Thursday, June 16, 2005 @ 18:29
[…] Post Levels Enhancer makes the above plugin much easier to use. […]
Pingback by tylerwillis.com - added a few more plugins — Friday, August 26, 2005 @ 01:05
[…] Anyway, take a look. There are three blocks of code that have large comments around them that say “idlemind.org”. The last two of these blocks contain the fix. The first commented out block is to make PostLevels usable with user_level of 0, as described here. […]
Pingback by idleMind.org Journal » Blog Archive » Post Levels “Branch” — Friday, November 11, 2005 @ 22:41
How does this affect registered users though? If you make private posts viewable to anyone with a level of 0 and above, that means ANYONE can register and read your private entries right after they register on your blog. That kind of defeats the purpose of having private entries, doesn’t it?
I am using V1.5 of WP and V0.2.1 of the Post Levels plugin. My main concern is that I do not want to give ANYONE but myself access to post or edit anything on my blog. In order to make this plugin work, I have to set the user’s levels to 1, which gives them access to my blog. If I change the code in the post-levels.php file like you suggested that means anyone who registers automatically is set with a level of 0, which means they can automatically see my private posts. Does that make sense?
I guess I need to upgrade my WP, but I don’t see having the time anytime soon. Bummer. I really wanted these plugins to work.
Comment by Daisyhead — Wednesday, December 28, 2005 @ 01:06
Daisyhead, you are a little confused. It you make the edits that I suggest, it will NOT make ALL your private posts readable to all registered users. Just as with the original PostLevels plugin, only those private posts that have a “post_level” custom field set will be available to anyone other than yourself.
The only thing that my edits accomplish is to allow you to set a post_level of 0 on your posts if you want registered-only users (users that are registered but have no privileges) reading access to certain private posts.
I hope this explanation helps. Let me know if you have other questions.
Comment by dima — Saturday, December 31, 2005 @ 18:29