• Resolved meganmasterson

    (@meganmasterson)


    Hi,

    We are experiencing a critical error message for some users when logged into our online portal, trying to access event links. “There has been a critical error on this website”

    This only impacts those with a specific user role but there are no associated restrictions prohibiting them from accessing Events, event links, or the calendar. This issue does not occur with admin roles.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support Darian

    (@d0153)

    Hi @meganmasterson

    Thank you for reaching out and for providing the details about the issue. Let me assist you with troubleshooting this.

    Could you please enable debugging on your website and then try to replicate the error? This should display a more detailed error message. If you see one, kindly share the full error message so I can investigate further on my end.

    Additionally, if you haven’t already, please ensure that you’re using the latest versions of our plugins, as outdated versions can sometimes cause this type of issue.

    Let me know how it goes.

    Thread Starter meganmasterson

    (@meganmasterson)

    Plugin Support Darian

    (@d0153)

    Hi @meganmasterson

    Thanks for your response and for sharing the debug file.

    Unfortunately, I wasn’t able to locate any fatal or critical error messages in the logs you provided. Were you able to replicate the issue after enabling debugging? If not yet, please try to reproduce the issue on your site, and then send us the updated debug log file right after. This will help us investigate the problem more effectively.

    Thread Starter meganmasterson

    (@meganmasterson)

    Plugin Support Darian

    (@d0153)

    Hi @meganmasterson

    Thanks for your response.

    Unfortunately, I still don’t see any Fatal Errors or Critical Errors in your logs.

    To help us move forward, could you confirm if you’re able to replicate the issue on your end? If not, perhaps one of your teammates can try to replicate it from their end—this way, we can capture any error messages that appear in the logs.

    If you’re still unable to reproduce the issue but receive another report, please ask the user to include a screenshot of the error. That would be really helpful for our investigation.

    Thread Starter meganmasterson

    (@meganmasterson)

    Hi @d0153 ,

    I’m unsure of how to replicate the issue, other than replicating in our staging environment which we’ve done & tested debugging with. But yes I have a test role that is still receiving the error: https://ibb.co/VWpTnBn5
    This happens in both the staging and the production environments of wordpress. Thank you!

    Plugin Support tristan083

    (@tristan083)

    Hi @meganmasterson ,

    Thank you for your message and the information.

    When a “There has been a critical error on this website” occurs on screen, a corresponding error normally gets logged in the debug log for that message, which provides more information about the “critical error”. Would you be able to clear your log file, reproduce the “There has been a critical error on this website”, and then, check and send over the debug log file again?

    Thread Starter meganmasterson

    (@meganmasterson)

    Hi @tristan083 ! Thanks for bearing with me, I am relaying messages from our support side to get this info. Here’s what I was told to relay:
    https://ibb.co/m5sTgyh2

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the learndash-notifications domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/clientport1stg/wp-includes/functions.php on line 6121

    Deprecated: Creation of dynamic property PublishPress\Permissions::$default_advanced_options is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/publishpress/publishpress-permissions/classes/PublishPress/Permissions.php on line 186

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the presspermit-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /nas/content/live/clientport1stg/wp-includes/functions.php on line 6121

    Deprecated: Creation of dynamic property LearnDash_Notifications_Status_Page::$show_settings_page_function is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/learndash-learndash-notifications-40c18854865d/includes/admin/class-status-page.php on line 17

    Deprecated: Creation of dynamic property LearnDash_Notifications_Logs_Page::$show_settings_page_function is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/learndash-learndash-notifications-40c18854865d/includes/admin/class-logs-page.php on line 12

    Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 133

    Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 98

    Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 79

    Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 143

    Deprecated: Creation of dynamic property PublishPress\EDD_SL_Plugin_Updater::$beta is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/includes-pro/library/edd-sl-plugin-updater/EDD_SL_Plugin_Updater.php on line 50

    Plugin Support tristan083

    (@tristan083)

    Hi @meganmasterson ,

    Thank you for your message and the information.

    Unfortunately, I’m not finding anything from the logs you shared that would correlate to a “critical error” nor am I finding a log that relates to The Events Calendar plugin.

    At this point, I suspect there’s a conflict that’s causing the issue here. It would be good to test for conflicts. Kindly try to:

    1. Deactivate all other plugins except for The Events Calendar Plugins.
    2. And, switching to the Default theme.

    Please read the Testing for Conflicts Article before doing anything. 
    To be safe, we’d recommend conducting tests and updates on a Staging Server. Also, please keep a working backup of your website.

    Plugin Support Darian

    (@d0153)

    Hi @meganmasterson

    I hope all is going well for you. I noticed that it’s been a bit since we last heard from you. Have you had a chance to try the recommendation provided above?

    Thread Starter meganmasterson

    (@meganmasterson)

    Hi @d0153 , I relayed Tristan’s suggestion to my support rep to work through earlier this morning. Thank you for checking in!

    Plugin Support tristan083

    (@tristan083)

    Hi @meganmasterson ,

    Thank you for your message and the update.

    Please feel free to let us know how things went or if you have further questions/concerns.

    Plugin Support Darian

    (@d0153)

    Hi there,

    It looks like we haven’t heard back from you in a while, so I’ll go ahead and close this thread for now.

    If you still need assistance, feel free to reopen this thread or start a new one

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Critical Error for Some Users’ is closed to new replies.