|
ElevatedSafety
|
October 19, 2023 at 4:00 pm
We have been taking payments with Authorize.net AIM for years with no problems. Now we want to allow payment via invoice on a small number of events. I’ve installed the Payment Methods Pro add-on and set Available By Default to No. If I select invoice on the event and save, I get several database errors (see below) and am unable to save the event.
If I set to invoice payment method Available By Default to Yes, it seems to work fine, but that is not the behavior I want.
DATABASE ERRORS
[19-Oct-2023 21:34:11 UTC] PHP Notice: WPDB Error "WordPress database error: Processing the value for the following field failed: EXJ_first_model_ID. The supplied value may be too long or contains invalid data." while running wpdb method "insert" with arguments [“wp_esp_extra_join”,{“EXJ_first_model_ID”:”1529012″,”EXJ_first_model_name”:”Event”,”EXJ_second_model_ID”:”6″,”EXJ_second_model_name”:”Payment_Method”},[“%s”,”%s”,”%s”,”%s”]]. Automatically attempting to fix EE Core DB in /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2521
[19-Oct-2023 21:34:11 UTC] PHP Notice: WPDB AGAIN: Error "WordPress database error: Processing the value for the following field failed: EXJ_first_model_ID. The supplied value may be too long or contains invalid data." while running the same method and arguments as before. Automatically attempting to fix EE Addons DB in /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2521
[19-Oct-2023 21:34:11 UTC] PHP Fatal error: Uncaught EE_Error: WPDB Error: "WordPress database error: Processing the value for the following field failed: EXJ_first_model_ID. The supplied value may be too long or contains invalid data." in /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:2450
Stack trace:
#0 /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(3135): EEM_Base->_do_wpdb_query(‘insert’, Array)
#1 /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2937): EEM_Base->_insert_into_specific_table(Object(EE_Primary_Table), Array, false)
#2 /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/relations/EE_HABTM_Any_Relation.php(235): EEM_Base->insert(Array)
#3 /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(2667): EE_HABTM_Any_Relation->add_relation_to(Object(EE_E in /nas/content/live/elevatedsafety/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 2450
Wordpress 6.3.2
EVENT ESPRESSO PLUG-INS
Event Espresso 5.0.11.p
Attendee Mover 1.0.7.p
Automated Upcoming Event Notification 1.0.7.p
MailChimp 2.5.0.p
Promotions 1.0.16.p
Price Modifier For Event Espresso 4 1.3.1
OTHER PLUG-INS
Advanced Custom Fields PRO
BigCommerce for WordPress
Classic Editor
Contact Form 7
Contact Form CFDB7
Easy WP SMTP Pro
Really Simple SSL
Redirection for Contact Form 7
Tracking Code Manager
WP Engine Smart Plugin Manager
Yoast SEO
|
|
Tony
|
October 20, 2023 at 9:10 am
Hi there,
When you use Payment Methods Pro we have to save the payment method selections you make on specific events within the database and we do that within a custom table (on your database its wp_esp_extra_join).
The error you are getting relates to the EXJ_first_model_ID being too big for the current field and to fix that your database will need to be updated.
Do you have access to PHPMyAdmin through your host?
|
|
ElevatedSafety
|
October 20, 2023 at 2:13 pm
Yes, I have access to phpMyAdmin.
|
|
Tony
|
October 23, 2023 at 3:44 am
Then a quick fix is to edit the wp_esp_extra_join table and set the EXJ_first_model_ID field to be varchar(8)
Currently it will be varchar(6):
https://monosnap.com/file/wxKpDD3itKeLoiZFYWBaORsAauwWyQ
So open up the database in PHPMyAdmin, find the wp_esp_extra_join table, open it and click on the structure tab:
https://monosnap.com/file/cqjXMQHppDZB9CW4fwsISjiQFAdlDf
Set the field to be 8 chars and save:
https://monosnap.com/file/FP0AuBzUi4SMgzLMsZmgAe2DfpPFJ2
Then retry the above.
I have created a ticket for our developers to investigate this and we will likely update the field to be an INT field but the above should get the event working for you for now.
|
|
ElevatedSafety
|
October 23, 2023 at 8:43 am
That fixed it. Thank you.
|
