[Plugin: Yet Another Related Posts Plugin] Unexpected output during activation

I got this too.

No problems in using YARPP though.

No, there’s no reason to actually be concerned about this. I’ve been trying to squash these but it’s very frustrating as WordPress doesn’t actually tell you *what* was printed. Most likely it’s some PHP warnings which can be ignored.

If you could tell me about your PHP version etc. that would be great.

I got the exact same error, too. Having never see that error before, it’s somewhat unnerving, even if it is nothing to be concerned about.

My server runs PHP 5.3.0 and MySQL 5.0.67.

What else do you need to know?

Mitcho, in case my other post has slipped past ?? my installation gives the same error, PHP 5.2.3 MysQL 5.0.37 excpt it generated generated 202 characters. My problem is that the interface works fine (change templates etc.) but it’s not drawing anything from the cache. I’m using the mediamag theme.

I am getting the same exact error with PHP 5.2.4 and MySQL 5.1.48.

Not sure why the status of this topic has been set to ‘resolved’ when the problem is still occurring? I’ve just installed and activated it today (22nd Sept 2010) on a brand spanking new wordpress install and had the following error:

The plugin generated 116 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.

While this particular error may or may not cause any problems, it makes me wonder could there be more errors that we don’t see? I’ve used this plugin on a few sites and don’t recall receiving this error before.

Just installed today and same error as everyone above. 116 characters of unexpected output. Seems to be working, but yes, unnerving.

Michael, on activation I receive the following error output:

[29-Sep-2010 14:33:12] WordPress database error  for query CREATE TABLE IF NOT EXISTS wp_yarpp_keyword_cache (
			ID bigint(20) unsigned NOT NULL default '0',
			body text collate utf8_unicode_ci NOT NULL,
			title text collate utf8_unicode_ci NOT NULL,
			date timestamp NOT NULL default CURRENT_TIMESTAMP,
			PRIMARY KEY  (ID)
			) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci COMMENT='YARPP''s keyword cache table'; made by activate_plugin, do_action, call_user_func_array, yarpp_activate
[29-Sep-2010 14:33:12] WordPress database error  for query CREATE TABLE IF NOT EXISTS wp_yarpp_related_cache (
			reference_ID bigint(20) unsigned NOT NULL default '0',
			ID bigint(20) unsigned NOT NULL default '0',
			score float unsigned NOT NULL default '0',
			date timestamp NOT NULL default CURRENT_TIMESTAMP,
			PRIMARY KEY ( score , date, reference_ID, ID )
			) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; made by activate_plugin, do_action, call_user_func_array, yarpp_activate

Hope that helps.

The plugin generated 116 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.

Any advice on a fix or alternative plugin?

Hello guys,

I had this very same issue. After several minutes of tinkering around, I found that the plugin I am creating outputs that error if I encode the plugin (the plugin being a one-file program) into UTF-8.

If I encode it back to ANSI, the error disappears.

I wish this observation helps the WordPress developers to solve this bug.

Additional update: I am using Notepad++ as my plugin editor, and if I encode the file to UTF-8 without BOM, the unexpected error message goes away as well…

@thenbrent thanks. That’s good to know. Does it tell you what the SQL errors were?
@azureardee so you put the YARPP files in UTF-8 without BOM and that fixed it?