
![]() |
Show Changes |
![]() |
Edit |
![]() |
|
![]() |
Recent Changes |
![]() |
Subscriptions |
![]() |
Lost and Found |
![]() |
Find References |
![]() |
Rename |
![]() |
Administration Page |
| Search |
History
| 9/13/2007 2:27:37 PM |
| -74.15.247.173 |
| 8/31/2007 9:53:12 AM |
| -74.12.232.125 |
![]() |
List all versions |
Related Topics
One of the early steps in configuring your system is to create (or edit) your web.config file. This is the standard ASP.NET application configuration file that contains settings specific to your web application (in this case: FlexWiki).
The web.config file contains a variety of important configuration options for your site.
Here's a simple (valid) one:
<?xml version="1.0" encoding="utf-8" ?> <configuration> <appSettings> <add key="FederationNamespaceMapFile" value="/files/NamespaceMap.xml" /> <add key="SMTPServer" value="mail.flexwiki.com" /> <add key="SMTPUser" value="davidorn@flexwiki.com" /> <add key="SMTPPassword" value="yourpassword" /> <add key="NewslettersFrom" value="wiki@yourserver.com" /> <add key="OverrideStylesheet" value="/override.css" /> <add key="DoubleClickToEdit" value="True" /> </appSettings> <system.web> <authentication mode="None" /> <pages validateRequest = "false" /> </system.web> </configuration>
The settings are as follows:
This mandatory setting points to a FederationConfiguration file using a web-server virtual path (not a file system path). See FederationConfiguration for more details.
If you want your system to deliver email WikiNewsletters, you need to do two things:
By default, FlexWiki's rename function will offer users the ability to automatically fixup all pages that point to the one being renamed. In some situations this can create a lot of work for site maintainers to do to deal with accidental or malicious renames. The ability to do this automatic "fixup" can be disabled by setting the DisableRenameFixup key in <appSettings> to true (or false to enable it, the default).
This optional setting allows you to override the visual appearance of your site. See StylesheetOverride for more details.
This optional setting, available as of build 1674, allows you to disable double-click-to-edit on topic pages. A value of FALSE will disable double-click-to-edit.
You should configure your site for some form of authentication. See AuthenticationOptions for more details.
You must set this setting or users will be unable to edit pages on your site.