WP Job Manager plugin review and common issues

The job board requires a page with the [jobs] shortcode. Check: (1) in WP Job Manager → Settings → Pages, verify the Job Listings page is assigned — this should be a page containing [jobs]; (2) if the raw shortcode is visible, the WP Job Manager plugin is not active or the page was not saved correctly; (3) verify the page uses the default page template (not a blank template that ignores post content); (4) create a new page, add [jobs] as the only content, and assign it in WP Job Manager → Settings → Pages.

Published job listings should appear in search. If they do not: (1) check if the listing has expired — newly approved listings should have a future expiry date, not a past one; (2) verify the listing’s job category and type are not filtered out by the default search parameters; (3) check if the listing was approved but has a scheduled future publish date instead of immediately published; (4) clear all caches; (5) verify the listing post type is included in WordPress search — use a test search for a unique word in the listing title.

WP Job Manager sends notifications via WordPress wp_mail(). Configure: (1) WP Mail SMTP with a reliable SMTP provider for transactional email; (2) in WP Job Manager → Settings → Email Notifications, verify notifications are enabled and recipient emails are correct; (3) test WordPress email function independently; (4) check spam folders for notification emails; (5) the application email requires the Application extension for candidate application emails.

The WP Job Manager Paid Listings extension integrates with WooCommerce. After installing: (1) create WooCommerce products for listing packages (Basic $29, Featured $79) — each product corresponds to a job listing package with different features (duration, highlighted status, number of listings included); (2) configure the package features in WP Job Manager → Paid Listings Settings; (3) when an employer submits a job, they are presented with package selection before the submission form; (4) after WooCommerce checkout, the listing is created with the package’s features.

WP Job Manager custom fields require either: (1) the WP Job Manager resume/field extensions; (2) a code-based approach using the job_manager_job_listing_data_fields filter to add custom fields to the submission form and display. Example: add_filter(“job_manager_job_listing_data_fields”, function($fields) { $fields[“_job_salary”] = array(“label” => “Salary Range”, “type” => “text”, “placeholder” => “e.g. $50,000-$70,000”, “listing_side_only” => false); return $fields; }); The custom field appears in both the front-end submission form and the listing detail page.

Resume management requires the WP Job Manager Resume Manager extension. The free core provides an application form (basic contact + message) but not full resume profiles. The Resume Manager extension adds: candidate registration, detailed resume profiles (work history, education, skills), resume search for employers, application management dashboard, and resume alerts. For a complete recruitment platform with both employer and candidate sides, the extensions bundle provides all necessary functionality.

WP Job Manager has its own application form system. Integration with WPForms or Gravity Forms is possible using community-developed add-ons or custom code that hooks into the WP Job Manager application submission process. The approach typically involves creating a WPForms/Gravity Forms form and connecting it to a WP Job Manager listing using hooks. For complex multi-step application forms with advanced conditional logic, using a capable form plugin as the application layer provides more flexibility than WP Job Manager’s built-in application form.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.