Posted: October 20, 2015 at 1:06 pm
|
I’m running the latest EE4 version of everything. We add events, and then tie people to it. For some users only, the Editor is broken. This appears to be a JS issue just for some users. RELATED ISSUE *notice the last bullet on Donna, where there is no event listed For working people, there events appear normally & their editor works. Here is a working person page: |
|
The image I posted did not show in my post. For the People Addon Editor, the menu is gone, and text is whited out in the textarea. |
|
oops I did the image wrong, here is what the broken editor looks like: |
Hi Donna, If you enable WP_DEBUG and view the People editor, are there any errors shown? Do you have trashed events within EE that are assigned to these people? |
|
|
WP_DEBUG is on, and I get to no errors when going to the page. Yes I have trashed events assigned to Donna, and this would explain why the links are returning 404’s. Why are trashed events showing on the person’s page? |
|
I tested by restoring the trashed items, and it did not fix it. I further tested by deleting all the trashed events and did not fix it. Should note that we used the “Duplicate” events functionality to create some of these new events, and I’m wondering if there is a bug with duplicated events causing unforeseen issues. We’re also experiencing a myriad of other issues to include: 2. Backend registration of these events also fails, but this time with DEBUG on I get this:
Just mentioning the above in case it helps to correlate with the issue mentioned above. |
Hi Donna, Could you go to your plugins page in the WP dashboard and deactivate Event Espresso? Then reactivate it along with the promotions add-on. Do you still see a database error afterwards? — |
|
They should not be displayed, I have created a ticket for our developers to investigate this.
There could be lots of reasons for this, for example if you site is running out of memory the request to update the DB could fail. I would recommended checking your current memory limit, go to Event Espresso -> Maintenance -> System information. Search for both wp_memory_limit and memory limit, post those values here. You may want to setup error logging, so that the errors are writen to a log file and we can troubleshoot this further. You can do this by adding:
To your wp-config.php file. That should create a dubug.log file within /wp-content/ so you can save the errors thrown.
Can you go to Event Espresso -> Maintenance -> System information. Search for ‘maintenance’, you should find a section just below where wp_memory_limit is, does that show a .maintenance file has been detected? |
|
|
Lorenzo: I did the de/reactivate and it did not clear the issues: Tony: I’ve added the DEBUG code in wp-config.php Memory Info
*There is no wp_memory_limit setting anywhere in the System Information box There is also no field that shows wp_memory_limit, so I’m unsure where to check for a maintenance file. I should note that this is on a Multisite setup, so it may be different than single install |
|
I just found this setting below under wp_settings: I also found that there is no .maintenance file detected. However, if I turn on maintenance mode, my understanding is that it will break normal functionality of the site? We’re currently live, and taking customers, so unsure if I should turn maintenance mode on. |
No don’t activate maintenance mode, what I was checking is that a .maintenance file wasn’t present (which could indicated a failed update) but seems that’s not it.
My apologies, that wp_memory field shows the value set for wp_memory_limit, so I used the wrong title to search for. What kind of hosting are you using? Do you have access to phpMyAdmin or similar? |
|
|
I use WPEngine, and we have PHPMyAdmin. On a sidenote, we noticed that this issue seems only to be occuring on events that were “duplicated”. When we restart a class schedule, we use the “Duplicate” button in the Event’s Editor. It may be possible that there are issues in how the duplicate is recreated wherein it is trying to reference the previous (trashed or expired) class. |
|
Things just got worse. Customers are stating that the system is sending out 100’s of confirmation emails for one signup. Here’s an excerpt: |
Hi Donna, As your using WPEnigne have you contacted them to exclude EE from caching? We have details on this here: https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/ The multiple emails is caused by server side caching and should stop once WPEngine has excluded those pages. I’ll do some further testing with duplicated events to try and track down the issue with ‘people’. |
|
|
Hi Tony, Yes, quite a few pages are no-cached with them, like events, signup, etc. WHich page in particular needs to be uncached to correct this email issue? |
|
WPEngine has nocached every possible thing it could find related to EE, and we’re now monitoring the million email situation. Yet another issue has arisen: The Ticket QTY is set to 6, and there is only 1 Registration. Likewise for the Events (Limit is 6 with 1 registration) I’ve tried: We are using the recurring events addon. WHich I’m beginning to think is the culprit in all this mess. How can I force this back into Published? |
There is no EE4 recurring events add-on, do you have the EE3 Recurring Events Add-on installed? If so de-activate it and any other EE3 Add-ons you have installed as none of them work with EE4.
The thank-you page that should prevent it. In the sold out events do all of your datetimes have a ticket assigned to them? Can I take a look at your system information within the admin? If so please send temporary login details using this form: |
|
|
Temp Login Sold Out PENDING ISSUES Multiple Email Confirmations URGENT People Editor broken URGENT Datetimes cannot be deleted from trashed events Duplicated Events have various issues |
Did you have the limit fields set to 0?
Are you still seeing this? The only reason we have seen for this is caching. If WPEngine has disabled all caching then this should no longer happen. One way to test this is to setup an event with a free ticket and register onto that event (whilst NOT logged into the site) then see if duplicate emails are sent.
It sounds like the people issue is linked to the duplicate event issue you are having. However I’ve been testing duplicating events with both the People Add-on activate and inactive and how not run into any issues with registering, or editing people assigned to those events.
Its not the Datetimes that you need to remove to delete the events, it’s the registrations assigned to the event. If you click to view that event, then click to view the registrations for that event, you’ll see something like this – http://take.ms/xSVT4 Notice the incomplete registration? That needs to be removed before the event can be deleted – http://take.ms/BjVPe Trash and perm delete that registration and the event will unlock and allow you to delete it. Can you let me know which event is a duplicate event on your site so I can run some tests on that? |
|
|
1. SOLD OUT. In the particular case of one that was problematic, the fields were set to 6 or null. Neither fixed it. Only changing the dates did. 2. MULTIPLE EMAIL. We tested (before going live) with Free events, and we never had issue. With paid tickets, this is when it happens. Yes, it would still be happening if I didn’t turn off all outgoing emails. This is not a fix, but I had no choice as WPENGINE warned of shutting off my entire email service. I need to know which exact URL-string is causing this so WPEngine can nocache it. They have looked at it thoroughly and believe they have nocached everything 3. PEOPLE FORMS BROKEN. The form is still broken (and front end for person), so there is still an issue. How do we correct the broken People pages? |
Hi, could you provide a list of the slugs that you provided to WP Engine to exclude from the cache? In your original post you mention that the people editor is broken for some users. Are the users that are working on your site using an administrator account or are these accounts restricted? — |
|
|
Any instance below is detected in URL it auto-no-caches. So even subpages & url-params are nochaced: http://smartypaws.cmsadminpanel.com/events http://smartypaws.cmsadminpanel.com/student-login *They also nocached an EE cookie on the registration-checkout page above I’d like a list of all cookies that need to be nocached as well. In my research on other EE forum pages, it would appear that the referral from Authorize.net back to the Thank You page is where the issues arises. Not sure if it’s due to the /transactions page or the /thank-you page cookies not being nocached. |
|
Disregard the domain in the response above. I copy/pasted from an older ticket in WPENGINE. The Nocache requests above are actually for smartypaws.com Not smartypaws.cmsadminpanel.com (this is the subdomain the install is on, but we use the DomainRewrite plugin for the Smartypaws.com to work right now). |
Hi there, Can you test, with an email messenger active, an Authnet SIM transaction while logged in as admin? This will not be cached since you’re logged in as admin, and will help us all narrow down the cause of the multiple email issue on your server. The People CPT Editor is throwing a PHP error when it loads the page for the affected users:
I suspect that’s related to the trashed/duplicated events, so likely any of the users that do not have trashed or duplicated events assigned to them have the pages that load up as expected. We’ll update the dev team with what we find. |
|
|
For the AUthnet SIM transaction, I will need to coordinate this with the Donna (I am the Developer). This will likely be tomorrow, as it is after-hours now. |
Were any of the events deleted directly from the wp_posts table by using phpmyadmin or similar? |
|
|
No. Acutally none of the events were deleted yet (that I remember). They are all still in Trash. |
That’s strange. Are you blocking access to trashed events, for the admin account that you sent to us? The reason I ask is because it shows 0 trashed events. |
|
|
Oh Great, the client must have deleted them. My apologies for that. But you can create a Duplicate Event if you’d like and trash it. I’ve gotten approval from Donna to do whatever I need to just get it working. |
Hi there, I tried doing just that, duplicating an event, assigning a People CPT to the duplicated event, then trashed the event. This doesn’t result in a fatal error like on the other People CPTs. It appears that somehow, someway, someone has deleted events that have People CPTs assigned to them, and that results in the errors you’re seeing when you go to edit some of them. Normally Event Espresso will prevent the deletion of an event if there’s a relationship between the event and another post type, but somehow that mechanism that prevents this got worked around here. Here’s how you fix the broken relationships between some of the People CPTs and the events that were permanently deleted: 1) Back up the database just in case you accidently delete the wrong record(s). 2) You get the People CPTs IDs that are throwing fatal errors when you try to edit them. These include: 74, 70, 72, 29, 75, 78, 79, but it would be good for you to verify and get the full list. Examples of People CPTs that are intact are 77 and 229. 3) Then you go into PHPmyadmin and browse to the wp_esp_people_to_post table. You’ll match the each row’s PER_ID to the IDs in your list. Then within that group, you make a list of the OBJ_IDs, those are the event IDs. If any of those entries have OBJ_IDs that do not have corresponding entries in the wp_posts table, you can delete the row in the wp_esp_people_to_post table. |
|
|
Hi Josh, In the meantime, can you look at this: I can’t get it to PUBLISH (stuck on SOLD OUT) What am I doing wrong here? |
|
I think someone needs to look at Recurring Events. Perhaps recurring events do not have the People-type check, when they are deleted. So you get a bunch of orphaned entries left in the esp_people_post_table |
Hi there, In the Novice Agility | North event, the one ticket is archived. A ticket will automatically be archived when you change the price if there’s already a registration for it. You can create a new ticket for the remaining available spaces, you click “Create Ticket”. Recurring events are not currently available in Event Espresso 4, so maybe you mean something else, like an event with multiple datetimes? |
|
|
I tried creating a 2nd ticket, it doesn’t fix it. You can look at the Editor now to see. The 2nd ticket for 5 still wont force it to Publish. Yes, I mean recurring DateTimes. |
You’ll note that if you change the Qty to blank, it will un-sell out. You can update to the current version of Event Espresso 4 (4.8.18.p). The .17 update included a fix for the ticket Qty for each datetime calculation. With the events with multiple and the People add-on check. That’s not something we’ve seen in any of our testing. I’m still not sure how they were able to delete those events because they had more than people CPTs assigned to them. Does anyone that works on that site go into PHPmyadmin? I wonder if the events got deleted directly from the posts table. |
|
|
I’m the only one with access to PHPMyAdmin, and I’m 100% sure I didn’t do it. I talked to the client and they said remember Bulk Deleting items from trash. This had to be how it was done. |
If you try to bulk delete the event I added today, you’ll find that it throws an error that says “This Event is currently linked to one or more Item records. If this is incorrect, then please remove it from all Items before attempting to delete it.” The reason it will not let you bulk delete that event is because there’s a People CPT assigned to it. |
|
|
I’m unsure how they did it. But it was done. They do have Admin access. UPDATES: – We’ve performed the ADMIN-purhcase of a ticket, and so far, no repeat emails are coming in (but we are monitoring it). PENDING ISSUES: 1. Although Admin purchases appear to not cause repeat emails (still monitoring), non-admin purchases seem to still do it. I’m wondering if there is some cookie on the /thank-you page that needs to be nocached. Here’s a sample link: 2. The client has reported that when some events have a new registration, the Event goes into SOLD OUT. They then have to go and “Update” the post for it to go back live. I’m currently monitoring this situation. 3. I believe there is some variation of “Duplicate” posts, and the Multiple Event Datetimes, that caused many of the issues we’ve seen above. I think more testing needs to happen with Duplicating Events with Multiple Datetimes. |
|
We are also experiencing an extremely slow Calendar: I’ve talked to WPENGINE and they stated that we are running on fast, WP-optimized SQL servers, but the many objects being queried is slowing it down. This is much slower than another client’s calendar that is running on EE3 My concern is that we have very few events in the system now. What happens a few months from now when we have more? Are the multiple DateTimes the issue with this? |
Hi there, With your issue #1, EE does not use cookies on the Thank You page. Maybe WPEngine can add a no cache rule if there’s a e_reg_url_link in the URL. With issue #2, have you updated to Event Espresso 4.8.18? That should fix it.
Thanks for the feedback. We have not seen these issues on our testing sites, and we do test, a lot, and then we test some more. We’ve also tried to reproduce the same issues you’ve seen on your site by duplicating events with multiple datetimes and have not seen it where it affects the ability to delete trashed events. The issue with the event that sold out after the ticket price was changed (due to no automatic replacement for the archived ticket) was found in testing a while ago and was assigned to a developer to fix. It is not related to duplicating events or having multiple datetimes. Regarding the calendar, it can be slow if it’s looping through a lot of datetimes, and it can also be slow if many of its options are activated. For example, you can speed things up by disabling Enable CSS for Categories and in Calendar > Advanced Settings set Disable Categories to Yes. |
|
|
We’re still monitoring the million email situation. I’ve tentatively turned the Reg. Confirmation email back on (to Admin), the client is monitoring it. I’ve disabled the (2) Cal Features as you suggested, but the Calendar still runs slow: – The speed is not too bad now. But my concern is 4 months from now when we have many DataTimes in the system, is this going to get dramatically slower? I’m unsure of how your query is, or if an index is built per month negating the full DB query. If it is determined that the multiple datetimes (compounded over many months of additions) is going to slow the Cal to a grinding halt eventually, then I will have no choice but to have the client stop using them. |
Hi there, It turns out that the calendar does not load up all the months initially. Instead, it only loads up the events for current month, then when you advance forward to the next month, it loads up more events via an AJAX call. |
|
The support post ‘People Add-on Bug: Editor Broken & Event List broken for some users’ 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.