Installing a Module in DNN , Folder permissions - dotnetnuke

I am trying to install a module in a DNN project residing on Godaddy.
I am getting an error installing the module
I know the error I am getting in DNN is coz of permissions.
I thought giving write permissions to the App_Data and DesktopModules folder will resolve the error, but it doesn't, is there any other folder I have to give write permission to
BTW, I am trying to install the already existing "Feedback" module in DNN

Okay the Feedback module and most modules that are installed as PA's have binary/compiled files for the data provider and much of the actual code for the controls. First thing I would check is that the 'bin' folder has write permissions as well as 'app_code' and 'desktopmodules'

Related

reactjs: files served into public folder resolve into a 404 error in production build but work in development with npm start

I am trying to serve 2 files needed by javascript for a web assembly package. The files example.wasm and example.data are in the public folder in the react js project file structure. When running with a development server using npm start, the files can be found by the project and can be read correctly. When building the project the files end up in the root directory of the project as expected. In spite of using the current PUBLIC_URL path for the files, the files can not be found, but the paths in the web console seem to be correct.
I am hosting the reactjs app from IIS 7.
Can you help me with the process to debug the problem described above?
Thank you in advance for your help.
After the help of #LexLi I have enabled the Failed Request Tracing Module in the IIS following this documentation:
[https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis][1]
Reading the log generated by the Failed Request Tracing Module I saw that when requesting the files example.wasm and example.data from the server the actual error was not 404 Not Found but:
SECURITY_DENIED_BY_MIMEMAP
After googling the error above I realized that the Default MIME Types configured in the IIS do not include files with extensions .data and .wasm. After adding those MIME Types to the IIS configuration using the MIME Type Module in the Web Server Level in IIS Management and restarting the server the problem was resolved.

DNN Module installation

Is it possible to "install" a module just by pasting the file of the module and just paste it into the DesktopModules folder and have the modules working on the website?
If not, is there a way where I can export the whole module from one system and install it onto another system?
Have you tried creating a module package for this module? (when you click the edit pen for the extension, you should find a "Create package" button on the top right).
Take care to include the assembly/assemblies needed, and also the Sql Server scripts to install the module correctly (often found in the module folder under Providers/DataProvider/SqlDataProvider/*.SqlDataProvider). There might be other files in the module folder (images, css, etc), be sure to include them in the package, then try to create it. You will find the ZIP file under /install/Modules then, move it away from there somewhere on your local file system (otherwise the installer might try to install it with the next update). Then try to update the extension in a testing system, check if it works and you're done. If there are errors it might be that you are missing some files that have to be included. Check the error messages, and restart.
There used to be a way using the /Install/Module/ folder (put ZIP file there, then call /install/install.aspx?mode=installresources) If you are on an old version of DNN (7 and earlier?) you can still use this. But you've got a load of security issues that should drive you to upgrade.
I don't know of a good way to do this now. For security purposes DNN removes the Install resources after an upgrade.
IF you already have the module installed in both locations, you could copy the resources for the file from server to server (DLL in the BIN folder and the contents of the desktopmodules folder) assuming you don't have any MANIFEST file changes that need registered.

Install.aspx file issue while upgrading Evoq Content

Currently my application is running on Evoq Content 7.3 and I was trying to upgrade it to Evoq Basic 8.5. I have copied the upgraded file into my application directory And now when I try to access the http://MYWEBSITE/install/install.aspx?mode=upgrade , It is giving error "resource can not found Requested URL: /install/install.aspx.
Please advise.
This looks like some files were removed from the install directory, probably as part of a security precaution. I'm not sure why they were not added back with the upgrade package.
You might be able to fix this by copying the install directory from an appropriate install package. Just the install directory.
As always, make a copy of your database and complete file directory first, just in the event that what you do fails.

Umbraco Package (ImageProcessor) Crashing site

So I tried to install a package called 'Image Processor' to our Umbraco build which I later found was incompatible. How do I manually remove this package from the build? I've tried removing all mention of 'ImageProcessor' from the Web.config, packages.config etc still no cigar.
This is the error we're getting.
Check in the /bin/ folder for the Image Processor DLL file. If this file is present, I believe that the application is trying to load it. However, this file requires something from Umbraco.Core which isn't there, so it crashes.
If you find the DLL, try deleting it and reloading the application.
Also, I assume you installed this package through Umbraco. In the future I would recommend using NuGet to install packages, as it allows you to add, update and remove packages without running the application (so if you were to get an error like this again, you would be able to easily uninstall the package).

Bower (bower_components) item missing in browser but present on server

I'm trying to debug a really bizarre issue. As part of the build process on a project I'm working on, a bower_components folder is created with all the packages listed in the bower.json file. This process seems to complete successfully. However, when I refresh the project and view it in the browser, there is a single missing package (in this specific case it is angular-ui-sortable). The package is present in bower_components directory on the server, but absent when viewing that same directory in Chrome devtools. The missing package is breaking the UI since Angular throws an "$injector error" because it is unable to find the missing package. The question I have is, how do i even begin to debug this issue. I've confirmed that I'm looking at the correct folder as well as checked the missing package's permissions. I've also confirmed that the package is correctly included in the project's index.html file.
Any advice is greatly appreciated.
Thank you.

Resources