This thread is resolved. Here is a description of the problem and solution.
Problem:
If you set up a View with a filter using a date field and subsequently want to change the date, the month trips back to 01-Jan when you select Edit and has to be changed every time. t's still a UNIX timestamp that is saved to the database.
I want to display posts based on a custom (date) field. There seems to be two ways of achieving this in the query filter section (please refer to the two screenshots provided).
Can you confirm what the difference is between the two filters or are they essentially the same? Is using the timestamp perhaps more efficient or better for resources?
Both are producing the expected results but I'd appreciate clarification please.
Thank you for contacting Toolset support. Yes these are wyo ways and you can use any of these. I think DATE option is better since its easier to read as well and its what we normally use for Date filters.
Many thanks for clarifying. I assume that even if DATE is used, it's still a UNIX timestamp that is saved to the database? Can you confirm please?
I do agree that using DATE is easier as the format is instantly understandable however I've noticed a small but niggling issue. If you set up a View with a filter using a date field and subsequently want to change the date, the month trips back to 01-Jan when you select Edit and has to be changed every time. I did prepare a video for you but I can't upload it - sorry!
Can you confirm you're able to replicate this please?
Yes you are correct, dates are stored as UNIX timestamp.
For the issue, I am not clear on it exactly. Can you please upload video to google drive or dropbox and share the link here, I have enabled private reply box now.
OR provide step by step screenshots of the issue so I can see and reproduce it.
Thanks for sending video. I am able to reproduce this issue at my end, when I set the date (to a past date or today). I have escalated this issue to our 2nd tier support for further review and we will get back to you with an update.
Just wanted to send an update, that this issue is fixed and will be released in the upcoming Views version. Once new Views version comes out, you can update all Toolset plugins to latest versions and confirm that this issue is fixed.