User talk:Bcooksley

Jump to: navigation, search


Thread titleRepliesLast modified
can not upload a new version of an image810:33, 6 August 2017

can not upload a new version of an image

When I go to upload a new version of an image onto userbase I get this error. I can upload brand new images but not a new version of an existing image. The latter is a useful feature as you get to propogate the changes to all the pages that use the image automatically.

Could not read or write file "mwstore://local-backend/local-public/4/45/Kdenlive_Effect_stack_icons2_0.9.3.png" due to insufficient permissions or missing directories/containers. Could not store file "/tmp/phpnHNgMS" at "mwstore://local-backend/local-public/4/45/Kdenlive_Effect_stack_icons2_0.9.3.png".

Roger (talk)01:23, 6 August 2017

Oops. That should now be fixed.

Bcooksley (talk)02:08, 6 August 2017

That has indeed fixed it. Thanks for the prompt service. What is still frustrating about the upload new file is that somewhere along the way the old version of the file seems to be cached somewhere and I have a hell of a time to get the new version to display. I can see it if I open the page on a completely different PC. But if I refresh the page, hard refresh the page, go into Chrome Dev Tools and do "empty cache and hard reload" I still see the old cached version. Totally anoying. - But probably nothing to do with

Roger (talk)02:57, 6 August 2017

The cached file is likely being delivered by Incapsula. If memory serves you can get the latest version of the image by refreshing using Ctrl + F5.

Bcooksley (talk)05:55, 6 August 2017

Ctrl + F5 did not do it for me.

So userbase/kde etc are Incapsula customers ?

Roger (talk)08:46, 6 August 2017

Interesting, it should have. Guess Mediawiki must be caching as well. Yes, we are users of Incapsula.

Bcooksley (talk)09:58, 6 August 2017

This page was last modified on 6 August 2017, at 01:23. Content is available under Creative Commons License SA 4.0 unless otherwise noted.