Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go_maps_ext falsely declared as "not cachable by Typo3 frontend" #52

Closed
the-hotmann opened this issue Feb 3, 2019 · 0 comments
Closed

Comments

@the-hotmann
Copy link

This Issue is related to the use of go_maps_ext combined with staticfilecache.
When I create a page with a Google Map in it, the page will be declared as not cachable and is beeing slow.
This is most probably related to this extension as it is somewhere declared as not cachable.
But as far as I see it could be cachable just by "not declaring it as not cachable" as allways the same html/css/js is getting fired out.

A workaround is: forcing staticfilecache to cache it, but this will break a lot of other things.
Much cleaner solution is to not declare go_maps_ext as not cachable and let it cache its html staticly.

Would love to see this extension beeing compatible with staticfilecache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant