Hi Team,
just wanted to check, Is there any harm to store custom CSS/JS in Resources folder. is there any chances that it can be overwritten when we upgrade DNN.
Do we have any best Practice to store Custom CSS/JS in DNN e.g. site assets or desktop folder etc.
Thanks in advance!
you may store custom css in portal.css file or any css/JS in individual skin folder or any custom subfolder folder inside /desktopmodules or /providers
Thanks a lot, Sebastian Leupold
Is it bad to store custom files in the Resources folder? is there any chance that it can be overwritten when we upgrade DNN?
thanks, Joe Craig
Idea is to create a common module for all shared static resources.
These are CSS/JS shared files across the portals, which we want to put in the Resources folder through the install package.
Posted By Jasbir on 06 Apr 2021 02:09 PM thanks, Joe Craig Idea is to create a common module for all shared static resources. These are CSS/JS shared files across the portals, which we want to put in the Resources folder through the install package.
As long as you use a unique path, these will not be overwritten. BTW, you can create a package just for installing resources.
https://www.dnnsoftware.c...sourcefile-component
There is also a module for that I use quite often: Will Strohl's Content Injection, available here: github.com/hismightiness/dnnextensions. The current release can be found here.
Happy DNNing! Michael
Michael TobischDNN★MVP
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.