Item12372: Configure "Initial configuration" issues on trunk

Currently:

• Checker complains about invalid {ScriptUrlPath} and {ScriptUrlPaths}{view}. This is expected on initial configuration. The error needs to be suppressed when in the initial config mode.

  Warning: I guessed this setting. You are advised to confirm this setting (and any other guessed settings) and hit 'Save changes' to save before changing any other settings.
  Error: Content under /bin is inaccessible. Check the setting and webserver configuration.
  

  • - fixed. Path check is not run if the LocalSite.cfg file is marked as bad (missing).

• After the initial save, the screen remains in the initial configuration mode, and no other configuration is displayed. This leaves the impression that the configuration is complete.
  • - "fixed" by triggering a page reload. Not ideal but the JS code is really nasty. We'll definitely want a proper reworking of this.

• After refresh, Enable S/MIME is selected by default, and generates numerous errors about certificates. This will be rather daunting to the newbie admin. This should be disabled by default.
  • SMIME is now disabled by default.

• Generate a NOTE under the {WebMasterName} <== Run the S/MIME certificate tools to enable S/MIME email signing.
• Ensure that the certificate wizards enable S/MIME if appropriate.

• After clicking "Autoconfigure", and it detects the mail server, the below is displayed. It remains displayed until after the save, and then only after a screen refresh.
  • If errors are present, would it be possible to auto refresh the screen after the save completes, so that the user is not confused by unresolved errors?
  • Also a "Refresh / Re-check" button on the action bar - to the left of the Errors / Warnings / Unsaved Changes buttons/indicators, might be useful.

{SMTP}{MAILHOST}      ---- Unused when MailProgram selected ---
Error: Mail server specification required: [IPv6]:port, IPv4:port, or hostname:port. Port is optional, and not recommended when auto-configuring e-mail.

---

Also: running FW with no LSC causes crashes in several places, due to no hard-coded defaults for some stuff.

-- CrawfordCurrie - 19 Feb 2014

Many of the above problems were resolved (or worked around) at the FoswikiCamp and subsequently. Enough that I'm marking this as releaseable - individual problems need to be opened.

-- CrawfordCurrie - 25 Apr 2014