Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expiration date picker on a job listing won't save #2518

Closed
kevindherman opened this issue Mar 18, 2024 · 6 comments
Closed

Expiration date picker on a job listing won't save #2518

kevindherman opened this issue Mar 18, 2024 · 6 comments

Comments

@kevindherman
Copy link

Source

Describe the bug

Expiration date picker on a job listing won't save.

To reproduce

Steps to reproduce the behavior:

  1. Go to ['...'](https://www.montgomeryohio.gov/wp-admin/post.php?post=22348&action=edit)
  2. Use date picker in "Listing Expiry Date" field in "Job data" section
  3. Update
  4. "Listing Expiry Date" field is empty once the update loads

Expected behavior

The expiration date should be saved. Job listing should expire after set date.

Screenshots

Screenshot-2024-03-18-110145

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context

Add any other context about the problem here.

QA

Notes:

Links:

@curtismchale
Copy link
Contributor

@kevindherman the date does save it just doesn't show due to a bug in WP Job Manager which I reported here: https://wordpress.org/support/topic/expiration-date-not-visible-in-admin/

There is nothing for me to fix.

@kevindherman
Copy link
Author

@curtismchale since this is closed. Do you think something like this would get resolved with one of their plugin updates?

@curtismchale
Copy link
Contributor

@kevindherman yes. It's a bug between WordPress and their JavaScript so every user that uses this plugin should be seeing the same issue.

I can keep checking back on the bug report if you want but outside of me hacking their plugin I don't see a way to contribute back to the plugin outside of adding my code to the support item I raised. If I start running a custom version then we have to keep maintaining it and that's more work I don't need.

They've had 3 releases in 2024 already so I wouldn't expect the issue to stay around too long, though it may not be fixed next week.

@kevindherman
Copy link
Author

@curtismchale thank for the clarity.

Lets just keep an eye out for this item in their releases and if you can flag when you do our release notes that would be perfect.

@curtismchale
Copy link
Contributor

They say this has been fixed now but version 2.2.3 hasn't been rolled out yet so we're still waiting.

@kevindherman
Copy link
Author

@curtismchale super helpful. Thanks for the update.

I passed along to the customer since they're interested in this stuff.

Fingers crossed they roll out the version soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants