Re:Django CMS version 3.3 has been released
by nkozyra on Thursday June 09, 2016 @11:43AM
(#11870125)
It's a 403 error, so it's probably unlikely it has anything to do with browser cache (but of course possible, though I don't know what Django would need from cookies/webstorage/cache). I did try on another machine in a incognito window and got the same thing 3 times.
Re:Django CMS version 3.3 has been released
by DanieleProcida on Thursday June 09, 2016 @11:51AM
(#11870190)
OK, really sorry about that. We're working on it back here, we can definitely see a caching issue somewhere in the pipeline. Would you try once more in incognito mode?
It's working for me here, anyway...