WPMJ – submit button after navigating from single job listing

  • Resolved klnfln

    (@klnfln)


    5 months, 2 weeks ago

    hello! it will be a quick one

    Why submit button after navigating to a single job listing and back is not doing any action? If you don’t do this scenario or navigate to and back with any other page it fires /get-listings.. u have to edit something in filters or reload the page in order for it to fire again if coming back from a single job listing.

    is there a fix to this?

    thanks!

    • This topic was modified 5 months, 2 weeks ago by klnfln.
    • This topic was modified 5 months, 2 weeks ago by klnfln.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Deric (a11n)

    (@dericleeyy)

    5 months, 2 weeks ago

    Could you elaborate further on the use case for your site? Could you provide an example on how this issue can be replicated?

    Thread Starter klnfln

    (@klnfln)

    5 months, 2 weeks ago

    Hi @dericleeyy , absolutely. I created a local-hoste website from scratch to ensure it is not conflicting with other customization while replicating. Sorry if I use incorrect terminology or overlook something.

    When I visit the output of the [jobs] shortcode, clicking the search submit button triggers the following events on each click:

    1. A request to /jm-ajax/get_listings/ is fired.
    2. This also triggers a request to /wp-content/plugins/wp-job-manager/assets/dist/images/ajax-loader.ea183bf2.gif.
    3. All job listings are re-populated.

    These events occur under the following scenarios:

    • Clicking the search submit button.
    • Reloading the page.
    • Navigating away and returning to the page.
    • Using any of the filters.

    The Issue:

    However, when I navigate in this specific way:
    1. [jobs] (http://getlistingsdebug.local/jobs/) → 2. A single job listing (http://getlistingsdebug.local/job/test-test-2-test/) → 3. [jobs] (http://getlistingsdebug.local/jobs/) including navigating through any other pages in between 2. and 3. steps:

    The events described above do not fire as they normally would when reloading the page or arriving from any other page. Specifically:

    1. The search submit button does not trigger the events and does nothing.
    2. The events only begin firing after a filter is changed or the page is reloaded, or I navigate back and forth one more time using browser navigation.
    3. Once the events are triggered (e.g., by changing a filter), the search submit button starts working as expected again.

    Thanks!

    Plugin Support Cara

    (@dcka)

    5 months, 1 week ago

    @klnfln So far, I have not been able to replicate the behavior you describe. In my tests, which follow the steps you shared, I am able to search as expected.

    Can you clarify step 2, however? Are you pressing the “Back” button on your browser to return to http://getlistingsdebug.local/jobs/? Or are you clicking the “Jobs” link in your menu again? Please feel free to share more details to help us replicate the issue.

    Thread Starter klnfln

    (@klnfln)

    5 months, 1 week ago

    @dcka Hi

    I recorded a video of replicatingi the issue. In case you are unable to preview it embedded here, I am sharing the link as well: https://vimeo.com/1046343097/a6c2782446?ts=0&share=copy

    To specify further, once I use job filters the submit button works again, it does not re-populate jobs without it however.

    Plugin Support Jay

    (@bluejay77)

    5 months, 1 week ago

    Hi @klnfln,

    Thanks for sharing that video recording. I see what you mean, and I was able to reproduce the issue on my end.

    Would you confirm if you’re using any WP Job Manager Core Add-ons by chance? We’ve had a report like this from users on Job Tags add-ons, so I wanted to double check.

    Thread Starter klnfln

    (@klnfln)

    5 months, 1 week ago

    hey @bluejay77

    I am not using any WP Job Manager add-ons at all, I am planning to upgrade later, but this issue persist without any other add-ons and also on a test page without any other plugins or other type of customization installed.

    As of now I use a workaround of simply opening single job listings in a new tab.

    • This reply was modified 5 months, 1 week ago by klnfln.
    Plugin Support Jay

    (@bluejay77)

    5 months, 1 week ago

    Hi @klnfln,

    Thanks for confirming. I have reported this issue to our development team. We don’t have an ETA on the fix, but please be assured that it’s on our team’s radar. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.