-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting it up as a subsite #39
Comments
I've not tested that, but I will get on it in the morning. Have you tried setting the setting the site URL in the configuration under admin? I'll ensure that that setting is used to reference all site resources (like CSS and images). |
Added a pre-release that should work for you. While you should still set the site name under configuration as I mentioned above, you are correct that the sub-directory configuration was unsupported. You will need to use the prerelease 2.19.0 and alter the "BasePath" in the appsettings.json, setting it to "/yourSubFolder". Let me know if you run into any issues. https://github.com/NTDLS/TightWiki/releases/tag/2.19.0 |
@beerpal243 let me know if this works for you. |
Are you using the pre-release and setting the base bath in the appsettings? https://github.com/NTDLS/TightWiki/releases/tag/2.19.0 |
Yes sir, I am. |
Wtf…. on it |
@beerpal243 If you wouldn't mind, give it another go. https://github.com/NTDLS/TightWiki/releases/tag/2.20.0 |
Is it possible to setup the site as a subsite? The problem I'm having is that I have the main site, then I want to setup the TightWiki as a Subsite. While I was successful getting the site up and running, all the Css, js and page references are looking for the resources on the main site, not the subsite. Am I missing a setting?
Thank you
The text was updated successfully, but these errors were encountered: