critical error on user’s backend

yes but WPJM has been running together with wyz-toolkit for some years, so I wasn’t expecting any breaking like this. Maybe it’s better you tell me if you have made some big changes to the code/templates. My theme is not being updated by the developers so I’m stuck.

For critical errors, could you enable WP Debug https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/#example-wp-config-php-for-debugging and check the error logs for the exact errors that are causing the critical error on the site?

I keep seeing nothing related to WPJM. I have this error:

PHP Deprecated: Function create_function() is deprecated in /…/wp-content/plugins/code-snippets/php/snippet-ops.php(582) : eval()’d code on line 11

but disabling “code snippet” doesn’t prevent the critical error from appearing. I cannot pinpoint the problem.

Hi @devsaredead,

Based on what you’ve shared so far, the errors appear to be server or plugin related to the customization of your site.

Since this is a site-specific setup that we cannot reproduce on our end, we’re unable to help you.

If you can reproduce the errors on a new WordPress install and WP Job Manager core plugin (with other plugins disabled), please let us know and we’ll take a closer look.

If you believe there’s a plugin compatibility issue, please reach out to your plugin developer for further assistance.

You can submit an enhancement request on our GitHub repository like these:

https://github.com/Automattic/WP-Job-Manager/labels/Third-party%20Conflict

You can submit a feature request here (you’ll need a free GitHub account to submit a request):

https://github.com/Automattic/WP-Job-Manager/issues/new?assignees=&labels=%5BType%5D+Enhancement&projects=&template=Enhancement.md&title=

Thank you for your time but, again, I reckon there are no conflicts with other plugins. The error appears only when I enter the user-dashboard, but the core plugin running that has not been updated for quite a long time. I always updated WPJM and never got this error, only with 2.3.0. I have also recreated a new staging site, but the problem persists.

I wouldn’t know how to get support from Github because it’s for developers.

Hi @devsaredead!

Following up on the error details, it seems like we did make a mistake with the latest version — the function that wyz-toolkit uses was moved to a new class and removed from the old one, instead of being marked as deprecated. We’ll include a fix in the next patch release to make sure this change is backwards compatible.

Eventually, wyz-toolkit will have to update their WP Job Manager integration, so do reach out to them as well as there might be other changes that affect the integration. The current issue is caused by this change:

WP_Job_Manager_Shortcodes::job_dashboard_handler has been moved to \WP_Job_Manager\Job_Dashboard_Shortcode::handle_actions

I’m glad my issue has helped you spot a mistake. Once the fix is released I hope I will be able to amend the class on my own (maybe it will just be a matter of changing some words) because wyz-toolkit is currently not being upgraded by the developers. I will let you know what happens after the fix.

That sounds like a plan @devsaredead. Thanks again for reporting and troubleshooting with us!

Following up on the error details, it seems like we did make a mistake with the latest version — the function that wyz-toolkit uses was moved to a new class and removed from the old one, instead of being marked as deprecated. We’ll include a fix in the next patch release to make sure this change is backwards compatible.

Hello, I was hoping you had fixed the class, but you have now released a new update and I still get an error when going to the user’s dashboard. I guess you have overlooked it. Can you please fix it?

Hi?@devsaredead!

Thanks for reporting that the user dashboard error persists after the update.

We do have an open issue for this problem on GitHub: https://github.com/Automattic/WP-Job-Manager/issues/2824

To help us investigate further, we recommend continuing the discussion directly on the GitHub issue. You can share any additional details about the error you’re encountering. Any updates will be posted on the GitHub issue.