uBlogsy Config file and uTagsy files not found when using Virtual Directory
Hi Anthony,
As mentioned in the following post (http://our.umbraco.org/projects/starter-kits/ublogsy/ublogsy-razor-blog/35956-Latest-source-code) , when Umbraco is installed as a virtual directory, uBlogsy requires that that the uBlogsy.config file, uTagsy.json, and uTagsy UserControls are copied to the parent website's folders.
Is there any work around for this, or will it require a code fix? And if it does require a fix, is it something that you are looking into? Of course having Umbraco related files split between website poses a problem when the two websites are modified independently.
The the stack trace below for the error that is returned:
Yes. I have done that to get it to work. Though I was wondering if there is a code fix in the works to make uBlogsy compatible with virtual directories? The parent website is actually another application so I didn't really want to mix the the configuration files together if I could avoid it.
uBlogsy Config file and uTagsy files not found when using Virtual Directory
Hi Anthony,
As mentioned in the following post (http://our.umbraco.org/projects/starter-kits/ublogsy/ublogsy-razor-blog/35956-Latest-source-code) , when Umbraco is installed as a virtual directory, uBlogsy requires that that the uBlogsy.config file, uTagsy.json, and uTagsy UserControls are copied to the parent website's folders.
Is there any work around for this, or will it require a code fix? And if it does require a fix, is it something that you are looking into? Of course having Umbraco related files split between website poses a problem when the two websites are modified independently.
The the stack trace below for the error that is returned:
A work around is to copy the config files to the locations noted in the error.
Hi Anthony,
Yes. I have done that to get it to work. Though I was wondering if there is a code fix in the works to make uBlogsy compatible with virtual directories? The parent website is actually another application so I didn't really want to mix the the configuration files together if I could avoid it.
is working on a reply...