Closed adamcik closed 12 years ago
Current code uses a specific fork of django-compress with this feature. On the down side it seems that the package is fractured an no effort is being made to integrate forks :(
django-compress is no longer used, we've switched to django-compressor.
Currently the site simply caches entire http responses for the sake of simplicity. However with django-compress as part of the current setup this causes problems. New media files can be synced, removing the old ones, while the cached responses still point to the old files.
This can either be fixed by
Personally I'm inclined towards providing a patch upstream or using signals.