|
lt3030
|
June 19, 2019 at 9:57 am
Hello,
My client is having issues with completing registrations in EE4. Users (frontend) and admins (backend) are able to select the number of tickets and go to Step Two to enter Registrant Details (Personal Info). When clicking on “Save Registration and Continue to Details” the registration bombs out and returns an error page: “This page isn’t working. If the problem continues, please contact the site owner. HTTP ERROR 414”
This has happened on several occasions. Note: All plugins and WP Core are up to date. WordPress 5.2.2 running Sela Child theme. Running PHP version: 7.0.33
Hosting: GoDaddy – Economy Hosting
I’ve been unable to recreate the error on my end could you shed some light on why this is happening?
|
|
Josh
|
June 19, 2019 at 10:07 am
Hi,
The error code indicates the URI is too long, which would be strange unless the web page’s URL was very long (like over 2048 characters long).
May I ask can you share a link to the event in question so we can investigate further? Please feel free to check the box “Set as private reply” if you prefer to not share the URL publicly.
|
|
lt3030
|
June 19, 2019 at 10:29 am
This reply has been marked as private.
|
|
Josh
|
June 19, 2019 at 10:36 am
Hi,
It looks like, at this moment, the Event Espresso plugin is deactivated so there’s no content on those pages. When the Event Espresso plugin is reactivated we can check again.
Do you by chance have the iThemes Security plugin installed? If so, that may be what’s causing the 414 error. To fix, you can turn off the “Filter Long URL Strings” checkbox. This setting can be accessed at Security –> Settings –> System Tweaks.
|
|
lt3030
|
June 19, 2019 at 10:37 am
This reply has been marked as private.
|
|
lt3030
|
June 19, 2019 at 10:42 am
This reply has been marked as private.
|
|
lt3030
|
June 19, 2019 at 10:44 am
This reply has been marked as private.
|
|
Josh
|
June 19, 2019 at 10:59 am
Hi,
What they mentioned about deactivating, then reactivating the Event Espresso plugin makes no sense to me. Specifically, this makes no sense:
Sure the plugin was generating the error log that was the reason you are facing this issue however when you face such issue I suggest you to disable the plugin that will help you in resolving
If there is an error in the log, it will be most helpful to know what that error is, then a real solution can be investigated.
|
|
lt3030
|
June 19, 2019 at 12:11 pm
This reply has been marked as private.
|
|
lt3030
|
June 19, 2019 at 12:14 pm
This reply has been marked as private.
|
|
Josh
|
June 19, 2019 at 12:16 pm
As you can see the error is pointing to a custom function in the child theme’s functions.php file, specifically the ee_move_cart_markup() function.
Something within your custom ee_move_cart_markup() function may need fixing/error-proofing.
|
|
Josh
|
June 19, 2019 at 12:18 pm
Class EED_Single_Page_Checkout not found would likely be caused when the EE4 plugin was temporarily deactivated. In other words, the logged error that Godaddy found was from when they deactivated the plugin.
|
|
lt3030
|
June 19, 2019 at 12:27 pm
This reply has been marked as private.
|
|
lt3030
|
June 19, 2019 at 12:28 pm
QUICK QUESTION: GD giving me static about PHP version. What version of PHP is EE4 compatible with?
|
|
Josh
|
June 19, 2019 at 2:33 pm
We recommend PHP 7.2 or PHP 7.3. Older versions of PHP are OK but we do not recommend using anything older than PHP 5.6.
The code is OK, except if Event Espresso is deactivated. So to error-proof that you can add a check for the class e.g.
add_action( 'loop_start', 'ee_move_cart_markup', 1 );
function ee_move_cart_markup(){
if (! class_exists('EED_Single_Page_Checkout)) {
return;
}
if( is_page( ) ) {
remove_action( 'loop_start', array( EED_Single_Page_Checkout::instance(), 'set_checkout_anchor' ), 1 );
}
}
|
