Cache not invalidated after (un)publishing content

[vntw]

Hey there,

thanks for the bundle, it saves quite some time building custom content when the article bundle can't be used!

It seems like the content bundle doesn't take care of invalidating the HTTP cache when (un)publishing a content item. I assume this should be the case since it is for pages (using the \Sulu\Bundle\HttpCacheBundle\EventSubscriber\InvalidationSubscriber triggered by the \Sulu\Component\DocumentManager\DocumentManager). The article bundle also uses the DocumentManager so it should work there as well.

Is this sth. that should be done in a workflow subscriber in this bundle?

Steps

Reproduction: https://github.com/vntw/sulu-reproduction/tree/repro

This uses the sulu-skeleton (2.5 branch) with the example test application from the content-bundle.

1. Create example content
2. Open example content page once to propagate var/cache/common/prod/http_cache/
3. find var/cache/common/prod/http_cache/ -type f
4. Change example content and re-publish
5. find var/cache/common/prod/http_cache/ -type f
6. HTTP Cache is unchanged since no invalidation takes place, old data is displayed until you manually clear all website cache or (I assume) the configured cacheLifetime has passed