Latest version of SDWebImage allows app to override its rigorous caching mechanism and honor HTTP Cache headers with this flag - SDWebImageRefreshCached but its not available in older versions. Is it possible to do the same with older version 2.7.4?
Thx
This is not really an answer to the question but it did solve my problem. Looking more into the code I found that the images are not cached for ever. The api uses maxCacheAge to expire the cache and clear the images and this is set to 1 week by default. In 2.7.4 this value can not be modified but I believe it can be in later versions. in case this helps someone.
static NSInteger cacheMaxCacheAge = 60*60*24*7; // 1 week
Related
I am migrating from spring data ES 4.1.15 to 4.4.1. The old code has below
ElasticsearchRepository.save()
ElasticsearchRepository.refresh()
What should I use to replace refresh?
Nothing. This was changed in version 4.2 (released in April 2021) and is described in https://docs.spring.io/spring-data/elasticsearch/docs/current/reference/html/#elasticsearch-migration-guide-4.1-4.2.breaking-changes.
Doing a refresh is automatically done in repository methods, unless the user explicitly defines a refresh policy.
I updateted to the latest tx_news Version 9.0. Since the ViewHelper <n:widget.paginate> are no longer supported as of TYPO3 11, I have changed the pagination template as recommended. Unfortunately, so the setting of the maximum links no longer works: settings.list.paginate.maximumNumberOfLinks = XYZ Is there a workaround for this?
Screenshot of cropped pagination
Thanks and best regards
Michael
If you want to use settings.list.paginate.maximumNumberOfLinks, class GeorgRinger\NumberedPagination\NumberedPagination is required.
You can use the following extension (beta) by Georg Ringer:
https://extensions.typo3.org/extension/numbered_pagination
We are adding version in the url for making our application backward compatible.
We have an url version: {mysite}.com/v1/author/id
May be in the next version of the app we may use something like this - {mysite}.com/v2/contributors/author/id
In order to support old url format in the new app, we are adding version in the url. By using the version in the path, we will know the url format and handle accordingly.
Is this the best way to do this or is there any other recommend approach for this?
I prefer React Router(Navigate to specific file/folders) on the version differentiation , if your both version is managed in same repository.
Explanation
I'm having an issue with Workbox where my website doesn't update when a file's content is changed, unless I manually clear storage/site data in my browser.
Since v4 release this year, the cleanupOutdatedCaches, which is in my code, should take care of this, but the problem persists.
Example
I created this website to exemplify. Once you access it, Workbox will install the service worker, but if I change, for example, test1 to test2, you won't see the change, unless you clear the site data in your browser and refresh.
I also tried only unregistering the sw; it shows the updated version (test2), but when refreshing twice it goes back to the old version (test1).
You can see the website's code in GitHub here.
Thanks in advance,
Luiz.
cleanOutdatedCaches will only clean caches created by older versions of the workbox library. In this case, since you are using the same version fo workbox, the call to this method does nothing.
https://developers.google.com/web/tools/workbox/reference-docs/latest/workbox.precaching#.cleanupOutdatedCaches
Once a particular file is precached by Workbox, it will never attempt to retrieve that file from the network, unless the revision you have specified in the precacheAndRoute call is different from what was previously cached.
Since you changed index.html but not the revision in precacheAndRoute, workbox assumes the file is unchanged. So,what you need to do is to update the precacheAndRoute with a new hash that corresponds to the new version of index.html
You can achieve this by either using injectManifest
https://developers.google.com/web/tools/workbox/modules/workbox-build
or any other build tooling you use.
Edit:
You can invoke skipWaiting programmatically as well
https://developers.google.com/web/tools/workbox/modules/workbox-core#skip_waiting_and_clients_claim
But you do need to use it with caution. Here is one way to do it :
https://developers.google.com/web/tools/workbox/guides/advanced-recipes
This is a feature request, from link below seems like no other workaround yet but to do the operation in the current connection in the context:
https://groups.google.com/forum/?fromgroups=#!topic/scriptella/BpfD6BJc804
Is it possible to support 'connection-id' in 'onerror' tag? Thanks
Update: The feature has been implemented and it will be included into 1.2 release. Current development snapshot can be download from here: http://javaforge.com/displayDocument/scriptella-1.2-SNAPSHOT.zip?doc_id=222665
I've created a change request and will consider adding this feature in future releases.
Regarding the workaround. Why is it not acceptable?