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

[Bug]: Project environment path is not encoded when the name includes a forward slash #2461

Open
kristinatong opened this issue Jun 11, 2024 · 0 comments · May be fixed by #4364
Open

[Bug]: Project environment path is not encoded when the name includes a forward slash #2461

kristinatong opened this issue Jun 11, 2024 · 0 comments · May be fixed by #4364
Assignees
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged.

Comments

@kristinatong
Copy link

kristinatong commented Jun 11, 2024

Description

I am locked out of accessing my production environment because it was renamed to include a forward slash in the name. When clicking into the environment, I am redirected to the home page because the path is not encoded.

Minimal Reproduction (if possible, example repository)

  1. Go to /projects and click into a project
  2. On any environment, click "Settings"
  3. Rename the environment to include a forward slash e.g. feature/123
  4. Click Save
  5. Go back to the project page and click the environment card

Exception or Error

You are redirected to the home page because the path references the environment name and it's not encoded.

Version

v4.0.0-beta.294

@peaklabs-dev peaklabs-dev reopened this Oct 28, 2024
@peaklabs-dev peaklabs-dev added 🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. labels Oct 28, 2024
@peaklabs-dev peaklabs-dev self-assigned this Nov 22, 2024
@peaklabs-dev peaklabs-dev added the ✅ Done Issues that are fixed and a PR is ready to be merged. label Nov 22, 2024
@peaklabs-dev peaklabs-dev linked a pull request Nov 22, 2024 that will close this issue
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🐞 Confirmed Bug Verified issues that have been reproduced by the team. ✅ Done Issues that are fixed and a PR is ready to be merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants