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.
Related
I use Windows Application Packaging Project to generate MSIXBUNDLE for my WPF app.
App installed failed with error message: Windows cannot install package xxxxxx_3.8.3.0_neutral~_hijkl because a different package xxxxxxx_3.8.2.0_neutral~_abcde r with the same name is already installed. Remove package xxxxxx_3.8.2.0_neutral~_abcde before installing. (0x80073cf3)
I think the reason is that I signed the new package (3.8,3) with a new EV code signing certificate. Does WAP tool support option to uninstall previous package? Under the project property tab "Debug" ->"Start option", there is a check box for "Uninstall and then re-install my package. All information about the application state is deleted". But enable it does not seem to do the job.
Thanks,
"Uninstall and then re-install my package. All information about the application state is deleted"
I think this option is useful only for debugging purposes. It sounds like an option to remove a previous copy of the package (that has the same version and product name). So, this does not help with removing older versions.
For MSIX packages, you don't top configure anything specific in the package to trigger the removal of a previous version, as you used to do with an MSI. This is handled automatically by the OS.
But the OS needs to somehow understand which package to remove and I suspect the digital certificate is part of that check. Just manually remove the old version, install the new one, and then build a test version (3.8.4) to confirm if the different certificate was the problem.
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.
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.
I would like to ask you if someone has similar problem. I am using Sitecore.NET 7.2 (rev. 151021) with Solr. I need to add some items from prod to my local sitecore instance. When I create package and tried to install specific content I get exception null reference exception. It doesnt depend on the content. I tried to used package designer with varios content and always I get this exception.
As the comments indicate: Make sure that all of the supporting items that each item in the package require are in place in the destination before trying to install them through a package.
Normally, separate packages are created for Templates, Layouts and Content and installed in that order to avoid missing dependencies.
You can also look into disabling Index builds during package installation. I have a module out there that does this:
https://marketplace.sitecore.net/en/Modules/Detailed_Package_Installer.aspx
I changed source of DotNetnuke (a little!) and I want to package an install version of my new DotNetNuke.
How Can I do this?
p.s: I know It's not recommended to change the source but I have no another option
(Telerik calendar do not support my date format and I have to replace it with another calendar !)
Thanks in advance
Answer depends on what you have changed, but the simplest way is to deliver patch that should be installed after normal dnn installation. For example, if you have only changed dll, you can ask to follow normal dnn setup instructions and finally relpace dll. If it's more than on file, you can review how dnn upgrade package is built. It follows same folder structure and places only changed files. So if you have couple of dlls changed in bin, the will be placed in bin folder, and if you have changed some ascx file it should be placed in same path by creating same folder hierarchy.
You can also create a package that can be installed to deploy your changes but for smaller set of files it will be complecated.
Let me know if you need more help.
You can package any change into a DNN install package by including the compiled files along with a DNN Manifest file. This can then be installed via the Extensions page. A manifest file is an Xml file which controls where the contents of an install zip are installed. You can make it as simple or as complicated as you need. You can also include xml merge statements to make changes to the web.config file upon install and uninstall. See the wiki for reference : http://www.dotnetnuke.com/Resources/Wiki/Page/Manifests.aspx
Incidentally, you may have been able to deliver your modified telerik source as a separate provider, and configure it via the web.config, thus saving you from modifying the source code. To do something like that, you would build your own module, and plug it in and replace the standard Telerik references.