Support

Home Forums Event Espresso Premium More bugs discovered with EE4

More bugs discovered with EE4

Posted: May 30, 2014 at 2:23 am


gbox

May 30, 2014 at 2:23 am

Hi,

I like some of the new features of EE4 but my installation does not seem as stable as EE3 was. Not sure if the issue is to do with migrated events from EE3 as I’ve only added one new event since upgrading and it’s too early to tell if the problems I’m experiencing would also occur with newly added events.

Here’s my latest problem.

As reported on another support ticket I raised events that are sold out but are due to occur in the future don’t show on the calendar (but do on the event list). I’ve been assured they should and to check the event dates to make sure they are in the future (which they are).

Today I had 2 cancellations for an event next weekend. I noticed that you cannot simply delete registrations like you could in EE3 as it sees that it is locked to a registration. However it seems you can mark a partial or full refund against a cancellation and change the status to cancelled. Once I have cancelled these 2 registrations the event shows the new registration total of 16 correctly and but still shows the event status as ‘sold out’ when I would expect it to allow 2 tickets to sell. Indeed if you go to the direct link for the event it will allow you to purchase 2 tickets so why does the status you see if you click edit event show ‘sold out’? Also even though 2 tickets are available the fact status is still showing ‘sold out’ means it still does not show in the calendar. This is a huge problem as people casually looking at the calendar will assume no such event exists! Please fix this. I don’t mind adding you as a user to look more deeply at my installation.

Also to anyone reading this who has also upgraded can you suggest how you are now dealing with waiting lists? It’s the only real feature of EE3 I miss as I used it to re-sell spaces when I get cancellations like this morning and I’m not sure how I am going to capture those interested in a waiting list going forward.

Thanks
Gary


gbox

May 30, 2014 at 6:41 am

Hi,

Beginning to think EE4 was rushed out with little testing. Having major problems which is impacting my business. I’ve had 3 cancellations for an event next weekend and made partial refunds as per my booking conditions. I have people wanting these 3 spaces but they cannot register as the trip shows ‘sold out’.

Interestingly the event status shows sold out even though ticket limit is 18 and sold shows 15. If I try and visit the event link while I’m logged in I seem to be able to buy a ticket whereas if you log out of your wordpress admin it shows ‘sold out’. I’m beginning to wish I had not upgraded as the one new feature I actually wanted is not worth the amount of bugs I’m finding which is causing huge problems and time in manual work arounds.

Can someone PLEASE assist?

Gary


Tony

  • Support Staff

May 30, 2014 at 7:02 am

Hi gbox,

Could you create a user within your site for us to look into this please?

Please send log in details via https://eventespresso.com/send-login-details/

I can assure you EE4 was and still is rigorously tested through multiple stages, within multiple different test sites with each release. However with the vast amount of plugins and themes available for WordPress we can not test each and every combination of those so unfortunately some issues are to be expected although we will (if we can) address those as quickly as possible.

Once we’ve taken a look at the site we can investigate further to resolve this issue.


gbox

May 30, 2014 at 7:22 am

Hi,

I’ll send login details now but all I can say is I’m very tired of so many bugs. I use genesis themes which are probably the most popular and respected within WordPress. In the past when I’ve found issues it was never found to be due to another plugin but an event espresso issue. I’d not raised any issues for ages because EE3 finally seemed stable. EE4 is full of issues and I’m far from a complex user. I don’t use many fancy features and no addons. I also only use Paypal as a gateway. Despite keeping my business as simple as possible I’m finding customers complaining about our website since the upgrade. Indeed I’ve manually added someone to the event that is incorrectly showing as sold out which generated an email to them but still it will not allow them to pay! I can forward you their email to me if you like.

I’m also getting display problems that I used to get in EE3 where the register button is barely visible.

Gary


Tony

  • Support Staff

May 30, 2014 at 8:47 am

Hi Gary,

Your event should now be fixed.

To explain what happened, EE4 will automatically change the status of an event to ‘Sold Out’ when the ‘Sold’ value reaches the ‘Limit’ value set on the Datetime.

If you then cancel a Registration the Sold value will drop below the Limit value and EE will automatically update the event status to ‘Upcoming’ once again, unless the event has been updated in the meantime by yourself (or any admin).

EE will consider user actions as absolute, so if an event is set as Sold out by EE and then that event is updated manually, the Sold out status is considered ‘final’ as it is a user action.

So then when the Registration was removed/cancelled the Sold value change, but the user action still overrides this. So then once the new values are set (Sold vs Limit) the event must be updated. This then triggers EE to change those values and set the Correct status based upon that.

This is not a bug within EE4 but is actually expected behaviour. As an example say your event is in high demand, but you are informed that your venue has over estimated and you need to remove 10 registrations, if EE updated the status automatically regardless these could be filled as are removing them from the event. The feature above stops those issues.

We have an open ticket for the Calendar issues mentioned within the email and are currently investigating this.

In regards to the register button, I assume you are referring to to black on black colour in use within the Submit button? Here – http://take.ms/pdfvE

Is so this is actually being cause my some styling you are applying within the My Custom CSS plugin:

input[type="button"], input[type="reset"], input[type="submit"], .button, .entry-content .button {
color: #000;
}

Which is setting the font color of those buttons to black, removing that style applies the theme default styling (white) which looks like this: http://take.ms/y3q25

Does that help?


gbox

May 31, 2014 at 2:10 am

Hi Tony,

Ok good news that you think that once the sold value is less than the limit value the event should revert back to upcoming and hopefully allow people to buy the cancelled tickets. What I don’t understand is what user action I’ve done to prevent this. Maybe I’ll explain the sequence of events for this particular event and you can then explain where I’ve gone wrong and the correct way to handle it.

The event was created in EE3 and migrated to EE4 when I upgraded this week. It was already sold out prior to upgrading. After upgrading I was informed of 3 cancellations. In EE3 I would have simply deleted the registrations to free up places. I keep a separate spreadsheet for each event for accounting purposes so did not worry about deleting registrations linked to payments as the still appear in my PayPal account.

As you know in EE4 you cannot delete a registration linked to a payment. What I did was mark these registrations as refunded and entered the partial refund given as per booking conditions. This seemed to have the effect of reducing the sold spaces but did not change event status to upcoming.

Perhaps therefore you can explain step by step how in EE4 you free up places and obtain a upcoming status when someone advises you they want to cancel? If I’m doing it wrong it’s not clear the right way to do it.

On the register button issue I’ll remove that code. It was added on your instructions because of styling problems in EE3 which it seems don’t exist in EE4.

I also look forward to hearing about the other outstanding issues I have with the calendar.

Thanks
Gary


gbox

May 31, 2014 at 4:03 am

Hi again,

OK on the issue of the registration button I’ve deleted that code and also deleted the custom css plugin but still the registration button is hard to read. All other buttons like ‘confirm registration’ seem to look ok so any ideas why this one button looks so bad? It’s a pretty crucial button for users to notice!

Thanks
Gary


gbox

June 2, 2014 at 6:12 am

Hi,

Today I tried to add the category color feature which does not seem to work on my calendar and has been logged as different issue. However it seems to have solved an issue I was having with sold out events not appearing in the calendar. The example is my Iceland trip taking place in July. I applied the category ‘overseas’ to it and hey presto now it shows in the calendar.

Thought you might want to test this out. I’ll try something similar with my other sold out events not showing in the calendar to see if applying a category will make them visible.

Thanks
Gary


Tony

  • Support Staff

June 2, 2014 at 8:35 am

Thank you for the feedback Gary I will add that to the notes within the Calendar tickets.

In regards to your previous questions, we are currently writing up a post to explain the various Event status, how/when they will be used, and when they will become ‘Sticky’ (in my previous reply I used the phrase ‘final’) this will (hopefully) provide an in depth explanation in to what was happening on your events.

However, I did some testing when migrating Sold Out EE3 events to EE4 and found that the Sold Out status is sticky at that point, meaning EE4 will not automatically update the status when you alter registrations as you correctly pointed out.

The steps you provided are the correct steps you should take, with a single exception. Once the attendee(s) registration status has been changed and you now have empty spaces, simply Update the event itself to force EE to recalculate the status.

At that point the status will be set to (depending on the Datetimes) upcoming and allow registrations. At that point (because EE has recalculated the status) the status is no longer sticky and will automatically update based on your registration limits, again unless you manually update whilst the status is sold out. Does that make sense?

These are actually edge cases in that your regular EE4 events will update automatically unless specifically set to Sold Out and then updated manually.

Ultimately if you have open registration spots and the status still states ‘Sold Out’ simply update the event to force EE to recalculate this.

In regards to the CSS, EE4 uses vastly different templating from EE3. EE4 is much more heavily based on the sites theme, whereas EE4 has its own styling, layout which was forced into the site. It is the sites theme which controls these submit buttons, some of your buttons are also being styled by the plugin ‘wp-reviews’

For example the ‘Proceed to payment options’ button has styling applied from ‘wp-reviews’ plugin – http://take.ms/Xch6i

Whereas ‘Register Now’ button does not – http://take.ms/Xch6i

We can add styles to override these, but if those plugins are applying styling to buttons in some posts and not others there isn’t must we can do from within EE (other than apply the same styles to the other buttons)

So to confirm, the ‘Register Now’ button linked above is the button you would like to add styles to, is that correct? If so what would you like applied?


gbox

June 2, 2014 at 9:37 am

Hi Tony,

Yes the explanation of status makes sense and it’s good to know that even where the status is not correct on migrated EE3 events that you can still change the status and force the plugin to ‘upcoming’ so you can sell any spaces still left before it reaches the set limit. I don’t have that many events created in EE3 that are still to take place so hopefully some of the issues I’m facing will begin to vanish.

On the CSS styling issue I hear what you are saying about other plugins but I had similar issues with EE3 which were fixed by adding some code to a custom CSS plugin. You mention my wp-reviews plugin styling some of my buttons. I’m not quite sure why this plugin would style buttons for event espresso. Indeed the reviews plugin is relatively new to me and I’ve had styling issues with buttons before so I know in the past this plugin was not the culprit.

Interestingly when I look at the website today the buttons look ok so I don’t know what’s happening and why it seems to have fixed itself now.

Currently things are looking acceptable again. I still have the issue of the event category colors not working but this is by no means urgent. I’ve also noticed that if I am logged in to the admin area of my wordpress website the calendar page does not load (the events list does). As soon as I logout though the calendar works fine. Again this is a niggling issue and does not affect my customers which is the main thing.

Thanks
Gary


Josh

  • Support Staff

June 3, 2014 at 9:20 am

Hi Gary,

I’ll try to follow up with your remaining concerns:

You mention my wp-reviews plugin styling some of my buttons. I’m not quite sure why this plugin would style buttons for event espresso.

It might help to explain that Event Espresso’s buttons are html <input>s, so if a theme or another plugin has its own styles that change the look of an <input> and those styles run on every page on the site, they will have an affect.

I still have the issue of the event category colors not working but this is by no means urgent.

Here’s a link to some code that you can add in a custom snippet plugin that will add a CSS class for each category an Event Espresso 4 event is assigned to:

https://gist.github.com/joshfeck/11383932

I’ve also noticed that if I am logged in to the admin area of my wordpress website the calendar page does not load (the events list does).

I can imagine that this can happen from a script loading in the background that only loads for the admin (but also loads on the front end but maybe wasn’t intended to) that’s breaking the calendar page. The thing about JavaScript (which the calendar is a JavaScript plugin) is if there’s an error in script that loads before the page finishes loading, everything stops. If you’d like, I’d be happy to log in and investigate. There’s likely a way to programmatically remove the script from the calendar page, but we’d need to be able to log in to see it in action. If that works for you, please send temporary WP admin creds via our secure contact form:

http://eventespresso.com/send-login-details/


gbox

June 4, 2014 at 4:05 am

Hi Josh,

I don’t understand why the calendar does not show different colors for event categories when I have created them in settings. If it means adding extra code I will not bother as this is a nice feature rather than essential.

Also as mentioned the buttons seem to have fixed themselves for now. My MAIN ISSUE though remains unresolved and I need urgent fix. The following event does not allow any registrations and the error message you get does not really give any clues. The event is about a week away and I’m losing customers because of it.

PLEASE try and register for this event so you can see the error and advise what the problem is.

http://londonadventuregroup.org/events/chilterns-day-walk-2/

Regards
Gary


Josh

  • Support Staff

June 4, 2014 at 10:47 am

Hi Gary,

I went and registered twice, once with Firefox and once with Chrome. In both tests they went through as expected and took me to PayPal where I cancelled from PayPal.

If you go in to view the registration list for this event, are my tests there?

With the calendar, I am sorry, I misunderstood your question about the category colors. I thought you were referring to the event list. Can you post a link to the calendar page so we can investigate?


gbox

June 4, 2014 at 3:52 pm

Hi Josh,

Yes customers are able to register for events again as the issue was the cache plugin I was using which I have now deleted.

My calendar page is here:

http://londonadventuregroup.org/trips/

You will see that currently all the events show white text on black background as I’ve dictated in the settings. If I remove these in settings they revert to red and white and are not too legible. In any case each event has an assigned category, for example Day Events, Activity Weekends and Overseas Events. I’ve assigned different colors to each category but they don’t appear in the calendar.

The only other outstanding issue as far as I can tell is the fact that old events still show on the calendar when the default for the plugin is not to show them.

Thanks
Gary


Josh

  • Support Staff

June 5, 2014 at 2:24 pm

Hi Gary,

I’ll follow up with your concerns below:

I’ve assigned different colors to each category but they don’t appear in the calendar.

Can you check the calendar settings and make sure that “Enable CSS for Categories” is set to Yes?

The only other outstanding issue as far as I can tell is the fact that old events still show on the calendar when the default for the plugin is not to show them.

Can you change the shortcode on the calendar page to:

[ESPRESSO_CALENDAR show_expired=”false”]


gbox

June 6, 2014 at 12:19 am

Hi Josh,

Yes ‘Enable CSS for Categories’ is set to Yes but does not seem to have any impact.

Shortcut changed to include false and now old events vanish so it seems the default state does not work and you actually need to specify you don’t want them.

Regards
Gary


Lorenzo Orlando Caum

  • Support Staff

June 6, 2014 at 10:47 am

Hello,

I shared feedback here on how the Category colors are assigned:

https://eventespresso.com/topic/ee4-category-color-issue/#post-100237


Lorenzo

The support post ‘More bugs discovered with EE4’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Lorenzo Orlando Caum 5 years, 5 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[for="input_96_5_3"]
[for="input_96_5_3"]
[gravityform id=96 title=false description=false]
  • This field is for validation purposes and should be left unchanged.
[i]
[i]
[gravityform id=69 title=false description=false]
  • This field is for validation purposes and should be left unchanged.