Hi, A different way to deal with this problem by overriding modified_time function, which actually fetches the object again from storage if modified_time is None:
from storages.backends.s3boto import S3BotoStorage, parse_ts_extended > > class MyS3BotoStorage(S3BotoStorage): > def modified_time(self, name): > name = self._normalize_name(self._clean_name(name)) > entry = self.entries.get(name) > # only call self.bucket.get_key() if the key is not found > # in the preloaded metadata or if modified time stamp is empty. > if entry is None or not entry.last_modified: > entry = self.bucket.get_key(self._encode_name(name)) > self._entries[name] = entry > # Parse the last_modified string to a local datetime object. > return parse_ts_extended(entry.last_modified) And then reference this new class from STATICFILES_STORAGE and DEFAULT_FILE_STORAGE of your settings. By the way, it looks like the original project in bitbucket https://bitbucket.org/david/django-storages is not being maintained. Is there any fork or alternatives? On Wednesday, June 10, 2015 at 1:19:52 AM UTC+1, Tom Longson wrote: > > I'm having the ts.strip error still, tried using django-storages-redux, > but ran into another error: > > ImproperlyConfigured at /admin/media-library/browse/ > Error finding Upload-Folder. Maybe it does not exist? > > Looking for a solution still. > > Tom > > On Wednesday, April 22, 2015 at 6:53:44 PM UTC-7, Flavio Barros wrote: >> >> I Tryed the solution here but is not woking yet. >> >> >> [image: photo] >> *Flavio Barros* >> Doutorando, Unicamp >> w:www.flaviobarros.net >> >> <https://www.linkedin.com/profile/public-profile-settings?trk=prof-edit-edit-public_profile> >> Meu Blog Handwritten digit recognition – Part1 >> <http://feedproxy.google.com/~r/FlavioBarros/~3/dlnBN09FQAI/> >> "In every CHOICES that we choose, There's always a RISK; But always >> remember that there's also a chance" - Kent Solatorio Lopez >> <https://www.quotesdaddy.com/quote/1430413/kent-solatorio-lopez/in-every-choices-that-we-choose-theres-always-a-risk> >> >> Get a signature like this: >> <https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9> >> Click >> here! >> <https://ws-stats.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS8/dXRtX3NvdXJjZT1leHRlbnNpb24mdXRtX21lZGl1bT1lbWFpbCZ1dG1fY2FtcGFpZ249cHJvbW9fNDUiLCAiZSI6ICJwcm9tb180NV9jbGljayJ9> >> >> >> On Wed, Apr 22, 2015 at 10:28 PM, Flavio Barros <flaviom...@gmail.com> >> wrote: >> >>> I'm still having this problem. Any solutions? >>> >>> Em terça-feira, 9 de abril de 2013 11:37:39 UTC-3, Marcos Scriven >>> escreveu: >>>> >>>> Ah... well spotted! >>>> >>>> Looks like it is indeed a new issue. Was introduced here a couple of >>>> weeks ago: >>>> >>>> >>>> >>>> https://bitbucket.org/david/django-storages/commits/a3b2540a10a99e7332fa4ba2a9cd9a262a9a63f9 >>>> >>>> >>>> Whereas I've not updated since Jan (version 1.1.6) >>>> >>>> Marcos >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Mezzanine Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to mezzanine-use...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
