Closed leedavi closed 3 months ago
If you assign a default skin and use a default container from another skin, all modules using the default container will throw an error.
Error displayed
No error and it uses the default container selected in themes option.
No response
This worked in DNN9.12, so this bug will break upgrades if no container is specified for the module
9.13.2 (latest release)
Chrome, Microsoft Edge
Sorry, I didn't realize this was the Skin forcing a container that was not installed. I'll close it.
Is there an existing issue for this?
What happened?
If you assign a default skin and use a default container from another skin, all modules using the default container will throw an error.
Steps to reproduce?
Current Behavior
Error displayed
Expected Behavior
No error and it uses the default container selected in themes option.
Relevant log output
No response
Anything else?
This worked in DNN9.12, so this bug will break upgrades if no container is specified for the module
Affected Versions
9.13.2 (latest release)
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
Code of Conduct