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
was a ZMS5-backport that was introduced in 2020 to allow a preview_time_travel to check activity-controlled content changes in time and providing a way to explicit http header cache control by the request variable ZMS_CACHE_EXPIRE_DATETIME : https://github.com/zms-publishing/ZMS/blob/main/docs/develop_api_exampels_en.md#4-set_response_headers_cache
According to the wishes of some extensive users the content timing (caching) should be precise in time and not just daily intervals like before:
dt.isFuture() or (dt.equalTo(dt.earliestTime()) anddt.latestTime().isFuture())
As a side effect, now, an activity-ending date has to be given cannot be given as date, exp: 01.02.2022, because this is considered as
01.02.2022 00:00:00
but as datetime. exp:
01.02.2022 23:59:59
n
The text was updated successfully, but these errors were encountered:
The latest Change (12/2021) on _objattr.isActive()
ZMS3/_objattrs.py
Lines 748 to 794 in 95f5905
was a ZMS5-backport that was introduced in 2020 to allow a
preview_time_travel
to check activity-controlled content changes in time and providing a way to explicit http header cache control by the request variableZMS_CACHE_EXPIRE_DATETIME
:https://github.com/zms-publishing/ZMS/blob/main/docs/develop_api_exampels_en.md#4-set_response_headers_cache
According to the wishes of some extensive users the content timing (caching) should be precise in time and not just daily intervals like before:
As a side effect, now, an activity-ending date has to be given cannot be given as date, exp: 01.02.2022, because this is considered as
01.02.2022 00:00:00
but as datetime. exp:
01.02.2022 23:59:59
n
The text was updated successfully, but these errors were encountered: