Is there an existing issue for this?
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?
- Create a child portal, call it "Site1" with a path of www.mysite.com/Site1
- Delete the child portal
- Restart the app, just to be safe
- 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
Is there an existing issue for this?
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?
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