Most Scripts and some CSS not loading

[ceto...@gmail.com]

So I did a brand new install and noticed that multiple features, like the editor (tags, markup, preview, etc.) and the file manager, weren't working.

JQuery and other scripts in the /assets/scripts directory aren't loading. Some of the stylesheets that [I think] should be loaded aren't either.

Managed to shoehorn them into the HeadContent.cshtml to get things working a little bit by adding stuff like the following:

<link href="[insert stylesheet path/name here]" rel="stylesheet" type="text/css" /> and @Url.ScriptLink("[insert script path/name here]")

But I'm sure that isn't the right way of doing it, and there are multiple features that still aren't working. I can do things like add tags and simple markup, but still can't add images/files or see the page preview.

[frank....@gmail.com]

I am having the same issue. Everything works great on localhost, but when I publish to our local IIS server, /Assets/CSS/roadkill2.0.275.css and Assets/Scripts/roadkill2.0.275.js fail to load, which means I do not have the .css or .js files on the published site. This results in certain features not working, including file management which constantly says loading.
From my understanding, this is supposed to be complied during the build so I'm not sure why it does not work. I've also tried to precompile during my publishing, and that did not work either. I'm just not sure what else to do. Does anyone else have any suggestions? Thanks.

[frank....@gmail.com]

I ended up not removing the wiki site and starting from scratch. Rather than using Nuget I just downloaded the zip file including all of the contents and opened the files that way. Visual Studio opened them up as a Website. When I was trying to use Nuget I was doing an empty asp.net web application (with references to web forms and mvc). Either that was the issue and I should have used an empty website before installing the nuget package, or something doesn't work properly with the nuget package, my guess being the former. Hope this helps someone else.

[kanok...@gmail.com]

I had same problem while installing - no js or css files attended. Problem was with rights to folders. I moved project from C disc to another and gave all rights to main folder.

[Chris Small]

The next version of Roadkill will be IIS-less (Kestrel in Docker) which will resolve a large portion of the problems reported here on Google Groups.

In the meantime I'll post a powershell script here later to automate (it shouldn't apply to shared-hosting).

On Sat, 12 Nov 2016 at 19:00 <kanok...@gmail.com> wrote:

I had same problem while installing - no js or css files attended. Problem was with rights to folders. I moved project from C disc to another and gave all rights to main folder.

--
You received this message because you are subscribed to the Google Groups "Roadkill Wiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roadkillwiki...@googlegroups.com.
To post to this group, send an email to roadki...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/roadkillwiki/0ba3627d-24cf-4a45-8416-51a6df0f7419%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris S.]

As promised:

https://gist.github.com/yetanotherchris/200a70840a21d3c8fa9ef30f448e48b0

Change the directory as needed, but the user should be IIS_IUSRS