Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
"..event has reached the maximum number of attendees" even attendee number is 0! | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › "..event has reached the maximum number of attendees" even attendee number is 0!

"..event has reached the maximum number of attendees" even attendee number is 0!

Posted: February 4, 2013 at 9:24 am

Viewing 6 reply threads


Mircea Dima

February 4, 2013 at 9:24 am

I get “We are sorry but this event has reached the maximum number of attendees!” message on an event even that there are no people registered to the event.

I get this on two events even that I’ve deleted and recreated them.

Can you please help me with this issue?


Garth

  • Support Staff

    •

February 4, 2013 at 9:22 pm

Are you using registration limits on the time slots?


Mircea Dima

February 5, 2013 at 12:25 am

I forgot to mention that I get this message only on
[SINGLEEVENT single_event_id=”andy-szekely-%e2%80%9ccum-sa-vinzi-fara-sa-vinzi%e2%80%9d-1-510fda2d1c530″] added on a post.

If I go to registration page like this: /event-registration/?ee=8
everyting is ok.

Here you can find events exported from data from “wp_events_detail” table
http://justpaste.it/1wqf
and I get this only on id events 7 and 8 that are recreated


Dean

  • Support Staff

    •

February 5, 2013 at 1:40 am

Hi Mircea,

It looks like the event title has a type of accent in it. Sometimes these can cause issues. I havent seen it work like this before but I can recreate the issue.

Right now the only thing that can be done is to recreate the event without the accent (in this case on the i “importante în comunicare”) so it creates a valid Unique ID and then edit the name afterwards to be grammatically correct.

I will get this raised with the developers.


Mircea Dima

February 5, 2013 at 5:03 am

Editing the “event_id” and removing special characters solved the issue.

It wold be great if can add a filter in the code so it automatically remove unwanted chars.

Thank you!


Dean

  • Support Staff

    •

February 5, 2013 at 5:14 am

Hi,

It wold be great if can add a filter in the code so it automatically
remove unwanted chars.

Agreed, I have already raised a ticket over this as they should be stripped down to basic Latin characters.


Tyson Stelzer

February 11, 2013 at 5:57 am

I just got tripped up on this one too – in the Free version of EE. Please fix it asap as I’m sure my client will make the same mistake I did!
Viewing 6 reply threads

The support post ‘"..event has reached the maximum number of attendees" even attendee number is 0!’ 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.

The original Forum description...

Status: closed

Updated by Tyson Stelzer 11 years, 11 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server