WordPress.org

1. shaythong
   Member
   Posted 5 years ago #
   

   There's a bug in the latest Akismet 2.1 for WordPress plugin.
   If you get a "Parse error: syntax error, unexpected '}'".

   Just open akismet.php and on line 284 where it says:
   

   <?php
   }
   
   function akismet_caught() {
   ?>

   Replace with:
   

   <?php
   
   function akismet_caught() {
   ?>

   But I still get another message caused by Akismet:
   

   Warning: Cannot modify header information - headers already sent by (output started at /wp-content/plugins/akismet/akismet.php:283) in /wp-includes/pluggable.php on line 391

   .

2. Funnnny
   Member
   Posted 5 years ago #
   

   I get the Parse error too, but it's easy to solve.
   I think your second error because of another plugins. Try to disable Akismet and active it again

3. shaythong
   Member
   Posted 5 years ago #
   

   Is my fix correct? I don't think so, but it should be fixed soon.

4. WheresWaldo
   Member
   Posted 5 years ago #
   

   It might be better to wait for version 2.1.1 I have the same two issues with a new install of WP (meaning no other plugins except for Akismet

5. raianoat
   Member
   Posted 5 years ago #
   

   I'm having the same issue with my blog. Anybody know where I can get the old version again?

6. Matt Mullenweg
   Troublemaker
   Posted 5 years ago #
   

   Sorry about that, 2.1.1 is available now and doesn't have that problem.

7. raianoat
   Member
   Posted 5 years ago #
   

   Updated to 2.1.1 and now I am getting this error:

   Warning: Cannot modify header information - headers already sent by (output started at /home/tivoblog/public_html/wp-content/plugins/akismet/akismet.php:283) in /home/tivoblog/public_html/wp-includes/pluggable.php on line 391

   Thoughts?

8. Funnnny
   Member
   Posted 5 years ago #
   

   The old version has 2 bugs, Parse Error (seem to be fixed) and "Cannot modify header information". I think everyone still get the 2nd error on 2.1.1

9. gfindlay
   Member
   Posted 5 years ago #
   

   Nope, not everyone gets the headers error. Me, for example. Upgrade to 2.1.1 and no errors at all. And I'm running about 100 other plugins too.

10. Lester Chan
    Member
    Posted 5 years ago #
    

    count me in on the header error.

11. Funnnny
    Member
    Posted 5 years ago #
    

    Nope, not everyone gets the headers error. Me, for example. Upgrade to 2.1.1 and no errors at all. And I'm running about 100 other plugins too.

    You don't get this error when active the plugin. You only get this when Post, Comment...

12. raianoat
    Member
    Posted 5 years ago #
    

    I get the error when I try and "Delete All" spam comments.

13. Funnnny
    Member
    Posted 5 years ago #
    

    Try to install Akismet 2.0, It's still work.
    We need new version soon

14. raianoat
    Member
    Posted 5 years ago #
    

    Where can I find 2.0?

15. greatfirewall
    Member
    Posted 5 years ago #
    

    Where can I find 2.0?

    Just download WordPress 2.3.1 and copy the akismet.php from it...

    (./wordpress/wp-content/plugins/akismet/akismet.php)

16. raianoat
    Member
    Posted 5 years ago #
    

    I don't know why I didn't think of that.....

    Thanks :)

17. sahaskatta
    Member
    Posted 5 years ago #
    

    I've got the same problem too. I receive an error when trying to delete the comments from the Akismet Moderation Queue. I never had a problem of this sort before. I'm going to downgrade back to the previous version until a fix becomes available.

18. Samuel Wood (Otto)
    Tech Ninja
    Posted 5 years ago #
    

    Try this version. It's 2.1.1 with a slight modification that I made to try to correct that warning message:
    http://wordpress.pastebin.ca/820999

19. Matt Mullenweg
    Troublemaker
    Posted 5 years ago #
    

    2.1.2, available since last night, fixes everything mentioned in this thread.

20. shaythong
    Member
    Posted 5 years ago #
    

    Hey, I see v2.1.2 has been released. Thanks for the help.

21. UniverseJDJ
    Member
    Posted 5 years ago #
    

    Yep, confirming 2.1.2 fixes everything,

Topic Closed

This topic has been closed to new replies.