Breaking: #64200 - Custom [cObject].cache.* TypoScript evaluation
See forge#64200
Description
The std
property is now available as first-class function to all
content objects. This skips the rendering even for content objects that evaluate
std
after rendering (e.g. COA
).
Additionally, stdWrap support is added to key, lifetime and tags.
Impact
If you've previously used the cache.
property in your custom cObject,
this will now fail, because cache.
is unset to avoid double caching.
std
continues to exist and can be used as before. However
the top level std
of certain cObjects (e.g. TEXT
cObject)
will not evaluate cache.
as part of std
, but before starting
the rendering of the cObject. In conjunction the storing will happen
after the std
processing right before the content is returned.
Top level cache.
will not evaluate the hook
$GLOBALS
any more.
Affected Installations
All installations with custom c
implementations which make use of the cache.
property.
Installations that purposely rely on the content object being evaluated before the cache is tried.
Installations that rely on the order of the cache.
evaluation.
Installations that make use of the hook
$GLOBALS
on top level cache.
.
Migration
Rename your property or rely on the Core implementation.
If you need cache.
being evaluated as part of std
, please move it down one level
by writing std
instead.
If you used the hook
$GLOBALS
,
please use std
and the available hooks inside std
to achieve your goal.