Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add a warning about not being able to edit the current alias
See original GitHub issueRenamed the issue as per discussions. After the below comments, the issue is not that it is not possible to edit portals aliases after changing the primary but that there is no way (by design) to edit the alias used to access the site at the moment. This is to prevent a user from locking the site down by error.
So this becomes an enhancement to the UI to explain this behavior. Probably disabled buttons with a tooltip about why they are disabled.
One comment though, probably not related to this PR:
- fresh install, only 1 site alias (primary)
- add alias “platform.com”, click
Set Primarybutton
Primary alias is now “platform.com”, and now there is no way to set the initial alias as primary any more. Ever.
_Originally posted by @daguiler in https://github.com/dnnsoftware/Dnn.AdminExperience/pull/343#issuecomment-456225695_
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah, the current behavior is that you cannot edit the current alias, but it should be that you cannot change the HTTP Alias for the current alias, but you can update the Primary flag.
This issue has been closed automatically due to inactivity (as mentioned 14 days ago). Feel free to re-open the issue if you believe it is still relevant.