Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Filenames with # cannot be opened

Open
#6,926 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
backend

Research direction

Start by reading StandardFolderProvider.GetFileUrl, which the issue identifies as the source of the filename handling. Reproduce the problem with a file named “My File Example #1.PDF” in the Asset manager and check how its URL is generated. Done means opening the file no longer returns a 404 because of the # character.

Written by the indexing model from the issue text.

Description

Status: New
Is there an existing issue for this?
  • I have searched the existing issues
What happened?

If I add a file with # in it's name, when I try to open-it throgh asset management it cannot be accessed.
Example: "My File Example #1.PDF"
I have checked using the APIs in the code and when I use the default FolderManager GetUrl method, it returns the fiilename without handling the # character that becomes invalid to use in the browser.

Steps to reproduce?

Go to Asset manager
Add a file with the filename: "My File Example #1.PDF"
Right click on the file after upload
Chose the option Open
File will try to oned on a new tab bot a 404 page is displayed because of the # in the URL

Current Behavior

No response

Expected Behavior

I think that the StandardFolderProvider implementation of GetFileUrl should handle the # as any of the other InvalidFileUrlChars and render a LinkCLick url for the file instead of the direct link.

Or replace the # char with %23

Relevant log output

Anything else?

No response

Affected Versions

10.2.0 (latest v10 release)

What browsers are you seeing the problem on?

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
C#
Stars
1.1k
Forks
791
Avg merge
2d 2h
Merged PRs (30d)
24

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dnnsoftware/Dnn.Platform

All issues in dnnsoftware/Dnn.Platform

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.