[kmbradley]

Thanks for the info. I’ve purchased eStore and am testing various situations. Everything seems to work, except when an existing free emember upgrades their existing account, and the email address on the account is different than the Pay Pal email. The process works, and the emember account membership level was changed. However, the system sends the email to the PayPal account email not the emember email. Is this the way it’s supposed to work, or have I missed a setting somewhere? Could the code (or API) be modified to sent the email to the emember address?

Thanks,

Karen

[kmbradley]

Hello support,

I’m going to purchase eStore and change my payment buttons from Plain Pay Pal buttons to to eStore buttons. I will have a Subscribe and a Buy now buttons for different membership levels. When an existing free member wants to upgrade to a paid membership, do I need to have a separate button for upgrading, or can the member use the same Subscribe button that is displayed for a new member.

thanks,

Karen

[kmbradley]

Yes, the error messages work with the standard login form. How do I evoke them with the fancy login? I’m using the [wp_eMember_compact_login] shortcode in a widget.

Thanks, Karen

[kmbradley]

I have a similar problem. We converted over 1000 existing members from another database to an eMember database. This worked great. All members were converted as “free” members. Now the “free” members want to upgrade to a “subscriber’ membership level using a Plain Pay Pal Button. The member’s email address is different that the Pay Pal email. The plugin added a new record to the database with no username and the first name and last name and email address on the PayPal account. Now there are 2 records on the emember database for the same person with different information.

I don’t know how to correct the issue with 2 records for the same person. The membership level is for a recurring subscription. PayPal only knows about the record with the PayPal email address. The member doesn’t want to use the PayPal email address for their ember account. Do we have to delete both records and start over?

Although there is documentation for How to create Payment Buttons for Membership Upgrade or renewal, I failed to notice the difference in the text between Option A – Plain Pay Pal Button and Option B –Using an eStore button for membership. I never looked at the eStore option because I wasn’t interested in have a “Store”.

Do I need to purchase eStore in order to fix this situation? How will estore affect my existing website and databases? Can I receive a “bundled” price since I’ve already purchased eMember?

Thanks for your help.

[kmbradley]

Hello Support,

The CVS file had blanks in the file name. This won’t work in PHP. Now I have error messages, so I think I’ll be able to solve my problem.

Karen

[kmbradley]

It sounds like you have made changes to the password field and added a confirm password field. How is this supposed to work?

A few days ago, I deleted the emember databases and reinstalled the plugin. On the “update member profile” page, a password field and a retype the password word field are displayed with nothing in the fields. These fields are required and the user must enter their password and confirm it to change their profile. This is very inconvenient for the user. Is this the way the system works now?

From reading the previous posts in this thread, it sounds like there are supposed to be “dots” in the password field. That’s what I remember from the previous version. Is my version working correctly?

Thanks,

Karen

[kmbradley]

I’m having a problem with required fields and custom fields. Recently the custom field requirements changed for my project. I deleted the custom fields, all the members that were already in the database and all the entries in the wp_wp_members_meta_table. I then added 25 new custom fields. To check the required fields, I entered a user name and password on the registration page, and then clicked update, the screen changed to an Internal Server Error 500, but the member was added to the database with no data. All the required fields were blank, including the emember fields that are supplied with the plugin.

Then I added 2 new members and fill out some, but not all of the required fields. I did not get an Internal Server Error 500. The member is added to the database, but no “required field” messages ever appear for either the required default fields and the custom fields.

The required message processing worked before I deleted and added new custom fields. I’m not sure what’s happening. Can you help? I’m not sure where to look to solve the problem.

Thanks,

Karen

[kmbradley]

OKay, thanks. An option would be helpful.

[Author]

Posts