[reedmaven]

1. I did not update the eStore plugin. As stated, I upgraded WordPress from v.2.9.1 to v.2.9.2.

2. I de-activated, then re-activated eStore as suggested, with no change in the malfunction (or more appropriately non-function.)

3. I am using eStore v.2.8.9.1.

4. I have responded to your personal email.

Thanks.

[reedmaven]

Some more information: All of my plugins are current, and are not requesting an update.

[reedmaven]

Just 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.

[reedmaven]

Just an update: most of the visual styling can be accomplished by editing the eMember_style.css file, located in the “css” sub-folder of your eMember installation.

[reedmaven]

This is quite helpful. Thanks, gymgangsta.

[reedmaven]

Thanks. Found it. (I had already opened that file, but missed it the first time round. )

[reedmaven]

I 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.

[reedmaven]

I 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.

[reedmaven]

The email to the customer is configured thus:

==========

Dear {first_name} {last_name}

Thank you for purchasing {product_name}.

==========

This also appears to be configured properly. Any ideas? Thanks.

[reedmaven]

Thanks, Ivy. I checked my email form on the settings page, and it reads:

==========

Dear Seller

This mail is to notify you of a product sale. Product Name: {product_name} Product ID: {product_id}

The sale was made to {first_name} {last_name} ({payer_email})

==========

It appears to be configured correctly, so why do you suppose that the customer’s first and last name were omitted?

[reedmaven]

Nevr mind. I found it! I neglected to look across the very top of the “Settings” page and lo! there it was in the Payment Gateway section. Sorry to have bothered you.

[Author]

Posts