WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Yet Another Related Posts Plugin] YARPP Breaks Admin JS in WP 3.0RC1 (12 posts)

  1. Jonathan Brinley
    Member
    Posted 4 years ago #

    I have YARPP running on a blog I recently upgraded to 3.0RC1. It seems to break JavaScript on the admin screens. E.g., you can't expand menu sections, you can't add tags to posts, et al.

    Additionally, I get an error when activating the plugin:

    The plugin generated 972 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    Right now, I'm disabling the plugin when I need to do anything on the back end, then re-activating it when I'm finished. It doesn't seem to cause any ill effects on the public-facing side of the site.

    http://wordpress.org/extend/plugins/yet-another-related-posts-plugin/

  2. @jbrinley I've been testing on 3.0-trunk for a while now and have yet to run into this issue. I'd be interested in knowing what exactly that output is.

  3. dankind
    Member
    Posted 4 years ago #

    I'm getting the same error trying to activate YARPP, different amount of characters though...

    The plugin generated 876 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin

  4. carll
    Member
    Posted 4 years ago #

    I too got the same error, but with a few less characters though. I did try deactivating it, then reactivating it, and no error the second time.

  5. Thanks for the reports. I've been unable to reproduce this myself. Does it only happen the first time? Did you all install YARPP on top of a clean 3.0, or upgrade a site with YARPP to 3.0?

  6. monove
    Member
    Posted 4 years ago #

    I installed a fresh WP 3.0.
    Installed YARPP 5 mins ago and got the following error during activation:

    The plugin generated 932 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

  7. Hi all, I believe I just figured out what the issue was!

    Please give this new version a try and see if you still get the same error. Any feedback would be appreciated!

    http://downloads.wordpress.org/plugin/yet-another-related-posts-plugin.zip

  8. rokonboss
    Member
    Posted 3 years ago #

    I created a custom plugins. But when its active, then the error show in header……

    “The plugin generated 1 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”

    Why the problem occur….please help….!!!!!!!

  9. @rokonboss, I don't know. It totally depends on the plugin, but if it's one character, you most likely have a space or a return before one of your files' <?php .

  10. SAkErFA
    Member
    Posted 3 years ago #

    Hello, I'm having the same problem

    "The plugin generated 86 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin."

    I tried reinstalling with the version above and the up-to-date version.

    Any ideas?

  11. Jeff
    Member
    Posted 3 years ago #

    I was having the same problem with a plugin I was developing and I was going crazy trying different things to clear it. The issue didn't have anything to do with white space before/after <?php ?>, it ended up being because I was passing in a definition to the "add_option" method. Definition was deprecated beginning with WP 2.3. Removing this cleared things up. So, it may be possible this is the issue with other instances of "unexpected output". It also may be due to some other deprecated method besides the add_option method.

    Good luck!

  12. Thanks Jeff.

Topic Closed

This topic has been closed to new replies.

About this Topic