Oops, sorry.
As you might guess, I did NOT see this in testing.
Would you please tell me which browser and version you are using?
If you happen to know what version of PHP you are using or server (Apache, IIS, etc.); that might also be helpful.
Expect Version 1.5 within a few hours.
Thanks,
Peter
1.5 is a rollback to version 1.3
I am unable to reproduce the error reported by you and another that exists in 1.4
Like 1.3, 1.5 does NOT give you a list of who has NOT read the posts.
I will look closer this weekend, but any information that you could provide to help me see the problem would be appreciated.
Peter
I need to be able to replicate this error.
What exactly do you do to produce this error? Does it happen whenever a page is displayed? When you go to the RnU Settings page? When you attempt to extract the list?
Please give me step-by-step instructions of what you do and what you see.
Could anyone supply with versions of browsers that produce this error? It would be especially nice to also know which web server (apache?? iis?) and version of php and wordpress are being used.
I would love to fix it; but at the moment, it is invisible to me.
I think that I found the error in version 1.4 that I still cannot replicate.
My hypothesis is that I went out of bounds on an array, and it generated an error that was destined for the output. In order to display that error, WP naturally output a context header as the error was the first message to be sent to the browser.
However, the context header had already been output in an attempt to write the exported CSV file. I think that might be the cause of the “headers already sent by …” message.
I believe that I have fixed the issue and would release it as version 1.6
However, I am in desperate need of a BETA tester. I need someone who experienced the ” headers already sent by … ” error in version 1.4 to whom I may send a link to version 1.6 (or at least a corrected copy of class_wp_rnu.php )
Any Volunteers??
Version 1.6 has been released. Unfortunately, I could not reproduce the error seen in version 1.4 and have no beta testers for v1.6
