Forum Replies Created
August 6, 2013 at 2:54 pm in reply to: eMember – Secondary Memberships, unique information per membership #56174
Hi, I submitted a request for custom work about a month ago, and never heard a response back. Still interested in this feature… can you suggest how I can get a response? Thanks.June 19, 2013 at 4:42 pm in reply to: eMember – Secondary Memberships, unique information per membership #56172
Thanks for your creativity! And the formbuilder addon looks pretty sweet!
I’m afraid this won’t work for this client though. They need the option to have the client add/change/delete addresses at any time. So, for instance, they might subscribe for a home address today, then a month later decide to subscribe their work… three months later drop the home address and add a vacation home. So the membership records really need to be 1:M with the member record… and, in thinking about it more, the “Active/Inactive” status on the member record would need to be derived from whether or not there are any active memberships.
Is this something you would consider as a customization? Love your software, documentation, and response time! If it’s possible, I’d much rather consider customization than looking for another solution….
Thanks!June 17, 2013 at 11:05 pm in reply to: eMember – Secondary Memberships, unique information per membership #56170
The application provides a remote energetic charging service that is unique to a physical address. Protecting content is not a consideration here. The different address types (home, work, non-profit) each have a different cost associated with them.
1 Home address, 1-year prepay
2 Work address, 1-year prepay
3 Non-profit address, 1-year prepay
4 Home address, ongoing subscription
5 Work address, ongoing subscription
6 Non-profit address, ongoing subscription
It’s possible that one member would want to charge his home address and his business address, for example. Or, his home and vacation home.
After reviewing your database structure, I see that the custom fields occupy a table separate from the member table, and appear to be 1:1 to the member table. It would seem that our app would require a 1:M relationship between member & custom fields… and some additional logic to provide “modify profile” or “cancellation” transactions among several individual address records.
the site is
perhaps that will give a better idea than what I’m able to explain here.
Thanks for your help!
4) When you issue a refund or when a subscription is cancelled, the plugin will automatically block the access privilege of that account and set the account status to “inactive”.
Is this the same effect on the member database as the “Delete Account” shortcode?
Can you point me toward a post or documentation that shows how to issue a refund, in such a manner that it will reverse the affiliate commission as well?