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

Amazon S3 Assets with spaces getting linked with two spaces resulting in a broken link #4567

Closed
mcasey-svcc opened this issue Jan 26, 2021 · 0 comments
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Topic: CMS Related to data and components primarily for the external website. Type: Bug Confirmed bugs or reports that are very likely to be bugs. x-Fixed in v12.5
Milestone

Comments

@mcasey-svcc
Copy link

mcasey-svcc commented Jan 26, 2021

Description

When attempting to insert a link to an S3 asset filename which contains spaces, the URL linked [broken] contains 25 which to my understanding means the URL was encoded twice (https://stackoverflow.com/questions/16084935/a-html-space-is-showing-as-2520-instead-of-20#:~:text=A bit of explaining as,the to %2520 .).

image

Steps to Reproduce

  1. Go to Asset Manager
  2. Click on Amazon S3 and choose a file which contains spaces.
  3. Attempt to access the link.
  4. See error

Expected behavior:

URL should be: https://svassets.s3.us-west-1.amazonaws.com/docs/K-3 JAN PARENT CUE WK 4.pdf

Actual behavior:

URL from Rock is: https://svassets.s3.us-west-1.amazonaws.com/docs/K-3%2520JAN%2520PARENT%2520CUE%2520WK%25204.pdf

Versions

  • Rock Version: Rock Version: Rock McKinley 11.3 (1.11.3.1)
  • Client Culture Setting: Client Culture Setting: en-US
@sparkdevnetwork-service sparkdevnetwork-service added Topic: CMS Related to data and components primarily for the external website. Type: Bug Confirmed bugs or reports that are very likely to be bugs. labels Mar 11, 2021
@cwomack cwomack added the Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. label May 18, 2021
@crayzd92 crayzd92 added this to the v12 milestone Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. Topic: CMS Related to data and components primarily for the external website. Type: Bug Confirmed bugs or reports that are very likely to be bugs. x-Fixed in v12.5
Projects
None yet
Development

No branches or pull requests

5 participants