Posted: September 30, 2024 at 6:42 am
EventEspresso caused a critical error on my site. When i go into recovery mode it shows that the plugin failed to load properly: An error of type E_ERROR was caused in line 317 of the file /home/peafnet/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Capabilities.core.php. Error message: Uncaught TypeError: EE_Capabilities::map_meta_caps(): Argument #2 ($cap) must be of type string, null given, called in /home/peafnet/public_html/wp-includes/class-wp-hook.php on line 324 and defined in /home/peafnet/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Capabilities.core.php:317 Stack trace: #0 /home/peafnet/public_html/wp-includes/class-wp-hook.php(324): EE_Capabilities->map_meta_caps(Array, NULL, 570, Array) #1 /home/peafnet/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) #2 /home/peafnet/public_html/wp-includes/capabilities.php(842): apply_filters(‘map_meta_cap’, Array, NULL, 570, Array) #3 /home/peafnet/public_html/wp-includes/class-wp-user.php(782): map_meta_cap(NULL, 570) #4 /home/peafnet/public_html/wp-includes/capabilities.php(985): WP_User->has_cap(NULL) #5 /home/peafnet/public_html/wp-includes/capabilities.php(877): user_can(Object(WP_User), NULL) #6 /home/peafnet/public_html/wp-content/plugins/event-tickets/src/Tribe/Admin/Notices.php(48): current_user_can(NULL) #7 /home/peafnet/public_html/wp-includes/class-wp-hook.php(324): Tribe__Tickets__Admin__Notices->maybe_display_rsvp_new_views_options_notice(”) #8 /home/peafnet/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #9 /home/peafnet/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #10 /home/peafnet/public_html/wp-admin/admin.php(175): do_action(‘admin_init’) #11 /home/peafnet/public_html/wp-admin/plugins.php(10): require_once(‘/home/peafnet/p…’) #12 {main} thrown |
|
Hi there, That error means Event Espresso is loading as expected, but something is calling a function with details it doesn’t expect. That specific error means that something is calling a capability check, without passing a capability to check and you can see that within your stack trace:
This part, We found that multiple instances of other plugins calling capability checks without an actual capability then caused that to fatal (as above) and updated the codebase to prevent it in 5.0.13+ Which specific version number of Event Espresso was/is the above error being thrown with, please? |
|
You must be logged in to reply to this support post. Sign In or Register for an Account