|
Jennifer Warner
|
July 6, 2015 at 4:58 pm
My site is using the latest version of EE3.
Periodically, additional Start/End times appear automatically on the Create Event screen, in the Event Times section.
When it happens, it looks like:
Start 1
End
Start 2
End
Start 3
End
etc.
We had previously opened a trouble ticket and were told these extra times and prices appeared because we had not updated EE3 before a WPEngine security patch was applied. We successfully deleted times and prices with event_id of zero, and the extra times and prices no longer appeared. However, more start-end times have returned recently. We can supply examples of the start-end times and prices, but they do not appear to be very informative.
What is causing these additional start/end times to appear and how can they be prevented?
|
|
Lorenzo Orlando Caum
|
July 6, 2015 at 5:25 pm
Hi Jennifer, are you experiencing this issue with the latest version of WordPress (e.g. WP 4.2.2)? The reason I ask is when we noticed this issue some time ago, there were a series of WP releases that were going out.
—
Lorenzo
|
|
Jennifer Warner
|
July 6, 2015 at 5:27 pm
Hi Lorenzo,
Yes, the site is on the latest version of WordPress 4.2.2.
Jennifer
|
|
Lorenzo Orlando Caum
|
July 7, 2015 at 2:35 pm
Hi Jennifer, members that have experienced this issue have resolved it by removing the errant data and then upgrading to the current software. I don’t think we have seen this reappear as you described.
Can you recall making any specific changes that we could test out on our end?
—
Lorenzo
|
|
Jennifer Warner
|
July 8, 2015 at 1:10 pm
We’re using:
EE3 3.1.37.4.P (up to date, just upgraded one version last night)
EE calendar 2.2.6.p (up to date)
EE Members 1.9.8.p (up to date)
EE permissions 1.5.5.p (up to date)
EE recurring events 1.1.8.p (up to date)
EE roles and permissions pro 2.0.8.p (I don’t think my license supports this anymore, anyway)
We are monitoring our server and will know if another zero event appears, though we won’t know what caused it. I can provide the actual event start-stop and pricing lines from the database, if that would help.
Jen
|
|
Josh
|
July 8, 2015 at 2:03 pm
Hi Jen,
The issue that you’re reporting will happen if an event is created but is not saved due to more characters being input past a limit for a field.
|
|
Jennifer Warner
|
July 8, 2015 at 2:05 pm
Hi Josh,
This could be the scenario triggering the issue we’re experiencing!
Can you further clarify which field(s) and the character limits that cause this issue?
Jen
|
|
Josh
|
July 8, 2015 at 4:30 pm
The fields that could most likely go over a limit are
Event Title (200)
Ticket price option name (150)
It’d be good to check your database to make sure that the columns in the _events_details table match the above limits. If they have lower limits, you can deactivate EE3, change the espresso_version value in espresso.php to something like 3.1.37.4.p.007, save, then reactivate EE3. This will force the database update script to run.
|
|
Jennifer Warner
|
July 9, 2015 at 10:21 am
Hi Josh,
In our database:
wp_events_detail.event_name is 200 characters
wp_events_detail.event_desc is TEXT (unlimited)
wp_events_detail … there is no ticket price option name in the table
Because the front-end event entry screen doesn’t limit characters but the database does, this is a bug. I have many different people creating events in our system, and they could easily trigger this bug without realizing it (and pretty frequently). Do you have any other suggestions to avoid the bug?
Jen
|
|
Josh
|
July 9, 2015 at 12:23 pm
Hi Jennifer,
It may help to explain this isn’t a bug, it’s a security feature that WordPress added a few versions back to prevent malicious scripts from getting written to your database. Before this was added you could input character past a limit and WordPress would still allow saving. It doesn’t allow saving anymore, even if you go past a limit by one character.
So with that in mind, you can avoid the issues you’re seeing by setting the frontend event manager input fields to also limit the number of characters. For example, if your frontend event manager template has an Event Title field, you add You open up your frontend event manager template and add
maxlength="199"
to the Event title <input> element.
|
|
Jennifer Warner
|
July 10, 2015 at 12:03 pm
We are using standard EE3 interactions and do not have our own template for event editing. It’s standard EE3. I checked and the places where an event can be added or edited have maximum length 199 specified. We have code in place that will catch the event_id==0 when it happens, and maybe we can pin it down more precisely. Yes, we were surprised too because we thought it was all fixed, but somehow a bunch of zero entries got into our system. Next time we will know more precisely when, if not why.
THIS URL (we replaced our site name with example.com)
http://example.com/wp-admin/admin.php?page=events&action=add_new_event
HAS THIS HTML
<input type=”text” name=”event” size=”30″ maxlength=”199″ tabindex=”1″ value=”” id=”title” autocomplete=”off” />
THIS URL
http://example.com/wp-admin/admin.php?page=events&action=edit&event_id=17418
HAS THIS HTML
<input type=”text” name=”event” size=”30″ maxlength=”199″ tabindex=”1″ value=“This is a test event” id=”title” autocomplete=”off” />
At this point, I don’t think we need anything else from your team, until we see the problem happen again.
|
|
Josh
|
July 10, 2015 at 1:05 pm
Since you mentioned the Front end editor, did you check the Front end event editor event name inputs? There’s an update to the Front End Event Manager beta add-on that has the same maxlength limits set.
|
|
Jennifer Warner
|
July 10, 2015 at 2:27 pm
Hi Josh,
Can you explain what you mean? My developer and I aren’t clear on what you are referring to.
I thought gave you the inputs to the event editor forms. Do they appear somewhere else? I think 199 is exactly what they are in our system, and what you’re telling us to use.
Jen
|
|
Josh
|
July 10, 2015 at 3:04 pm
Hi Jen,
You mentioned earlier:
Because the front-end event entry screen doesn’t limit characters but the database does, this is a bug.
By front-end entry, do you mean on the front end of the site, or the WordPress admin? The links you posted are for the WordPress admin, but if you are using the Event Espresso Front End Event Manager plugin to display an event creator form on the front-end, you’ll need to update that plugin.
|
|
Jennifer Warner
|
July 10, 2015 at 3:27 pm
Hi Josh,
We’re not using the Event Espresso Front End Event Manager plugin.
Our users create new events in Event Espresso by going to WP Admin -> Event Espresso -> Event Overview -> Add New Event. That is what I was referring to.
Jen
|
|
Josh
|
July 10, 2015 at 3:46 pm
Thanks for the clarification. The WordPress admin isn’t generally referred to as the front end, so that’s why I mentioned the EE Front End Event Manager plugin.
|
