Form indexes end up in parent application when CMS is deployed to a sub directory

[joel-cass]

The Indexes will end up in the incorrect folder when the CMS is deployed to a virtual directory within a parent application. If permissions are not set up, a 500 error occurs on the editor screen.

FormEditor/Source/Solution/FormEditor/Storage/Index.cs

Line 477 in 036d93a

return new DirectoryInfo(HostingEnvironment.MapPath($"/App_Data/FormEditor/{_contentId}"));

I'm pretty sure this can be solved by changing the line to return new DirectoryInfo(HostingEnvironment.MapPath($"~/App_Data/FormEditor/{_contentId}"));

[kjac]

Hey,

I'm sure you're right. I'll have a look at it this weekend.

Thanks for reporting.

[kjac]

@joel-cass 1.3.1.0 is out now with a fix for this issue :)