|
eosw
|
June 5, 2020 at 2:04 pm
Hi – when you go to checkout for our bootcamp events, there is an error that pops up saying A database error has occurred. Turn on wp_debug for more information. The transaction and charge goes through, but the error is making folks contact us. I think the issue might be that the proceed to Finalize Registration button is visible before you pay, so how would we fix this?
|
|
Tony
|
June 8, 2020 at 3:53 am
Hi there,
Are you comfortable editing PHP files?
What I would do here is enable WP_DEBUG mode to see what the error being thrown actually is, to do that you edit your sites wp-config.php file and replace the line that has define( 'WP_DEBUG', true ); with the code here:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
That enabled WP_Debug mode and logs the errors to /wp-content/debug.log
You may need to create a test event and run through a registration to trigger the error again (or wait for another user to trigger it) so that you can view the full error. If you can post that error we can investigate further to see what is going on.
|
|
eosw
|
June 17, 2020 at 11:07 am
Hi Tony – Below is the log. Please let us know next steps.
[17-Jun-2020 13:28:24 UTC] PHP Notice: WPDB Error “” while running wpdb method “insert” with arguments [“wpeos_esp_message”,{“MSG_token”:”da22a3f77a2a704d288e915f46bdcee2″,”GRP_ID”:24,”TXN_ID”:830,”MSG_messenger”:”email”,”MSG_message_type”:”payment”,”MSG_context”:”admin”,”MSG_recipient_ID”:547,”MSG_recipient_type”:”WP_User”,”MSG_content”:””,”MSG_to”:”abaird@eosworldwide.com, lhofmann@eosworldwide.com, jsedick@eosworldwide.com, byeakey@eosworldwide.com, kmosher@eosworldwide.com, jmcnellis@eosworldwide.com, msimpson@eosworldwide.com, jdiamond@eosworldwide.com, abaird@eosworldwide.com, lhofmann@eosworldwide.com, jsedick@eosworldwide.com, byeakey@eosworldwide.com, kmosher@eosworldwide.com, jmcnellis@eosworldwide.com, msimpson@eosworldwide.com, jdiamond@eosworldwide.com”,”MSG_subject”:””,”MSG_priority”:10,”STS_ID”:”MIC”,”MSG_created”:”2020-06-17 13:28:23″,”MSG_modified”:”2020-06-17 13:28:23″},[“%s”,”%d”,”%d”,”%s”,”%s”,”%s”,”%d”,”%s”,”%s”,”%s”,”%s”,”%d”,”%s”,”%s”,”%s”]]. Automatically attempting to fix EE Core DB in /nas/content/live/eos7/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2377
[17-Jun-2020 13:28:24 UTC] PHP Notice: WPDB AGAIN: Error “” while running the same method and arguments as before. Automatically attempting to fix EE Addons DB in /nas/content/live/eos7/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2377
[17-Jun-2020 13:28:24 UTC] PHP Fatal error: Uncaught EE_Error: WPDB Error occurred, but no error message was logged by wpdb! The wpdb method called was “insert” and the arguments were “array (
0 => ‘wpeos_esp_message’,
1 =>
array (
‘MSG_token’ => ‘da22a3f77a2a704d288e915f46bdcee2’,
‘GRP_ID’ => 24,
‘TXN_ID’ => 830,
‘MSG_messenger’ => ’email’,
‘MSG_message_type’ => ‘payment’,
‘MSG_context’ => ‘admin’,
‘MSG_recipient_ID’ => 547,
‘MSG_recipient_type’ => ‘WP_User’,
‘MSG_content’ => ‘<table class=”head-wrap” style=”margin-bottom: 15px;” bgcolor=”#FFF”>
<tbody>
<tr>
<td></td>
<td class=”header container”>
<div class=”content”>
<table bgcolor=”#FFF”>
<tbody>
<tr>
<td> </td>
<td align=”right”>
<h6 class=”collapse”></h6>
</td>
</tr>
</tbody>
</table>
</div></td>
<td></td>
</tr>
</tbody>
</table>
<table class=”body-wrap”>
<tbody>
in /nas/content/live/eos7/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2314
|
|
eosw
|
June 17, 2020 at 11:10 am
Actually I have an attached log file, Can I have an email to send the attachment?
|
|
Tony
|
June 18, 2020 at 2:46 am
No need for an additional error log, the above gives me (just) enough information to see the problem, which is the number of email addresses you currently have sent in the ‘To’ field of the Event Admin context.
MSG_to (which is the field in the database that stores the ‘to’ field for a specific message) has a max length of 255 characters. Your message above has over 400 characters so it can’t insert the value.
I tested this locally and can see that you can set a value in the message template field that is greater than what EE can currently use, that’s something we’ll need to fix but it may simply mean we limit the field rather than adjusting the database field.
So right now, for the event admin email to function you’ll need to remove some of those email addresses from the To field of your event admin context(s). The message shown above is for a ‘payment’ email so I assume that’s your ‘Payment Received’ message type, but if you’ve set that many email addresses in other messages you’ll also need to remove those.
Rather than including all of the emails in the to field I recommend setting up an alias within your mail provider, for example, create info@domain.com and then add all of the above emails into that alias. You then set one single email address in the message template to send.
|
|
eosw
|
June 18, 2020 at 7:51 am
Ahhhh got it. Is the CC field also 255 characters only?
|
|
Tony
|
June 18, 2020 at 8:29 am
CC should actually allow for more, its an extra_meta field of type text which allows up to 64KB.
|
|
eosw
|
June 19, 2020 at 7:41 am
Hi Tony – Perfect. Thank you, we are all set. We have tested it all is good.
|
|
Tony
|
June 19, 2020 at 7:46 am
Great!
Whilst using the CC field is fine, I should note that I still recommend creating an alias/group email for this and then using that single email in EE.
There are a few benefits to doing it but the main one is that once you start editing multiple templates to add edit those emails it gets much harder to track. For example, say one of those admins leaves or their email is no longer valid. You need to edit each template it is used on to fix it. Creating an alias and including them all in that means you simply edit the alias.
Either way, the choice is yours and I’m glad you have a working solution.
|
