-
Notifications
You must be signed in to change notification settings - Fork 9
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
Year is stored as "Y" instead of the actual year #7
Comments
I'm seeing the same thing. It's being saved as:
This might be related to this bug? CMB2/CMB2#300 In addition, although the value is stored, it doesn't display in the metabox after saving the post. |
Ditto. Seeing the same. |
Since this plugin appears to be broken and unsupported I thought I'd share a work around I've used.
then add this JS to run on your admin pages
|
@jtsternberg Thanks for submitting a fix for this. I have already implemented another solution but may come back and test it out if I get time. Appreciate you supporting this plugin - sorry if my comments offended. |
No offense taken. It's been over a year since this was reported, and you provided a workaround, so your comments were both truthful and helpful. That's what open source is about. Unfortunately, sometimes things get abandoned or neglected. |
Not sure if I'm doing something wrong but when defining the field as:
This is what gets saved to the database:
a:2:{s:5:"start";s:6:"9/28/Y";s:3:"end";s:7:"10/31/Y";}
i.e. the year is saved as "Y" instead of the actual year
The text was updated successfully, but these errors were encountered: