Hi,
The Checkin & Publish workflow for stories that already exist on the
production server is causing files to be generated with their originally
published timestamp.
Since we use a little bit of Mason on the production server to
dynamically tie components together this causes problems: the Mason
cache on the production server reads the same old timestamp, doesn't
invalidate the cache and we see the old content instead of the newly
published content.
Republishing said stories generates files with new timestamps but this
is a two-step process where we would ideally prefer one.
What are other people doing to get around this kind of problem? Is
there a way for the Checkin & Publish workflow to generate files with
newer timestamps?
Thanks,
Matt
--
Matt Adams
Radical Dynamic
www.radicaldynamic.com
The Checkin & Publish workflow for stories that already exist on the
production server is causing files to be generated with their originally
published timestamp.
Since we use a little bit of Mason on the production server to
dynamically tie components together this causes problems: the Mason
cache on the production server reads the same old timestamp, doesn't
invalidate the cache and we see the old content instead of the newly
published content.
Republishing said stories generates files with new timestamps but this
is a two-step process where we would ideally prefer one.
What are other people doing to get around this kind of problem? Is
there a way for the Checkin & Publish workflow to generate files with
newer timestamps?
Thanks,
Matt
--
Matt Adams
Radical Dynamic
www.radicaldynamic.com