Posted 9 months ago #
Hi,
Latest version of the plugin (1.5.3) not activating in WP 2.7. Get the following error message:
Warning: Cannot modify header information - headers already sent by (output started at .../wp-content/plugins/acronyms/acronyms.php:1) in /.../wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 8
Compatibility issue or perhaps incorrect coding?
Awaiting feedback.
R
Posted 9 months ago #
I'm not sure what's causing the error for you. I installed Bad Behavior (2.0.26) on a fresh test blog and activated it, then activated Acronyms with no problems. Activating Acronyms without Bad Behavior active also yielded no errors.
It does seem like there might be some empty whitespace at the beginning of your copy of the file; you could try opening acronyms.php and make sure that the first line of the file is "<?php".
Posted 9 months ago #
Hi,
Thanks for the prompt response.
Did the following:
- checked for whitespace at the beginning of file... looks OK.
- Deleted and re-installed plugin. On activation... same error.
- Deactivated Bad Behaviour and was able to activate plugin OK but when going into "Write Post" to create a test post - edit.php crashed with a similar error message to above.
- I also noted that with "acronyms" activated the edit post panel was layed out very differently... weird.
- Have de-activated "Acronyms" and re-activated "Bad Behaviour".
Let's wait and see what other feedback comes in and see if anyone else has experienced similar issues.
Cheers,
R
Posted 9 months ago #
Hi,
Have tried "Acronyms" on my test blog (WP 2.7 and same theme - K2)...
- had all plugins deactivated except for "Bad Behaviour" and "Maintenance Mode" plugins... same error.
- enabled the Default WP theme and deactivated "Bad Behaviour"... exactly the same errors!
I can't see how the cause of this issue would lie with WP or another plugin.
Something else definitely going on here.
Hopefully we'll get some feedback from other users.
R
- enabled the Default WP theme and deactivated "Bad Behaviour"... exactly the same errors!
You get the same error with Bad Behaviour deactivated--now that doesn't seem right.
Delete Bad Behaviour in wp-content/plugins and see if you get the same error.
Posted 9 months ago #
BTW I'm getting the same error on my production blog (ketsugi.com) as well so hopefully a fix is imminent. I can't seem to figure out what's causing it, though.
Posted 9 months ago #
Michael,
When I say exact same errors - I'm referring to (see previous response)
-
Deactivated Bad Behaviour and was able to activate plugin OK but when going into "Write Post" to create a test post - edit.php crashed with a similar error message to above.
- I also noted that with "acronyms" activated the edit post panel was layed out very differently... weird.
- Have de-activated "Acronyms" and re-activated "Bad Behaviour".
The errors that come up when BB is deactivated refer to pluggable.php.
Glad to see someone else is experiencing the same issue on using the plugin.
At this stage I feel that I have done enough testing as I strongly suspect something strange in the coding of the plugin. The fact that the same errors occur on an installation with default theme and no plugins would suggest this.
R
Posted 9 months ago #
At this point I'm getting pretty frustrated. The error isn't being consistently reproduced on my test systems. I'm beginning to suspect it might be a text encoding issue and RapidSVN might be messing it up.
Could you try this development version? I have this working on a fresh test blog (running on WAMPServer) and am experiencing no errors with this.
Posted 9 months ago #
Had a go on my test blog...
1) Acronyms activates without any issues.
2) When going into "New Post" get the following error:
Warning: Cannot modify header information - headers already sent by (output started at .../wp-content/plugins/acronyms/acronyms.php:1) in .../wp-includes/classes.php on line 1571
Looks like we are slowly getting there but not quite there yet.
R
Posted 9 months ago #
I had the exact same problem. If you look well at the first line of acronym.php, you will see that:
<?php
There is a blank character before the <?php which produces output. I'm not sure it's a but related to this plugin: I checked in the SVN sourcecode and there is no such whitespace.
Hope it helps.
PS: I had trouble since I did the plugin auto-update. I'm pretty sure it comes from that way of update.
Posted 9 months ago #
Very odd...
I have checked and rechecked my "acronyms.php" and I don't have a white space as you mention. When I saw that error it's the first thing I looked for.
I am curious about one thing... if the SVN sourcecode does not have the whitespace then how did it end up in your local copy of "acronyms.php"? Isn't that where the plugin package is actually downloaded from?
Lets hope that the author is able to resolve this issue - I rather like the idea of what his plugin can offer.
R
Posted 9 months ago #
Maybe I wasn't clear enough about this, but I'm the author >.>
Rschilt, can I get you on AIM or GTalk to try and figure this out? I'm no longer experiencing this issue with the exact same version that I asked you to try out (1.6DEV) so I'm not sure why you're still seeing the error.
Add me on AIM: panjieyi or GTalk: toastyou@gmail.com
Posted 9 months ago #
Hi,
Apologies for perhaps not being clear in my previous response. The bit about "the author" was directed at "oncletom". I have been aware since first posting to this forum that "ketsugi" is the plugin author.
Anyway...
I have tried a couple of times to contact you via GTalk. Note that I'm not much of a "chat" user as I access the internet over dialup type speeds and we still have timed calls where I am (Papua New Guinea).
I suppose we also have the time zone differences - when you're asleep - I'm awake - and vice-versa.
Forget about AIM - lets GTalk... my id is "rjschilt@gmail.com" - please keep your eye out for "jungle" boy.
R
Posted 9 months ago #
I haven't had any error messages, but after the last update, WordPress started acting funny. When I submitted edited posts or tried to activate or deactivate plugins I'd either get a blank page or a page with just a couple of punctuation marks in the upper lefthand corner.
This occurred after updating Acronyms, Maintenance Mode and Bad Behavior on the same day. Bad Behavior isn't activated, so I didn't do anything with that. After deactivating Acronyms, the problems stopped.
Let me know if you need more details -- I'm willing to help however I can. I love this plugin.
Posted 9 months ago #
K,
Doesn't look like we are having any luck getting hold of each other on GTalk.
Thought I'd give the DEV version another go and interestingly - on activation it comes up with the original message:
Warning: Cannot modify header information - headers already sent by (output started at .../wp-content/plugins/acronyms/acronyms.php:1) in .../wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 8
Honestly, I don't have the time to be involved in further testing. What I will do is keep my out for future versions. Perhaps as more folks take your plugin for a test run - some of these "kinks" will be ironed out.
Regards,
R
Posted 9 months ago #
Thanks, Rschilt. I'm getting incredibly frustrated with this bizarre error. Sometimes I get it, sometimes I don't... with exactly the same file in place. I can't pinpoint what's causing it, but the errors only started showing up in version 1.5.3, which I edited in TextPad in Windows. My usual development environment is TextMate on my Mac, so I'm guessing there's a text encoding issue.
Hopefully I can issue a 1.6 beta soon to see if it fixes your problems.
Posted 9 months ago #
K,
Understand the frustration. As with all technical problems - there's always a solution. In the end it will be something simple (for than likely) and you would have learnt that little bit more.
Will keep my eyes open for any updates of your plugin and test as they become available.
Regards,
R
Posted 9 months ago #
I'm currently running 1.6beta1 on my test and production blogs without problems.
http://downloads.wordpress.org/plugin/acronyms.1.6BETA1.zip
Please let me know if you continue to have issues with this one. If you do, please also let me know whether you're running on a Windows or *nix server. Thanks.
Posted 9 months ago #
I just tested beta 1.6, it is working well. There are no more conflicts with nextgen gallery plugin. By the way, for the edit function, we are only allowed to edit the full acronyms?
Thanks :)
Posted 9 months ago #
Hi Lovelidicious, yes that's correct. The acronym is the identifier. If you wish to change the acronym itself, please delete your old one and add a new one.
Posted 9 months ago #
K,
A quick post to let you know that I have tested 1.6b and so far I have not been able to fault it. Looks like you cracked it bro!
All the issues I was having previously when activating, creating a new post and deactivating the plugin seem to have been fixed.
Are you able to share with us what the issue was in the end?
Thanks for persisting.
R
Posted 9 months ago #
Sadly, 1.6Beta1 is almost identical to 1.6DEV. The only difference is that I saved the file on my Mac instead of on my Windows machine.
Posted 9 months ago #
K,
Trust Windows to foul up on something as simple as that!
R
Posted 9 months ago #
K,
Sorry to tell you this but the same issue has surfaced with 1.6
Where's that beta version?
R
Posted 9 months ago #
K,
I have reinstalled the beta version as it works fine.
R
Posted 9 months ago #
Getting a similar error with 1.6:

Warning: Cannot modify header information - headers already sent by (output started at /path/to/htdocs/wp-content/plugins/acronyms/acronyms.php:1) in /path/to/htdocs/wp-includes/pluggable.php on line 850
Posted 9 months ago #
I auto upgraded to the 1.6, and it's still messing with my admin activities. For example, I just deactivated the plugin, and instead of bringing me back to the plugin page, it gave me a page with  in the upper lefthand corner. I was also unable to preview draft posts while the plugin was activated. Any kind of confirm or submit action would bring me to either a blank page or a page with  in the upper lefthand corner. Deactivating the plugin corrects those problems.
I'm running WordPress v. 2.7
BTW -- if I'm putting this in the wrong place or should be starting a new topic for my issue since it's slightly different from the one that initiated this topic, please let me know and I'll gladly do so.
Posted 9 months ago #
Hey guys,
I had the same issue with 1.6 and have reverted back to 1.6beta which works fine.
R
Posted 9 months ago #
Yeah, for some reason I am sometimes getting a hidden control character before the <?php and I don't know what's causing it. 1.6.1 seems to have fixed the issue and I'm never going to edit my files on Windows again.
Posted 9 months ago #
K,
1.6.1 working like a dream!
R
You must log in to post.
