First, what I tried to do is update DAMP from 2.6 to 2.7. After uninstalling DAMP 2.6 (big mistake), I tried to install new version and got YSOD:
The file '/site/Umbraco/plugins/DigibizAdvancedMediaPicker/Installer.ascx' does not exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The file '/site/Umbraco/plugins/DigibizAdvancedMediaPicker/Installer.ascx' does not exist.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I never tested DAMP in a virtual directory, but it probably won't work. If you want to have it fixed you could download the source code and check for relative paths.
it seems that package files where unpacked under the "site"(virtual directory name) subdir in root folder. After copying them to right directories installation was successful.
DAMP is not working/installing for Umbraco running in virtual directory
After putting my Umbraco installation in virtual directory DAMP is not working any more as in this issue https://damp.codeplex.com/workitem/4 ; .
First, what I tried to do is update DAMP from 2.6 to 2.7. After uninstalling DAMP 2.6 (big mistake), I tried to install new version and got YSOD:
The file '/site/Umbraco/plugins/DigibizAdvancedMediaPicker/Installer.ascx' does not exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The file '/site/Umbraco/plugins/DigibizAdvancedMediaPicker/Installer.ascx' does not exist.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Now I can't use DAMP at all :(
This should be fixed.
Hello,
I never tested DAMP in a virtual directory, but it probably won't work. If you want to have it fixed you could download the source code and check for relative paths.
Jeroen
Hi,
it seems that package files where unpacked under the "site"(virtual directory name) subdir in root folder. After copying them to right directories installation was successful.
Will check source code when have more time.
Thanks,
Pavel
is working on a reply...