paulspen

DUH! OK I figured it out. There were many blank line returns at the end of viewlevel.php and wp-blog-header.php Not sure how they got there, but when I deleted them all, everything worked OK. Hope this helps someone else!

Hey Kendra: I’ve been getting this message again after I installed 1.1.2
Warning: Cannot modify header information – headers already sent by (output started at /home/sitename/sitedir/blog/wp-content/plugins/viewlevel.php:345) in /home/sitename/sitedir/blog/wp-login.php on line 257
Tried all sorts of things: logging out, deleting cookies, etc, but once this error comes up, then other parts of the blog stop working soon after. Once it wouldn’t even let me log in again! The only thing I can think of is does it matter if the blog is stored in its own directory and not on the top level of the site? I only ask this because I noticed I needed to add the directory to the line in viewlevel that calls padlock.gif in order for the lock to show up. Could my directory structure be causing the above problem?
Please help a fellow Ithacan.
Thanks!

OK. I reinstalled and it seems to have fixed itself. Now the only issue is that when I view the blog as me (viewlevel 10) and see view-level protected posts, the protected post title reads:
Title”> X Title
where X is the missing padlock image.
When I view it as viewlevel 0, the post doesn’t appear at all, which I guess means it’s working.
Thanks again!

Thanks, Kendra.
Nope, I’m using the right one, but let me mess around a little more and get back to you.
Thanks for the response!

Installed per instructions and get the following:
Warning: Cannot modify header information – headers already sent by (output started at /home/sitename/sitedir/blog/wp-content/plugins/viewlevel.php:345) in /home/sitename/sitedir/blog/wp-login.php on line 257
followed by three or four more of the same message with different line numbers. Any ideas? Thanks

Hi:
I apologize, but I’ve looked over several of your postings regarding this issue and seem to find conflicting (to a newbie) pieces of code. Some require editing config, others require editing config and blog-header, still others say to replace whole sections of code while others limit to one line.
I would be most grateful if you could “cobble it all together” into this one posting. All I need is that the author should be able to see his private posts on the main page, not just on the edit page, while to all other users they are hidden. If however, if you think it more useful to do it using some sort of ranking system, like one of the prior posts on this subject, that would be great as well.
Thanks so much for considering this!