Support

November 13, 2018 at 3:39 am

Hi there,

By the term “member”, does this means a visitor needs a WP account to view tickets?

Yes, for the WP User integration add-on to work you need your ‘members’ to log in.

From what I’ve read, I must add certain codes to my tickets under “Ticket Capability Requirement”. The only one described in the EE4 WP User Integration usage section is “read” capability. All I’m getting from this is that it gives a visitor the basic WP-Subscriber role and they will then have to have a WP account to see the tickets. How can I display non-member pricing?

You add a capability to the ticket that the users (the ‘member’) have on their account. If the user has that capability, that can purchase the ticket, if they do not, they can not.

Logged out visitors have no capabilities at all.

Note that by default within WordPress every user role has the ‘read’ capability, so using that does not just give subscribers access to the ticket.

Most who register for our events will not have a WP account. However, most will already be “members” of our professional society and will be paying member-only pricing

They can’t use ‘member’ pricing without an account, or at least, you can’t limit the member tickets to only members without requiring accounts.

The only way we can differentiate a ‘member’ from a ‘non-member’ is by their WP User account, EE has no way to know if a normal, logged out visitor is a member or not.

How do I set these tickets to show non-member pricing, and then require a login to show member pricing?

You would need 2 ‘sets’ of tickets.

The first set would be the normal ticket prices, the second would be the ‘member prices’, but you’ll still need a user account for the user to be able to use those.

Before trying to work out a way to set this up for you, I’m a little confused by this:

Our society members are also logging into our website (www.sawe.org) so maybe there is a way to integrate that login into the WP Event Espresso event pages.

Your members are logged into the site? Above you mentioned that the society members do not have WP User accounts, but then above they appear to be logging into the site?

I’m not sure what to do with these settings:
Forced login for registrations (yes/no)
Auto-create users with registrations (yes/no)

We’ll come back to this shortly, it depends on the above.

—-

In short, to use the WP User integration add-on to give ‘member’ (logged in users) and ‘non-member’ (logged out users) pricing, your members need a WP User account.

How are you wanting member pricing to work?

Do all of your ‘members’ have an account they can log onto the site with?

November 15, 2018 at 9:46 am

None that I know of as they are two separate systems.

In order to offer hidden ‘member’ pricing using EE, you society members will need to log into the WP site.

November 16, 2018 at 8:47 am

OK – How would I get this started?

You’re basically going to need 2 ‘sets’ of tickets that you have now.

One ‘set’ being the public pricing without a ‘minimum capability’ set on the tickets and another set with member pricing that does have a minimum capability set (that can be just ‘read’ for logged in users, if you want even finer control you can use custom capabilities and membership plugin capabilities, it really depends on how much control you want.

Event Espresso will show both sets to each group of people by default:

Logged in users would see both the member and non-member tickets

Logged out users would see the non-member tickets and then the member tickets would show as ‘member only’ (like they do now – http://take.ms/JJ8UP)

However we have a snippet you can use to prevent that and only display the one ‘set’ of tickets to the relevant visitor if you prefer that.

Also, our Drupal based website has a CiviCRM database to manage our society membership, primarily for dues and fees. Is there a way to import or integrate this existing CiviCRM database to the WordPress site?

Possible, yes, however I’m not familiar with CiviCRM so can’t help with this and its outside the scope of support for Event Espresso. You would need to find a developer familiar with both Civi and WordPress to help import your Civi contacts into WordPress. (If you then have both the Durpl site and WordPress site using the contacts from Civi your going to also need a method to keep those in sync).