WordPress.org

1. antorera
   Member
   Posted 3 years ago #
   

   Hello,

   I just moved my wordpress site from the development server to the actual server. It is residing under here.

   However, when I look at the site, I am getting error messages above the site:
   

   Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/content/p/a/s/passionolive/html/wp/wp-content/plugins/nextgen-gallery/lib/rewrite.php:557) in /home/content/p/a/s/passionolive/html/wp/wp-content/plugins/si-contact-form/si-contact-form.php on line 1691
   
   Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/content/p/a/s/passionolive/html/wp/wp-content/plugins/nextgen-gallery/lib/rewrite.php:557) in /home/content/p/a/s/passionolive/html/wp/wp-content/plugins/si-contact-form/si-contact-form.php on line 1691

   Then, when I try to login to the admin, I can't even get the user/password login page. All I get is the same error message as above.

   I tried deleting spaces in the wp-config file but that didn't work. I'm not sure how to identify the problem from here. Is it something to do with the plugins? They work on the development server. I have nextgen installed, but not using it. I think I did leave it activated. Can I just delete the plugin from the FTP client?

   Any advice is greatly appreciated as I am in the middle of launching this site!

   Thanks,
   Antonella

2. antorera
   Member
   Posted 3 years ago #
   

   Okay, I reread the helpful article FAQ support, section on "How do I solve the headers already sent warning...", particularly the part about interpreting the error messages. I was indeed blank lines at the end of the files. I was trying to fix the victim file, but it was the first file that I should have been fixing.

   In addition, once I fixed it, then there were other ones that kept cropping up. So, I went through them all until it got fixed.

   Or, you can also download a new version of the plugin and update the corrupted files. That worked too.

Topic Closed

This topic has been closed to new replies.