|
Ying-Fu Li
|
October 21, 2014 at 3:50 am
Hi,
A few smaller questions. I’m rather pressed for time so I’m asking the questions here in one topic so as to resolve them as quickly as possible 😉
– My client organises markets where merchants can hire stands. Is it possible to include stand numbers in an event report or should such a field be added in for instance Excel?
– Does EE work with third-party plugin PrivateContent? Or is there a way to simplify the password generation in the EE Membership add-on? The merchants in question are rather computer illiterate and the password requirements for WordPress users are too steep for them (if it were completely up to them they would do everything on paper and pay cash, the latter which they will do most of the times).
Two rather pressing questions for now. I really appreciate the swift responses on these support forums, a great help!
Regards,
Ying-Fu
|
|
Dean
|
October 21, 2014 at 4:11 am
Hi,
1) If you are referring to the event export rather than the attendee export, then the only way I can think of doing it would be to use a venue as a stand. Other than that you would need to manually add them in.
2) We have no formal integration with that plugin, nor have we tested with it. I assume you are using this code to generate a user at the time of registration: https://gist.github.com/sethshoultes/5574217 ?
If so then you could swap out the $password = wp_generate_password( 12, false ); for something else.
|
|
Ying-Fu Li
|
October 21, 2014 at 4:22 am
Hi Dean,
I use the Membership addon so haven’t had to use the github-code (I guess?). Do I understand correctly that the code you linked to auto-generates a password rather than having the registrant making one up? If so I would rather set that line to ‘true’…?
|
|
Dean
|
October 21, 2014 at 6:04 am
Hi,
The WP Member Integration (members) addon doesn’t generate an actual WordPress user which is why I queried the usage of that code, as that function will create a user when someone registers.
This line
$password = wp_generate_password( 12, false );
is what generates a password, it just uses the WordPress function wp_generate_password.
The “false” bit refers to using special characters ( @£$%& etc) in the password. See here for more info http://codex.wordpress.org/Function_Reference/wp_generate_password
|
|
Ying-Fu Li
|
October 21, 2014 at 6:41 am
Ah, okay (fairly new to this bit)
So, using this code along with the WP Member Integration addon will result in a registration proces that generates a WP user ánd setting it to ‘false’ will require no special characters in the password (so registrants won’t have to make up a difficult password)?
|
|
Dean
|
October 21, 2014 at 7:01 am
That’s right, the function basically creates a use on registration. I did a slightly modified version of it here https://gist.github.com/Apina/9596012 that checks via email rather than name.
The password created by this function will still be something like uHbnGcErlk9f3 even with the special characters set to False.
If you wanted something even simpler (perhaps less secure) you would have to re-code the function to accommodate it. A PHP developer could do it quite quickly depending on what’s needed.
|
|
Ying-Fu Li
|
October 21, 2014 at 7:43 am
Okay, thanks. What would you recommend I’d do? I thought of having the users register per event so to circumvent the need to register as a WP-user, but my client does need the data of every user ánd we want the user to be subsequently able to apply for future events without having to fill out all data anew. Hence also my previous question concerning compatibility with PrivateContent which let’s you register users outside the WP-user system.
Again, thanks for the great support!
|
|
Lorenzo Orlando Caum
|
October 21, 2014 at 8:12 am
Hi,
You could reduce the password requirements further based on your users:
$password = wp_generate_password( 8, false );
The line above would then create an alpha numeric password with no special characters.
Event Espresso does not integrate (no native add-on) with PrivateContent. However, you could do some testing to see if it works.
—
Lorenzo
|
|
Ying-Fu Li
|
October 21, 2014 at 8:25 am
Okay. Yes, I have used PrivateContent on another site: it allows you to restrict access to certain pages/content to registered users. It has a Mailchimp addon for example but who hasn’t these days 😉
I’ll have a go at it. Thanks again!
|
