[woodwardmatt]

Awesome! Thank you very much, that’s a great response time

Cheers, Matt

[woodwardmatt]

Excellent, thanks for the update nur! Any initial thoughts on timescales?

Cheers, Matt

PS: Loving your support team, excellent work!

[woodwardmatt]

**ignore** – duplicate post

[woodwardmatt]

Ahh ok, thanks for the help

[woodwardmatt]

For anyone stuck with this issue at the moment, the following SQL statement will reformat your existing users within the WP database:

UPDATE wp_users SET user_nicename = REPLACE(LCASE(user_nicename),' ','-');

[woodwardmatt]

I’ve just had my expiry email through at 15:45 having set the Timezone to Australia/Adelaide. Not sure if that’s quite right or not but hey it came through so its a good start

I did spot that the {first_name} and {last_name} codes are not being replaced however. The codes have not been altered in anyway and I have had initial registration emails with information replaced correctly. Any thoughts on why this would not work for the expiry email?

[woodwardmatt]

Excellent! Thank you very much I’ll just give it a whirl and see how it turns out!

Matt

[woodwardmatt]

Ahh great thanks for the extra info Which file would I need to change if I wanted to change the time the reminder went out?

E.g. The client site is hosted in Canada but is for a membership base in Australia. I’m just trying to figure out which clock will be used for the timing of the email.

[woodwardmatt]

In the end I have used the primary key for this and just used the member_id property for use on the site. In the instance the client hadn’t used their membership number anywhere to prominent for this to be an issue.

Going forward I can see a legitimate business case for this though. Imagine a client where they had a few thousand members and had printed membership cards etc. already. Not being able to have an arbitrary membership number as part of the plugin would be a bit of a feature gap.

I’d foresee the following requirements:

– Read-only membership number for the user

– Membership number auto-creation based on a defined set of rules (may not always be numeric) defined in the settings

E.g. Length of “X” – Where X is an integer representing Length

Format of “AAXXXAXX” – Where A is alphabetic and X is a numeric, and the format is user-defined

Option of “Sequential” or “Random” for generating new membership numbers

Option to pad numeric membership numbers with leading zero’s

Option of providing a “seed” i.e. the point where the membership numbers should begin from e.g. I have already used up to 4550, so my next member should be 4551

My thinking is that the primary key is really for database use, not for membership numbers. Hopefully some of the ideas above show where the differences lie.

I’ll keep my fingers crossed that this gets considered! I kinda see it as a bit of a fundamental part of a membership system / platform.

Otherwise thanks for the awesome work, really impressed with the plugin

[woodwardmatt]

Hey there,

Sorry perhaps I should have been a little more specific. When I say Member Number, I am not referring to the “User ID” which acts as the primary key for the member list. I was more so querying if there was a concept of a “Membership Number” field that could be managed solely by the WP-site administrators and that the Member could only view (envisage the concept of a membership number on a member’s card).

The current member list (that i’m importing) essentially has a “membership number” meta data field, which I was hoping I could incorporate into the eMember member list – but on first glance the only way I can foresee of doing this is using a custom field – however the member could then edit this which is not desirable.

I can appreciate this facility may not be in the plugin at the moment, I was just looking for confirmation that I wasn’t missing anything?

Many thanks, Matt

[Author]

Posts