|
cprdave
|
March 14, 2024 at 1:46 pm
Will there be a fix in the next update? Obviously, I can’t use .18, unless there is some trick to the update I’m not aware of.
|
|
Tony
|
March 14, 2024 at 2:16 pm
Hi there,
Will there be a fix in the next update…
We need more information on what is happening within the pages, what does it show?
Any errors in the error logs?
Obviously, I can’t use .18, unless there is some trick to the update I’m not aware of.
There’s no trick to the updates but due to the sheer number of possible plugin and theme combinations its always possible for a plugin conflict as we simply can’t test against them all.
Can you link me to a page show the issue so I can take a look?
|
|
cprdave
|
March 14, 2024 at 2:25 pm
Hi Tony,
The registration forms simply went blank. They disappeared. There were 4 other plugins that needed updating, so I restored the site from backup and updated them 1-by1. The site was okay. With the backup in place utilizing the previous version of EE, I can’t show you a page with the issue without crashing all the registration pages again. Also, I don’t think the error(s) would show up in the log since the restored version of the site didn’t experience the error. Maybe I’m wrong? Thank you for your help.
|
|
Tony
|
March 14, 2024 at 4:28 pm
If you restored the full site it may have also restored the error logs so they wont be available (depends how your server stores errors).
Hmmm… I’m guessing you don’t have a staging site?
Any objections to me cloning the whole site locally?
|
|
cprdave
|
March 15, 2024 at 7:58 am
Hi Tony. No, I don’t have a staging site. Here is what I found in the error log:
[Thu Mar 14 10:56:45.835356 2024] [autoindex:error] [pid 20301] [client 109.123.254.126:0] AH01276: Cannot serve directory /nas/content/live/cprdave/wp-admin/css/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive, referer: binance.com
[Thu Mar 14 11:19:32.834919 2024] [php:notice] [pid 7418] [client 51.195.71.13:0] preventing possible attempt to enumerate users
[Thu Mar 14 13:28:54.575335 2024] [php:notice] [pid 24070] [client 104.28.58.17:0] WordPress database error Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT) for operation ‘=’ for query SELECT Currency.CUR_code AS ‘Currency.CUR_code’, Currency.CUR_single AS ‘Currency.CUR_single’, Currency.CUR_plural AS ‘Currency.CUR_plural’, Currency.CUR_sign AS ‘Currency.CUR_sign’, Currency.CUR_dec_plc AS ‘Currency.CUR_dec_plc’, Currency.CUR_active AS ‘Currency.CUR_active’, Currency_Payment_Method.CPM_ID AS ‘Currency_Payment_Method.CPM_ID’, Currency_Payment_Method.CUR_code AS ‘Currency_Payment_Method.CUR_code’, Currency_Payment_Method.PMD_ID AS ‘Currency_Payment_Method.PMD_ID’, Payment_Method.PMD_ID AS ‘Payment_Method.PMD_ID’, Payment_Method.PMD_type AS ‘Payment_Method.PMD_type’, Payment_Method.PMD_name AS ‘Payment_Method.PMD_name’, Payment_Method.PMD_desc AS ‘Payment_Method.PMD_desc’, Payment_Method.PMD_admin_name AS ‘Payment_Method.PMD_admin_name’, Payment_Method.PMD_admin_desc AS ‘Payment_Method.PMD_admin_desc’, Payment_Method.PMD_slug AS ‘Payment_Method.PMD_slug’, Payment_Method.PMD_order AS ‘Payment_Method.PMD_order’, Payment_Method.PMD_debug_mode AS ‘Payment_Method.PMD_debug_mode’, Payment_Method.PMD_wp_user AS ‘Payment_Method.PMD_wp_user’, Payment_Method.PMD_open_by_default AS ‘Payment_Method.PMD_open_by_default’, Payment_Method.PMD_button_url AS ‘Payment_Method.PMD_button_url’, Payment_Method.PMD_scope AS ‘Payment_Method.PMD_scope’ FROM wp_ioqm_esp_currency AS Currency \n LEFT JOIN wp_ioqm_esp_currency_payment_method AS Currency_Payment_Method \n ON Currency_Payment_Method.CUR_code=Currency.CUR_code \n LEFT JOIN wp_ioqm_esp_payment_method AS Payment_Method \n ON Payment_Method.PMD_ID=Currency_Payment_Method.PMD_ID WHERE Payment_Method.PMD_ID = 10 /* From [cprdave.com/registration-checkout/?uts=1710422933] in [/nas/content/live/cprdave/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:2499] */ made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/Avada/100-width.php’), get_header, locate_template, load_template, require_once(‘/themes/Avada/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, wp_enqueue_scripts, do_action(‘wp_enqueue_scripts’), WP_Hook->do_action, WP_Hook->apply_filters, EE_SPCO_Reg_Step_Payment_Options->enqueue_styles_and_scripts, EE_PMT_Aim->generate_new_billing_form, EE_PMT_Base->settings_form, EE_Payment_Method_Form->populate_model_obj, EE_Model_Form_Section->populate_model_obj, EE_Base_Class->get_many_related, EEM_Base->get_all_related, EE_Model_Relation_Base->get_all_related, EEM_Base->get_all, EEM_Base->_get_all_wpdb_results, EEM_Base->_do_wpdb_query, EEM_Base->_process_wpdb_query, referer: https://cprdave.com/events/aha-basic-life-support-bls-provider-cpr-white-plains-in-person-classroom-course-3/
Please feel free to clone the site locally, if you think it will help.
|
|
Rio
|
March 16, 2024 at 12:21 am
This reply has been marked as private.
|
|
cprdave
|
March 17, 2024 at 8:53 am
Please tell me what revert back means.
|
|
Rio
|
March 17, 2024 at 6:21 pm
This reply has been marked as private.
|
|
Tony
|
March 18, 2024 at 6:08 am
Hi there,
Reverting to the previous version of Event Espresso would not have fixed the above error (restoring the site would/did, but that’s different as it also restores the DB), but that error would likely of caused the issue you are posting here.
What has happened there is the site has created a new table but the MySQL version on your server has changed since the original tables were created and the new table now uses a different collation, the two don’t mix.
To fix this, first, make a backup of the database using whichever method you prefer. One option is using updraft:
https://en-gb.wordpress.org/plugins/updraftplus/
But there are plenty of others if you prefer something else.
Then use this plugin:
https://wordpress.org/plugins/database-collation-fix/
That should fix the collation issue and if that is the only fatal error being thrown will fix the above.
So I would update to 5.0.18.p, go to Event Espresso -> Payment methods and see if there is an error. If so, run the above collation fix plugin and test again. Then retest the checkout page to see if it works.
If not we can investigate further.
|
|
cprdave
|
March 23, 2024 at 7:27 am
Thank you. I just updated EE, and I don’t see any problems. I noticed that the update was version .19, not .18, which gave me trouble. As a safeguard, I also uploaded and activated the database collation fix. Thanks again.
|
|
Rio
|
March 24, 2024 at 4:47 pm
Awesome, Good to hear that everything is fine now. If you need anything, feel free to reach us again.
thanks
|
