You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
Currently, GatherPress stores datetimes and timezone to a custom table which is used to query events in a scalable way. This change is to ALSO store this data as post meta so it is more easily accessible to developers and in the API. We can use the same approach of pseudo post meta illustrated in this ticket #560
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
This sounds interesting, but I wonder if you really want to STORE the data in a second place or just make it available through the common APIs, post_meta for example?
@carstingaxion yeah, i was thinking that. the approach you illustrated in #560 for getting data from other places via post meta filter could suffice here.
I agree. One thing to keep in mind is, in opposite to #560, we need to make sure that meta revisions are disabled for that. Otherwise we could ran into out-of-sync issues with the custom db table.
I agree. One thing to keep in mind is, in opposite to #560, we need to make sure that meta revisions are disabled for that. Otherwise we could ran into out-of-sync issues with the custom db table.
Is your enhancement related to a problem? Please describe.
Currently, GatherPress stores datetimes and timezone to a custom table which is used to query events in a scalable way. This change is to ALSO store this data as post meta so it is more easily accessible to developers and in the API. We can use the same approach of pseudo post meta illustrated in this ticket #560
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: