Support

February 22, 2019 at 5:55 am

Hi there,

1. Is there a way to show the respective member price and regular price, only for logged in members? All other (too many) options are just very confusing.

Yes, you’d use the minimum capabiliy setting on the ticket and then we have snippets to remove tickets that aren’t available to the user rather than displaying a message, but… one of your other questions touches on this more so we can address this once everything else is working as expected.

2. Can I take off ‘on sale’ and ‘goes on sale’?

I’m not sure what you mean here, can you add more details

3. Can I only show the relevant tickets according to the sale dates?
3a. Once early-bird is over, can that amount be crossed out with the regular amount shown?

Those are set up as 2 separate tickets, correct? If so, you can hide expired and ‘pending’ tickets, meaning your early bird shows until it expires at which point your ‘regular’ ticket would show up.

I can provide details on how to do that, but is that what you are looking for?

4. Can you please explain ‘ticket capability requirement’ further? I added a separate role for each member option, but I’m not sure how ‘manage options’ plays into that? I have identical roles for ‘student’ and ‘individual member’. When I add ‘student’ to WP User Capability, I get the correct price option, but when I add ‘individual’ or ‘individual member’, I only get the regular price option.

May I ask why you are using ‘manage_options’?

That capability would normally be set on an administrator account, you normally don’t want to to set that on your sites as a requirement.

So you’re currently setting the ‘role’ in that field rather than a capability?

5. I set the limit for the event at ‘Event Datetimes’ and deleted all Quantities in the individual tickets, but every time after updating, the overall limit number shows in each ticket. How can I avoid that?

You can’t, may I ask why you want to remove the limit?

Each ticket can only sell up to a maximum of the overall limit (the datetime limit). You can have a combination of any of those tickts to make the 50 and you can have lower quantities than the datetime limit set on tickets, but not higher.

February 24, 2019 at 3:51 pm

>>You didn’t answer that question below. Please send me those snippets incl instructions on how to use them.

I didn’t say I’d answer that question below, to quote myself:

but… one of your other questions touches on this more so we can address this once everything else is working as expected.

Adding snippets to hide various ticket setups may not work as expected until the settings/capabilities used are correct, so please don’t add snippets to hide tickets based on user capabilities until it’s clear the add-on and capabilities are used as they are expected to be.

>>It doesn’t look like I can upload anything so let me try to explain further:

What would you like to upload? A screenshot? You’ll need to host the image and post the link here, we have some suggestions on how to add screenshots here:

https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots

It sounds like you mean the status legend on the ticket editor, here – https://monosnap.com/file/lW69Q5hWYyfzrzxyyr9lcLOHLJHREu

Hovering over that should show you the current ticket status – https://monosnap.com/file/Yi2rGAiDrIhP2RSynSv5Zf1s4nW3Yf

Is that what you want to change?

1. Can I change the ‘On Sale’ that appears automatically to ‘Early Bird’?

If it’s the location above, then no you can’t change it to ‘Early bird’ as it is the status of each individual ticket to give you (the admin) a quick overview of what your tickets are doing at any given time. So if you have a ‘normal ticket’ that has a status of ‘On Sale’ it would also show (if you changed the above) to ‘Early Bird’ so it wouldn’t make sense for other tickets.

2. If not, can I take it out?

You could use some CSS to hide it it within the admin, however, if you see text rather than the screenshot I added above for that location it sounds like something is interfering with the ticket editor as you should just see a coloured bar, unless you hover over it.

If you can add a screenshot of what you see we can advise further from there.

>>Correct, they are set as different tickets. WHERE can I hide expired and pending tickets?

For expired tickets you can go to:

Event Espresso -> Events -> Templates -> Ticket Selector Template Settings

Set the option ‘Show Expired Tickets?’ to No and save.

For pending tickets you can use some CSS:

.tkt-slctr-tbl .ticket-pending {
    display: none;
}

Add that to Appearance -> Customize -> Additional CSS.

>>I’m not actually using ‘manage_options’ but it’s mentioned in your Add-on documentation (several times) and I have no idea what to make out of that.

manage_options is a capability that gives the user with that capability access to the ‘Settings’ section (and others) of the WP Dashboard. It is set on the ‘administrator’ role by default but no other role.

In short, don’t use that capability on tickets, it’s an example in the documentation as we can’t provide examples of specific capabilities due to the many different ways in which people set up their users capabilities and each use case is different.

>>What capability would be set on an administrator account?

I was referring to the fact that only an administrator would have that manage_options capability on their account, no other role will.

So if you set the ‘Ticket Capability Requirement’ to manage_options it means the only users that would be able to view it are administrators.

I just want to link the correct member to its pricing…

Ok, what plugin are you using to manage your user accounts currently?

You posted above that you want pricing for ‘non-members, students, regular members, corporate members, etc.’

Are non-members logged out members or is that another type of user? As in do they have a user account they log into but aren’t classed as a ‘member’ or just normal public visitors without an account?

The others I’m assuming are different roles on the site, is that correct? If so what are you using to create the roles? S2 Member for example?

>>Yes, it was a try since I don’t know what else ‘WP User Capability’ could be. Your question mark reveals:
“How do I use it? Creating these type of restrictions utilizes the Roles and Capabilities feature of WordPress. In this field, you indicate the capability that a visitor must have as a part of their user profile when logged in and viewing the ticket options. For instance if you have “manage_options” in this field, then the visitor must be logged in and have the “manage_options” capability assigned to their user (or to the role that is assigned to their user).”
How else do I link a member type to its correct pricing?

Ok, I don’t know if you’re familiar with roles and capabilities so here’s a quick explanation.

A role is a collection of capabilities, the role itself is nothing more than a title as it’s the capabilities you get from that role which give you the access. So as an example I could create a user account for you on my site and give you the administrator role, but then edit your account to have ONLY the ‘read’ capability. That would mean that although you have the ‘Administrator’ role, you would only actually have access to what a subscriber would as a subscribe role only give you the read capability.

So in that field your telling EE what capability the current user needs to have to view/purchase that ticket and if they don’t have it, they can’t view the ticket.

You’ve asked how you link a member type to a ticket, but with the info we have can’t give you a definitive answer. You need to set a capability that the user account you want to access the ticket has so they can view it. Problem is, depending on how the role/user account is set up that can differ and depending on the plugin you are using to create/manage those user accounts can differ again.

This also links to my #1 comment and is why I didn’t just hand over snippets as there more to it than just a snippet to ‘fix’ the problem.

It gets a little confusing with WordPress because, at one point, someone thought it was a good idea that checking for a specific role was a good idea and so they’ve had to leave that function in core to keep backwards compatibility. That means you CAN set a role in a capability check and it will work, but its advised you don’t, you should use a capability available on the user account to make sure it continues to work as expected. The only reason I mention it is because you may find some tickets work as you have their role set in the field, but its not the correct method to use.

>>Are you making a WP User Integration Video anytime soon? I doubt I’m the only one with questions.

We don’t have plans to currently, but I can make a note of it to see what we can do.

The reason why we don’t have an in-depth video of this all ties into the above, we make a video that shows how to do it with X and then it’s completely different for every user using Y and it just complicates things more.

EE doesn’t have a set way to do it, as long as you are using capabilities, it will work. The problem is that not everyone is using capabilities as they should and some don’t even know the difference, they just used a plugin as recommended by X post they read which may not even use capabilities at all by default (Paid Memberships Pro is an example of a membership plugin that doesn’t use capabilites).