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

[Bug]: Creating Portals When a Prior Portal Existed Fails With Workaround

Open
  • Is something wrong?
#7,247 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing the reported sequence: create a child portal, delete it, restart the app, and try to create it again with the same path. Then trace the child-portal creation and deletion flows to find where the old alias is treated as already used. Done means the same alias can be reused after deletion without the dummy-name workaround.

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?

Using a clean installation a number of child portals were created, for the purposes of example /child1, /child2, /child3, etc.

A mistake was made and a child portal was deleted. The system was restarted an there was no history of the child portal being there.

An attempt was made to create a new portal with the same alias, it failed with an error that the name was already used (but it wasn't).

A site was created with a dummy name, and it created, and then it was possible to add the desired alias without error.

Steps to reproduce?
  1. Create a child portal, call it "Site1" with a path of www.mysite.com/Site1
  2. Delete the child portal
  3. Restart the app, just to be safe
  4. Try to create a new child portal "Site1" and see the failure

In looking at this, I believe it may be related to the default.aspx that is added into the sub-folder, which isn't really needed.

Current Behavior

Unable to create the portal and have to workaround the use of a dummy value and adding a new one.

Expected Behavior

I should be able to create a new portal with a name of a prior deleted/removed portal.

Relevant log output
Anything else?

The above workaround is an easy way to get aroud it if you understand, but not easy for those new to the platform.

Affected Versions

10.3.1 (latest 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.