iBlogPro breaks admin login after upgrade to WP 3.0.5

[aeverse 0]

Hi, I upgraded to WP 3.0.5 last night, and since then haven been unable to log in at my usual http://mysite.com/wp-login.php location. The site is still functioning on the front-end/user perspective, and I could access my files via ftp. First, I thought that perhaps it was a conflict with a plugin. However, if I deactivate plugins (by renaming the folder via ftp), nothing improves. If I rename the iBlogPro theme, WordPress defaults to the TwentyTen theme, and I can log in again. So, I turned on wp-debug in wp-config.php and now I get this clue as to what is going on: Warning: Cannot modify header information - headers already sent by (output started at /home/xyz/public_html/xyz/wp-content/themes/iblogpro/functions.php:31) in /home/xyz/public_html/xyz/wp-login.php on line 337 Warning: Cannot modify header information - headers already sent by (output started at /home/xyz/public_html/xyz/wp-content/themes/iblogpro/functions.php:31) in /home/swimmy/public_html/wp-dev/wp-login.php on line 349 What is completely bizarre is that with debugging on, I can log in at /wp-admin/ -- but not at wp-login.php. And when I log out, I get the same errors above, plus this one: Warning: Cannot modify header information - headers already sent by (output started at /home/xyz/public_html/xyz/wp-content/themes/iblogpro/functions.php:31) in /home/xyz/public_html/xyz/wp-includes/pluggable.php on line 717 Can anyone give me a clue as to what could be going on and how to fix it?

[bryan-hadaway 3]

Okay, marking for developer review. Thanks, Bryan

[Andrew 207]

which version of iBlogPro are you on?

[aeverse 0]

I'm using iBlogPro 4.2.4

[cmunns 16]

Well assuming you have all your information backed up you could restore your iblogPro settings back to default and I'm sure that would fix it, but generally speaking upgrading to most recent version of WordPress is never a good idea right off the bat because the likelihood of theme and plugin developers having tested for the arrival of a surprise WP version is low until at least a few weeks have passed.