In the umbraco
installations we use, we have renamed the path to the admin portal from the
standard 'umbraco' to something else (ie, "http://oursite.com/siteadmin/").
As part of this,
we have updated the "umbracoPath" setting in the web.config file. Its been working fine with what we have been doing so far.
However, we just
installed the uCommerce package onto a website with this modified path, and
very few things actually worked. It automatically installed itself into the ‘\umbraco\’
directory (which hadn’t existed before the install). The ‘\umbraco’ path is also hard coded in many places (paths to images, config/xml entries, paths to controls, paths to dlls/code, etc.).
I spent time to
find/replace every reference I could find to the ‘\umbraco\’ directory
structure with the name of the path we use. This meant updating config
files, xml, ascx, etc. I even had to make some updates to entries
in the database (uCommerce_AdminPage table). I seemed to get nearly everything to work.
However, when I
went to update the payment methods, I received an exception:
[DirectoryNotFoundException:
Could not find a part of the path 'C:\inetpub\wwwroot\BMOSDev\wwwroot\umbraco\ucommerce\pipelines'.]
The call stack
suggests that the ‘\umbraco\’ path is hard coded down into the core DLLs.
Am I missing
some configuration item somewhere that uCommerce uses to define the
installation path? Is there an easy way to let uCommerce know where it should be installed?
Or do I need to
get the source code for the core DLLs and make code and package changes, rebuild, and reinstall?
uCommerce 2.0 and previous do not support installation outside the default Umbraco directory. However, our work preparing for Umbraco 5 means that uCommerce 3 will be able ot be install anywhere.
This functionality will not be backported to 2.0. Sorry.
Issues with install into non-default directory
In the umbraco installations we use, we have renamed the path to the admin portal from the standard 'umbraco' to something else (ie, "http://oursite.com/siteadmin/").
As part of this, we have updated the "umbracoPath" setting in the web.config file. Its been working fine with what we have been doing so far.
However, we just installed the uCommerce package onto a website with this modified path, and very few things actually worked. It automatically installed itself into the ‘\umbraco\’ directory (which hadn’t existed before the install). The ‘\umbraco’ path is also hard coded in many places (paths to images, config/xml entries, paths to controls, paths to dlls/code, etc.).
I spent time to find/replace every reference I could find to the ‘\umbraco\’ directory structure with the name of the path we use. This meant updating config files, xml, ascx, etc. I even had to make some updates to entries in the database (uCommerce_AdminPage table). I seemed to get nearly everything to work.
However, when I went to update the payment methods, I received an exception:
[DirectoryNotFoundException: Could not find a part of the path 'C:\inetpub\wwwroot\BMOSDev\wwwroot\umbraco\ucommerce\pipelines'.]
The call stack suggests that the ‘\umbraco\’ path is hard coded down into the core DLLs.
Am I missing some configuration item somewhere that uCommerce uses to define the installation path? Is there an easy way to let uCommerce know where it should be installed?
Or do I need to get the source code for the core DLLs and make code and package changes, rebuild, and reinstall?
Any help is appreciated.
Hello,
uCommerce 2.0 and previous do not support installation outside the default Umbraco directory. However, our work preparing for Umbraco 5 means that uCommerce 3 will be able ot be install anywhere.
This functionality will not be backported to 2.0. Sorry.
is working on a reply...