Glitches during job entry since last update

Hi! It sounds to me like possibly the site might be running out of memory for those users? On the off-chance that that’s the problem, try increasing the memory available to WordPress:

https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/

If that doesn’t solve it, check for errors in the console when they add the jobs:

https://en.support.wordpress.com/browser-issues/advanced-browser-troubleshooting/#javascript-errors

If you don’t find anything obvious there, let’s have a look at some error logs. Could you add the following code to your site’s wp-config.php file?

define('WP_DEBUG', true);

if ( WP_DEBUG ) {
?
????????@error_reporting( E_ALL );
????????@ini_set( 'log_errors', true );
????????@ini_set( 'log_errors_max_len', '0' );
?
????????define( 'WP_DEBUG_LOG', true );
????????define('WP_DEBUG_DISPLAY', false);
????????define( 'CONCATENATE_SCRIPTS', false );
????????define( 'SAVEQUERIES', true );
?
}

Once you’ve done that, navigate to your site, try adding a job as you mentioned, and then check the?wp-content/debug.log?file for error messages.

If there are any errors, post them here (taking care to remove any private information such as root directory names and so on), and then replace:

define('WP_DEBUG', true);

… with this:

define('WP_DEBUG', false);

… in your wp-config.php file.

Lastly, note that even though you have been adding jobs from the back-end, WPJM has always been designed with front-end job listing in mind, as that’s where we do the proper field validation:

https://wpjobmanager.com/document/adding-jobs-via-admin/

Hi! After I submitted my post I found another post that referenced rolling back to a previous version of WP Job Manager, which is what I decided to do as we did not have the issues described above on the previous version. I think the most recent updates to WordPress and WP Job Manager are just not compatible. I installed WP Rollback, which is a pretty good plugin to have anyway, and rolled back WP Job Manager to version 1.31.3 and now the plug in works like it used to. I understand the way we use the plug-in (only from the back end) may not be what was intended but it works for us – at least for the time being.

As for the instructions you provided above, I really don’t have any idea where to find the wp-config.php file. I’m a business owner – not a coder. That’s why we use WordPress – it’s supposed to be EASY! I am hoping that future updates to the plugin will address the conflict indicated above. I also installed a test site plugin that I can use to try out the updates before I install them. Ha! Maybe I’m a little techie after all ??

Hi Diana!

Testing updates is always a good idea, especially if your business relies on certain plugins. So, good on you for doing that! ??

As for the incompatibility, the plugin *is* actually compatible with the latest version of WordPress. However, there were some changes made in 1.32 which caused problems with some themes and plugins that rely on WPJM. I don’t know which of those you might be using on your site, but it would be a good idea to update your theme if there’s an update available. But, like you said, test the update first! ??

I’ll leave this thread as Unresolved for now. If you are able to figure out what plugin is causing the problem, or if it’s the theme, come back and let me know!

I’m marking this thread as Resolved as it’s been more than a month since the last reply. If you still need help, please do reply again and mark the thread as Unresolved!