View Import Error with Templates in Subfolders

[bmusgrove-accuraty]

I'm submitting a

[x] bug report
[x] feature request

...about

[x] admin experience UI
[x] Content Types or data management

Current Behavior

When Importing a 2sxc view I have created and exported from another website project onto my current project, I get an error with my Razorblade file, and the error message is not clear.

1. The issue is that it does not automatically create the subfolder structure after ...\2sxc\Content... and it seems like it should.
2. The error received is not very informative on what/where the issue happened. It looks like the path exists, but in reality the file path after \2sxc\Content... is not there.
3. Had to do some trial and error until I figured out the "AETA" folder needed to be created on the server for the import view to recognize it.

Expected Behavior

When you Import a View, it should build the rest of the file path connected to that particular view if it does not exist already. This helps the user keep a quick workflow and they wouldn't need to create these folders themselves.

Instructions to Reproduce the Problem

1. Ensure that your existing View is using a template file in a subfolder under your app, e.g. /Portals/0/2sxc/Content/MyFolder/Review-list.cshtml.
2. On a separate website, I Exported the 2sxc View
3. To see the error, make sure the /MyFolder does NOT exist on the site you are importing to
4. On my current website, I am in the Content Admin window > View
5. Clicked the "View" in the bottom left and select the Import option
6. I drag and drop my Exported 2sxc View into the file area
7. Once the file got in there, I received the error in the image above

Your environment

• 2sxc version(s): 16.7.0
• Browser: Chrome
• DNN: 09.13.00
• Language: English

[jeremy-farrance]

@iJungleboy - this seems well explained and easy to reproduce... and possibly quick/easy to fix. Any chance this can get a little love soon? Definitely a high PITA factor for us and the way we re-use apps.