Item10616: When installing an extension, the logs should be saved

Priority: Enhancement
Current State: Closed
Released In: 1.1.4
Target Release: patch
Applies To: Engine
Component: Configure
Reported By: KipLubliner
Waiting For:
Last Change By: GeorgeClark
When an extension is installed, there is lots of nice information given on the webpage about what changed. It would be nice if everything was stored in a logfile for future reference. There are two ways to do this: store the raw actions in a text file, or save the result page as a static HTML page.

-- KipLubliner - 08 Apr 2011

See EnhanceConfigureLogging

Probably needs to be done by recording the text output of the installation. Extensions can be installed from either the Web, or from the shell, so capturing results page as HTML wouldn't apply to the shell installation.

  • Write a summary record to working/logs/configure.log
    • File format doesn't really support logging an install. Needs some discussion. Format is tabular, for example:
Timestamp Userid IP Address Config variable New Value
Fri Mar 25 23:02:58 2011   127.0.0.1 {Plugins}{TopicDataHelperPlugin}{Module} Foswiki::Plugins::TopicDataHelperPlugin
[Date of extensions installation]   127.0.0.1 NameOfExtension Action: failure/success message

  • Write the detailed report to working/logs/configure/NameOfPackage-[action]-yyyymmdd-hhmmss.log

Not sure if this one needs a feature proposal. Probably does if any log file formats are changed. To make the log format more useful, add an Action column, Set, Install, Remove, Passwd, Set being the current format of Variable / Value? Proposed revised layout:

Timestamp Userid IP Address Action Item Changed New Value
Fri Mar 25 23:02:58 2011   127.0.0.1 SET {Plugins}{TopicDataHelperPlugin}{Module} Foswiki::Plugins::TopicDataHelperPlugin
Fri Mar 25 23:03:18 2011   127.0.0.1 INSTALL NameOfExtension failure/success message

To late for 1.1.3, but this could probably make it into 1.1.4.

-- GeorgeClark - 09 Apr 2011

Committing the change to extension installation to log the results of the install. This needed some refactoring. The Package::install method was renamed to Package::_install and Package::fullInstall renamed to Package::install. The uninstall method was modified to be consistent with install, they now both run the pre and post (un)install routines and log all results.

-- GeorgeClark - 20 Jul 2011
 

ItemTemplate edit

Summary When installing an extension, the logs should be saved
ReportedBy KipLubliner
Codebase 1.1.3, 1.1.3 RC1, 1.1.3 beta1, 1.1.2, trunk
SVN Range
AppliesTo Engine
Component Configure
Priority Enhancement
CurrentState Closed
WaitingFor
Checkins distro:e0512382f978 distro:3a4355bc2a91 distro:353bd7eaa8a6 distro:3aac6c28aac5 distro:2eccf429faec distro:c552796b6ccd distro:236264d4bc47 distro:f6238825ccee
TargetRelease patch
ReleasedIn 1.1.4
Topic revision: r14 - 17 Dec 2011, GeorgeClark
 
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. see CopyrightStatement. Creative Commons License