I have recently completed Clinton Patterson's guide on DNN module development and was just playing around with the module that I have developed (reinstalling the module, uninstalling the module, etc).
However, some of my source files including View.ascx, Settings.ascx, Edit.ascx, module.css, 00.00.01.SqlDataProvider, Uninstall.SqlProvider, ReleaseNotes.txt, License.txt went missing all of a sudden and is nowhere to be found.
I am not too sure why this is happening but I am suspecting it's due to me uninstalling the module and selecting the "Delete Files?" option when uninstalling. Now I am unable to install the module anymore as all the files mentioned above can't be found in my project anymore.
So my question here is whether my assumption is correct in which I have 'accidentally' deleted my source file when uninstalling the module? And if so, is there any way that I can recover those files because I can't seem to find them anywhere (not even in the recycling bin).
Anyway, shouldn't uninstalling a module deletes those files that were installed and not touch the original source files? Sorry I am rather new to this and I can't really find any similiar questions about this online. Thank you very much!
P.S: I am using DotNetNuke Community Version 07.01.02 if that helps.
Uninstalling the module:
Selecting the 'Delete Files?' option when uninstalling the module:
I don't believe that will remove the files if there's a PROJECT or SOLUTION file in the directory.
It's a safety catch for development environments. I would just manually delete them after you go though the uninstall process.
Related
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.
After installing and enabling module adminstration menu with update manager, I have moved the installed module to the contrib directory of my project.
I have also cleared the cache in the administration/configuration/development/performance.
How can I make it visible?
The first thing I'd try is to move the module back to where ever it was originally installed and then enable it, disable it and uninstall it. Uninstalling will remove any references in the system table that might be confusing Drupal.
If you don't know where it was before you moved it, you can find that info in the system table.
Then move it to the new location and it should be visible and you can enable it from there.
If that doesn't work, you should be able to use the registry rebuild module to clear out any remnants the old version. Backup your database first.
I installed CKEditor, but for some reason, when I opened the configuration, Drupal says: "CKEditor not installed."
I deleted the folder from sites\modules\ckeditor, then tried to install a different version. On trying to install, it still said "CKEditor is already installed", even though I'd deleted it (and checked it was no longer in the list of modules).
I guess there might be some trouble with the database.
How do I solve this?
Im idiot. Cause I opened by mistake a different FTP, user and was looking at different folder all/sites/modules.....in this folder I deleted everything, but of course the web I was working on had different module folder :-(. So it kept telling me CKEDITOR was installed why I couldn see it... I ll shoot myself soon. Sorry.
A user has tried to install a new skin for the simulator and things did not work, see screenshot:
He uninstalled / reinstalled the CodenameOne plugin but the preview remains bugged as indicated on the screenshot above. Is there some hidden config files he should delete elsewhere?
Skins are installed in this directory: C:\Users\UserName\.codenameone, some of them might have been corrupted during addition.
You can try removing all before re-installing CN1 plugin to see if it solves the problem. Particularly the skins with recent Date modified.
This happens if you pick a corrupt skin file, we made several attempts at fixing it which apparently still didn't resolve the issue.
To workaround it in Windows launch the resedit tool and type into find: "JavaSEPort".
Delete everything you find in that search and it should restore you to the default state.
When I am trying to build a solution file which has WPF projects, I get this error
Could not copy the file "bin\Debug\test.exe.config" because it was not
found.
I tried Clean Solution, Rebuild solution. Tried deleting the bin directory. This started yesterday. Not sure what I changed.
How do I fix this. so I can do a build.
Just a thought, but anti-virus software could potentially cause this type of problem if it decides that your exe is suspicious.
If you have any AV software running, try disabling it temporarily, and/or excluding your project build folders from its protection.
OK. The problem with my solution was a extension(a config Transform extension) that was installed. I updated the Visual studio extension and the build succeeded.