toumoro / tm_cloudfront

This is the official repository of the TYPO3 extension tm_cloudfront. This extension clears the AWS CloudFront cache based on the speaking path of a page by creating an AWS CloudFront invalidation queue based on clearCacheCmd.

TYPO3 Extension tm_cloudfront

This extension clears the AWS CloudFront cache based on the speaking path of a page by creating an AWS CloudFront invalidation queue based on clearCacheCmd.

tm_cloudfront's Issues

TYPO3 10.4: Error when invalidating cache

I tried the extension on TYPO3 10.4.20 and if I hide an entry from the News extension I get the following error>:

TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given.

The error goes away, if I deactivate the tm_cloudfront extension.

Tested with extension v1.0.7.

TYPO3 11 Compatibility

Is a compatibility for TYPO3 11 LTS planned?

Invalidating caches for news extension pages

Are there any known problems when the extension is running in combination with the news extension?
Currently my cdn cache for the news detail page is not cleared when a news entry is edited :-(
(Typo3 Version 11)
I would be very happy to receive a helpful answer.

Ideas on invalidation optimization

Well, I have some ideas how the invalidation costs can be decreased a lot.
Also the CDN contents will stay faster most of the time because there is a lot of more caching and less warming up again :-)
I have managed to implement some of the things in my local enviroment but I cannot say if these changes would work in all possible enviroments. Complicated to say because of single- or multi-site configurations, single- or multi-domain settings, language fallbacks, detailed language configurations and so on.

Here are my suggestions:
-Invalidate only the caches of pages in languages, which are activated (active site languages, not page languages). Currently all are invalidated also for inactive languages.
-Invalidate only caches of the site, which contains the changed page. I managed to get this running by adding a typoscript snippet on each top level site which only contains a single distribution id. Before all in the backend configured distributions got invalidations for a change on a page of one site.
-Invalidate the page cache only for the current language if the content element is in a specific language and not in "All languages".
Othervise clear all language urls for this page.
-Invalidate the page cache only for pages which are not hidden.

We have a few hundred pages and a just a few editors but the invalidations are exploding a bit. Hopefully this can help someone.