Posted: April 23, 2017 at 6:45 am
|
|
When I created a new event, Event Espresso crashed somehow.
The event is there in the database, but will not display correctly. greetings, |
|
Hi there, Can you link us to a page we can use to view this, please? When you created the event, did you first give the event a title before publishing the event? |
|
|
|
Thanks for the quick reply. the link: I do not remember if I gave a title or not before saving – anyway saving without title shouldn’t throw an uncaught exception, I suppose? Event Espresso would prevent saving without title, of course. Or you would have hundreds of support tickets like mine, wouldn’t you? It would be helpful if you could provide information about how I can delete an event in the database completely, which database tables to touch and how to find the information related to the event in order to delete it wholly. That’s the information I need from you, I believe. I could not find any information about how to delete an event in the database in your documentation or in the forums. Thank you! |
|
We don’t recommend going into the database to delete events. Instead, you can go to the Event Espresso > Events page, select the event (or click on Trash). Then once the event is in the trash you can view the trashed events and permanently delete them. With regards to the fatal error, something on your website prevented the Datetime from being saved when you tried to save the event. Can you try temporarily deactivating all other WordPress plugins, then go to edit the event, then Save? Does the event now correctly save? |
|
|
|
My dear Sir, the problem is that I cannot reach the event in the backend, it is never shown. Otherwise – of course – I would have immediately done as you suggested. But I have no other choice than deleting it in the database, since I have no access to the event in the WP backend. Therefore I desperately and quickly need the technical information in which database tables I have to delete the corresponding records, and how to find them (use event ID or what). I also cannot try to create another event and see what happens when saving, the backend displays the same error and doesn’t allow me create another new event. Nothing was changed in the system, the error appeared after saving that ominous event… I suppose there was a short connection failure so the event data wasn’t saved completely. Please provide information about the database tables to check and the records to change/delete. Thank you! |
|
You do have a better option than going directly into the database. You can go to the native WordPress admin list table for the post type, and trash and delete the event post there. Step 1: You add the following to a functions plugin: Then you activate the plugin. Step 2: The above code will add a new menu item to the WP dashboard, “Events”, where you can delete the event. |
|
|
|
Worked like a charm! Thank you very much! Problem solved. |
|
|
Now I still have a massive problem. I cannot create a new event. If I do, the message I sent you in my first post is displayed again. Seems that datetimes are not created in the database or what… I took care to fill in all necessary fields for the new event, but the error appears when I try to save a new event. I noticed that EE displays a warning about missing pages in the backend: “A potential issue has been detected with one or more of your Event Espresso pages. Go to Event Espresso Critical Pages Settings to view your Event Espresso pages.” If I look at the “Critical Pages” settings, everything is marked “OK” – in green color. No Page or shortcode seems to be missing or wrong. Can you help me please? |
|
It sounds like your site doesn’t have the correct permissions to write to the EE tables. Can you check with your host that your site has the correct permissions to write to the Did events previously work and now do not or is this a new install? |
|
|
|
Thank you for the advice, I will check with the hosting provider if there is anything wrong with the db tables’ permissions. Unfortunately I cannot look into the privileges myself. – I will inform you about the answers. Answer to your question: |
|
So can you confirm that you could create a new event before the site was moved to the remote server? |
|
|
|
Yes I can confirm that, just tried it again on the local server, no problem there.- I remember I had to change the collation of some database tables to avoid import failures on the remote server. |
|
Changing the collation of a database table that already has data without properly converting the data tends to cause problems. The way forward will be to find out why there were import failures in the first place. Perhaps the remote server doesn’t support utf8mb4_unicode_ci, in which case you can the server admin if they can make that allowance. Then you should be able to re-import the data from the local server with no problems. |
|
|
|
thank you very much for your support, I will try that but time is running out a little … well maybe it will be best to reinstall everything new. do i also have to delete all EE addons and reinstall them? I suppose so, but what would you suggest? – we don’t have so many events yet, but it’s still some work, also the configuration of the plugins and so on… Are the database tables deleted when I deinstall all EE and its AddOns? |
|
|
Before I try a re-import the data of the *esp tables I have 2 questions: |
You should first perform the same upgrades on the local server before migrating data to the remote server.
No because Event Espresso saves events, venues, and contacts to the wp_posts table. Settings for Event Espresso are saved to the wp_options table.
You can go to the Event Espresso > Maintenance > Reset page and click on the button that says:
|
|
|
|
After the reinstallation of EE and all AddOns everything seems to work now. – Except that the Headers of the Transaction Emails seem to be broken, above the Header Section (grey) with the logo html tags appear: |
|
Those email templates are stored in the database. The quick way to reset them is you go into the editor for the emails, and click on the reset button. |
|
|
|
didn’t help… only the emails to the seller got a litte more ugly, but never mind. isn’t there a global php-template for the email header, where I can correct the html-tags before the header? good day to you |
|
|
Any ideas? |
|
|
Please help quickly, event espresso is unuseable, we cannot send out those corrupted emails! If I should create a new ticket, please just tell, or if there are any other formal problems for you in answering to my problem. Again: on a freshly installed Event Espresso System the Emails sent to the customer are corrupted, showing some dubious HTML-Tags before the content. Please help. |
|
|
sorry, i was wrong, you didn’t react for 1 1/2 days. |
|
We have seen this previously and it turned out to be an issue with the mail server configuration used by the host. Please note that support hours are: |
|
|
|
good morning. in the article you suggested it says: “Are you having email deliverability issues such as emails getting lost or some being marked as SPAM or junk mail?” Before I try your advice to use a transactional email service, I send you the html code of one of the transaction emails, maybe it is of help finding the cause of the problem. As you can see, there are incorrect line breaks (look at the first <!DOCTYPE… line), causing the email to look broken. Any ideas about that? THANKS for your efforts… |
If this was an issue with EE’s template files we would see this same problem across all sites using Event Espresso, but we do not, its currently only happening on your site. We have seen something similar happen on a couple of other sites which as Josh mentioned turned out to be the host mail server setup.
There is nothing wrong with the DOCTYPE set in the output you mentioned unless I’m completely missing something with this: The problem is the additional HTML that’s been added to the beginning of the email: And at the end: So the EE email HTML is being wrapped within another header, opening the HTML and BODY tags, then closing them. So theres a HTML doc, within a HTML Body tag? That additional code is not from Event Espresso, so either another plugin is hooking into wp_mail() and adding its own header to every email generated on the site, or your host has it setup to do that.
If its another plugin its not likely using a transactional email service will help, the plugin will continue to hook in and add those details to the email before its then sent off to the transactional email service to send. If it’s the hosts mail server setup then using a transactional email service will help.
Some of the services available have a free tier for you to use so there is no cost involved for yourself whilst testing this (other than time to setup) and most of them a farily easy to setup so you can test as they use a plugin you install and then add your api details for the service you want to use. Have you tried de-activating ALL non EE plugins AND switching to a default theme such as twentyseventeen and creating a NEW registration to view the email from that? |
|
|
|
thank you for your detailed answer! so at least now I know our options. |
|
You configure which question groups get displayed for the event within the event editor. Here’s a link to the documentation that explains more: https://eventespresso.com/wiki/questions/#how_to_set_questions_for_registants |
|
|
|
Thank you for your answer, everything has been done properly – as advised – already. All questions (“First Name”, “Last Name”, “Country” etc.) have been assigned to one of the 2 question groups, “Personal information” and “Address information”. |
|
|
sorry sorry now I found it, it’s configured in the event, not in the reg. form settings… thank you!! |
|
That’s correct. You create your questions/question groups and assignments within the Reg form settings, but each individual event may ask different questions, so each event has its own individual settings for which question groups are shown on its registration form – http://take.ms/1CBvc |
|
The support post ‘Fatal error: Uncaught exception 'EE_Error' with message 'Could not create instan’ 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.
