davros
davros copied to clipboard
Uploading/deleting from menu not working
I'm using 0.14.1 (on Microsoft Edge), a freshly created grain on the Sandstorm Alpha server. I opened each preincluded file, and selected "Delete File" from the top right menu. I got the message prompt, but the files did not delete. I also tried selecting Upload File from the home folder, and nothing happened.
Interestingly, trying to delete it again is giving me this in console: HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier). (XHR): DELETE - https://alpha-37f9f984da43c5ad8f413d2bccc17466.sandstorm.io/remote.php/webdav/voyager.jpg
As if the browser/grain has not noticed I deleted it.
After closing the grain, giving the supervisor time to kill it, and reopening, the actions I took, such as deleting files, creating a folder, etc. were represented. It seems like the interface isn't refreshing for actions taken.
Thanks for the report. I just got a machine running Edge so I'll take a look. The update is supposed to happen via websockets so I wonder if it's related.
Ok, I submitted v0.14.2 to the marketplace. I haven't yet tested it in IE Edge, but if you'd like to test it ahead of it showing up in the marketplace, you can do so here: https://mnutt.sandcats.io/shared/hNttoEKpQeWvGUCRmybPMReK9At3QjgZlOqpr54CIjd
Okay, so, this is NOT fixed for me.
In fact, upgrading to 0.14.2 re-added the demo files I had deleted, oddly enough! Drag-drop to upload does work, but the display didn't refresh. And I still get no options when I click "Upload" from the menu.
I still get nothing when I click on the Upload menu option. Drag-drop uploading still works alright.
v0.21.6 still has no action no matter how many times I mash the upload button.
this is happening to me too... I'm using vivaldi on ubuntu, it seems this behavior is affecting chromium based browsers, not sure about chrome itself. But every other app is working well... not only sandstorm apps, I consume a lot of "web socket apps" since I develop on meteor. I don't have time right now to look into the code. If you know a way to fix this let me know. Else, I will browse the code and when I have something useful I will post back here.
Still experiencing this in Chromium; seems to be the same bug as #25.