Hi Tim,
I am now using podpress 8.8.5 beta 14.1 with WP 3.0 on one of my sites. This version of podpress seems to work well with WP 2.9.2 and I bit the bullet and upgraded to WP3.0 (using svn).
After the WP upgrade and deactivating and reactivating podpress I get this message at the top of the admin console:
The plugin generated 2533 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.
So far things look like they are working. I use a feed that is redirected through feedburner into iTunes. If I notice problems with iTunes I will post again but the feed validates and so far so good.
Thanks for supporting this plugin!
-Ray
Thread Starter
ntm
(@ntm)
Hmm … Is this messages occurring each time you de-/reactivate podPress? If this happens each time then please take a look at beginning of the source code of your plugins page after the reactivation. Maybe you can see the original text of the PHP warning which stands probably behind this message of WordPress. The original message is probably helpful tfor the debugging.
In general it might be a good idea to save the settings at each podPress page after an podPress upgrade.
I will probably mark the trunk/-version as stable in the next week.
Yes. I get the same error msg each time I de/re-activate the podpress plugin. I just looked at the source of the page after re-activating and there doesn’t seem to be any extra info:
</div>
<div id="message" class="updated"><p>The plugin generated 2533 characters of <strong>unexpected output</strong> during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.</p>
</div>
There is no change in behavior after saving the settings on each option page. I had “Enable PodPress Statistics” checked so I tried unchecking that also, but no change. Every time I enable the plugin I get the same message on the top of the plugins page in the admin console.
-Ray
FWIW,
I googled this error msg and noticed that some had a similar msg apparently when plugin source files became corrupted. So I deleted the entire podpress dir and did a fresh checkout from the svn trunk. No change – same error msg appears each time I disable/enable the plugin.
-Ray
Here I am again. I really would like to figure out this unexpected output error msg before I use podpress on several production sites. I will create a new thread about it.
Thread Starter
ntm
(@ntm)
Notice: the mentioned other thread is here.
