ajax-filters.min.js “Bad Request” on WPML secondary/tertiary language

  • Resolved magicalbjorn

    (@magicalbjorn)


    5 years, 11 months ago

    Goodday one and all!

    I have been working on a WordPress Multisite instance for a while now, and recently added the WP Job Manager plugin to help with creating a “vacancy” website. The plugin would allow us to add job listings, which visitors to our website can view and respond to.

    I have run into an issue though; adding a job in the admin panel, including the translated variants of it works great. I can view the list of jobs fine, in the primary language (NL), but when changing to the other languages (EN and FR), the spinner keeps on spinning, never loading the jobs. In the browser console, I see an error with the “ajax-filters-min.js?ver=1.31.3” file. “error: Bad Request” it says.

    I have scoured the internet for some solutions, including:
    – Disabling debugging in wp-config.php
    – Disabling all plugins, except WPML and WP Job Manager
    – Using the default Twenty… theme

    I’ve also tried modifying the permalink settings, WPML settings for translations and even default WordPress Multisite settings.

    All of this without much avail.

    I have also tried disabling WPML alltogether, which results in the job list being filled with all jobs in all languages, but this is not the expected result.

    I can, however, go into the job details in the primary language, and then switch language. The job details is then correctly shown. But, once again, if I go back to the job list on the non-primary languages, there’s the infinite loading and error again.

    I would like to ask some assistance with this issue. I’m still working on this issue in a local development environment, so it is not accessible outside my PC.

    With kind regards,
    Bj?rn Broer

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hey @magicalbjorn,

    Interesting! Thanks for your thorough attempts at troubleshooting already. Previously, when we’ve seen this issue, the theme was the culprit — its possible that footer.php isn’t calling wp_footer(). WP Job Manager needs wp_footer() to call the ajax javascript for get_listings.

    However, since you tried using a default theme, and the problem persisted, that’s not the case, here. The addition of WPML complicates the issue a bit. Which theme are you using?

    One thing stands out:

    adding a job in the admin panel

    We recommend that all jobs are added via the frontend form on your site, on the page where you’re using the [submit_job] shortcode. Several verification steps are not taken when adding a job via the Job Listings > Add New path in wp-admin. Just to rule it out as a problem, can you please try adding a job listing through the frontend form, and see if the issue persists?

    Also, when you used the default theme, were plugins (except WPJM and WPML) deactivated at that time as well?

    Looking forward to hearing back from you.

    Thread Starter magicalbjorn

    (@magicalbjorn)

    Goodday @jenhooks,

    I am using the “Customify” theme by default. This theme has the customisability requested by requirements. Also, another requirement is that jobs be added via the admin panel, not by users in the front-end. Despite this, I did try to add a job via the front-end, which was successful, but still the list remains empty, with the error message in the console.

    I have re-tested the job manager with the default theme and all but it and WPML disabled. Even with no job listings added, it gives the error.

    With kind regards,
    Bj?rn Broer

    Thread Starter magicalbjorn

    (@magicalbjorn)

    @jenhooks Do you have any update on the issue?

    Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hi @magicalbjorn,

    Very sorry for the delay getting back to you on this!

    I did some deeper digging, and I’m fairly certain what you’re reporting is the same as what we have reports of here:

    https://github.com/Automattic/WP-Job-Manager/issues/1176

    The short version is that this is something going wrong with WPML — have you made contact with them yet?

    Thread Starter magicalbjorn

    (@magicalbjorn)

    Hey @jenhooks,

    No, I have not yet made contact with them. I took a look at the GitHub link you’ve sent, but I’m not sure the issue is the same. I have created a screenshot with the logged errors:

    https://imgur.com/So1bFKF

    I shall also contact WPML to see where the issue could be exactly, but so far no successes.

    With kind regards,
    Bj?rn Broer

    Plugin Contributor Richard Archambault

    (@richardmtl)

    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!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘ajax-filters.min.js “Bad Request” on WPML secondary/tertiary language’ is closed to new replies.