Tips and Tricks HQ Support Portal › Forums › WP eMember › WP eMember Troubleshooting › Error Message When Logging in to WordPress
- This topic has 4 replies, 2 voices, and was last updated 14 years, 10 months ago by reedmaven.
-
AuthorPosts
-
February 8, 2010 at 11:26 am #757reedmavenMember
I receive this message now when logging in to WordPress as Admin. (I have substituted “…” for some path information):
==========
Warning: Cannot modify header information – headers already sent by (output started at /…/…/public_html/wp/wp-content/plugins/wp-eMember/emember_general_settings.php:1) in /…/…/public_html/wp/wp-includes/functions.php on line 790
Warning: Cannot modify header information – headers already sent by (output started at /…/…/public_html/wp/wp-content/plugins/wp-eMember/emember_general_settings.php:1) in /…/…/public_html/wp/wp-includes/functions.php on line 791
==========
What does this mean? Should I be worried about a corrupted file? Or is there a modification which I can make to correct this? It is very disconcerting, as I have just switched to WordPress, coupled with your plugins, for my store for stability and ease of maintenance. Any help would be greatly appreciated.
February 8, 2010 at 11:56 am #17829reedmavenMemberI have looked at the functions.php file, and lines 790 and 791 are as follows:
==========
setcookie( ‘wp-settings-‘ . $user->ID, $settings, time() + 31536000, SITECOOKIEPATH );
setcookie( ‘wp-settings-time-‘ . $user->ID, time(), time() + 31536000, SITECOOKIEPATH );
==========
So, is there a setting within wpMember that requires my attention, insofar as cookies are concerned?
Thanks for any help.
February 8, 2010 at 12:17 pm #17830reedmavenMemberI also received the following when logged in as site Admin after updating a page file:
==========
Warning: Cannot modify header information – headers already sent by (output started at /…/…/public_html/wp/wp-content/plugins/wp-eMember/emember_general_settings.php:1) in /…/…/public_html/wp/wp-includes/pluggable.php on line 868
==========
This was presented on a blank(!) page, as though the Dashbord/backend no longer existed; but when using the back button on my browser, the updated information was present and the small changes to the file were included.
I investigated line 868, and here are the lines 865 through 868:
==========
} else {
if ( php_sapi_name() != ‘cgi-fcgi’ )
status_header($status); // This causes problems on IIS and some FastCGI setups
header(“Location: $location”, true, $status);
}
==========
Hope that this helps you decipher what is going on. For what it’s worth, I am on shared hosting with Bluehost.com, which is Linux-based (I think the kernal is v.2.6.31-12.9), running mySql v.5.1.41, php v.5.2.11. I generally use Firefox v.3.5.7.
February 8, 2010 at 1:04 pm #17831amin007ParticipantYou shouldn’t receive any error message. I will need to take a look at your site to see why this is happening. I have sent you an email.
February 11, 2010 at 11:31 am #17832reedmavenMemberJust an update.
Problem: It turns out that the problem was caused by certain files which had been transferred unintentionally in a non-Unix format, and for some reason my server’s setup was not dealing with the issue very well.
Solution: I re-transferred all of the files in “binary” format, instead of letting my FTP program (Filezilla) decide whether each file’s format was ASCII or binary.
Result: No further error messages, so far, for the past few days. Thanks to amin007 for pointing me in the right direction.
-
AuthorPosts
- You must be logged in to reply to this topic.