Support

August 25, 2021 at 4:46 am

Strange, that’s definitely the same page I’m viewing and the ticket selector shows the register now button for me.

Have you checked another browser? Or, try clearing the cache on your current browser and refresh.

To hide the sidebar on the single event output you can use this CSS:

.single-espresso_events .content .content-column {
    width: 100%;
}
.single-espresso_events .sidebar {
    display: none;
}

August 25, 2021 at 6:45 am

So perhaps this plugin is not complatible with Firefox? Moving on….

Event Espresso is compatible with Firefox although it aggressively caches responses, the above isn’t an issue specifically from EE.

1) So while I no longer see the sidebar, which is great, is there any way you know of to make this actually full screen, not just hiding the sidebar?

The selector in my last reply sets the width to be 100%, you have an addition . at the beginning of that selector which is stopping it from working, remove that so its just:

.single-espresso_events .content .content-column {
    width: 100%;
}

The other option for setting the event page not to display a sidebar needs a custom template for your theme which can then be loaded for EE events without loading the sidebar at all rather than hiding it.

If your theme already loads a full page template you can set it on the event itself in the ‘Page Template’ option (side bar of the event editor).

2) When I click on ‘Show Details’ for this Event it opens up and shows BOTH an ‘Access’ listing as well as a second listing of the event time/dates and for simplicity I’d only like one of these to show up.

We don’t have an option to display each specific section, you can hide them using CSS or disable the ticket details completely.

To hide a section use:

/* Hide sale dates */
.tckt-slctr-tkt-sale-dates-sctn {
    display: none;
}

Or:

/* Hide access section */
.tckt-slctr-tkt-datetimes-sctn {
    display: none;
}

To remove the ticket details completely go to Event Espresso -> Events -> Templates -> Ticket Selector Template Settings (Bottom of the page)

Set ‘Show Ticket Details’ to No and save.

August 26, 2021 at 9:39 am

1) One time slot keeps repeating on the day it is scheduled. It also shows up one more time on that day with every week that you view. I can’t figure out why this is doing this! Screenshot;

Have you removed that screenshot? It goes to a 404 page currently.

and screenshot here of where it appears with arrow pointing to where I WANT it to appear. Right now there is this floating word “Description’ and I don’t want the floating word with no content.

Apologies but I don’t follow this.

Have you added some details into the ticket description? If so those should be showing in the section you highlighted, right below the ‘Description’ heading.

August 31, 2021 at 10:08 am

Ah, ok, my apologies.

That section does not show the ticket description, it shows the description for any price modifiers attached to the ticket itself (which you don’t have). The description for the ticket is displaying correctly above that table and as you don’t have any price modifiers on your tickets you could hide that description field using some CSS:

.tckt-slctr-tkt-details-tbl thead tr th:nth-child(2) {
    visibility: hidden;
}

I had made a couple of test registrations to try things out and now I would like to delete them EE is telling me I can’t delete them because there is a payment attached to the registration and that I need to delete the payments before I can delete the registration. Do you know how I am to do this?

When you have payment objects assigned to a registration EE won’t allow you to remove the registration, so you first need to delete those within the transaction.

To do that, fid the Registration(s) in Event Espresso -> Registrations.

For example, here’s one of mine:
https://monosnap.com/file/RVyDlULVpqQ9AOjvkUweLb6ft3CAVV

Click on the TXN Date field to show the EE Transaction:
https://monosnap.com/file/h1qq5mOqkLWYT7eVVtAxEpM8qIDhuu

Once the payments have been removed the padlock will be removed and you can trash them:
https://monosnap.com/file/D8fed7q6W7QbfV0uswuXhNup7zAPGM

September 14, 2021 at 3:05 am

No problem and your most welcome 🙂

Threads stay open for 2 weeks from the last reply date and then they automatically close. However, we can always reopen them if needed so if this closes just start another and if we need to re-open and merge the new thread into here we can although we may just continue in the new thread.

September 21, 2021 at 7:12 am

Error 503 basically means the server is not ready to handle the request you just sent to it, usually because it’s doing too much at once so the usual answer is to upgrade your hosting so it can handle more traffic… but it depends on multiple different factors.

What hosting plan are you using with GoDaddy currently?

When I contacted GoDaddy again to see about ‘buying more resources’, they then told me it was a plugin issue and I needed to set up/enable an Error log in WordPress to determine the plugin error.

Yep, as mentioned earlier… it is always a plugin issue 🙂

Error 503 is a server-side error, as mentioned above it means your server can’t keep up with the load it’s been placed under.

Could that be caused by a plugin? Sure!

Are you likely to get any helpful information from Error logging? Probably not.

You’ll get a bunch of errors from the site trying to do things whilst the server can’t keep up, but thats not really going to help find the cause. To give a mental image of this, if I simply throw 200 books at you and tell you to catch them it’s likely most, if not all, will fall on the floor (Error 503). Now you take a picture of all of those books on the floor (logging) and you can see there are 200 books on the floor…. but what did you have in your hands when I threw those books at you? What prevented you from catching them? That picture doesn’t help tell you that at all and it’s why “it’s a plugin issue and you need to enable logging” simply doesn’t help.

Is it likely Event Espresso causing the error? ‘Yes’, but because your server can’t keep up with the requests. But which requests and what part of those requests? Your WPDEBUG error logging can’t tell you, only the server can.

If you are wanting to stay with GoDaddy, you will likely need to upgrade your account with them (it depends on what you have now). 50 ‘visitors’ at once isn’t all that taxing on the server, 50 e-commerce transactions (like EE event registrations) can be as it is much heavier on the database than a ‘static’ request and it’s going to depend on their packages and how they have the servers set up as to what you need.

September 24, 2021 at 6:30 am

Thank you for the feedback 🙂

With regards to switching up to a Business plan being a sales pitch, it is but also likely correct for their servers. It’s going to depend on how their servers are set up as to how many visitors you’ll be able to serve at once with EE.

The problem is there are big differences between ‘A WordPress Site’ and ‘A WordPress site running e-Commerce’ (such as Event Espresso) in terms of load on the server. So when the likes of GoDaddy set up a cheap hosting package stating it’s for ‘A WordPress Site’, it is, but it won’t cover everything WordPress can do.

A static site set up using WordPress, with caching enabled where possible, can squeeze a lot of traffic from few resources. e-Commerce sits can’t do the same because of how they work with a lot of requests being totally unique to the specific visitor (meaning caching is out) and a lot more database usage.

Unfortunately, you aren’t going to know if the server can handle the traffic hitting your site until you have that traffic hitting the site and your host would normally work with your to adjust your package to something suitable. With GoDaddy the business package is likely what they would recommend.

Are you set on sticking with GoDaddy?

September 27, 2021 at 5:33 am

We don’t recommend any specific hosts as there are just so many variables to consider.

For me personally, a VPS and manage it myself but it’s not everyone’s cup of tea.

For clients, I’d use a managed service (with pretty much anyone but GoDaddy 🙂 ) so I’m not fixing something critical at 2 am.

We have a few users on here using Bluehost and when issues come up Bluehost support have been responsive.

September 30, 2021 at 5:18 am

The short answer is I can’t answer you.

The numbers they give you (2 CPUs and 1GB of memory on a shared server) aren’t the whole story so the only way you’ll know is to try it.

2 CPUs and 1GB of ram is more than enough to run Event Espresso but those numbers are mainly marketing when it comes to a shared server, yes the server will handle more traffic but how much I can’t tell you.

How many database connections are you allowed? (You don’t know)

How many other users are on that server and how close is the server to having its resources fully utilized? (You don’t know and they wont tell you)

You’ll only know if the hosting package you currently have (or are about to update to) will work for your traffic when you are using that package. Should it work based on the values they’ve given, sure, but unfortunately that doesn’t mean it will. If it’s the same server they’ve just bumped the resources mentioned up, then it will likely do the same as before.

Personally, I would most likely switch away from GoDaddy (in your case to BlueHost) but I can’t force/tell you to do that.

September 30, 2021 at 10:55 am

Thank you 🙂

I’m sorry I can’t give you a definitive answer though, wish I could.

October 13, 2021 at 6:39 am

I am wondering if there if I post my Events with a ‘Sale Begins on Date’ of a date in the future, will that prevent people from registering early?

Yes, if all of your tickets have a ‘Sale Starts’ date set into the future then no-one will be able to register until that specific date/time.

So something like this:

https://monosnap.com/file/GsxH5Kra8wSBwaIUj5BnZ6kDyEdISX

Will show like this:

https://monosnap.com/file/sij0i9Y34QASUwStPBBZBchaRZGDLs

Until Decembet 1st 2021 when the tickets will go on sale.

You also have the option of setting the ‘Display Ticket Selector’ option to No on the event (its in the ‘Event Registration Options’ metabox when editing an event) that will completely remove the ticket selector from the event. However, note that if you do that you need to edit each event and enable it again to allow registrations on that event.

October 21, 2021 at 8:55 am

Currently not, those types of events are something we don’t have a specific setup for currently, however what you can do if you are just suing a single datetime for this is set the date for some time in the distant future to keep the event going.

Then use some CSS to hide the dates (and times) on the event itself.

If you link me to the event in question I can give you the CSS to do that.

October 21, 2021 at 9:41 am

This:

#ee-event-datetimes-li-219 span,
#ee-event-datetimes-li-219 br,
#download-iCal-frm-219 {
    display: none;
}

Will hide the dates, times and iCal download for that specific event which I think is what you’re looking for.

October 22, 2021 at 3:15 am

Awesome, glad it helped 🙂

October 26, 2021 at 5:03 am

My issue is I got a critical error that said my php was not up to date

A critical error from where? What showed that message?

Your server is running PHP 7.4.24 which is fine for Event Espresso.

(Note – You can find that in Event Espresso -> Maintenance -> System information.
Search for php_version and it should show the current version number.)

Well now it turns out that in running the Combability checker it is STUCK on scan…

Looks like that scan is for PHP7.0, your using 7.4 (which the plugin doesn’t have a scan for). Compatability plugins are great and all but its really difficult for them (the plugin) to know the full story based on the code it finds in the plugin alone (which is what the plugin is trying to say with these 2 lines:

This tool cannot detect unused code paths that might be used for backwards compatibility, potentially showing false positives. We maintain a whitelist of plugins that can cause false positives.
This tool does not execute your theme or plugin code, so it cannot detect runtime compatibility issues.

Have you run into PHP issues on the new site?

If it were me I’d disable that plugin for now, if you aren’t running into issues you don’t need it as it stands.

I guess at this point I just cross my fingers and hope for the best

Unfortunately, I was unavailable yesterday so didn’t see this until now, just letting you know that I wasn’t ignoring you.

While my site has not crashed (yay) Registrations feels very messy as it is 🙁

May I ask why that feels messy?

In short, what is happening there is people (or possibly bots but we’ll get to that shortly) are posting submissions on the ticket selector (selecting a ticket qty and clicking to submit) and EE is creating registrations in the background waiting to update them as then step through the registration process.

I have one event that has been moved to SOLD OUT status. I had 7 tickets available, ONE sold and is complete and there are 6 listed under Reserved. I don’t see these “reserved” registrations anywhere and wondering why that would affect the Sold Out status?

Registrations are placed in reserve to prevent overselling and EE holds registrations in reserve for the duration of the user session (by default thats 1 hour) where they should then ‘release’ back to be available for sale.

For example lets say we didn’t do the above and you had say 2 tickets on an event. User A selects the tickets adds their registrant details and stops on the payment details page for a couple of minutes to go find their card to pay. In the meantime User B comes along and selects those same 2 tickets and steps throughout the checkout, they have their card details saved and proceed through the checkout. Effectively swiping the tickets from User A without them knowing.

User A returns, is already on the payment options step and submits their card details to complete payment… what course of action does EE take?

Oversell the event and allow User A to complete payment or somehow reject the payment right before it is processed (which isn’t as simple as it sounds if using an offsite payment method like PayPal Express or Stripe)?

Neither are a good experience for the admin or the user(s).

So with the above, User A select those 2 tickets and they are placed in reserve, the reserved tickets temporarily count towards your sold values, which prevents User B from swiping the tickets in the above. If User A continues with the payment, those tickets are allocated to them and all is normal, if they do not 1 hour(ish) later User B can try to purchase those tickets in the same way as before.

—

With regards to bots submitting your ticket selector (bots will basically submit any form they find on your site), one option is to set up reCaptacha on the ticket selector.

Go to Event Espresso -> Registration Form -> reCAPTCHA Anti-spam Settings

There you’ll see a link that takes you to Google reCaptcha to create a key, I recommend using reCaptch v2 and selecting Invisible. Add the keys in your settings and enable reCaptcha.

That should reduce the number of bot submissions.

October 26, 2021 at 11:29 am

The ‘critical error’ is showing up on my WP dashboard>Site Health status.

Ahh, ok. I thought you meant a PHP critical error.

So, the first thing that comes to mind with this is Event Espresso uses sessions and did used to throw this error in site health, however, whilst we do still use sessions, we fixed the code to prevent the above issue.

We did that a while back and I double-checked on a couple of test sites to confirm that is still fixed, so I’m guessing that error is coming from another plugin using sessions.

Regarding your question; ‘Have you run into php issues on the new site?’ my question back to you is ‘how would one know if they were?’

In short, ‘things’ would break.

Features on your site wouldn’t work as you expect them to. The session issue (even when being thrown by Event Espresso itself) didn’t cause any issues that we could find at all but it depends on what the code is doing.

This feels scary to me to do this while the scan is stuck and in all of the forums and advice I read no one ever mentioned doing this.

The code that would be running the scan will no longer be available, so it shouldn’t cause any issues.

Do Bluehost have a backup solution? If so, create a backup, disable the plugin and if there’s and issue revert to the backup, if not (you’ll know pretty quickly as if there’s an issue it will likely throw a fatal error) then all is good.

October 26, 2021 at 12:35 pm

So, just to update this thread with my findings. I downloaded the plugin, activated the plugin and started a scan.

Then in another window I deactivated the plugin whilst is was still ‘scanning’. No issues on my sites.

October 26, 2021 at 1:13 pm

Check your server error logs, there should be a log for that error.

Post that here and I may be able to tell you what the problem is.