You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/07/20 22:54:00 UTC
[jira] [Commented] (AIRAVATA-3351) Uploaded file doesn't go into
newly created directory
[ https://issues.apache.org/jira/browse/AIRAVATA-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161595#comment-17161595 ]
ASF subversion and git services commented on AIRAVATA-3351:
-----------------------------------------------------------
Commit 43c37335ffec380503a62d50a6eb67fcfb0120b8 in airavata-django-portal's branch refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=43c3733 ]
Merge branch 'AIRAVATA-3351-uploaded-file-doesn-t-go-into-newly-created-direct' into develop
> Uploaded file doesn't go into newly created directory
> -----------------------------------------------------
>
> Key: AIRAVATA-3351
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3351
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> Steps to reproduce
> # Log into Django Portal
> # Portal must not be configured for tus upload (this bug doesn't affect tus uploads)
> # Go to /workspace/storage
> # Create a new directory
> # Navigate to new directory
> # Try to upload a file in the new directory
> Actual Result
> # file uploaded in parent directory
> Expected Result
> # file uploaded into new directory
> The problem is that the xhrUploadEndpoint changes based on the directory one is in but this was only specified on the XHRUpload Uppy plugin when it is initialized. The code fix is to update the XHRUpload configuration as the storage viewer path changes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)