Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fields not being submitted from Uppy v3.4.0 to Transloadit #4295

Closed
2 tasks done
dseravalli opened this issue Feb 1, 2023 · 2 comments · Fixed by #4316
Closed
2 tasks done

Fields not being submitted from Uppy v3.4.0 to Transloadit #4295

dseravalli opened this issue Feb 1, 2023 · 2 comments · Fixed by #4316
Labels

Comments

@dseravalli
Copy link

dseravalli commented Feb 1, 2023

Initial checklist

  • I understand this is a bug report and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

No response

Steps to reproduce

On Uppy v3.4.0

Uppy configuration

new Uppy.Uppy()
    .use(Uppy.Dashboard, {
      trigger: '.file-upload-btn',
    })
    .use(Uppy.RemoteSources, {
      companionUrl: Uppy.Transloadit.COMPANION_URL,
      companionAllowedHosts: Uppy.Transloadit.COMPANION_ALLOWED_HOSTS,
      sources: [
	'Box',
	'Dropbox',
	'GoogleDrive',
	'Instagram',
	'OneDrive',
	'Facebook',
	'Url',
      ],
    })
    .use(Uppy.Webcam, { target: Uppy.Dashboard })
    .use(Uppy.Audio, { target: Uppy.Dashboard })
    .use(Uppy.Form, {
      target: 'form',
      resultName: 'uppyResult',
      getMetaFromForm: true,
      addResultToForm: true,
      submitOnSuccess: false,
      triggerUploadOnSubmit: false,
    })
    .use(Uppy.Transloadit, {
      assemblyOptions (file) {
	return {
	  params: {
	    auth: { key: 'xxxx' },
	    template_id: 'xxxx',
	  },
	  fields: {
	    submissionId: '1234',
	  },
	}
      },
    });

I have also tried passing assemblyOptions as an object instead of a function.

Transloadit template:

{
  "steps": {
    ":original": {
      "robot": "/upload/handle"
    },
    "export": {
      "use": [
        ":original"
      ],
      "robot": "/s3/store",
      "bucket": "xxxx",
      "path": "${fields.submissionId}/${file.md5hash}/${file.url_name}",
      "acl": "bucket-default",
      "bucket_region": "us-east-1",
      "key": "xxxx",
      "secret": "xxxx"
    }
  }
}

Expected behavior

I expect submissionId to be present in the assembly JSON, and I expect my S3 paths to start with 1234

Actual behavior

submissionId is not present anywhere in transloadit UI or assembly JSON. S3 paths start with the MD5 hash instead of 1234

@rorito
Copy link

rorito commented Feb 7, 2023

Can confirm we got hit by this same bug in testing upgrading to 3.4.0

@arturi
Copy link
Contributor

arturi commented Feb 13, 2023

Hi, thanks for reporting and sorry about this, we are looking into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants