1. Home
  2. Web Host Known Issues

Web Host Known Issues

This page covers some known issues with various web hosts.

Flywheel Matador Jobs Known Issues

Matador Source Tracking “Fallback” Will Fail

Flywheel filters utm_* variable values from the PHP layer to simplify page caching. The do-not-track/disabled javascript/no javascript fallback for Application Source tracking will not work. The “fallback” relies on the “PHP layer” being able to read utm_* variables. While this is a backup for the less than 3% of the users who don’t allow tracking or disable javascript or use devices that don’t support javascript, this means that all of those users will be tracking in Matador as “Direct/None” users.

Matador Jobs All-Access Extension XML Feeds Customized Campaign

Also due to the utm_* variable filtering in the PHP layer, Customizing Campaign variables in the XML Feeds Extension will not work using the primary method.

We suggest the following work-arounds:

WPEngine Matador Jobs Known Issues

WPEngine is a force in the Managed WordPress hosting community, and we see more than 1 in 6 of our users are on WPEngine. WPEngine is a stable, reliable host for Matador Jobs, but there are a few things to be aware of when deploying Matador Jobs on WPEngine.

Please note, even though there are several known issues, we do not want to give the impression that we do not support WPEngine as a viable host for Matador Jobs. In fact, we love WPEngine and fully support your use of them to host your Matador Jobs powered website when you have fewer than 300 jobs active, on average.

Slower Matador Jobs Performance for Uncached Routines

WPEngine delivers speed mainly through aggressive caching. This means that routines that Matador must run that cannot be cached, like processing applications and modifying settings run with a slower-than-expected level of performance.

We suggest the following work-arounds:

  • Use “Submit Applications in the Background (Slower)” setting for “Sync Applications to Bullhorn” option to provide a faster application response for users. The “slower” part in that setting explains the speed to which the application gets to Bullhorn, and is actually a speed improvement for the applicant.
  • Otherwise, allow for additional patience during Matador Jobs settings page loads in the WP Admin, which is not cached.

More Instances of “Bullhorn Sync Failed” Error Notices

WPEngine, like many hosts, employ a “Kill Long Processes” rule on their servers. That means that when a code routine is running, like Matador Jobs, it if runs too long, it is stopped.

On WPEngine, the combination of an industry-standard 15-second kill long processing PLUS the lower system resources for non-cached routines (see above) means that more of Matador’s Bullhorn calls can fail before they are completed. This results in above-average appearances of “Bullhorn Sync Failed.” These are most common when doing initial syncs upon install or “Full Syncs.”

We suggest the following work-arounds:

  • When initially installing Matador Jobs, allow multiple sync cycles to download all your jobs, especially if you have more than 200 jobs.
  • Avoid using the “Full Sync” button to re-sync job data. Republish Jobs and/or use “Sync This Job” from the job’s edit page to force a data update. Allow multiple sync cycles to download all updates when forcing a “Full Sync”, especially if you have more than 200 jobs.
  • Note that changing some settings, including ones that affect Description, Title, Category, Location, and URL Slugs will require a “Full Sync”. Allow multiple sync cycles to download all updates when expecting a “Full Sync”, especially if you have more than 200 jobs.
  • Do not panic when seeing a “Bullhorn Sync Failed” warning. This may happen when the long process killer kills a Matador routine. Matador is built to recover, and in most cases, will pick up where it left off on the next attempt.

Matador Source Tracking “Fallback” Will Fail

WPEngine filters utm_* variable values from the PHP layer to simplify page caching. The do-not-track/disabled javascript/no javascript fallback for Application Source tracking will not work. The “fallback” relies on the “PHP layer” being able to read utm_* variables. While this is a backup for the less than 3% of the users who don’t allow tracking or disable javascript or use devices that don’t support javascript, this means that all of those users will be tracking in Matador as “Direct/None” users.

Matador Jobs All-Access Extension XML Feeds Customized Campaign

Also due to the utm_* variable filtering in the PHP layer, customizing campaign variables in the XML Feeds Extension will not work using the primary method.

We suggest the following work-arounds:

GoDaddy Managed WordPress Known Issues

GoDaddy is one of the most well-known domain registration providers in the world, and as such, many users sign up for their add-on hosting services. The GoDaddy Managed WordPress product, unfortunately, was designed for more personal and small business use and our software needs more from its web host. Our users on GoDaddy Managed WordPress commonly see any/all of the following issues:

Error 429 Too Many Requests

For an unknown reason, manual syncs will trigger a 429 Too Many Requests error.

Error 504 Gateway Timeout

For an unknown reason, automatic syncs will fail due to 504 Gateway Timeout errors.

Late Matador Cron Tasks

For an unknown reason, GoDaddy’s Managed WordPress interrupts WordPress Cron, which is the automation system Matador Jobs and other plugins use to manage any automation.

There is a partial solution by instructing your WordPress to use WordPress Alternate Cron. This can be done by adding the following line to your wp-config.php file:

define( 'WP_ALTERNATE_CRON', true );

Unfortunately, this doesn’t fix the two previously mentioned issues and it introduces incredible loading delays on the site as a whole. Alternate Cron runs all the heavy Matador Jobs automation while the person loading the site waits for it to complete.

Our Opinion: Don’t Use Go Daddy Managed WordPress

We love GoDaddy! We use GoDaddy to register our domains and we share a home city and state with GoDaddy. Matador Jobs co-owner Jeremy even has friends who work at GoDaddy. We’ve reached out and the consensus at this time is that the GoDaddy Managed WordPress Product is not designed for Matador Jobs user’s and we strongly recommend other providers.

Updated on February 23, 2021

Was this article helpful?