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.
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.
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).
We are trying to upgrade the site from Kentico 8.2 To Kentico 9. In this there is lot of custom code.
We are using Code Upgrade tool as mentioned in the documentation to upgrade the code: Please check this
It will be really helpful if you could help us in this.
The error being referenced, the path's format is not supported can typically be resolved by copying and pasting the actual path from file explorer AND wrapping it in double quotes. If your WebsiteFolder and/or the .sln file have spaces in them, it will error out unless wrapped in double quotes.
Have you changed the file structure of your project? Have you changed the name or location of the CMS folder? What I would try is to install clean K8.2 installation, hotfix it to the same version you have and copy the "CMS" folder from your project to the clean install and see if it makes a difference.
I have a drupal installation running on OpenShift. I have been installing all modules and themes using git (commandline). However, I attempted to install the modules directly and the installation worked.
The problem that I now face is that when I attempt a pull request all I get is the modules and themes I had installed using the commandine and not the ones that I installed 'directly'.
Any one with a heads up on this?
OpenShift runs your code form a checkout of the git repository located at ~/app-root/repo within your gear. When you upload files using Drupal (instead of the git repository), the modules and themes are installed in this checked out directory and are not tracked in git.
I you are using a scaled application, I would recommend that copy the modules/themes and check them into git instead of the Drupal install method.
For now, to retrieve all your files you can try the rhc export command.
Thanks to #kraman above I got a hint of what to do.
I ran rhc snapshot save -a appname and got all the files. At least I know where to start off from since I can access the files.
A word of caution though for drupal users on openshift, just use git or sftp for pushing files and save yourself the headache.
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.