michael-e
michael-e
> but we would gladly sent bad cache for our local files ;) AFAIK, we don't serve a cache file if the original local file has been **removed** (which is...
Like you, I am not fond of involving the database. So yes, your proposal sounds like a solution. (Documentation is king, of course.)
Cool. Tell us how it works in production!
I have only done a short test (looking at the debug headers), and it seems to work "as advertised". But I guess in this case your production environment is a...
IMHO, not sending cache headers does **not** mean that a response should not be cached. It means that the sending server doesn't care, so we can do whatever we like.
It does use `EventPostSaveFilter`! > `edit` is currently not supported on the Frontend What do you mean by this?
Yep. Thinking about it, the issue with the Reflection field is completely different from the [Hashid field](https://github.com/nathanhornby/hashid_field/issues/31). Not sure if I can dive deep into this...
> one has to include reflection field in the form to get its value updated via frontend event Yes, this is due to what I said in my initial post:...
Wouldn't it be better to automatically call the compile function (in all cases)? It simplifies things. See [my current pull request for the Hashid field](https://github.com/nathanhornby/hashid_field/pull/33).
I can put it on the list. But the list is very long, unfortunately...